Forum Discussion
How to Perform Redundancy Switchover on BIG-IP
Regarding Redundancy Switching Methods on BIG-IP
Can I understand that the following ① and ② exhibit identical behavior? If there is a difference in operation, please let me know.
① Force to Standby on the Active Unit
② Force to Offline ⇒ Release Offline on the Active Unit
2 Replies
This really depends on what you are attempting to do. If your objective is to just failover from the active to the standby and allow it to take over should a failure occur on the new active then you can just do a "Force to Standby" and that will cause a failover event. If your intent is to failover and keep it in that state no matter what then you would do a "Force to Offline" which should make it so that F5 device never comes back into rotation until you mark it online again. In instances where you have both units as active unintentionally or in a failover loop you can also use "Force to Offline" to resolve that issue.
- richaed
Cirrus
Thank you.
The purpose is to switch to the redundant path during the server replacement,
so we anticipate no particular issues with forcing it to standby.
We would appreciate your guidance on which approach is recommended.
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