Method used to query bit errors based on logs

You can query bit errors based on logs as follows:
If you cannot log in to a remote device, collect logs and analyze them.
1. Bit error of a SAS port
Analyze the message log.
a. Determine the failure time based on the Event.txt log.
b. Query the message log that corresponds to the failure time and search keyword bit err overflow disable.
Possible Cause
A cascading SAS cable is insecurely connected.
A cascading SAS cable is contaminated.
A cascading SAS cable is damaged.
Troubleshooting
a. Check events. If the cascading SAS cable has been removed and inserted before the failure, the cable may be insecurely connected.
b. Remove and insert the cable to check whether more bit errors are displayed. If no more bit error is displayed, the previous bit error is caused by insecure connection. If bit errors continue to display, replace the cascading SAS cable.
c. If spare cascading SAS cable is available on the site, replace the faulty cable. Otherwise, apply for a spare cable.
2. Bit error of a Fibre Channel port
The FC loop feature may lead to multiple possible bit errors. To analyze the spreading status of Fibre Channel bit errors, you must confirm the networking mode and the spreading direction of the bit error based on the SES log. During fast locating, you only need to pay attention to SES logs.
Keywords: HD
Format of the bit error log: HD: [Port ID:Number of LCV bit errors:Number of CRC bit errors]
a. Bit errors of a disk
b. Bit errors of a link
Possible Cause
Connection of Fibre Channel cables
Optical fiber fault
Optical module fault
Troubleshooting
Remove and reinsert the optical fiber. If no more bit error is displayed, the fault is caused by insecure connection.
Replace the optical fiber. If no more bit error is displayed, the fault is caused by the optical fiber failure.
Replace the downstream optical port. If no more bit error is displayed, the fault is caused by the downstream optical port failure.
Replace the upstream optical port. If no more bit error is displayed, the fault is caused by the upstream optical port failure.

Scroll to top