Nimbostratus
Nimbostratus
Thanks for your thoughts. Not sure I want to run the AOSD in "None" all the time..... I am trying to find a solution where by our operators don't need to access the F5 GUI or CLI, hence my thinking around changing the string returned in the monitored page - the operator could do this though scripts on the backend server they already have access to.
The plot thickens.....
I guess I could have AOSD set to "Reselect" all the time, have the member marked down by changing the string returned to the monitor to MAINTENANCE. This will reroute, on the server side, client sessions so there's no impact to them. Do the upgrade and then put the server back into the pool by changing the returned string back to RUNNING so new sessions can be sent to it and then through CLI on the F5 for the other server call LocalLB.PoolMember.set_session_enabled_state() and change its state to "STATE_DISABLED" knowing that this will not fully disable the pool member but will just stop new connections from being established and I get my existing sessions completing naturally. Once all sessions have been finsihed, change it's returned string to MAINTENANCE, update the server, call LocalLB.PoolMember.set_session_enabled_state() and change its state to "STATE_ENABLED" and change its returned string to RUNNING - hey presto I have two updated servers with - in theory - no client session impacts.
What do you think?