DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid-67851

Trap Buffer Description

Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67851], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=A loop is formed between ICU(s), either because two connections are established between ICUs or two ports of the same ICU are interconnected.)

The control channel between physical entities is faulty.

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_S
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-67851

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 which 'contains' this 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. If dual MPUs are used, no services are affected but reliability is degraded.

2. If a single MPU is deployed, the entire chassis is restarted and all services on the chassis are interrupted.

Possible Causes

A loop is formed between ICU(s), either because two connections are established between ICUs or two ports of the same ICU are interconnected.

Procedure

1. View the EntPhysicalName field in alarm information. Check which two interfaces form a ring.

2. Remove the cables of the corresponding interfaces. Note that the alarm generated when the device is started with a ring will not be cleared after the ring is broken. You must run a command to clear the alarm or restart the device.

3. Connect the cables as specified.