enable/disable vs up/down

I think I got it right in my response. set_availability() corresponds to the "Enable Sessions" in the GUI. The set_state() corresponds to the "Enable Connections" in the GUI.

 

 

"Enable Sessions == get/set_availability()

 

If sessions are enabled, the BIG-IP sends traffic to the node as usual based on the load balancing method you chose. If sessions are disabled, no new sessions can be sent to the node. Clients with persistent connections remain connected to the node and can start new sessions until they timeout based on the persistence setting for the pool the node is a member of.

 

 

Enable Connections == get/set_state()

 

If connections are disabled, no traffic can be sent to the node. This is a Forced Down state. To take the node down without interrupting current client sessions, leave the Enable Connections box checked and clear the Enable Sessions box. Once all traffic has timed out from the node, clear the Enable Connection check box, stopping all traffic to the node."

 

 

And, yes, when I say GUI docs, I refer to the online help when accessing the product via the GUI administration.

 

 

As for your follow-up Q? Calling set_availbility() with AVAILABILITY_DOWN will cause all new connections to be routed to another node in the pool. Current or persistent connections will continue to be routed to that given node.

 

 

-Joe