Help with scheduled reboots

Hi Ryan,

 

 

The simplest option for this would be to configure a monitor that checks each server for a specific page and content within that page. When the server admins want to take a server down, they could change or remove the page being monitored, reboot the member, wait for the services to come up fully and then restore the monitor page. The downside to this approach is that when they change/rename the monitor page, all existing sessions will be broken.

 

 

If you did want to do this with connections drained off gracefully, you could create a simple iControl-based script run from the pool member(s) themselves that disables the node, checks for no connections to the node, reboots, and then re-enables itself in the pool once it's services have come up. The mechanism for disabling a pool member should be fairly simple with iControl.

 

 

There are a few related examples in the iControl Codeshare:

 

http://devcentral.f5.com/wiki/default.aspx/iControl.CodeShare

 

 

Aaron