Assistance Requested - iRule causes virtual to hang upon LTM reboot

Hi EBL,

 

 

You may want to change your methodology a little bit. You can configure LB re-select on the Pool (which should be synchronized across the HA Pair) by using the "Action On Service Down" option, which is set on the pool. Set this option to "Reselect".

 

 

So if the node fails then the client will be sent to another working member of the pool.

 

 

If no pool members are available (because you have taken them all down for maintenance) then you can use the "active_members" option inside of an iRule to determine if there are any members available. If so then the client would proceed to another node because of the Action On Service Down option being set to Reselect. If not, then you could redirect them to a different pool (which would negate the persistence).

 

 

See the active_members iRule command.

 

 

Hope this helps.