DEVM_1.3.6.1.4.1.2011.5.25.129.2.1.7 hwEntityCommunicateError-67072

Trap Buffer Description

Communication-channel is detected failed. (EntityPhysicalIndex=[ULONG], BaseTrapSeverity=4, BaseTrapProbableCause=67072, BaseTrapEventType=5, EntPhysicalContainedIn=[ULONG], EntPhysicalName=[STRING], RelativeResource=[STRING], ReasonDescription=Between mbus <slotID> and MPU, the communication channel of ARQ channels is failed)

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

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

1. When the MPUs work in 1+1 backup mode, the master and slave switchover will be triggered if the fault occurs on the master MPU.

2. When the MPUs work in 1+1 backup mode, and the fault occurs on the slave MPU, the master and slave switchover will fail before the fault is rectified.

3. When only one MPU is used, all the MonitorBus objects will be unavailable, the temperature and voltage monitoring will fail, and the Electrically Erasable Programmable Read Only Memory (EEPROM) cannot be operated.

Possible Causes

Cause 1: The ARQ communication channel of the MPU/SRU was faulty.

Cause 2: The MPU/SRU and the pinch board on it cannot communicate with each other.

Procedure

1. Check information about the device and check whether the environment power module works normally.

Run the display power command to check the type of the power module.

Run the display device command to check the status of the power module.

Then, check whether the power module is abnormal or the type of the power module is unknown.

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

2. Replace the power module.Then, check whether the trap persists.

If so, go to Step 3.
If not, go to Step 7.

3. Check whether the output power of the power module satisfies the requirements. Run the display power slot command to check the output power of the power module.

Check whether the output power of the power module can meet the requirements.

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

4. Change the input power of the power module to meet the working requirements. Then, check whether the trap persists after the input power of the power module satisfies the requirements.

If so, go to Step 6.
If not, go to Step 7.

5. Replace the MPU/SRU and check whether the trap is cleared.

If so, go to Step 7.
If not, go to Step 6.

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

7. End.