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
15-13
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 15 Troubleshooting Distributed Device Alias Services
Validation and Commit Failure Issues
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 would result in the resolution of enhanced device alias member
A2 in 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 IVR. IVR detects the configuration problem
and rejects the device alias database validation.
switch-1#
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-2#
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-1#
conf t
Enter configuration commands, one per line. End with CNTL/Z.
switch-1(config)#
device-alias database
switch-1(config-device-alias-db)#
device-alias name A2 pwwn 21:01:01:01:01:01:01:02
switch-1(config-device-alias-db)#
exit
switch-1(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 then issuing the commit command again.
Resolving Application Busy Situations
A device alias commit can fail because an application is busy and cannot perform the requested
validation. If that occurs, the device alias CFS lock is not released and the pending database contents
remain unchanged. When the application is no longer busy, retry the commit request.
Example 15-9
shows the console output that occurs when an application busy situation causes the
commit to fail.
Example 15-9 Application Busy Console Output
switch-2(config)#
device-alias commit
Some of the registered modules are busy handling other requests. Please
retry the command after some time.
Review the syslogs (
Example 15-10
) and use the
show device-alias
commands (
Example 15-11
) to
gather additional details about the application that returned busy.
Example 15-10 Application Busy Syslog Message
2007 Apr 10 02:30:55 switch-2 %DEVICE-ALIAS-3-VALIDATION_FAILED: Failed SAP:
==>Status
110 Reason: Some of the registered modules are busy handling other requests.
==>Reason
Please retry the command after some time. Expln: there is a pending action.
==>Resolution
