Analyzing A Zone Merge - HP Cisco MDS 9216 - Fabric Switch Configuration Manual

Chapter 30 Configuring and Managing Zones
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
Table 30-4
Local Database
Empty.
Contains data.
1. In the enhanced zoning mode, the active zone set does not have a name in interop mode 1. The zone set names are only present
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.
The merge process operates as follows:
1.
2.
3.

Analyzing a Zone Merge

To perform a zone merge analysis using Fabric Manager, follow these steps:
Step 1 Choose Zone > Merge Analysis.
You see the Zone Merge Analysis dialog box shown in
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Database Zone Merge Status (continued)
Adjacent Database
Contains data.
Empty.
for full zone sets.
The software compares the protocol versions. If the protocol versions differ, then the ISL is isolated.
If the protocol versions are the same, then the zone policies are compared. If the zone policies differ,
then the ISL is isolated.
If the zone merge options are the same, then the comparison is implemented based on the merge
control setting.
If the setting is restrict, the active zone set and the full zone set should be identical. Otherwise
a.
the link is isolated.
If the setting is allow, then the merge rules are used to perform the merge.
b.
Merge Status Results of the Merge
Successful. The adjacent database
information populates the
local database.
Successful. The local database
information populates the
adjacent database.
Figure 30-39.
Cisco MDS 9000 Family CLI Configuration Guide
Enhanced Zoning
30-43