DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.5 hwBoardInvalid-132614

Trap Buffer Description

The board totally failed. (EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalIndex=[EntPhysicalIndex], EntPhysicalName=[EntPhysicalName], EntityType=[EntityType], EntityTrapFaultID=132614, Reason=The EPLD logic of the board failed.)

The overall function of the board does not take effect.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Alert
Mnemonic Code	hwBoardInvalid
Trap OID	1.3.6.1.4.1.2011.5.25.219.2.2.5
MIB	HUAWEI-ENTITY-TRAP-MIB
Alarm ID	0x0813002e
Alarm Name	hwBoardInvalid
Alarm Type	equipmentAlarm
Raise or Clear	Raise
Match trap	DEVM_1.3.6.1.4.1.2011.5.25.219.2.2.6 hwBoardInvalidResume-132614

Trap Buffer Parameters

Parameter	Description
EntityPhysicalIndex	Indicates the index of the physical entity.
EntPhysicalIndex	Indicates the index of the physical entity.
EntityTrapFaultID	Indicates the error code.
EntPhysicalName	Indicates the name of the entity such as a chassis.
EntityType	Indicates the type of the physical entity. The value can be one of the following: 1: mpu(1) 2: lpu(2) 3: sfu(3) 4: pic(4) 5: cfcard(5) 6: ofc(6) 7: npu(7)
Reason	Indicates the description of the cause of the trap.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.219.1.1	hwEntityPhysicalIndex	-
1.3.6.1.2.1.47.1.1.1.1.7	entPhysicalName	entPhysicalIndex
1.3.6.1.4.1.2011.5.25.219.1.2	hwEntityTrapEntType	-
1.3.6.1.4.1.2011.5.25.219.1.3	hwEntityTrapFaultID	-
1.3.6.1.4.1.2011.5.25.219.1.13	hwEntityTrapReasonDescr	-
1.3.6.1.4.1.2011.5.25.31.1.1.1.1.2	hwEntityOperStatus	entPhysicalIndex

Impact on the System

Services on the board will be affected or even interrupted. This problem must be resolved immediately.

Possible Causes

The EPLD logic of the board failed.

Procedure

1. Go to Step 2 if the faulty board is not the main control board.

2. If the faulty board is registered, run the EPlD upgrade command in the user view: upgrade mpu/lpu/sfu slotid startup firmware. Then, go to Step 4.

3. If the faulty board is not registered, power off and then power on the faulty board.

4. If the faulty board cannot be registered or the fault persists after the board is registered, replace the faulty board.

5. If the alarm persists, collect alarm, log, and configuration information and contact technical support engineers.

6. End.