Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual page 652

Database Merge Guidelines
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
Figure 29-25
Cisco MDS switch
Cisco MDS switch
You can configure different IVR configurations in different Cisco MDS switches.
•
Be aware that the merge follows more liberal approach in order to avoid traffic disruption. After the
•
merge, the configuration will be a union of the configurations that were present on the two switches
involved in the merge.
VSANs with the same VSAN ID but different AFIDs are counted as two separate VSANs.
Note
Cisco MDS 9000 Family Fabric Manager Configuration Guide
29-32
Fabric Merge Consequences
Fabrics with
dissimilar zones
Fabric X
Cisco MDS switch
ivzs1
ivz1
wwn1
wwn2
The configurations are merged even if both fabrics have different configurations.
–
A union of zones and zone sets are used to get the merged zones and zone sets. If a dissimilar
–
zone exists in two fabrics, the dissimilar zones are cloned into the zone set with appropriate
names so both zones are present.
The merged topology contains a union of the topology entries for both fabrics.
–
The merge will fail if the merged database contains more topology entries than the allowed
–
maximum.
The total number of VSANs across the two fabrics cannot exceed 128.
–
The total number of IVR-enabled switches across the two fabrics cannot exceed 128.
–
The total number of zone members across the two fabrics cannot exceed 10,000. As of Cisco
–
SAN-OS Release 3.0(3), the total number of zone members across the two fabrics cannot exceed
20,000. A zone member is counted twice if it exists in two zones.
Cisco MDS switch
Fabric Y
Cisco MDS switch
ivzs1
ivz1
wwn3
wwn4
Chapter 29 Configuring Inter-VSAN Routing
Both zones contained
in the zone set
Fabric XY
Cisco MDS switch
ISL
ivzs1 ivzs1
ivz1 ivz1
wwn1
wwn2
ivz1 wwnC ivz1 wwnC
wwn3
wwn4
OL-17256-03, Cisco MDS NX-OS Release 4.x
witch
wwn1
wwn2
wwn3
wwn4