Table of Contents
Advertisement
Chapter 19
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 .
Attach the attribute-group to a zone.
Step 3
switch(config)# zone name Zone1 vsan 2
switch(config-zone)# attribute-group SampleAttributeGroup
switch(config-zone)# exit
switch(config)#
Activate the zone set.
Step 4
switch(config)# zoneset activate name Zoneset1 vsan 2
The attribute-groups are expanded and only the configured attributes are present in the active zone set.
Merging the Database
The merge behavior depends on the fabric-wide merge control setting:
•
•
Table 19-3
Local Database
The databases contain zone sets with the same name
different zones, aliases, and attributes groups.
The databases contains a zone, zone alias, or zone
attribute group object with same name
members.
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 to avoid ISL
isolation.
OL-6973-03, Cisco MDS SAN-OS Release 2.x
Restrict—If the two database are not identical, the ISLs between the switches are isolated.
Allow—The two databases are merged using the merge rules specified in
Database Zone Merge Status
Adjacent Database
Contains data.
Empty.
for full zone sets.
Merge Status
1
but
Successful.
Failed.
1
but different
Successful.
Successful.
Cisco MDS 9000 Family Configuration Guide
About Enhanced Zoning
Table
19-3.
Results of the Merge
The union of the local and
adjacent databases.
ISLs are isolated.
The adjacent database
information populates the
local database.
The local database
information populates the
adjacent database.
19-31
Advertisement
Table of Contents
