For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

DBemis_150117's avatar
DBemis_150117
Icon for Nimbostratus rankNimbostratus
Jun 17, 2014
Solved

Pool member showing as force disabled after only setting the session enabled state to disabled

I am trying to set a pool member to simply be disabled by setting the session enabled state to disabled. For some odd reason, using either the deprecated set_session_enabled_state or the current set_member_session_enabled_state, when I set the session state to disabled and then check the session status it shows as force disabled.

Values before setting session enabled state:

get_member_session_status: SESSION_STATUS_ENABLED
get_member_monitor_status: MONITOR_STATUS_UP

Immediately after calling set_member_session_enabled_state to disable the pool member:

get_member_session_status: SESSION_STATUS_FORCED_DISABLED
get_member_monitor_status: MONITOR_STATUS_UP

I thought the status would only be FORCE_DISABLED when both monitor and session state were set to disabled? Is there something else I am missing that would cause it to have that status?

I am using iControl .Net API library v 11.5.0.0 and our F5 is BIG-IP 11.4.0 Build 2434.0 Hotfix HF6

Thanks!

application delivery
devops
iControl
LTM
  • mimlo_61970's avatar
    mimlo_61970
    Jun 18, 2014

    This is a bit gray for me as well, as I do not understand the difference between SESSION_STATUS_DISABLED(which I don't think I have ever seen) and SESSION_STATUS_FORCED_DISABLED, but it should work as you expect and be equivalent to a Disable state in the gui(allow persistent connections but not new ones)

     

    I think the common confusion is thinking FORCED_DISABLED is equivalent to the gui Forced Offline. Both the monitor and the session must be down to be Forced Offline(only active connections)

     

2 Replies

  • mimlo_61970's avatar
    mimlo_61970
    Icon for Cumulonimbus rankCumulonimbus
    Jun 18, 2014

    This is a bit gray for me as well, as I do not understand the difference between SESSION_STATUS_DISABLED(which I don't think I have ever seen) and SESSION_STATUS_FORCED_DISABLED, but it should work as you expect and be equivalent to a Disable state in the gui(allow persistent connections but not new ones)

     

    I think the common confusion is thinking FORCED_DISABLED is equivalent to the gui Forced Offline. Both the monitor and the session must be down to be Forced Offline(only active connections)

     

  • DBemis_150117's avatar
    DBemis_150117
    Icon for Nimbostratus rankNimbostratus
    Jun 20, 2014

    Thanks! I did more testing, checking the session status through code after updating through the web interface, and confirmed that get_member_session_status returned SESSION_STATUS_FORCED_DISABLED for a normal disable. I also confirmed the opposite - setting it to disabled via set_member_session_enabled_state showed as the standard disable through the web interface. Thanks for clearing that up!