Cisco MDS-9124 Troubleshooting Guide - Page 306

Merge Failure Issues Chapter 15 Troubleshooting Distributed Device Alias Services Send documentation comments to [email protected] • When merging device alias databases, the combined number of device aliases in both databases cannot exceed 8K (8191 device aliases) in fabrics running SAN-OS Release 3.0(x) and earlier, and 20K in fabrics running SAN-OS Release 3.1(x) and later. If the combined number of device entries exceeds the supported limit, then the merge will fail. Merge Failure Issues The most common device alias problems occur when merging databases. This section describes measures to take when a merge of two fabrics fails because the merge of the device alias databases fails. See Table 15-2. Symptom Merge failed. Table 15-2 Device Alias Database Merge Fails Symptom Possible Cause Solution Merge fails for device A device alias is configured with the Change the conflicting device alias name on one fabric. See alias. same name but with a different pWWN the "Resolving Duplicate Device Alias Names" section on on either side of the fabric. page 15-5. The same pWWN is mapped to different device alias names on either side of the fabric. Change the mapping so the pWWN is mapped to the same device alias name on both sides of the fabric. See the "Resolving Mapping a pWWN to Different Device Alias Names" section on page 15-6. The device alias operation mode (basic Check the device alias mode. Both fabrics must be or enhanced) is not the same for both operating in the same device alias mode. See the fabrics. "Resolving Mode Mismatch" section on page 15-6. Note Device alias enhanced mode is only supported on switches running SAN-OS Release 3.1(1) and later. The size of the device alias database exceeds the limit supported by some switches in the fabric. Upgrade the SAN-OS release for all switches to 3.1(1) or later. See the "Resolving Merge Failures in Mixed Fabric" section on page 15-7. An application fails the validation of the merge database. Analyze the problem from the application perspective and make the appropriate corrections. See the "Resolving a Validation Failure" section on page 15-8. Merge remains in progress and does not complete. A user is editing the application database. A user edited the application database and forgot to release the lock. The application is busy handling its own merge. Determine which application database is locked, and take the appropriate steps to unlock it. When the application database is unlocked, the merge should be automatically retried. See the "Resolving Merge in Progress Issues" section on page 15-9. The application database is locked due to a defect in the application. 15-4 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05