Table of Contents
Advertisement
Chapter 9
Troubleshooting Config-Sync Issues
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 .
•
•
Import Failure
Use the show switch-profile status command to view import status.
Import failure has many possible causes:
•
•
•
The following describes import options and best practices.
OL-25300-01
Example:
No of sessions: 1 (Max: 32)
Total number of commands: 0 (Max: 102400)
Session Database Lock Info: Locked
Client: 2 (1: SSN, 2: CONF-T)
Ref count: zero-based ref-count
Lock acquired for cmd : some-command
Identify the command that acquired the lock using the show accounting log command.
–
After identifying the command, check for its SUCCESS/FAILURE status.
–
–
If the command did not return a status, then config-sync would not release the lock on conf-t.
–
Use the test csm ssn-db-lock reset conf-t command to reset the lock.
If switch-profile has taken the lock, the client id is reported as 1 in the show system internal csm
global info command.
–
Use the show switch-profile status command to determine if a merge is in progress.
A merge is indicated by pending_merge:1 /rcvd_merge:1.
–
If a merge/verify/commit session is already in progress, then sp ssn-db is locked.
Wait for the current session to complete and try again.
If the lock is not released, use the show cfs lock command to determine if the CFS fabric is
–
locked.
Identify the application that locked CFS. If the application is session-manager, then the CFS
lock was taken by config-sync.
Analyze the output from the show system internal csm info trace, show cfs internal
notification log name session-mgr, and show cfs commands.
Use the show system internal csm info trace command to view the events, trace, or error debug
traces.
Failed to collect running-config
Command does not exist in global-db
Mutual exclusion check failed on peer
Cisco Nexus 5000 Series Troubleshooting Guide
Import Failure
9-3
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
