Resolving Database Conflicts - Cisco MDS 9000 Series Configuration Manual

Distributing Device Alias Services
Total number of entries = 2
switch# show device-alias database
device-alias name A1 pwwn 21:01:01:01:01:01:01:01 => Pre-merge: A2 not defined on switch-2
Total number of entries = 1
Because IVR is enabled on switch-2, review the IVR zone set.
switch# show ivr zoneset
zoneset name s1
zone name z1
pwwn 21:01:01:01:01:01:01:02 vsan
device-alias A2
Prior to the database merge, device-alias A2 is not defined on switch-2. Because of the merge between switch-1 and
switch-2, device-alias A2 becomes available on switch-2, and A2 is mapped to pWWN 21:01:01:01:01:01:01:02.
The device alias-based member A2 in the IVR zone z1 is resolved and mapped to pWWN 21:01:01:01:01:01:01:02, and
is a member of VSAN 2. However, pWWN 21:01:01:01:01:01:01:02 is already a member of VSAN 1. The mapping that
occurs because of the device-alias merge makes the IVR configuration illegal. The same pWWN cannot be a member of
multiple VSANs.
In the case when IVR configuration is illegal, the pWWN in VSAN 2 is defined using the device alias (A2), while the
member in VSAN 1 is defined using the actual pWWN. The IVR detects this situation and rejects the device-alias
validation. As a result, the device-alias merge fails.

Resolving Database Conflicts

If an entry in the device-alias database conflicts with the configuration of a registered application, the
device-alias database commit fails the validation process. Correct either the device-alias database or the
application configuration.
To determine the application that failed the validation and the reason for the failure, perform these steps:
Step 1 Use the device-alias commit command to view the output.
This example shows that the commit failed because there is a conflict between the device-alias database and an application
configuration:
switch# configure terminal
Enter configuration commands, one per line.
switch(config)# device-alias commit
inter-VSAN zone member cannot be in more than one VSAN ===> reason for commit failure
Step 2
Determine which application configuration is in conflict with the device-alias database by reviewing the syslogs for the
switch in which the commit was issued.
This example shows that SAP 110 (IVR) on sWWN 20:00:00:0d:ec:04:99:40 (switch-2) has rejected the validation, and
therefore, the device-alias commit has failed:
2007 Apr 10 11:54:24 switch-1 %DEVICE-ALIAS-3-VALIDATION_FAILED: Failed=>Validation Status
SWWN: 20:00:00:0d:ec:04:99:40 Failed SAP: 110 Reason: inter-VSAN zone ==>Switch and SAP member cannot
be in more than one VSAN Expln:
2007 Apr 10 11:54:24 switch-1 %DEVICE-ALIAS-3-COMMIT_FAILED: Failed to
1 autonomous-fabric-id
vsan 2 autonomous-fabric-id
End with CNTL/Z.
==>Reason
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
Resolving Database Conflicts
1
1
==>Commit status commit the
181