Cisco N5K-C5010P-BF Troubleshooting Guide - Page 108

Lock failure troubleshooting

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

Cisco Fabric Services Chapter 5 Troubleshooting SAN Switching Issues Send document comments to [email protected]. admin 34684 Step 3 Enter configuration mode and enter the commit command for the application to restore all peers in the fabric to the same configuration database. Example: switch(config)# ntp commit switch(config)# show cfs merge status name ntp Physical-fc-ip Merge Status: Success [ Thu Aug 5 11:51:02 2010 ] Local Fabric Switch WWN IP Address 20:00:00:0d:ec:50:09:00 172.25.183.42 [Merge Master] 20:00:00:0d:ec:da:6e:00 172.25.183.124 switch Total number of switches = 2 switch(config)# show cfs merge status name ntp Physical-fc-ip Merge Status: Success [ Thu Aug 5 11:51:02 2010 ] Local Fabric Switch WWN IP Address 20:00:00:0d:ec:50:09:00 172.25.183.42 [Merge Master] MDS-9134 20:00:00:0d:ec:da:6e:00 172.25.183.124 Total number of switches = 2 Lock failure troubleshooting In order to distribute a configuration in the fabric, a lock must first be acquired on all switches in the fabric. Once accomplished, a commit can be issued which distributes the data to all switches in the fabric before releasing the lock. When a lock has been acquired by another application peer, you cannot commit new configuration changes. This is a normal situation and you should postpone any changes to an application until the lock is released. Use the troubleshooting steps in this section only if you believe the lock has not been properly released. A lock occurs when an administrator configures a change for a CFS-enabled application. If two administrators on the same switch attempt to configure the same application, only one administrator is given the lock. The other administrator is prevented from making changes to that application until the first administrator commits a change or discards any changes. Use the show cfs lock name command to determine the name of the administrator who holds the lock for an application. You should check with that administrator before clearing the lock. A CFS lock can also be held by another switch in your fabric. Use the show cfs peers name command to determine all the switches that participate in the CFS distribution for the application. Then use the show cfs lock name command on each switch to determine who owns the CFS lock for that application. You should check with that administrator before clearing the lock. Use the CFS abort option to release the lock without distributing the data to the fabric. 5-36 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-36
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 5
Troubleshooting SAN Switching Issues
Cisco Fabric Services
admin
34684
--------------------------------------------------------------------------------
Step 3
Enter configuration mode and enter the commit command for the application to restore all peers in the
fabric to the same configuration database.
Example:
switch(config)# ntp commit
switch(config)# show cfs merge status name ntp
Physical-fc-ip
Merge Status: Success [ Thu Aug
5 11:51:02 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
IP Address
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
[Merge Master]
20:00:00:0d:ec:da:6e:00 172.25.183.124
switch
Total number of switches = 2
switch(config)#
show cfs merge status name ntp
Physical-fc-ip
Merge Status: Success [ Thu Aug
5 11:51:02 2010 ]
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
IP Address
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
[Merge Master]
MDS-9134
20:00:00:0d:ec:da:6e:00 172.25.183.124
Total number of switches = 2
Lock failure troubleshooting
In order to distribute a configuration in the fabric, a lock must first be acquired on all switches in the
fabric. Once accomplished, a commit can be issued which distributes the data to all switches in the fabric
before releasing the lock.
When a lock has been acquired by another application peer, you cannot commit new configuration
changes. This is a normal situation and you should postpone any changes to an application until the lock
is released. Use the troubleshooting steps in this section only if you believe the lock has not been
properly released.
A lock occurs when an administrator configures a change for a CFS-enabled application. If two
administrators on the same switch attempt to configure the same application, only one administrator is
given the lock. The other administrator is prevented from making changes to that application until the
first administrator commits a change or discards any changes. Use the show cfs lock name command to
determine the name of the administrator who holds the lock for an application. You should check with
that administrator before clearing the lock.
A CFS lock can also be held by another switch in your fabric. Use the show cfs peers name command to
determine all the switches that participate in the CFS distribution for the application. Then use the show
cfs lock name command on each switch to determine who owns the CFS lock for that application. You
should check with that administrator before clearing the lock. Use the CFS abort option to release the
lock without distributing the data to the fabric.