DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.15 hwEntityCheckFail-69636

Trap Buffer Description

Physical entity is detected failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=69636, BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntPhysicalContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=MPU <slotid>%s is failed, the chassis ID conflict.)

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-69636

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

The system automatically resets an MPU. Services will not be affected because the trap is generated only during system startup.

Possible Causes

MPU slotid%s is failed, the chassis ID conflict.

Procedure

1. Check alarm information and locate the chassis with a conflicting ID.

2. Run the set [ chassis chassis ] chassis-id chassis-id command to set the ID of the chassis. Check whether the trap is cleared.

If so, go to Step 4.
If not, go to Step 3.

3. Collect trap information, log information, and configuration information, and then contact technical support personnel.

4. End.