Forum Discussion

Vim_113268's avatar
Vim_113268
Icon for Nimbostratus rankNimbostratus
Jan 20, 2010

Help-- Getting - Local configuration and peer configuration have changed: Duplicate the changes, then perform ConfigSync

I am not sure what is going on but i am getting following message when i get to Configs Sync Page:

 

 

Local configuration and peer configuration have changed: Duplicate the changes, then perform ConfigSync

 

 

when i attempt to sync the configs it looks as if it is successful yet status still shows "Sync Recommended"

 

 

Does anyone know what is going on?

 

 

3 Replies

  • Hi Vim,

     

     

    A search for "Sync Recommended" on AskF5.com returns these results:

     

     

     

    KNOWN ISSUE: SOL4860 - BIG-IP displays a "Sync Recommended" message in the Configuration utility every time dynamic ratio updates statistics

     

    KNOWN ISSUE: SOL10535 - BIG-IP redundant pair units may incorrectly report that a sync is recommended

     

    SOL9465 - Clicking Update on any page results in 'Sync Recommended' status even if no changes were made

     

     

    Can you have a look at those and reply back if none explain the issue you're seeing?

     

     

    Thanks,

     

    Aaron
  • We have a case open. We also notice that Active node is not Synchronizing with Standby unit. I think Secondary Node requires a reboot.
  • I myself have had many wierd Sync problems for a very long time - it has frustrated me very greatly. In fact, I just ran into another one last week, and now I have to restart my Active unit. I too can not perform a Sync from the Active to the Standby unit with the GUI: http://devcentral.f5.com/Default.aspx?tabid=53&forumid=32&postid=1167401&view=topic. However, I can pull the config from the Standby, and can push the sync from the Active from the command line.

     

     

    For a very long time, I have been affected by a slightly different, but equally frustrating behavior caused by our large config. When we sync from the Active to the Standby unit, the Standby "resets itself" while it is loading the new config. This "reset" takes a long time - so long sometimes that it seems to prevent the Active unit from believing the two are in sync: even though it just finished synching.

     

     

    Your best bet is to open a case - you did the right thing.