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
11-3
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
OL-9285-05
Chapter 11 Troubleshooting VSANs, Domains, and FSPF
VSAN Issues
•
show fcdomain
•
show fspf
•
show fspf internal route vsan
vsan-id
•
show fcns database vsan
vsan-id
Use the following zone CLI commands to validate your configuration:
•
show zoneset name
zoneset-name
vsan
vsan-id
•
show zoneset active vsan
vsan-id
Note
An asterix (*) near the device listed by the
show zoneset active
command indicates that the
device is logged into the name server.
•
show zone vsan
vsan-id
•
show zone status show
vsan
vsan-range
Note
For more information on zoning issues, see
Chapter 14, “Troubleshooting Zones and Zone Sets.”
VSAN Issues
This section includes the following topics:
•
Host Cannot Communicate with Storage, page 11-3
•
E Port Is Isolated in a VSAN, page 11-5
•
Troubleshooting Interop Mode Issues, page 11-9
Host Cannot Communicate with Storage
Communication problems between a host and storage devices can be caused by port, VSAN, or zone
issues.
Symptom
Host cannot communicate with storage.
Table 11-1
Host Cannot Communicate with Storage
Symptom
Possible Cause
Solution
Host cannot
communicate with
storage.
Host and storage are not in the same
VSAN.
Verify the VSAN membership. See the
“Verifying VSAN
Membership Using Fabric Manager” section on page 11-4
or the
“Verifying VSAN Membership Using the CLI”
section on page 11-4
.
xE port connecting to the remote switch
is isolated.
See the
“E Port Is Isolated in a VSAN” section on
page 11-5
.
Host and storage are not in the same
zone.
See the
“Zone and Zone Set Issues” section on page 14-4
.
