Send documentation comments to mdsfeedback-doc@cisco.com
14-4
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 14 Troubleshooting Zones and Zone Sets
Zone and Zone Set Issues
Example 14-3 Zone Set Analysis
switch# show zone analysis zoneset zs1 vsan 1
Zoning database analysis vsan 1
Zoneset analysis: zs1
Num zonesets: 1
Num zones: 0
Num aliases: 0
Num attribute groups: 0
Formattted size: 20 bytes / 2048 Kb
See the Cisco MDS 9000 Family Command Reference for the description of the information displayed
in the command output.
The debug zone change CLI command followed by the zone name in question can help you get started
debugging zones for protocol errors, events, and packets.
Note To enable debugging for zones, use the debug zone command in EXEC mode. To disable a debug
command, use the no form of the command or use the no debug all command to turn off all debugging.
For protocol errors, use:
debug zone change errors
vsan-id
For protocol events, use:
debug zone change events
vsan-id
For protocol packets, use:
debug zone change packets
vsan-id
Other useful debug commands include:
debug zone {all |
change {errors | events | packets} |
database {detail | errors | events} |
gs errors {errors | events | packets} |
lun-zoning {errors | events | packets} |
merge {errors | events | packets} |
mts notifications |
pss {errors | events} ||
read-only-zoning {errors | events | packets} |
tcam errors {errors | events | packets} |
transit {errors | events}} [vsan
vsan-id
]
Zone and Zone Set Issues
The section covers the following zone and zone set issues:
• Host Cannot Communicate with Storage, page 14-5
• Troubleshooting Zone Set Activation, page 14-8
• Troubleshooting Full Zone Database Synchronization Across Switches, page 14-11
• Mismatched Default Zone Policy, page 14-12
• Recovering from Link Isolation, page 14-15
• Mismatched Active Zone Sets Within the Same VSAN, page 14-17
To Next Page
Loading...
Need help?
General