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

Mattmans1_21101's avatar
Mattmans1_21101
Icon for Nimbostratus rankNimbostratus
Nov 24, 2016

HA - Sync Failed..

Hi Guys,   I have bought the Lab license and have two versions of 12.1 running on ESXI servers. I have issue though, against the F5 best practices, im wanting to cluster both these F5's, one in e...
application delivery
BIG-IP
Mattmans1_21101's avatar
Mattmans1_21101
Icon for Nimbostratus rankNimbostratus
Nov 24, 2016

I tried routing the HA self IP to each other instead of the whole subnet - now i got a different error.

 

StatusSync Failed SummaryA validation error occurred while syncing to a remote device Details Sync error on HAR-: Load failed from TC- 01070330:3: Static route gateway 172.16.73.9 is not directly connected via an interface. Recommended action: Review the error message and determine corrective action on the device

 

I have it working with having both HA self IP's on the same network and trunking the network between the DC's using a vlan. This is OK until the leased line goes down then both boxes will become active. Atleast before by using different HA networks i could route them via the ASA which would handle the failover if the leased line died and route it via the MPLS.

 

How can i achieve redundancy using the MPLS link with the F5's? IS there a secondary HA link/method i can use?

 

Many thanks if you know the answer :)

 

Matt