Send documentation comments to mdsfeedback-doc@cisco.com
14-13
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 14 Troubleshooting Zones and Zone Sets
Zone Merge Failure
Resolving Mismatched Default Zone Policies Using the CLI
To resolve mismatched default zone policies using the CLI, follow these steps:
Step 1 Issue the show zone status command.
v_188# show zone status
VSAN: 1 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow session: none <------------------
hard-zoning: enabled
Default zone:
qos: low broadcast: disabled ronly: disabled
Full Zoning Database :
Zonesets:5 Zones:18 Aliases: 11
Active Zoning Database :
Name: ZoneSet1 Zonesets:1 Zones:2
Status:
This example shows the default zone policy is deny, and the zone mode is basic.
Step 2 If you are using basic zoning, follow these steps:
a. Repeat Step 1 for all switches in the VSAN to verify that they have the same zone mode. Use the
zone mode basic command to change any switches that are not in basic mode.
b. Use the zone default-zone command on each switch in the VSAN to set the same default zone
policy.
Step 3 If you are using enhanced zoning, follow these steps:
a. Use the show version command on all switches in the VSAN to verify that all switches are capable
of working in the enhanced mode.
All switches must have Cisco MDS SAN-OS Release 2.0(1b) or later. If one or more switches are
not capable of working in enhanced mode, then your request to move to enhanced mode is rejected.
b. Use the zone default-zone command to set the default zone policy.
c. Use the zone mode enhanced vsan-id command to set the operation mode to enhanced zoning
mode.
By doing so, you will automatically start a session, acquire a fabric wide lock, distribute the active
and full zoning database using the enhanced zoning data structures, distribute zoning policies, and
then release the lock. All switches in the VSAN then move to the enhanced zoning mode.
switch(config)# zone mode enhanced vsan 3000
Note After moving from basic zoning to enhanced zoning (or vice versa), we recommend that you use
the copy running-config startup-config command to save the running configuration.
Zone Merge Failure
A zone merge request may fail because of the following configuration issues:
• Too many zone sets
• Too many aliases
To Next Page
Loading...
Need help?
General