Send documentation comments to mdsfeedback-doc@cisco.com
15-5
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 15 Troubleshooting Distributed Device Alias Services
Merge Failure Issues
Resolving Duplicate Device Alias Names
To verify that a duplicate device alias name exists in the fabrics, follow these steps:
Step 1 Review the CFS or device alias merge failure syslogs to confirm that the merge failed. Optionally, you
can issue the following CLI command to view the status of the merge:
switch-1# show cfs merge status name device-alias
Physical-fc Merge Status: Failed [ Mon Apr 9 15:57:58 2007 ] ===> Merge status
Local Fabric
-------------------------------------------------------------------------
Switch WWN IP Address
-------------------------------------------------------------------------
20:00:00:0d:ec:2f:c1:40 172.20.150.38 [Merge Master]
switch-1
Total number of switches = 1
Remote Fabric
-------------------------------------------------------------------------
Switch WWN IP Address
-------------------------------------------------------------------------
20:00:00:0d:ec:04:99:40 172.20.150.30 [Merge Master]
switch-2
Total number of switches = 1
Step 2 Verify that the reason for the merge failure is a database mismatch by using the show device-alias merge
status command.
switch-1# show device-alias merge status
Result: Failure
Reason: Databases could not be merged due to mismatch.
Step 3 Identify the duplicate device alias name by using the show device-alias database command from the
appropriate switch in each of the two fabrics. In this example, both databases have the same device alias,
A1, mapped to different pWWNs.
switch-1# show device-alias database
device-alias name A1 pwwn 21:01:01:01:01:01:01:01
Total number of entries = 1
switch-2# show device-alias database
device-alias name A1 pwwn 21:01:01:01:01:01:01:02
Total number of entries = 1
Step 4 Make the appropriate changes to the device alias database for one of the fabrics. Refer to the Cisco MDS
9000 Family CLI Configuration Guide for details.