Merge Failure Issues - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Merge 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
•
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
Symptom
Table 15-2 Device Alias Database Merge Fails
Symptom Possible Cause
Merge fails for device A device alias is configured with the
alias. same name but with a different pWWN
on either side of the fabric.
The same pWWN is mapped to
different device alias names on either
side of the fabric.
The device alias operation mode (basic
or enhanced) is not the same for both
fabrics.
The size of the device alias database
exceeds the limit supported by some
switches in the fabric.
An application fails the validation of
the merge database.
Merge remains in A user is editing the application
progress and does not database.
complete.
A user edited the application database
and forgot to release the lock.
The application is busy handling its
own merge.
The application database is locked due
to a defect in the application.
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
15-4
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.
Table 15-2.
Merge failed.
Chapter 15 Troubleshooting Distributed Device Alias Services
Solution
Change the conflicting device alias name on one fabric. See
the "Resolving Duplicate Device Alias Names" section on
page 15-5.
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.
Check the device alias mode. Both fabrics must be
operating in the same device alias mode. See the
"Resolving Mode Mismatch" section on page
Note Device alias enhanced mode is only supported on
switches running SAN-OS Release 3.1(1) and later.
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.
Analyze the problem from the application perspective and
make the appropriate corrections. See the
Validation Failure" section on page
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.
15-6.
"Resolving a
15-8.
OL-9285-05