FC frames are 2148 bytes maximum (frames that were longer than the FC maximum - SOF+header+2112bytes+CRC+EOF).
Generally speaking CRC_errs indicates an issue with the SFP.
Therefore, it is important to know to what connection is being made and what is to be expected of this connection.
This loop initialization may not be noticeable from ONTAP.
ENC_out may be seen on loops connecting to a fabric (FMC for example) if a disk is changed or the loop initializes for any other reason. CRC and ENC_IN are pointing to a SFP and/or ASIC issue.
Statistically, crc_err and enc_out errors together imply a GBIC/SFP problem.
Receiving port uses the same formula to check and compare.
A mathematical formula generates counters at sending port.
This measured ratio is affected by many factors including: signal to noise, distortion, and jitter.
The ratio of how many bits received in error over the number of total bits received is the BER.
The BER is calculated by comparing the transmitted sequence of bits to the received bits and counting the number of errors.
The Bit Error Rate (BER) formula is BER= Nerr/Nbits.
Everything hitting the wire is encoded using 8/10b encoding.
Reinitialization/reboots of the associated Nx-port can also cause these errors.
Minimum compliance with the link bit error rate specification on a link continuously receiving frames would cause approximately one error every 20 minutes.
Words inside of frames are encoded, if this encoding is corrupted or an error is detected, enc_in is generated.
8bit/10bit encoding errors inside frame.
The output displays a message similar to the following:įrames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout
For proper analysis, the stats for the ports should be cleared ( portstatsclear or statsclear) and the switch should be run for some time to see what errors are currently accumulating, if any.
Errors in porterrshow are cumulative since the last time errors were cleared.
0 kommentar(er)
