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

Doran_Lum_13484's avatar
Doran_Lum_13484
Icon for Nimbostratus rankNimbostratus
Feb 21, 2015

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, w...
application delivery
config sync
f5
LTM
Amanpreet_Singh's avatar
Amanpreet_Singh
Icon for Cirrostratus rankCirrostratus
Oct 19, 2015

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

https://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.html

https://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.htmlverifyingcommit