DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid-67771

Trap Buffer Description

Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67771], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=Cause 1:The EPLD logic file was faulty. Cause 2: The EPLD hardware was faulty. Cause 3: The EPLD version is different from that of the system.)

Physical entity failed.

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	hwEntityInvalid
Trap OID	1.3.6.1.4.1.2011.5.25.129.2.1.9
MIB	HUAWEI-BASE-TRAP-MIB
Alarm ID	0x08130055
Alarm Name	hwEntityInvalid
Alarm Type	equipmentAlarm
Raise or Clear	Raise
Match trap	DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.10 hwEntityResume-67771

Trap Buffer Parameters

Parameter	Description
BaseTrapSeverity	To describe the level of trap.
ProbableCause	To describe the probable cause of trap.
BaseTrapEventType	To describe the type of trap.
EntityPhysicalIndex	The index of the physical entity.
EntContainedIn	The value of entPhysicalIndex for the physical entity.
EntPhysicalName	The textual name of the physical entity.
RelativeResource	This object may contain a key word to indicate the relative resource of an entity.
ReasonDescription	To describe the reason of trap in DisplayString style.

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

1. Board registration may fail to be properly started.

2. The board may fail to be reset.

3. The board may have potential risks.

Possible Causes

Cause 1:The EPLD logic file was faulty.

Cause 2: The EPLD hardware was faulty.

Cause 3: The EPLD version is different from that of the system.

Procedure

1. Run the corresponding command to upgrade the board EPLD by board type in the diagnostic view. After the upgrade is finished and the board is registered, check whether the alarm is cleared.

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

2. Replace the board and then check whether the alarm is cleared.

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

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

4. End.