Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67594], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=Cause1:A PMU was not detected. A PMU was removed or insecurely inserted. Cause2:The power supply module was not properly installed.The power supply module is absent.)
Physical entity failed.
In VS mode, this trap is supported only by the admin VS.
| 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 |
| 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 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 |
- |
1. A PMU was not detected.
Power module monitoring is affected, and newly inserted boards may fail to be properly powered on.
2. The power module was not properly installed.
The power supply failure may lead to power supply insufficiency, which may cause many issues and even board resetting due to loss of heartbeat packets. This indirectly affects services, and therefore this problem needs to be solved.
1. Check whether the power module is inserted completely. If the power module is in position, remove and insert the power module. Then, check whether the alarm is cleared.
3. Replace the power module and check whether the alarm is cleared.
4. Collect trap, log, and configuration information, and contact technical support.
5. End.