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-6
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 7 Troubleshooting Cisco Fabric Services
Merge Failure Troubleshooting
Recovering from a Merge Failure with Fabric Manager
To recover from a merge failure using Fabric Manager, follow these steps:
Step 1
Select the
CFS
tab for the application that you are configuring and check the merge field to identify a
switch that shows a merge failure. For example, choose
Fabricxx > All VSANS > DPVM
and select the
CFS
tab to determine if there is a merge failure for DPVM.
Step 2
Set the
Config Action drop-down menu to
commit
and click
Apply Changes
to restore all peers in the
fabric to the same configuration database.
Recovering from a Merge Failure with the CLI
To recover from a merge failure using the CLI, follow these steps:
Step 1
To identify a switch that shows a merge failure, issue the
show cfs merge status name
application-name
command. Example command output follows:
Switch#
show cfs merge status name ntp
Physical Merge Status:Failure [ Mon Nov 22 06:49:52 2004 ]
Failure Reason: Conflicting entries in the compared databases
Local Fabric
---------------------------------------------------------
Switch WWN IP Address
---------------------------------------------------------
20:00:00:05:30:00:6b:9e 10.76.100.167 [Merge Master]
20:00:00:0e:d7:00:3c:9e 10.76.100.52
Remote Fabric
---------------------------------------------------------
Switch WWN IP Address
---------------------------------------------------------
20:00:00:0d:ec:06:55:c0 10.76.100.205 [Merge Master]
Step 2
For a more detailed description of the merge failure, issue the s
how cfs internal session-history name
application name
detail
command. Example command output follows:
switch# show cfs internal session-history name ntp detail
--------------------------------------------------------------------------------
Time Stamp Source WWN Event
User Name Session ID
--------------------------------------------------------------------------------
Fri Aug 24 04:30:19 2007 20:00:00:0d:ec:04:99:c0 LOCK_REQUEST
admin 3848
Fri Aug 24 04:30:19 2007 20:00:00:0d:ec:04:99:c0 LOCK_ACQUIRED
admin 3848
Fri Aug 24 04:30:19 2007 20:00:00:0d:ec:04:99:c0 COMMIT
admin 3849
Fri Aug 24 04:30:19 2007 20:00:00:0d:ec:04:99:c0 LOCK_RELEASE_REQUEST
admin 3848
Fri Aug 24 04:30:19 2007 20:00:00:0d:ec:04:99:c0 LOCK_RELEASED
admin 3848
Fri Aug 24 04:33:07 2007 20:00:00:0d:ec:04:99:c0 LOCK_REQUEST
admin 3868