Resolving Database Conflicts - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Validation and Commit Failure Issues
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
Symptom
Table 15-3 Device Alias Database Commit Fails
Symptom Possible Cause
Commit fails due to a The device alias database conflicts with
validation failure the application configuration.
The application is busy.
Commit or The size of the device alias database
configuration fails. exceeds the supported limit.
Enhanced mode is not supported on
some switches in the mixed fabric.

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. You must either correct the device alias
database or the application configuration.
To determine the application that failed the validation and the reason for the failure, follow these steps:
Step 1 View the output from the device-alias commit command. In this example, the commit fails because there
is a conflict between the device alias database and an application configuration.
switch-1(config)# device-alias commit
inter-VSAN zone member cannot be in more than one VSAN ===> reason for commit failure
Determine which application configuration is in conflict with the device alias database by reviewing the
Step 2
syslogs for the switch where the commit was issued. In this example, 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 is
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
commit the pending database: inter-VSAN zone member cannot be in more ==>Reason
than one VSAN
Step 3 Review the syslog on the switch where the validation is rejected. In this example, the following syslog
is printed on the switch 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
Expln:
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
15-12
Commit or configuration failed.
Chapter 15 Troubleshooting Distributed Device Alias Services
Solution
Tune the device alias database or the application
configuration to eliminate the conflict. See the
Database Conflicts" section on page
Verify that the application that failed the validation is no
longer busy, and then retry the commit. See the
Application Busy Situations" section on page
Reduce the number of entries in the device alias database,
or upgrade the SAN-OS release for all switches to Release
3.1(1) or later. See the "Resolving Database Size Issues"
section on page 15-14.
Upgrade the SAN-OS release for all switches in the fabric
to Release 3.1(1) or later, or change the device alias mode
to basic. See the "Resolving Mode Issues" section on
page 15-15.
"Resolving
15-12.
"Resolving
15-13.
==>Reason
==>Commit status
OL-9285-05