Forum Discussion

Michael_Everet1's avatar
Michael_Everet1
Historic F5 Account
Oct 26, 2006

forcing down/disabling a node via iControl

I suspect someone has asked this question before, but maybe not. We have a very large environment with lots of BIG-IPs and BIG-IP vips/pools/nodes. We are in the process of migrating to the new F5 hardware/software and are attempting to update our iControl scripts. Also, we have a requirement (the validity is debatable) to have our support teams immediately pull a server from a cluster - (i.e force disable). Also, we use iControl scripts to do the same thing. Currently, we are using the following method:

 

 

LocalLB/NodeAddress/set_monitor_state

 

 

to force disable nodes. However, we have noticed that when we use this method the status display via the gui indicates that a nodes parent monitor is down. If we perform a hard disable via the GUI, by selecting the only active traffic allowed then we get the state as being forced down disabled. Is there a way to perform the action equal to selecting the only active traffic allowed on the node via iControl? This will help our support teams, as the hard disable via automation and manual intervention will display the same status??

 

 

Sorry for all verbage..
dev
devops
iControl

4 Replies

Sort By
  • Michael_Everet1's avatar
    Michael_Everet1
    Historic F5 Account
    Oct 26, 2006
    Found some docs that I think we will after looking a little while. Looks like to perform a hard disable we need two calls.. once on the monitor state and a second on the session state. I will try this and see if that answers my question regarding the gui display.

     

     

    Thanks
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Oct 30, 2006
    That's exactly it. Hopefully things worked out for you, let us know how they are going.

     

     

    -Joe