HP Cisco Nexus 5000 Cisco Nexus 5000 Series Switch CLI Software Configuration - Page 667

Chapter 50 Troubleshooting Troubleshooting Fibre Channel Send feedback to [email protected] Destination port: telnet (23) Sequence number: 0 (relative sequence number) Acknowledgement number: 0 (relative ack number) Header length: 20 bytes Flags: 0x10 (ACK) 0... .... = Congestion Window Reduced (CWR): Not set .0.. .... = ECN-Echo: Not set ..0. .... = Urgent: Not set ...1 .... = Acknowledgment: Set .... 0... = Push: Not set .... .0.. = Reset: Not set .... ..0. = Syn: Not set .... ...0 = Fin: Not set Window size: 64334 Checksum: 0x934f [correct] [Good Checksum: True] [Bad Checksum: False] 1 packets captured For more information on Wireshark, see the following URL: http://www.wireshark.org/docs/ Troubleshooting Fibre Channel This section describes troubleshooting methods to resolve issues with Fibre Channel. This section includes the following topics: • fctrace, page 50-5 • fcping, page 50-7 fctrace The fctrace feature provides the following capabilities: • Trace the route followed by data traffic. • Compute inter-switch (hop-to-hop) latency. You can invoke fctrace by providing the FC ID, the N port WWN, or the device alias of the destination. The trace frame is routed normally through the network until it reaches the far edge of the fabric. When the frame reaches the edge of the fabric (the F 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 failure. Note The fctrace feature works only on TE ports. Make sure that only TE ports exist in the path to the destination. If 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. OL-16597-01 Cisco Nexus 5000 Series Switch CLI Software Configuration Guide 50-5