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
medilyas's avatar
medilyas
Icon for Nimbostratus rankNimbostratus
Mar 03, 2020

A 3 years old post, but for those who are still struggeling with routing ConfigSync interfaces and routing table management in a Device-group, here is the solution that worked for me:

-create a user partition

-In this partition properties-->Redundant Device Configuration :

Set Device Group to None

Set Traffic Group to traffic-group-local-only

 

Now switch to this partition

Go to Network-->Route and create the route to the configsync ip of the peer

 

Repeat the same steps for the other peer

Hope this help.

 

Ilyas

 

 

  • DanielV's avatar
    DanielV
    Icon for Nimbostratus rankNimbostratus
    Jan 17, 2022

    Ilyas, thank you for this - i had the same issue and switching user local partition device group to NONE resolved it, i am able to run config sync.

    If anyone has the same issue, my software version is 16.1.2.1 and it is AWS VE version.

    Thanks again!!