eesun_276598
Cirrus
CirrusWhy 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
Forum Discussion
4 Replies
James_ThomsonEmployee
What version are you running? What is your HA mode set to? Load Aware, HA Order, etc..
If you can share the portion of your configuration in the /cm section that shows your HA features, that would be helpful.
If you have HA groups configured incorrectly, if you have a preferred active device set up, or the default load aware failover mode could cause this.
I'd try changing the failover type to HA Order if you're not using it now.
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
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
Nimbostratus
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.