Clearing The Error Counters; Enabling A Port - Brocade Communications Systems StoreFabric SN6500B Troubleshooting Manual

•
Tx/Rx errors
Following errors are seen when the port fails to transmit or receive the frames.
The following are debugging procedures:
•
•
•
•

Clearing the error counters

This procedure clears the port hardware statistics, including ALPA-based CRC monitor, End-to-End
monitor, and filter-based performance monitor statistics.
1. Connect to the switch and log in as admin.
2. Enter the portStatsClear <slot/port> command.

Enabling a port

1. Connect to the switch and log in using an account with admin permissions.
2. Enter the appropriate command based on the current state of the port and on whether it is
Fabric OS Troubleshooting and Diagnostics Guide
53-1002751-01
Using the SpinFab and portTest commands
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.
ERROR: DIAG PORTSTOPPED spinfab:spinfab, 0 nMegs,
Pt7/2(2) Ch0/2 No Longer Transmitting, FTX Counter Stuck at 116295726,
ERROR: DIAG TIMEOUT spinfab:spinfab, pass 2,
Pt0/17(7) Ch0/7 Receive Error/Timeout
Check whether the same port is reporting Link Errors as discussed in
If yes, follow the same set of debugging procedures as discussed in
Check whether the local/remote port is beyond port 255. If yes, try connecting to the lower
number of ports. This behavior is found in Fabric OS v6.2.0 and earlier versions only.
Check whether the local/remote port is part of shared-area region. If yes, try connecting to the
non-shared area ports. This behavior is found in Fabric OS v6.2.0 and earlier versions only.
Check whether the local/remote port is having its area swapped. If yes, try connecting to the
normal area ports. This behavior is found in Fabric OS v6.2.0 and earlier versions only.
necessary to specify a slot number:
•
To enable a port that is disabled, enter the command portEnable portnumber or
portEnable slotnumber/portnumber.
•
To enable a port that is persistently disabled, enter the command portCfgPersistentEnable
portnumber or portCfgPersistentEnable slotnumber/portnumber.
If you change port configurations during a switch failover, the ports may become disabled. To
bring the ports online, re-issue the portEnable command after the failover is complete.
10
"Link errors" on page 88.
"Link errors" on page 88.
89