Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual page 152

Commit Failure
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m .
This error message indicates that some feature commands have not been configured. Feature commands
are not allowed to be configured within SP and have to be configured on BOTH peers from conf-t.
Verify failed
Possible Cause
The commands listed failed mutual-exclusion checks. These commands have already been configured
under conf-t.
Solution
If you do not want these commands synchronized, remove the commands from conf-t.
Alternatively, delete these commands from the switch-profile buffer and reissue the commit.
To delete commands from the switch-profile buffer, perform the following:
•
•
•
Commands that failed commit
Possible Cause
Commands failed during commit.
Solution
Correct the reason for the failure and re-issue the commit.
If the commit continues to fail, issue the same command from conf-t. If it succeeds from conf-t, check
for any errors relating to the command using the show system internal csm info trace command.
For every command executed from config-sync, there is a csm_cmd_status[0x0] line in the trace log that
indicates that the command was successful.
Another session in progress
Possible Cause
Conflict occurs if conf-t or config-sync has taken a lock.
Solution
Compare the vPC domain IDs of the two switches and ensure that they match.
Use the show system internal csm global info command to check whether conf-t or config-sync has
taken a lock.
•
Note
Cisco Nexus 5000 Series Troubleshooting Guide
9-2
View commands in the SP buffer using the show switch-profile buffer command.
Delete commands indicated by the sequence numbers with the buffer delete <range> command.
Use the buffer-move <seq id> <seq id> command to rearrange commands in the buffer.
This is command is useful when commands in the buffer are not ordered correctly.
If conf-t has taken a lock and not released it, command output, similar to the following example, is
displayed.
The client type should be set to 2 as shown in the example.
Chapter 9 Troubleshooting Config-Sync Issues
OL-25300-01