Fabric OS Troubleshooting and Diagnostics Guide v7.0.0 (53-1002150-02, June 2011)

90 Fabric OS Troubleshooting and Diagnostics Guide
53-1002150-02
Using the SpinFab and portTest commands
10
Link errors
Once the frame is sent out of the port, the spinFab command monitors the link errors in the ASIC.
If any of the error counters are non-zero, spinFab reports ERROR and the test fails on the port.
ERROR: DIAG ERRSTAT spinfab, pass 6,
Pt0/17(7) Ch0/7 CRC_err Error Counter is 109738997 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 Enc_in Error Counter is 32 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 Enc_out Error Counter is 187725412 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 TruncFrm Error Counter is 32 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 FrmTooLong Error Counter is 32 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 BadOrdSet Error Counter is 32 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 BadEOF Error Counter is 1 sb 0,
ERROR: DIAG ERRSTAT spinfab, pass 1,
Pt0/3(33) Ch0/33 DiscC3 Error Counter is 32 sb 0,
If you receive any of the errors listed above, then follow the suggested debugging procedures:
• The spinFab command does not clear any existing error counters before running the test. You
should first clear all error counters and re-run the spinFab command.
• Verify that the link comes up by enabling and disabling the local or remote ports.
• Verify that the source of the error is either local port or remote port. This can be done by
monitoring the port statistics on both the ends simultaneously. Refer to “Displaying the port
statistics” on page 96 for more information on how to display the statistics for a port.
• Verify that the cables and SFPs are inserted properly. Remove and insert them again on both
the ends.
• Verify that the failing local port is working fine when connected to another remote port.
Similarly, check whether the failing remote port is working fine when connected to another
local port.
• Once the fault is isolated on either the local or remote port, replace the cable and SFPs
connected to the local and remote ports.
• In case of loopback ports, change the loopback plug. Refer to “Marginal links” on page 30 for
more information on changing the loopback plug.
• Further isolation can be done by running the portLoopbackTest command (Offline test) on the
failing port in-order to check whether the blade internal ports are having some problems.
- The -lb_mode 1 operand verifies that the SFP is working within normal operating
parameters. The use of this operand requires that loopback cables are connected.
- The -lb_mode 2 verifies that the ASIC port is working within normal operating parameters.
The use of this operand does not require any loopback cables.