Merge Process - Cisco MDS 9000 Series Configuration Manual

Hide thumbs Also See for MDS 9000 Series:
Table of Contents

Advertisement

Merge Process

Local Database
The databases contains a zone, zone alias,
or zone attribute group object with same
name 1 but different members.
Note
Empty.
Contains data.
1
Caution
Remove all non-PWWN-type zone entries on all MDS switches running Cisco SAN-OS prior to merging
fabrics if there is a Cisco MDS 9020 switch running FabricWare in the adjacent fabric.
Merge Process
When two Fibre Channel (FC) switches that have already been configured with active zonesets and are not
yet connected are brought together with an Extended ISL (EISL) link, the zonesets merge. However, steps
must be taken to ensure zone consistency before configuring and activating new zones.
Best Practices
When a zone merge occurs, as long as there is not competing information, each switch learns the others zones.
Each switch then has three configuration entities. The switches have:
• The saved configuration in NVRAM. This is the configuration as it was the last time the copy
• The running configuration. This represents the configuration brought into memory upon the last time the
• The configured zoning information from the running configuration plus the zoning information learned
The merge process operates as follows:
1. The software compares the protocol versions. If the protocol versions differ, then the ISL is isolated.
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
118
.In the enhanced zoning mode,
the active zoneset does not have
a name in interop mode 1. The
zoneset names are only present
for full zone sets.
In the enhanced zoning mode, the active zoneset does not have a name in interop mode 1. The zoneset
names are only present for full zone sets.
running-configuration startup-configuration command was issued.
MDS was brought up, plus any changes that have been made to the configuration. With reference to the
zoning information, the running configuration represents the configurable database, known as the full
database.
from the zone merge. This combination of configured and learned zone information is the active zoneset.
Adjacent
Merge Status
Database
Failed.
ISLs are isolated.
Contains data.
Successful.
Empty.
Successful.
Configuring and Managing Zones
Results of the Merge
The adjacent database
information populates
the local database.
The local database
information populates
the adjacent database.

Advertisement

Table of Contents
loading

Table of Contents