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
Troubleshooting Your Fabric
This chapter describes basic troubleshooting methods used to resolve issues with switches. This chapter
includes the following sections:
The fctrace feature allows you to:
You can invoke fctrace by providing the FC ID, the N port, or the NL port WWN, or the device alias of
the destination. The frames are routed normally as long as they are forwarded through TE ports.
Once the frame reaches the edge of the fabric (the F port or FL port connected to the end node with the
given port WWN or the FC ID), the frame is looped back (swapping the source ID and the destination
ID) to the originator.
If the destination cannot be reached, the path discovery starts, which traces the path up to the point of
The fctrace feature works only on TE ports. Make sure that only TE ports exist in the path to the
destination. In case there is an E port in the path, the fctrace frame is dropped by that switch. Also,
fctrace times out in the originator, and path discovery does not start.
You cannot use the fctrace feature in a locally configured VSAN interface (IPFC interface), but you can
trace the route to a VSAN interface configured in other switches.
OL-16184-01, Cisco MDS SAN-OS Release 3.x
fctrace, page 58-1
fcping, page 58-3
Cisco Fabric Analyzer, page 58-4
Loop Monitoring, page 58-14
The show tech-support Command, page 58-15
IP Network Simulator, page 58-22
Default Settings, page 58-30
Trace the route followed by data traffic.
Compute inter-switch (hop-to-hop) latency.
C H A P T E R
Cisco MDS 9000 Family CLI Configuration Guide