Forum Discussion

J__Pogeant_1557's avatar
J__Pogeant_1557
Icon for Nimbostratus rankNimbostratus
May 26, 2014

Sync problem with Sync-Failover ConfigSync

Hello,

I'm running two BigIp LTM (version 11.3 HF3) with Sync-Failover ConfigSync. I'm experiencing issues with the synchronisation on both devices.

All the configuration is well replicated excepts for the Virtual Server List in a particular Partition. On the other partition, the configuration is synchronised.

After digging on F5 support and devcentral, I've tried many workarounds :

None of them worked, the devices always consider themselves as "In Sync", but they still keep a different configuration on their side even by forcing the 

sync-leader
. This only happens with the Virtual Server configuration on this particular partition. The configuration is well synced on the other partitions....

If anyone could have a clue or a way to debug this problem that would greatly appreciated 🙂

Thanks in advance.

application delivery
availability
LTM
management

2 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    May 26, 2014

    This only happens with the Virtual Server configuration on this particular partition.

    is their traffic-groups floating one (e.g. traffic-group-1)?

    e.g.

    root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list sys folder /test/
sys folder /test {
    device-group dg
    inherited-devicegroup true
    inherited-traffic-group true
    traffic-group traffic-group-1
}

root@(ve11a)(cfg-sync In Sync)(Active)(/Common)(tmos) list ltm virtual-address /test/1.1.1.1
ltm virtual-address /test/1.1.1.1 {
    address 1.1.1.1
    inherited-traffic-group true
    mask 255.255.255.255
    partition test
    traffic-group traffic-group-1
}
  • J__Pogeant_1557's avatar
    J__Pogeant_1557
    Icon for Nimbostratus rankNimbostratus
    May 26, 2014

    Wow such a swift answer and you nailed it ! The IP wasn't in the floating group, this was causing the "Sync" issue.

     

    Thank you very much !