Database Merge Guidelines - Cisco DS-X9530-SF1-K9 - Supervisor-1 Module - Control Processor Configuration Manual

Mds 9000 family

Table of Contents

Configuring Inter-VSAN Routing

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 .

Database Merge Guidelines

A database merge refers to a union of the configuration database and static (unlearned) entries in the

active database. Refer to the

Fabric Merge Consequences

Fabrics with

dissimilar zones

Cisco MDS switch

OL-6973-03, Cisco MDS SAN-OS Release 2.x

"CFS Merge Support" section on page 5-7

Be aware of the following conditions when merging two IVR fabrics:

The IVR configurations are merged even if two fabrics contain different configurations.

If dissimilar zones exist in two merged fabrics, the zone from each fabric is cloned in the

distributed zone set with appropriate names (see

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.

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

The total number of VSANs across the two fabrics cannot exceed 64. As of Cisco MDS

SAN-OS Release 2.1(1a), the total number of VSANs across the two fabrics cannot exceed 128.

Both zones contained

in the zone set

Cisco MDS switch

Cisco MDS 9000 Family Configuration Guide

Database Merge Guidelines

for detailed concepts.