Forum Discussion

solaikumar_1217's avatar
solaikumar_1217
Icon for Nimbostratus rankNimbostratus
Jan 10, 2016

Synchronization problem in F5

Hi All,

 

We have two pair of big IP device in our network which is running with 11.6.0 HF6 . Post an upgrade from 11.6.0 HF5 ,we could see below error on both the pair. We have provisioned modules LTM,ASM,MGMT

 

"sync inconsistent, Sync failed on one or more devices in this device group, Sync status may not be consistent.." "Advertising device group /Common/data-sync-device-Host-name-dg, force true, error '' commit_id 14"

 

Kindly suggest to troubleshoot further.

 

Note : On WebUI the sync status frequently changes from In sync to Changes pending .

 

Best Regards, SK.

 

application delivery
ASM Advanced WAF
BIG-IP

5 Replies

Sort By
  • Javier_124486's avatar
    Javier_124486
    Icon for Nimbostratus rankNimbostratus
    Jan 10, 2016

    Hello, could you please tell us what the log is showing about the sync? It could be easier for you just to track the last few lines on the log after you force/overwrite the configuration from the active or primary device to standby/secondary device. At least this will help you to track the error. About SYNC inconsistent i am not sure but that sounds to me like both conf files are different and in conflict (this can happens when both devices are managed at the same time and changed on the configuration are performed simultaneously.Just force conf as a said before and reply with the results.This will not impact at all your environment. I am going to supposed that ASM sync is enabled. Right? if not do it, Security>Options>Application Security> Synchronization> and choose the device group. Regards

     

    • solaikumar_1217's avatar
      solaikumar_1217
      Icon for Nimbostratus rankNimbostratus
      Jan 10, 2016
      Hi Javier, Thank you for Quick reply . I have done manual sync multiple times , but still I am getting the same error. Yes , As you said ASM sync also have been enabled . Even I tried to create one Test ASM policy in active device and it got successfully synched to standby . and also the status shows as green. Herewith attached the logs. Jan 9 14:15:22 Device1info mcpd[8659]: 0107148b:6: Sending sync for device group /Common/datasync-device-Device2-dg to device /Common/Device2, current commit id 14 6237744475666113641 /Common/Device2 0. Jan 9 14:15:23 Device1notice mcpd[8659]: 01071038:5: Unit key hash from key header: f9:ab:6c:da:51:8b:1b:00:25:93:38:d0:68:df:ad:ec:bd:23:cd:5a Jan 9 14:15:23 Device1notice mcpd[8659]: 01071038:5: Unit key hash computed from read key:f9:ab:6c:da:51:8b:1b:00:25:93:38:d0:68:df:ad:ec:bd:23:cd:5a Jan 9 14:15:23 Device1notice mcpd[8659]: 01071038:5: Unit key read from the hardware. Jan 9 14:15:23 Device1info mcpd[8659]: 01071487:6: Commit id for device group /Common/datasync-device-Device2-dg updated to 14 6237744737119149308 /Common/Device2 0. Jan 9 14:15:23 Device1notice mcpd[8659]: 010714a0:5: Sync of device group /Common/datasync-device-Device2-dg to commit id 14 6237744737119149308 /Common/Device2 0 from device /Common/Device2 complete. Jan 9 14:15:23 Device1info mcpd[8659]: 01071528:6: Device group '/Common/datasync-device-Device2-dg' sync inconsistent, Sync failed on one or more devices in this devicegroup, Sync status may not be consistent.. Jan 9 14:15:23 Device1info mcpd[8659]: 0107148f:6: Advertising device group /Common/datasync-device-Device2-dg, force true, error '' commit_id 14 6237744737119149308 /Common/Device2 0. Best Regards, Solai.k
  • Javier_124486's avatar
    Javier_124486
    Icon for Nimbostratus rankNimbostratus
    Jan 11, 2016

    Morning Solaikumar,

     

    I was just trying to review your issue and so far i only step in two F5's Known issue that could match yours, the only difference is that both issues are for APM (But configuration sync is configuration sync, regardless the module -except ASM that requires specific activation- and in this case we do not have a problem with modules features but with synchronization). I am sure that you could come to this one, but just in case. Both error supposed to be solved in v11.6 but just in case i would recommend you to open a case. I am sorry but unfortunately i cannot help you more. These are the issues i found

     

    Regards and good luck. If i come to anything that could help i will let you know.