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

shadow_82's avatar
shadow_82
Icon for Nimbostratus rankNimbostratus
May 10, 2022

2x F5 VE in Azure doesn't ping each other

Hi! I'm building a F5 cluster. 2 VMs, 3 interfaces: MGMT, External, Internal (+ HA) I Azure I have 3 VNets - according to needs When I wanted to start forming a cluster, I noticed VMs does no...
cloud
Daniel_Wolf's avatar
Daniel_Wolf
Icon for MVP rankMVP
May 11, 2022

Hi shadow_82,

I strongly advise against building a failover cluster in the cloud. Resources in the cloud are far to expensive to use them in standby mode. Failover might take longer than expected (=bad customer experience).

I do recommend to have an active/active setup and utilize GSLB as a service (F5 DNS Load Balancer Cloud Service) to distribute traffic between the two instances. Use Terraform / AS3 (any form of automation) to keep the config on both BIG-IP nodes consistent.

If you insist on using failover - this is how it's done the F5 way: https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/

KR
Daniel

shadow_82's avatar
shadow_82
Icon for Nimbostratus rankNimbostratus
May 13, 2022

Thanks for answer!
This is something we are thinking about, maybe not active active due to heavier troubleshooting once something bad occurs (you have to divide traffic going though 2 F5s, not 1).

Yet maybe having only 1 F5 running and second being shut down in cluster - until some upgrade procedure will be needed.

This might be the sweet spot.

You pay for 1 VM running 24/7/365 and spin up the 2nd one for upgrade purposes (to switchover)