Forum Discussion
NimbostratusConfiguring HA on Azure F5 LTM 'Good'...
Hello,
Looking at the 12.0 Azure setup guide, https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-msft-azure-12-0-0.html
Due to the 1NIC limitation, HA is not yet supported. (page 5)
"As shown in the diagram, all access to the BIG-IP VE appliance is through the same IP address. Because of this, the BIG-IP VE high availability feature does not work in Azure. (You cannot create an active- standby pair.) "
Alastair_jones_Seth Yes thanks, I saw that. What's the workaround?- Page 8 suggests "BIG-IP high availability is currently not supported in Azure, so you should configure the BIG-IP to reboot if a daemon fails. For details, see the BIG- IP ® System: Essentials guide on AskF5.com .
rowanboy2012Hi Alastair,
Not sure if you've had any luck so far, but the only method of utilizing an HA pair of F5s in Azure so far is to use the Azure LBs to select the F5 device for the connection.
If the F5s are receiving connections directly from the perimeter this is easy as all you need is a "Public" LB configured. Both F5s share the same public IP (that of the Azure LB) but have different virtual server/self/mgmt. IPs. This basically creates a true Active/Active scenario where either F5 can receive the traffic. The Azure LB does have a client sticky feature (not dissimilar to F5s source address persistence) so one user can persist through one F5 for a given period.
If you are NAT'ing through another perimeter security device through to the F5s in Azure, then you would need to look into creating an internal Azure LB to carry out the same as above. I'm testing this at the moment so will let you know on the success of this once known.
(NOTE: I have heard rumours that full HA may be available in Azure eventually)
