DEVM/2/hwEntityCheckFail_active

Message

DEVM/2/hwEntityCheckFail_active: Physical entity is detected failed. (BaseTrapSeverity=[BaseTrapSeverity], BaseTrapProbableCause=[BaseTrapProbableCause], BaseTrapEventType=[BaseTrapEventType], EntityPhysicalIndex=[EntityPhysicalIndex], EntPhysicalContainedIn=[EntPhysicalContainedIn], EntPhysicalName=[EntPhysicalName], RelativeResource=[RelativeResource], ReasonDescription=[ReasonDescription])

In VS mode, this log is supported only by the admin VS.

Description

Physical entity is detected failed.

Parameters

Parameter Name	Parameter Meaning
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.
EntityPhysicalIndex	Physical index. The physical index varies with the chassis ID.
EntPhysicalContainedIn	Indicates the parent index.
EntPhysicalName	Indicates the name of the entity such as a chassis.
RelativeResource	Indicates the name of the part related to the trap.
ReasonDescription	Indicates the description of the possible cause.

Possible Causes

Cause 1: Chassis IDs conflicted.
Cause 2: Failed to detect the MPU confliction.
Cause 68142: The two power supply planes have different number of PMs.
Cause 68149: Traffic forwarding on the half chassis of a ccc was disabled.
Cause 68150: Optical fiber lengths of a clc conflicted.
Cause 68151: The SFU in ccc/slot number does not support traffic forwarding in current cascading mode.
Cause 68152: The fabric system is abnormal.
Cause 68159: The board is incompatible with the master mpu.
Cause 68173: The fiber length in 40G chassis is not set.
Cause 68174: The number of tm resources exceeded 90% of the total tm resources.
Cause 68186: The actual lengths of multiple optical fibers connected to the clc are different.
Cause 69500: Fan or power does not match in chassis chassisid.
Cause 69636: MPU slotid%s is failed, the chassis ID conflict.
Cause 69637: MPU is failed, system master conflict.
Cause 69638: The logical position of the optical module area is not activated. Therefore, the area does not support traffic forwarding.
Cause 69639: After you configure the time in which a non-security software package can still be used, an alarm is reported every hour in this time, informing you of the remaining time. After the time expires, no non-security software package can be used.
Cause 69640: Failed to set a secure start flag into the flash chip.
Cause 69641: The management network port receives more than 2000 packets per second for 10 consecutive seconds.
Cause 69642: There are two ICUs in %s.

Procedure

Cause 1: Chassis IDs conflicted.
1. Check alarm information and locate the chassis with a conflicting ID.

2. Run the set [ chassis chassis ] chassis-id chassis-id command to set the ID of the chassis. Run the display chassis-id command to view IDs of all chassis.

3. Check whether the trap is cleared.
- If so, go to Step 5.
- If not, go to Step 4.
4. Collect the trap information, log information, and configuration of the router, and contact technical personnel.

5. End.
Cause 2: Failed to detect the MPU confliction.
1. Check whether the LEDs of corresponding interfaces on the CCCs blink. If the cable between the CCCs is in good connection but the LEDs do not blink, replace the cable and then check whether the trap is cleared.
- If so, go to Step 3.
- If not, go to Step 2.
2. Collect the trap information, log information, and configuration of the router, and contact technical personnel.

3. End.
Cause 68142: The two power supply planes have different number of PMs.
1. Check the number of PMs installed on each power supply plane and install more PMs on the plane with less PMs to ensure that the two planes have the same number of PMs. Then check whether the alarm is cleared.
- If the alarm is cleared, go to Step 3.
- If the alarm persists, go to Step 2.
2. Collect alarm, log, and configuration information, and contact technical support personnel.

3. End.
Cause 68149: Traffic forwarding on the half chassis of a ccc was disabled.
1. Run the undo chassis{ ccc1 | ccc2 } { upper | lower} traffic close command.

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

3. End.
Cause 68150: Optical fiber lengths of a clc conflicted.
1. Check whether the optical fiber length set by the command is the same as the actual length of the optical fiber used on the clc.
- If so, go to step 4.
- If not, go to step 2 or step 3.
2. Change the optical fiber length in the command to be the same as the actual length of the optical fiber on the clc.

3. Replace the optical fiber on the clc with one that has the same length as that set in the command.

4. Replace the optical fibers of variable lengths with ones of the same length.

5. Collect the alarm information, log information, and configuration information, and contact technical support personnel.

6. End.
Cause 68151: The SFU in ccc/slot number does not support traffic forwarding in current cascading mode.
1. Remove the board.

2. Power off the board.

3. Change the cascading mode.

4. Collect the alarm information, log information, and configuration information, and contact technical support personnel.

5. End.
Cause 68152: The fabric system is abnormal.
Collect the alarm information, log information, and configuration information, and contact technical support personnel.
Cause 68159: The board is incompatible with the master mpu.
1. Change the board.

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

3.End.
Cause 68173: The fiber length in 40G chassis is not set.
1.Run the set fiber chassis chassis-id length fiber-length command to configure a correct optical fiber length, and check whether the trap is cleared.
- If the trap is cleared, go to Step 3.
- If the trap is not cleared, go to Step 2.
2. Collect the alarm information, log information, and configuration information, and contact technical support personnel.

3. End.
Cause 68174: The number of tm resources exceeded 90% of the total tm resources.
1. Remove unnecessary interface boards or subcards and clear configuration to check whether the fault is rectified.
- If the fault is rectified, go to Step 3.
- If the fault is not rectified, go to Step 2.
2. Collect the alarm information, log information, and configuration information, and contact technical support personnel.

3. End.
Cause 68186: The actual lengths of multiple optical fibers connected to the clc are different.
1. Check whether the optical fibers connected to the clc have the same length.
- If yes, go to Step 2.
- If not, replace the optical fibers with those having the same length.
2. Run the display fiber-length command to check whether the actual fiber length is consistent with the configured fiber length.
- If yes, go to Step 4.
- If not, go to Step 3.
3. Run the set fiber chassis chassis-id length fiber-length command to configure the optical fiber length to be the same as the actual optical fiber length, or change the actual optical fiber length to be the same as the configured length.

4. Collect trap, log, and configuration information, and contact technical support personnel.

5. End.
Cause 69500: Fan or power does not match in chassis chassisid.
Collect the alarm information, log information, and configuration information, and contact technical support personnel.
Cause 69636: MPU slotid%s is failed, the chassis ID conflict.
1. Check alarm information and locate the chassis with a conflicting ID.

2. Run the set [ chassis chassis ] chassis-id chassis-id command to set the ID of the chassis. Check whether the trap is cleared.
- If so, go to Step 4.
- If not, go to Step 3.
3. Collect trap information, log information, and configuration information, and then contact technical support personnel.

4. End.
Cause 69637: MPU is failed, system master conflict.
Collect the alarm information, log information, and configuration information, and contact technical support personnel.
Cause 69638: The logical position of the optical module area is not activated. Therefore, the area does not support traffic forwarding.
Collect the alarm information, log information, and configuration information, and contact technical support personnel.
Cause 69639: After you configure the time in which a non-security software package can still be used, an alarm is reported every hour in this time, informing you of the remaining time. After the time expires, no non-security software package can be used.
This trap message is informational only, and no action is required.
Cause 69640: Failed to set a secure start flag into the flash chip.
1. Attempt to set the secure start flag again.

2. If the attempt fails, collect trap, log, and configuration information, and contact Huawei technical support engineers.

3. End.
Cause 69641: The management network port receives more than 2000 packets per second for 10 consecutive seconds.
Collect the information about alarms, logs, and configurations, and then contact technical support personnel.
Cause 69642: There are two ICUs in %s.
remove the unused one.