ALM-303046917 Some Functions on the Card Were Invalid

Description

ENTITYTRAP/2/BOARDFAIL: OID [OID] Board become failure for some reason.(Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType= [INTEGER], EntityTrapFaultID=[INTEGER], EntityTrapReasonDescr="[OCTET]")

Some functions on the card are invalid.

Attribute

Alarm ID	Alarm Severity	Alarm Type
303046917	Major	equipmentAlarm

Parameters

Name	Meaning
OID	Indicates the MIB object ID of the alarm
Index	Indicates the entity index.
EntityPhysicalIndex	Indicates the physical entity index.
PhysicalName	Indicates the name of the physical entity.
EntityTrapEntType	Indicates the type of the physical entity, such as mpu(1), and lpu(2).
EntityTrapFaultID	Indicates the error code.
EntityTrapReasonDescr	Indicates the description of the alarm cause.

Impact on the System

The card is unavailable or some services are interrupted.

Possible Causes

Error Code	Possible Cause
132643	The Bluetooth function failed.
132642	The Reset button is faulty.
132641	The dual-edge connector is faulty.
132640	The CPU is faulty.
132623	The NP chip is faulty.
132103	The voltage failed.
132620	The power supply is faulty.
132619	The corrosion protection circuit is faulty.
132618	An overall fault occurs on the NP chip.
132149	The bad block rate for the NAND flash exceeds the threshold.
2125827	The temperature sensor is abnormal.
132865	The RTC was abnormal. NOTE: When the RTC is faulty, the system time may be incorrect after the device is restarted. However, services indifferent to system timing are not affected. If an NTP server is available on the network, the system time will be corrected after you enable the NTP client function on the device.
132146	The PSE power supply is faulty.
132121	The current on the USB flash drive exceeds the upper limit.

Procedure (AC device)

Check whether the faulty card is registered successfully and services are running properly.

Run the display device command to check whether the faulty card is registered successfully, and run the display interface command to view the statistics on received and sent packets. According to the statistics, check whether services are running properly.
- If the faulty card is registered successfully and services are running properly, no further action is required.
- If the faulty card is unregistered or services are not running properly, go to step 2.
If the faulty card is a main control board, run the reboot command to reboot the device. Then check whether the device is working properly.
- If the card can be registered successfully and services are running properly, no further action is required.
- If the card cannot be registered or services cannot run properly, the card hardware is faulty. Replace this card.
- If the fault persists, go to step 3.
Contact technical support engineers.

Procedure (Cloud AP device)

Check whether the faulty card is registered successfully and services are running properly.

Run the display interface command to view the statistics on received and sent packets. According to the statistics, check whether services are running properly.
- If the faulty card is registered successfully and services are running properly, no further action is required.
- If the faulty card is unregistered or services are not running properly, go to step 2.
If the faulty card is a main control board, run the reboot command to reboot the device. Then check whether the device is working properly.
- If the card can be registered successfully and services are running properly, no further action is required.
- If the card cannot be registered or services cannot run properly, the card hardware is faulty. Replace this card.
- If the fault persists, go to step 3.
Contact technical support engineers.