Forum Discussion
F5 BIG-IP's in Different Datacenters
- Oct 09, 2019
If all your links are down, then you go split brain. But if all your links are down, then you have more problems than just the split brain BigIP.
(Note that the way I usually do this is an HA pair in each DC (Or metropolitan DC pair). Then use GTM to provide global resilience).
Regarding fancy devices not requiring your network to be up to prevent split brain. Why bother? You can always put in a path that would encompass the same links as the failover clustering using witness. You're not limited to just two links.
Actually connecting two devices directly to each other is not supported by F5
The reason is pretty simple, if the link is down both devices will initate a failover process and you can end up with dual active scenario .
what F5 is recomanding is passing through switches on both sides, in this case phisical failure will be contained within the segment (switch to BIG-IP) and the high avalability monitoring still work because both devices are monotoring each other through TCP.
Passing through switches can also improve scalability, with direct connection you will be limited to only two BIG-IPs.
This is for a single data center, for more you should carefully take in consideration the F5 recommendations for high availability such as band width for synchronization and mirroring , latency etc...
good luck
- MohanadOct 09, 2019
Cirrostratus
Hi Azzeddine
thanks for your reply, this is just a diagram to describe the issue, we are using switches between all network devices.
im trying to achieve this:
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