Send documentation comments to mdsfeedback-doc@cisco.com
29-33
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 29 Configuring Inter-VSAN Routing
Database Merge Guidelines
Note If only some of the switches in the fabrics are running Cisco SAN-OS Release 3.0(3) or later, and the
number of zone members exceeds 10,000, you must either reduce the number of zone members in the
fabric or upgrade all switches in both fabrics to Cisco SAN-OS Release 3.0(3) or later.
–
The total number of zones across the two fabrics cannot exceed 2000. As of Cisco SAN-OS
Release 3.0(3), the total number of zones across the two fabrics cannot exceed 8000.
Note If only some of the switches in the fabrics are running Cisco SAN-OS Release 3.0(3) or later, and if the
number of zones exceeds 2000, you must either reduce the number of zones in the fabric or upgrade all
switches in both fabrics to Cisco SAN-OS Release 3.0(3) or later.
–
The total number or zone sets across the two fabrics cannot exceed 32.
Table 29-5 describes the results of a CFS merge of two IVR-enabled fabrics under different conditions.
Caution If you do not follow these conditions, the merge will fail. The next distribution will forcefully
synchronize the databases and the activation states in the fabric.
Resolving Database Merge Failures
If a merge failure occurs, use the following commands to display the error conditions:
• show ivr merge status
• show cfs merge status name ivr
• show logging last lines (and look for MERGE failures)
Depending on the failure indicated in the show command outputs, you can perform the following:
Table 29-5 Results of Merging Two IVR-Enabled Fabrics
IVR Fabric 1 IVR Fabric 2 After Merge
NAT enabled NAT disabled Merge succeeds and NAT
enabled
Auto mode on Auto mode off Merge succeeds and auto mode
on
Conflicting AFID database Merge fails
Conflicting IVR zone set database Merge succeeds with new zones
created to resolve conflicts
Combined configuration exceeds limits (such as maximum number
of zones or VSANs)
Merge fails
Service group 1 Service group 2 Merge succeeds with service
groups combined
User-configured VSAN topology configuration with conflicts Merge fails
User-configured VSAN topology configuration without conflicts Merge succeeds
To Next Page
Loading...
Need help?
General
