Chapter 23
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
Remove all non-pWWN-type zone entries on all MDS switches running Cisco SAN-OS prior to merging
Caution
fabrics if there is a Cisco MDS 9020 switch running FabricWare in the adjacent fabric.
The Merge Process
The merge process operates as follows:
1.
2.
3.
Configuring Zone Merge Control Policies
To configure merge control policies, follow these steps:
Command
Step 1
switch# config t
switch(config)#
Step 2
switch(config)# zone merge-control restrict
vsan 4
switch(config)# no zone merge-control
restrict vsan 2
switch(config)# zone commit vsan 4
Default Zone Policies
To permit or deny traffic in the default zone, follow these steps:
Command
Step 1
switch# config t
Step 2
switch(config)# zone default-zone permit vsan 5
switch(config)# no zone default-zone permit vsan 3
Step 3
switch(config)# zone commit vsan 5
OL-16184-01, Cisco MDS SAN-OS Release 3.x
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.
Purpose
Enters configuration mode.
Configures a restricted merge control setting for
this VSAN.
Defaults to using the allow merge control setting
for this VSAN.
Commits the changes made to VSAN 4.
Purpose
Enters configuration mode.
Permits traffic flow to default zone
members.
Denies traffic flow to default zone
members and reverts to factory default.
Commits the changes made to VSAN 5.
Cisco MDS 9000 Family CLI Configuration Guide
Enhanced Zoning
23-35