Cause why the alarm indicator of the OTU board is red even after the HARD_ERR alarm is suppressed

17

Question:
An OTU board on an OSN 6800 NE reports a HARD_ERR or HARD_BAD alarm. After the alarm is suppressed on the T2000, the board indicator on the T2000 is still red. When other alarms are suppressed and there is no additional alarm on the board, the board indicator is green.
Analysis:
The HARD_ERR and HARD_BAD alarms are at the hardware maintenance level. In general, the alarms indicate board hardware faults and the boards need to be replaced. Therefore, the alarm indicator is still on even when the HARD_ERR and HARD_BAD alarms are suppressed to instruct onsite engineers to replace the boards.
Root cause:
None
Answer:
The OSN 6800 is designed in this manner to instruct onsite engineers to replace faulty boards.

Other related questions:
Indication of the red alarm indicator on the Metro 1000
If the alarm indicator on the Metro 1000 is steady red, a critical alarm is generated. You need to check it on the NMS.

Why is the RUN indicator red
The device temperature exceeds the temperature alarm threshold or the fan is faulty. The PoE-support switches have a PWR indicator. If the PWR indicator is red, power supply is faulty. NOTE: Run the display environment command to view the temperature alarm threshold and the current temperature. Run the display fan verbose command to view the fan operating status. Run the display device command to view the power supply status.

Meaning of the alarm indicator on a board
The alarm indicator on the front panel of the board indicates the running status and alarm status of the board.

Problem and solution when a BBU fault alarm is reported and the alarm indicator is red
You can perform the following operations when a BBU fault alarm is reported and the alarm indicator is red: Check the SES log and search keyword invalid OnlineTest (the online BBU test fails). If the keyword exists, verify the BBU type in the SES log. If the product name of BBU is HSCB1-62, the BBUs are BYD BBUs which may cause the problem. Replace BYD BBUs with SCUD BBUs (pay attention to the change during replacement).

Board-side status after alarm suppression is enabled on an OSN 6800 NE
Question: There is no other alarm except R_LOS on an NS2 board on an OSN 6800 NE. Does the running status indicator of the board turn red or green if the R_LOS alarm is suppressed on the NMS? Does the indicator on the system control board turn red or green? Does the indicator on the top of the cabinet turn red or green? Analysis: None Root cause: None Answer: Generally, an NE on which alarm suppression is enabled does not monitor related alarms. The suppressed alarms are not reported on either the U2000 or NE. The indicator status, however, varies according to NE types. The OSN 6800 uses the alm-set-monevent command to configure alarm suppression on a board, and the indicator on the board and the indicator on the system control board turn green after alarm suppression is enabled. The indicator on the top of the cabinet reflects alarms of the system control board and therefore is green. Suggestion and conclusion: When alarm suppression is enabled on a board on an NG SDH NE and the NE actually still has alarms, the SRV indicator on the board is red. When alarm suppression is enabled on a board on a Metro 2500+ NE and the board has an alarm, the indicator is green.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top