Due to backplane faults, the GSCC board is not running properly and keeps reporting the HARD_BAD alarm. After the subrack is replaced, the alarm clears.
Cause Analysis
When parameter 5 in the HARD_BAD alarm parameters is 0x04, the NMS displays that an Ethernet communication port between boards is faulty. There are three possible causes:
- The GSCC board is faulty.
- The auxiliary interface board is faulty.
- The backplane is faulty.
Procedure
- Remove the standby GSCC board. The HARD_BAD alarm persists. So, the fault should be located on the active GSCC board, auxiliary interface board, or slot 17.
- Replace the active GSCC board in slot 17. The HARD_BAD alarm persists. So, the active GSCC board cannot be faulty.
- Exchange the active GSCC board in slot 17 with the standby GSCC board in slot 18. The standby GSCC board in slot 17 reports the HARD_BAD alarm. So, the fault should be located on the standby GSCC board, auxiliary interface board, or slot 17.
- Replace the standby GSCC board in slot 17. The HARD_BAD persists. So, the standby GSCC board cannot be faulty.
- Replace the auxiliary interface board. The HARD_BAD alarm persists, so the fault does not pertain to the auxiliary interface board. The fault should be located on slot 17.
- Check whether the backplane has bent pins.
- Replace the subrack. The HARD_BAD alarm clears.
No comments:
Post a Comment