Forum Discussion
Pool member showing as force disabled after only setting the session enabled state to disabled
- 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)
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!
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com