DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.9 hwEntityInvalid-67848

Trap Buffer Description

Physical entity failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[67848], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=The channel between ICUs became faulty.)

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

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

The channel between ICUs became faulty.

Procedure

1. View the EntPhysicalName field in alarm information. Check whether the ICUs are connected through an inter-chassis cable. If no, connect the cable and check whether the alarm is cleared. If the alarm persists, perform step 3. If the boards are connected, perform step 2.

2. Check whether the cables are correctly connected and the LEDs at the two ends blink. If the LEDs do not blink, replace the cables and optical module or optical/electrical module (if any). Then check whether the alarm is cleared. If the alarm persists, perform step 3.

3. Replace the board and check whether the alarm is cleared. If the alarm persists, go to step 4.

4. Collect log files and contact Huawei technical support personnel.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >