DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.7 hwEntityCommunicateError-67076

Trap Buffer Description

Communication-channel is detected failed. (EntityPhysicalIndex=[ULONG], BaseTrapSeverity=3, BaseTrapProbableCause=67076, BaseTrapEventType=5, EntPhysicalContainedIn=[ULONG], EntPhysicalName=[STRING], RelativeResource=[STRING], ReasonDescription=Slot 24 is failed, Between slave chassis with master chassis,The communication channel of BITS is abnoraml)

Communication-channel is detected 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

hwEntityCommunicateError

Trap OID

1.3.6.1.4.1.2011.5.25.129.2.1.7

MIB

HUAWEI-BASE-TRAP-MIB

Alarm ID

0x08130099

Alarm Name

hwEntityCommunicateError

Alarm Type

equipmentAlarm

Raise or Clear

Raise

Match trap

DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.8 hwEntityCommunicateResume-67076

Trap Buffer Parameters

Parameter Description

EntityPhysicalIndex

Indicates the physical index.

BaseTrapSeverity

Indicates the severity level of the trap reported to the NMS.

BaseTrapProbableCause

Indicates the possible cause of the trap.

BaseTrapEventType

Indicates the trap type.

EntPhysicalContainedIn

Indicates the parent index.

EntPhysicalName

Indicates the name of the entity such as a chassis.

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

The master chassis and the slave chassis cannot trace the same clock source.

Possible Causes

The clock channels between the master chassis and the slave chassis were faulty (the master chassis detected that the input clock was faulty).

Procedure

1. Replace the clock cables and check whether the trap is cleared.

  • If so, go to Step 3.
  • If not, go to Step 2.

2. Collect alarm information, log information and configuration information, and then contact technical support personnel.

3. End.

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