For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

eesun_276598's avatar
eesun_276598
Icon for Cirrus rankCirrus
Sep 27, 2016

Why we have to disable HA before "Force to Standby"

We have to disable HA before "Force to Standby". If not, the command cannot take effect. Any one can explain it? Thank you  
application delivery
LTM
Rhys_Peters_770's avatar
Rhys_Peters_770
Historic F5 Account
Sep 29, 2016

If you are using HA groups then you have to disable this before forcing to standby.

 

If you do not do this, the HA calculation will be run again (following the Active node becoming Standby). If the previous Active node is still healthy, the configured weights will dictate that this node become active again.

 

The result will be that shortly after you force the Active node to Standby, it will become Active again.

 

  • James_Thomson's avatar
    James_Thomson
    Icon for Employee rankEmployee
    Sep 30, 2016

    There is a feature called "Active Bonus" which should prevent this. Whichever device is active will get this extra added score to prevent flip-flopping.

     

  • arpydays's avatar
    arpydays
    Icon for Nimbostratus rankNimbostratus
    Oct 02, 2016

    Yes, active bonus should prevent flip-flopping but not in a 'force to standby' scenario as the force to standby does not allocate the bonus until after the recalculation, so as Rhys said the HA calculation is done first and if the previous active unit is preferred based on weights then it will flick back to this unit within 10secs of 'force to standby'. This is the case for HA-groups.