DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid-67661

Trap Buffer Description

Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67661], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=The signal carrying the slot information sent from the MPU to the interface board was abnormal.)

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

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

Services on the interface board will be affected.

Possible Causes

The signal carrying the slot information sent from the MPU to the interface board was abnormal.

Procedure

1. Run the reset slot slot-id command to reset the faulty board and then check whether the board can be normally registered.

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

2. Replace the faulty interface board and 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.