pending database: inter-VSAN zone member cannot be in more ==>Reason than one VSAN
Step 3 Review the syslog on the switch in which the validation is rejected.
This example shows that the following syslog is printed on switch-2:
2007 Apr 10 19:13:08 switch-2 %DEVICE-ALIAS-3-VALIDATION_REJECTED: Failed
SAP: 110 Reason: inter-VSAN zone member cannot be in more than one VSAN ==>SAP and reason
Step 4 Compare the existing device-alias database (including the desired changes) and the application configuration to find the
conflict.
This example uses the show device-alias database and show ivr zoneset commands along with the console logs of the
device-alias database changes made prior to the commit. The comparison shows that the definition of the new device-alias
A2 results in the resolution of the enhanced device-alias member A2 in the IVR zone z1 to pWWN 21:01:01:01:01:01:01:02,
which is already a member of zone z1. The pWWN is directly defined as a member of VSAN 1, while the enhanced
device-alias A2 is defined as a member of VSAN 2. This configuration is not allowed in the IVR. The IVR detects the
configuration problem and rejects the device-alias database validation.
switch# show device-alias database ===> existing device alias database
device-alias name A1 pwwn 21:01:01:01:01:01:01:01
Total number of entries = 1
switch# show ivr zoneset ===> display existing IVR zone set
zoneset name s1
zone name z1
pwwn 21:01:01:01:01:01:01:02 vsan 1 autonomous-fabric-id 1
device-alias A2 vsan 2 autonomous-fabric-id 1
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# device-alias database
switch(config-device-alias-db)# device-alias name A2 pwwn 21:01:01:01:01:01:01:02
switch(config-device-alias-db)# exit
switch(config)# device-alias commit
inter-VSAN zone member cannot be in more than one VSAN
Step 5 Correct the conflict by making adjustments to the application configuration, or by making changes to the device-alias
database, and running the device-alias commit command again.
Verifying the Device-Alias Database Status
This section provides information about verifying the device-alias database status.
Table 16: Verifying the Device-Alias Database Status
DescriptionCommand Name
Displays information about the status of the CFS
merge for the device-alias database.
show cfs merge status name device-alias
Displays the entire device-alias database.show device-alias database
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
182
Distributing Device Alias Services
Verifying the Device-Alias Database Status