Cisco MDS-9124 Troubleshooting Guide - Page 314

Validation and Commit Failure Issues Chapter 15 Troubleshooting Distributed Device Alias Services Send documentation comments to [email protected] Symptom Commit or configuration failed. Table 15-3 Device Alias Database Commit Fails Symptom Possible Cause Solution Commit fails due to a The device alias database conflicts with Tune the device alias database or the application validation failure the application configuration. configuration to eliminate the conflict. See the "Resolving Database Conflicts" section on page 15-12. The application is busy. Verify that the application that failed the validation is no longer busy, and then retry the commit. See the "Resolving Application Busy Situations" section on page 15-13. Commit or configuration fails. The size of the device alias database exceeds the supported limit. 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. Enhanced mode is not supported on some switches in the mixed fabric. 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 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 Step 2 Step 3 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 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: ==>Reason 2007 Apr 10 11:54:24 switch-1 %DEVICE-ALIAS-3-COMMIT_FAILED: Failed to ==>Commit status commit the pending database: inter-VSAN zone member cannot be in more ==>Reason than one VSAN 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: 15-12 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05