Cisco N5K-C5010P-BF Troubleshooting Guide - Page 159

Global-db modification in progress, Peer unable to accept lock request

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 159 highlights

Chapter 9 Troubleshooting Config-Sync Issues Verify Failure Send document comments to [email protected]. Global-db modification in progress Possible Cause Verify cannot be performed when global-db is being updated on the local/peer side. Solution Wait for the update to complete and run verify. Peer unable to accept lock request Possible Cause Verify cannot be performed when the peer is unable to accept the lock request. Solution The peer is handling a transaction and cannot accept a lock request. Run verify at a later time. Use the show switch-profile status command to determine if there is an ongoing transaction. If the peer remains in the same state for a long time, use the show cfs lock command to determine if the CFS fabric has been locked. Also check the application that has taken the CFS lock. If the application is ssnmgr, use the show cfs internal session-history name session-mgr command and the show cfs internal notification log name session-mgr command to view information about when a lock was acquired or released. It can also show the mapping to the csm transactions displayed with the show switch-profile session-history command. OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 9-9

  • 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-9
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 9
Troubleshooting Config-Sync Issues
Verify Failure
Global-db modification in progress
Possible Cause
Verify cannot be performed when global-db is being updated on the local/peer side.
Solution
Wait for the update to complete and run verify.
Peer unable to accept lock request
Possible Cause
Verify cannot be performed when the peer is unable to accept the lock request.
Solution
The peer is handling a transaction and cannot accept a lock request. Run verify at a later time.
Use the
show switch-profile status
command to determine if there is an ongoing transaction.
If the peer remains in the same state for a long time, use the
show cfs lock
command to determine if the
CFS fabric has been locked.
Also check the application that has taken the CFS lock. If the application is ssnmgr, use the
show cfs
internal session-history name session-mgr
command and the
show cfs internal notification log name
session-mgr
command to view information about when a lock was acquired or released. It can also show
the mapping to the csm transactions displayed with the
show switch-profile session-history
command.