Forum Discussion

Aviv's avatar
Aviv
Icon for Cirrus rankCirrus
Dec 10, 2015

Bigip HA sync Problem

Hi!

we have 2 Units of f5 ver 12 in HA . someone,by mistake start to create objects and a vs in the standby unit. when he saw that he is in the standby unit he started to create the some objects at the active unit and then he pressed on sync to group with the checkbox of overwrite. since then the standby unit is unsynced and we get this error:

Sync Summary Status Awaiting Initial Sync Summary One or more devices awaiting initial config sync Details 

F5-02.com is awaiting the initial config sync
Recommended action: Synchronize F5-01.com to group sync-group

we have tried to recreate the a Sync-Failover Device Group but problem still exist.

any help will be appreciated

thanks,

Aviv Hassidim

application delivery
BIG-IP
TMOS

5 Replies

Sort By
  • StephanManthey's avatar
    StephanManthey
    Icon for MVP rankMVP
    Dec 10, 2015

    Hi Aviv,

    the message "awaiting the initial config sync" typically indicates that units never were in synced state.

    (Maybe due to re-creating the sync-failover device group.)

    Please check both units for the device settings (failover, config sync, mirroring).

    Local self IPs need to be used for all these properties and the port lockdown should be set to "allow default". Both units are added to the new sync-failover device group?

    Device trust is established bi-directional (check device list on both machines).

    Make sure both units are on same time ("
    ntpq -p
    ").

    Watch the log file for error messages during config sync:

    tail -f /var/log/ltm

    Thanks, Stephan
  • Aviv's avatar
    Aviv
    Icon for Cirrus rankCirrus
    Dec 12, 2015

    Hi!

     

    I have tried the solution but it didn't worked for me. i get this now:

     

    Sync Summary Status Sync Failed Summary A validation error occurred while syncing to a remote device Details Sync error on TVLF5-02.com: Load failed from TVLF5-01.com 01070734:3: Configuration error: Modify of node attribute is not permitted. Recommended action: Review the error message and determine corrective action on the device

     

    any suggestions?

     

    Thanks, Aviv

     

    • StephanManthey's avatar
      StephanManthey
      Icon for MVP rankMVP
      Dec 13, 2015
      Hi Aviv, I guess, the configuration is somehow inconsistent. As you mentioned, changes were applied to both units. A logical configuration change (nodes, pool members, virtual servers etc.) should be synchronized in "overwrite" sync mode. If changes were applied to VLANs and self IPs it might become more complicated as the object names have to match in your cluster and i.e. for floating self IPs (which will be synced a VLAN and a matching self IP have to exist on the peer device). I am wondering, if you can locally save the configuration on command line: tmsh save sys config tmsh save sys ucs backup_bigip_date.ucs Thanks, Stephan
    • Aviv's avatar
      Aviv
      Icon for Cirrus rankCirrus
      Dec 13, 2015
      Hi! F5 support helped me. we deleted all vs &pools & nodes from the standby device and then sync worked perfect Thanks a lot, Aviv