Sync error on F5 LTM

Hi all, before we did some changes on the active F5 node it was already shown as “Pending Changes.” So we decide to go ahead and make changes on the active node first.

After adding some VIPS, we wanted to sync the changes over to the inactive node but got the error below. We try to force overwrite the changes from 02 but still failed.

have you checked /var/log/ltm?

Hi,

Please try below command..

touch /service/mcpd/forceload

You can force it to initiate a one time Config-Sync operation:

in tmsh:

modify cm device-group MyDeviceGroup devices modify { ltm.example.com { set-sync-leader } }

Has the sync ever worked between these two devices?

You might need to reset the device trust.

Why don’t we try Sync Device to Group instead Sync Group to Device? or else they may have taken activeF5 bakup already, now we can Revert it back right?

Hi, It could be multiple reasons but try to work on below basics first:

Have you check the commit ID on both the peers ? Does they match?

BIG-IP 11.2.1 and later:

tmsh run /cm watch-devicegroup-device

BIG-IP 11.0.0 through 11.2.0:

watch_devicegroup_device
  1. Below elements must be correctly configured between both peers:
  • Licensing and provisioning
  • Software versions
  • Management IP (must be unique)
  • NTP
  • ConfigSync IP
  • Failover IP
  • Ports( 443, 4353, 1026 (UDP), and 22)
  • Device trust