Forum Discussion
Force to StandBy button doesn't work
Are you using HAGroups and also have AutoFailback enabled on the traffic-group? If so, then we've seen the same thing. (Ours also had 2 nodes claiming to be the active, although only one really was). Note that in a 6 node cluster we had the same issues when only 2 nodes were left up, but neither of them were the default device...
F5 support eventually came back after duplicating the issue, and said this isn't a supported combination. We've removed the auto-failback, which has resolved the issue of nodes disagreeing who was active, but I haven't tried moving the traffic-group between nodes manually yet...
They were a bit guarded about manual moving with HAGroups as well... But I haven't need to push them on that yet. It may simply have been a misunderstanding between us...
H
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com