Debugging Spinfab Errors - Brocade Communications Systems 8 Troubleshooting And Diagnostics Manual

CAUTION
During the spinFab testing, the switch remains in normal operation. However, some performance
degradation will occur due to the ISL links being saturated with the test frames. This test should
be run with caution on a live fabric.
Table 15
command.
TABLE 15
Port type
Loopback
E_Ports
Trunk Master ports
Ports beyond index 255
Ports with swapped areas
Shared-area ports
Ports in logical switches
Ports in base switches
Trunk slave ports
Long distance ports
F_Ports connected to Brocade HBAs
ICL ports
F_Ports connected to Access Gateway
EX_Ports
Ports in an Access Gateway switch
1.
firmware version on the HBA is v2.1.1 or later.

Debugging spinFab errors

Link errors and tx/rx errors are seen when the spinFab test fails.
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.
Fabric OS Troubleshooting and Diagnostics Guide
53-1001769-01
lists the supported ports for the specified version of Fabric OS when using the spinFab
Port type support
If you use the spinFab command to test F_Ports connected to Brocade HBAs it is required that the
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,
Supported in v6.2.0 Supported in v6.3.0
Yes Yes
Yes Yes
Yes Yes
No Yes
No Yes
No Yes
No Yes
No Yes
No No
No No
No No
No No
No No
No No
No No
SpinFab and portTest
Supported in v6.4.0
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
1
Yes
No
No
No
No
10
91