Cisco N5K-C5010P-BF Troubleshooting Guide - Page 153

Import Failure

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 153 highlights

Chapter 9 Troubleshooting Config-Sync Issues Import Failure Send document comments to [email protected]. 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. Import Failure Use the show switch-profile status command to view import status. Import failure has many possible causes: • Failed to collect running-config • Command does not exist in global-db • Mutual exclusion check failed on peer The following describes import options and best practices. OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 9-3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
9-3
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Import Failure
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.
Import Failure
Use the
show switch-profile status
command to view import status.
Import failure has many possible causes:
•
Failed to collect running-config
•
Command does not exist in global-db
•
Mutual exclusion check failed on peer
The following describes import options and best practices.