Cisco N5K-C5010P-BF Troubleshooting Guide - Page 110

System state inconsistent and locks being held, Clearing locks using the CLI

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

Cisco Fabric Services Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. System state inconsistent and locks being held An inconsistent system state occurs for one of the following situations: • When locks are not held on all of the switches in the fabric. • When locks are held on all switches in the fabric, but a session does not exist with the lock holding the switch. In either case, it is necessary to use the clear option to release the locks. Clearing locks using the CLI When a lock is being held on a remote peer and entering the commit command or the abort command does not clear the lock, issue the clear session command to clear all locks in the fabric. After all locks are cleared, a new distribution must be started to restore all the switches in the fabric to the same state. Example: switch# clear ntp session switch# config terminal switch(config)# ntp commit switch(config)# Distribution status verification After configuring an application and committing the changes, you may want to verify that CFS is distributing the configuration change throughout the fabric or VSAN. Verifying distribution using the CLI Use the show cfs lock name command to determine if a distribution is in progress on the fabric. If the application does not show in the output, the distribution has completed. Example: switch(config)# show cfs lock name ntp Scope : Physical-fc-ip Switch WWN IP Address User Name User Type 20:00:00:0d:ec:50:09:00 172.25.183.42 admin CLI/SNMP v3 Total number of entries = 1 CFS regions troubleshooting The following rules apply to CFS Regions: • When using CFS Regions, an application on a given switch can only belong to one region at a time. • CFS Regions are only applicable to applications within the physical scope. You cannot create a CFS Region in the logical scope of an application. 5-38 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01

  • 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].
5-38
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Cisco Fabric Services
System state inconsistent and locks being held
An inconsistent system state occurs for one of the following situations:
•
When locks are not held on all of the switches in the fabric.
•
When locks are held on all switches in the fabric, but a session does not exist with the lock holding
the switch.
In either case, it is necessary to use the clear option to release the locks.
Clearing locks using the CLI
When a lock is being held on a remote peer and entering the
<application-name>
commit
command or
the
<application-name>
abort
command does not clear the lock, issue the
clear
<application-name>
session
command to clear all locks in the fabric. After all locks are cleared, a new distribution must be
started to restore all the switches in the fabric to the same state.
Example:
switch# clear ntp session
switch# config terminal
switch(config)# ntp commit
switch(config)#
Distribution status verification
After configuring an application and committing the changes, you may want to verify that CFS is
distributing the configuration change throughout the fabric or VSAN.
Verifying distribution using the CLI
Use the
show cfs lock name
<application-name>
command to determine if a distribution is in progress
on the fabric. If the application does not show in the output, the distribution has completed.
Example:
switch(config)# show cfs lock name ntp
Scope
: Physical-fc-ip
--------------------------------------------------------------------------------
Switch WWN
IP Address
User Name
User Type
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
admin
CLI/SNMP v3
Total number of entries = 1
CFS regions troubleshooting
The following rules apply to CFS Regions:
•
When using CFS Regions, an application on a given switch can only belong to one region at a time.
•
CFS Regions are only applicable to applications within the physical scope. You cannot create a CFS
Region in the logical scope of an application.