S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
7-5
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 7 Troubleshooting Cisco Fabric Services
Merge Failure Troubleshooting
-----------------------------------------------------------
103 20:00:00:0e:d7:00:3c:9e 10.76.100.52 [Local]
221 20:00:00:05:30:00:6b:9e 10.76.100.167
11 20:00:00:0d:ec:06:55:c0 10.76.100.205
Total number of entries = 3
Step 3
To determine if all the switches in the fabric constitute one CFS fabric, or a multitude of partitioned CFS
fabrics, issue the
show cfs merge status name
application-name
command and the
show cfs peers
name
application-name
command and compare the outputs. If the outputs contain the same list of
switches, the entire set of switches constitutes one CFS fabric. When this is the case the merge status
should always show success at all switches. Example command outputs follow:
Switch#
show cfs merge status name dpvm
Physical Merge Status: Success [ Sat Nov 20 11:59:36 2004 ]
Local Fabric
---------------------------------------------------------
Switch WWN IP Address
---------------------------------------------------------
20:00:00:05:30:00:4a:de 10.76.100.51 [Merge Master]
20:00:00:0d:ec:0c:f1:40 10.76.100.204
Switch#
show cfs peers name dpvm
Scope : Physical
--------------------------------------------------
Switch WWN IP Address
--------------------------------------------------
20:00:00:0d:ec:0c:f1:40 10.76.100.204 [Local]
20:00:00:05:30:00:4a:de 10.76.100.51
Total number of entries = 2
If the list of switches in the
show cfs merge status name
command output is shorter than that of the
show cfs peers name
command output, the fabric is partitioned into multiple CFS fabrics and the merge
status may show that the merge has failed, is pending, or is waiting.
Merge Failure Troubleshooting
During a merge, the merge managers in the merging fabrics exchange their configuration databases with
each other. The application on one of them merges the information, decides if the merge is successful,
and informs all switches in the combined fabric of the status of the merge. When a merge is successful,
the merged database is distributed to all switches in the combined fabric and the entire new fabric
remains in a consistent state. A merge failure indicates that the merged fabrics contain inconsistent data
that could not be merged.
If a new switch is added to the fabric and the merge status for any application shows "In Progress" for a
prolonged period of time, then there may be an active session for that application in some switch. Check
the lock status for that application on all the switches using the
show cfs lock
CLI command. If there
are any locks, then the merge will not proceed. Commit the changes or clear the session lock so that the
merge can proceed.
