Forum Discussion

emilio_104458's avatar
emilio_104458
Icon for Nimbostratus rankNimbostratus
Oct 16, 2012

sync problem only from the second appliance

hi all,

 

i've a pair of f5 (f5_1 and f5_2) when i try to sync the two appliance the only way to do it is from f5_1 to f5_2, otherwise if i use sync from f5_2 FROM f5_1 the following error is always displayed:

 

Oct 16 15:06:24 f5 notice mcpd[14567]: 01071475:5: Sync system files from device with IP address (192.168.12.129)

 

Oct 16 15:07:24 f5 err mcpd[14567]: 0107148e:3: Sync from device group /Common/device-group-failover-fad19c425da3 failed, this device /Common/f5.prod2.tgesc.local has the highest commit id 3 5799892693724349546 /Common/f5.prod2.tgesc.local.

 

 

 

in this way i cannot performe neither the sync via tmsh because the same error is displayed if i run:

 

tmsh run sys sync-sys-files from 192.168.12.129

 

 

 

can anyone have an idea?

 

 

 

thanks

 

Emilio

 

config
design

4 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Oct 16, 2012
    sol13887: Forcing a BIG-IP device group member to initiate a ConfigSync operation

     

    http://support.f5.com/kb/en-us/solutions/public/13000/800/sol13887.html

     

     

    hope this helps.
  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus
    Oct 16, 2012
    It's a known bug... (Basically it is stopping u from syncing over a NEWER config).

     

     

    There's a workaround (It didn't work for me though, it involves resetting a DB variable), OR you can simply make a change on the unit you're syncing FROM and try again (A newer change on the unit you're syncing from SEEMS to work so far. However I'm not really enamoured too much with the syncing in v11... It's been a bit flakey for me, especially with >2 units in a device group where the chances of multiple changes go up)...

     

     

    H
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Oct 16, 2012
    Here are steps for manually synching regardless of which unit has the most current config. Run this on the unit you want to sync from:

     

     

    tmsh

     

    modify cm device-group DEVICE_GROUP_NAME devices modify { DEVICE_NAME { set-sync-leader } }

     

    run cm config-sync to-group DEVICE_GROUP_NAME

     

    show cm sync-status

     

     

    Here's an RFE for correcting this. It's fixed in 11.2.1 and in 11.3 when it's released.

     

    BZ376309 - RFE: provide ability to sync in any direction, disregard timestamp

     

     

    Aaron
  • emilio_104458's avatar
    emilio_104458
    Icon for Nimbostratus rankNimbostratus
    Oct 16, 2012
    thanks a lot.. i will try the workarounds...otherwise i will update to 11.2.1 (i still have v11.1.0 Build 1943.0 )