Cisco Nexus 5000 Series - Troubleshooting Fibre Channel

Send feedback to nx5000-docfeedback@cisco.com
1-5
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
OL-16597-01
Chapter 1 Troubleshooting
Troubleshooting Fibre Channel
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 40
Identification: 0xa651 (42577)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 127
Protocol: TCP (0x06)
Header checksum: 0x2765 [correct]
[Good: True]
[Bad : False]
Source: 10.200.0.103 (10.200.0.103)
Destination: 10.193.24.42 (10.193.24.42)
Transmission Control Protocol, Src Port: 1288 (1288), Dst Port: telnet (23), Seq: 0, Ack:
0, Len: 0
Source port: 1288 (1288)
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 1-5
• fcping, page 1-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.