For Brocade SAN switch, the command porterrshow shows the statistics of each port, such as In Bytes, Out Bytes, and error counts etc..
Some of counts are easy to recognized, some are not. Here is a quick reference for admins to easy identify them, therefore easy to debug the problem/performance issue out.
For more trouble shotting commands, see Brocade SAN switch trouble shooting commands.
Porterrshow output example:
frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout pcs
tx rx in err g_eof shrt long eof out c3 fail sync sig tx rx err
0: 838.0m 2.4g 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0
1: 7.9m 1.8g 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2: 7.4m 1.1g 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
In the example output above, here are explainations for the counters.
– Counters representing the number of frames transmitted. This would be a place to gauge the traffic.
enc_in - 8bit/10bit encoding errors inside frame. Words inside of frames are encoded, if this encoding is corrupted or an error is detected enc_in is generated. If this counter is increasing, SFP/cable needs to be checked/replaced.
- 8bit/10bit encoding errors occurred in words (ordered sets) in/outside the Fibre Channel frame. Words in/outside of frames are encoded, if this encoding is corrupted or an error is detected enc in/out is generated. This is a sign of a hardware problem. Suggested actions would be to replace the cable or SFP, move cable to another port, or run porttest.
Note: Minimum compliance with the link bit error rate specification on a link continuously receiving frames would cause approximately one error every 20 minutes. Reinitialisation / reboots of the associated Nx-port can also cause these errors.
enc_out errors on their own imply a cable/connector problem. Enc_out errors and crc_err together imply GBIC/SFP problem
- A mathematical formula generates counters at the sending port. The receiving port uses the same formula to check and compare. Generally speaking. crc_err and enc_out errors together imply GBIC/SFP problem. Suggested actions would be to replace the cable or SFP, move cable to another port, or run porttest.
FC frames are 2148 bytes maximum. Frames that were longer than the FC maximum (SOF+header+2112bytes+CRC+EOF). If an eof is corrupted or data generation is incorrect a too_long error is reported.
The too_short error statstics counter is incremented whenever a frame, bounded by an SOF and EOF, is received and the number of words between the SOF and EOF is less than 7 words (6 words header plus 1 word CRC), i.e. 38 bytes (not 48) including the SOF and EOF.
This could be caused by the transmitter, or an unreliable link.
- After a loss of synchronization error continuous mode alignment allows the receiver to reestablish word alignment at any point in the incoming bit stream while the receiver is operational. Such realignment is likely (but not guaranteed) to result in code violations and subsequent loss of synchronization. Under certain conditions, it may be possible to realign an incoming bit stream without loss of synchronization. If such a realignment occurs within a received frame, detection of the resulting error condition is dependent upon higher-level function (e.g., invalid CRC,missing EOF Delimiter).
– Discard class 3 errors could be generated by a switch when devices send frames without performing a FLOGI first or send frames to an invalid destination. This error is just reporting that such a discard occurred.
– If a port remains in the LR Receive State for a period of time greater than a timeout period (R_T_TOV), a Link Reset Protocol Timeout shall be detected which results in a Link Failure condition (enter the NOS Transmit State). The link failure also indicates that loss of signal or loss of sync lasting longer than the R_T_TOV value was detected while not in the Offline state.
– Synchronization failures on either bit or transmission word boundaries are not separately identifiable and cause loss-of synchronization errors.
- Loss of signal
How about other switches?
Other SAN switches have similar commands to show the stats, for example, cisco, we need to check for the stats for individual switch ports using the command show interface <interface #>.