Professional Documents
Culture Documents
Hard Bad
Hard Bad
HARD_BAD
Description
Hardware failure. This alarm is generated when the system detects a hardware failure.
Attribute
Parameters
When you view an alarm on the network management system, select the alarm. In the Alarm Details field display the
related parameters of the alarm. The alarm parameters are in the following format: Alarm Parameters (hex):
parameter1 parameter2...parameterN, for example, Alarm Parameters (hex): 0x01 0x08. For details about each
parameter, refer to the following table.
Parameter Description
Parameter For packet service processing boards: Indicates the failure chip.
1 For other boards,
0x01: The power supply module is abnormal.
0x02: The board is not properly installed (the board is not in good contact with the
backplane, for example, the board is not secured).
0x03: 38M system clock 1 is abnormal.
0x04: 38M system clock 2 is abnormal.
0x05: The 2M clock source is abnormal.
0x06: The digital phase-locked loop (PLL) is abnormal.
0x07: The 38M service clock is lost.
0x08: The bus is abnormal.
0x09: The standby board under TPS protection is abnormal.
0x0a: The active crystal oscillator of the clock stops.
0x0b: The frequency deviation of the crystal oscillator is excessively large.
0x0c: The standby crystal oscillator of the clock stops.
0x0d: The CPU/DSP/coprocessor fails.
0x0e: The memory component fails.
0x0f: The component of the programmable logic device fails.
0x10: The SDH component fails.
0x11: The data communication component fails.
0x12: The clock component fails.
0x13: The interface component fails.
0x14: The power component fails.
0x15: Other faults occur.
0x16: The simulated PLL is abnormal.
0x17: The 32M clock is invalid.
0x18: The 66M clock is invalid.
0x19: The 25M clock is invalid.
0x1a: The loop of the cross-connect chip fails.
0x1b: The 8k online signal is pulled down.
0x1c: The chip of the probe laser fails.
0x1d: The chip of the loading laser fails.
0x1e: The clock of the DSP driver chip is lost.
0x1f: The output clock of the DSP is lost.
0x20: The RTM module is offline.
0x21: A chip fails.
0x22: 2M system frame header 1 fails.
0x23: 2M system frame header 2 fails.
0x24: The self-check fails.
0x25: The self-check of the PHY chip fails.
https://172.1.234.11/hedex/hdx.do?fe=2000&lib=OMC&p=h&id=help_alarmreference_wdmalarm_ap_alm_proc_hard_bad 1/2
3/17/2020 HARD_BAD
Parameters For packet service processing boards: Indicates the Failure type.
2 and 3 For other boards,
When parameter 1 is 0x08, bus A is abnormal if parameter 2 is 0x01 and bus B is abnormal
if parameter 2 is 0x02. Parameter 3 is 0xff.
When parameter 1 is 0x06, 0x0d, 0x0e, 0x0f, 0x12, 0x13, 0x14, 0x16, 0x19, or 0x21,
parameters 2 and 3 have different values, which indicate different component, module, or
chip faults.
When parameter 1 is 0x15, a fault occurs on other components of the local board, on other
boards, or on other components of other boards.
When parameter 1 is of another value, parameters 2 and 3 are fixed at 0xff.
The alarm affects the normal operating of the board and affects services.
Possible Causes
Procedure
1. Check whether the NE power supplies are normal. If they are abnormal, apply new power
supplies to the NE.
Cause 2: The board is not connected to the backplane properly or the board is faulty.
1. Remove and re-insert the system control board. Check whether the alarm is cleared.
2. If the alarm persists, replace the board. For details, see "Replace the board.".
Related Information
Related Cases:
MC-A143 The Service Alarm Indicator on an OTU Board Is Still Red After the HARD_ERR and
HARD_BAD Alarms Are Suppressed
https://172.1.234.11/hedex/hdx.do?fe=2000&lib=OMC&p=h&id=help_alarmreference_wdmalarm_ap_alm_proc_hard_bad 2/2