DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.15 hwEntityCheckFail-68142

Trap Buffer Description

Physical is detected failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=68142, BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=Power_BackPlane is failed, the number of pm on two plane is different)

Physical entity is detected failed.

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

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwEntityCheckFail
Trap OID	1.3.6.1.4.1.2011.5.25.129.2.1.15
MIB	HUAWEI-BASE-TRAP-MIB
Alarm ID	0x0813005d
Alarm Name	hwEntityCheckFail
Alarm Type	equipmentAlarm
Raise or Clear	Raise
Match trap	DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.16 hwEntityCheckResume-68142

Trap Buffer Parameters

Parameter	Description
BaseTrapSeverity	indicates the severity level of the trap reported to the NMS.
BaseTrapProbableCause	Indicates the possible cause of the trap.
BaseTrapEventType	Indicates the trap type.
EntityPhysicalIndex	Physical index. The physical index varies with the chassis ID.
EntPhysicalContainedIn	Indicates the parent index.
EntPhysicalName	Indicates the name of the entity such as a chassis.
RelativeResource	Indicates the name of the part related to the trap.
ReasonDescription	Indicates the description of the possible cause.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.129.1.1	hwBaseTrapSeverity	-
1.3.6.1.4.1.2011.5.25.129.1.2	hwBaseTrapProbableCause	-
1.3.6.1.4.1.2011.5.25.129.1.3	hwBaseTrapEventType	-
1.3.6.1.2.1.47.1.1.1.1.4	entPhysicalContainedIn	entPhysicalIndex
1.3.6.1.2.1.47.1.1.1.1.7	entPhysicalName	entPhysicalIndex
1.3.6.1.4.1.2011.5.25.129.1.4	hwBaseTrapRelativeResource	-
1.3.6.1.4.1.2011.5.25.129.1.5	hwBaseTrapReasonDescr	-

Impact on the System

Services will not be affected.

Possible Causes

The two power supply planes have different number of PMs.

Procedure

1. Check the number of PMs installed on each power supply plane and install more PMs on the plane with less PMs to ensure that the two planes have the same number of PMs. Then check whether the alarm is cleared.

If the alarm is cleared, go to Step 3.
If the alarm persists, go to Step 2.

2. Collect alarm, log, and configuration information, and contact technical support personnel.

3. End.