Send documentation comments to mdsfeedback-doc@cisco.com
30-46
Cisco MDS 9000 Family Fabric Manager Configuration Guide
OL-17256-03, Cisco MDS NX-OS Release 4.x
Chapter 30 Configuring and Managing Zones
Enhanced Zoning
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. The software compares the protocol versions. If the protocol versions differ, then the ISL is isolated.
2. If the protocol versions are the same, then the zone policies are compared. If the zone policies differ,
then the ISL is isolated.
3. If the zone merge options are the same, then the comparison is implemented based on the merge
control setting.
a. If the setting is restrict, the active zone set and the full zone set should be identical. Otherwise
the link is isolated.
b. If the setting is allow, then the merge rules are used to perform the merge.
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 Figure 30-44.
Table 30-4 Database Zone Merge Status
Local Database Adjacent Database Merge Status Results of the Merge
The databases contain zone sets with the same name
1
but
different zones, aliases, and attributes groups.
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
for full zone sets.
Successful. The union of the local and
adjacent databases.
The databases contains a zone, zone alias, or zone
attribute group object with same name
1
but different
members.
Failed. ISLs are isolated.
Empty. Contains data. Successful. The adjacent database
information populates the
local database.
Contains data. Empty. Successful. The local database
information populates the
adjacent database.
To Next Page
Loading...
Need help?
General
