The second category shall indicate that the frame content is valid. One category of delimiter shall indicate that the frame is valid from the senders perspective and potentially valid from the receivers perspective. There are three categories of EOF delimiters. The EOF delimiter shall designate the end of the frame content and shall be followed by idles. These errors are in the sum for the LLI errorsīad eof = Frames with bad end-of-frame delimiters: The end-of-frame (EOF) delimiter is an ordered set that immediately follows the CRC. Data frame size is a variable from 0 to 2112. Too long= Frames longer than maximum: The number of frames that are longer than the maximum frame size (36 bytes + data frame size). These errors are in the sum for the LLI errors
Too short = Frames shorter than minimum: The number of frames that are shorter than the minimum frame size (36 bytes + data frame size). Statistically, enc out errors alone imply cable problems, the enc out and crc err in combination implies GBIC/SFP problems. Frames that fail a CRC are noted but not modified and the destination device is responsible for rejecting and/or re-requesting the frame. For the purpose of CRC computation, the bit of the word-aligned four-byte field that corresponds to the first bit transmitted is the highest order bit. The CRC field shall be aligned on a word boundary. The CRC field shall be calculated on the Frame header and Data Field prior to encoding for transmission and after decoding upon reception. SOF (= Start-Of-Frame) and EOF (= End-Of-Frame) delimiters shall not be included in the CRC verification. The Cyclic Redundancy Check (CRC) is a four-byte field that shall immediately follow the Data Field and shall be used to verify the data integrity of the frame header and Data Field.
These errors are in the sum for the LLI errors.Ĭrcerr = Frames with Cyclic Redundancy Check errors: The number of frames that have failed a Cyclic Redundancy Check. Reinitialization and reboots of associated Nx-port can also cause these errors. Minimum compliance with the link-bit error rate specification on a link continuously receiving frames would allow approximately one error every 20 minutes for 1 Gb/s. This counter is generally a zero value, although occasional errors may occur on a normal link and give a nonzero result. This number is a statistic that provides a baseline for the error counters.Įnc in = Encoding errors inside frames: The number of 8b/10b encoding errors that have occurred inside frame boundaries. frames rx= Frames received: The number of frames transmitted by the port. This number is a statistic that provides a baseline for the error counters. The following document interprets and explains the porterrshow output (port errors) of Brocade SAN switches and possible causes of the errors.ĭetails When looked into the content of a Brocade supportShow or enter the standalone portErrShow command via a Telnet session to the switch, the user will get a similar table like the following on the screen:įrames enc crc too too bad enc disc link loss loss frjt fbsy
0 kommentar(er)
