Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual page 108

Troubleshooting guide
Table of Contents

Advertisement

Cisco Fabric Services
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 .
admin
--------------------------------------------------------------------------------
Enter configuration mode and enter the commit command for the application to restore all peers in the
Step 3
fabric to the same configuration database.
Example:
switch(config)# ntp commit
switch(config)# show cfs merge status name ntp
Physical-fc-ip
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
20:00:00:0d:ec:da:6e:00 172.25.183.124
Total number of switches = 2
switch(config)# show cfs merge status name ntp
Physical-fc-ip
Local Fabric
--------------------------------------------------------------------------------
Switch WWN
--------------------------------------------------------------------------------
20:00:00:0d:ec:50:09:00 172.25.183.42
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.
Cisco Nexus 5000 Series Troubleshooting Guide
5-36
34684
Merge Status: Success [ Thu Aug
IP Address
switch
Merge Status: Success [ Thu Aug
IP Address
MDS-9134
Chapter 5
Troubleshooting SAN Switching Issues
5 11:51:02 2010 ]
[Merge Master]
5 11:51:02 2010 ]
[Merge Master]
OL-25300-01

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents