Config-sync issue Nexus 5548P pair

[sokarlsson]

Our customer have a 5548P pair with 3 dual-homed N2000 fex.

The switch-profile looks to be out of sync between them. one has rev 47 and the other one 44.
Doing show switch-profile status give the following result in the one with revision 47

switch-profile  : CORE1DC11-12
----------------------------------------------------------

Start-time: 310987 usecs after Thu Jan 17 13:34:50 2013
End-time: 999212 usecs after Thu Jan 17 13:34:53 2013

Profile-Revision: 47
Session-type: Verify
Session-subtype: -
Peer-triggered: No
Profile-status: Verify Failed

Local information:
----------------
Status: Verify Success
Error(s):

Peer information:
----------------
IP-address: 10.1.1.12
Sync-status: Not yet merged
Merge Flags: pending_merge:0 rcv_merge:1 pending_validate:1
Status: Verify Failure
Error(s):
Following commands failed parsing: If the error is 'Command Parsing Failed', ple
ase check if some conditional feature(s) needs to be enabled
no lldp receive (Command is not sp-aware.)
no lldp transmit (Command is not sp-aware.)

The one with revision 44 has the same merge fail fort the lldp commands but under Local Information.

What can be done without impacting traffic? I have seen suggestions about removing the sync-peer config and/or doing resync-database.
There is very sparse documentation about resync-database. Can one try this safely in a live enviroment?
Need advice.

[Kevin Dorrell]

By way of a disclaimer, I cannot answer definitively for your environment.  However, I have done this in my environment, and it did work, and it was not disruptive.

• Before you start, make sure you have nothing in the buffers
  
• Remove the sync peer on each side, and commit
  
• resync-database on each side
  
• Put back the sync peer on each side, and commit
  
• Note: it may take a couple of minutes for them to reach "In sync"
  

However, I should point out that in my case, the Profile-Revision is still not the same on both sides.  (That is how I found this thread: I was searching for "Profile-Reision".)  But it did solve my problems with not being able to commit any new changes.

Hope this helps.

Kevin DORRELL

Luxembourg

[sokarlsson]

Sorry for not coming back to this. We finally did fix this te hard way a couple of weeks ago by totally this way

remove sync peers

delete the config sync config

upgrade the switches

reapplying the config without using config sync

The merge fail and the other problems related to the lldp commands was due to a bug in the release we were running earlier.

Since there is several people configuring these switches and obviously there have been some confuson on when to use sync and when not we decided to enforce using only config terminal.