ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.2.3 hwBoardFail

Description

ENTITYTRAP/2/BOARDFAIL: OID [oid] Board fails. (Index=[INTEGER], EntityPhysicalIndex=[INTEGER], PhysicalName="[OCTET]", EntityTrapEntType=[INTEGER], EntityTrapFaultID=[INTEGER], EntityTrapReasonDescr="[OCTET]")

Some functions on the device do not work.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.219.2.2.3	Major	equipmentAlarm(5)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
Index	Indicates the index of the alarm.
EntityPhysicalIndex	Indicates the index of a physical entity.
PhysicalName	Indicates the name of a physical entity.
EntityTrapEntType	Indicates the entity type.
EntityTrapFaultID	Indicates the error code.
EntityTrapReasonDescr	Indicates the description of the alarm cause.

Impact on the System

See the description in the procedure.

Possible Causes

See the description in the procedure.

Procedure

Rectify the fault based on the error code.

Error Code	Possible Causes and Impact on the System	Procedure
132096	The power module that provides power for the switch was faulty.	Collect alarm information and configuration information, and then contact technical support personnel.
132105	The sensor was faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132107	The PHY chip on the device was faulty.	Use other ports that can work normally or replace the card.
132121	The USB controller was faulty.	If there is no storage device on the USB port, services will not be affected. This alarm message is informational only, and no action is required. If you need to use the USB port, choose another USB port on the device or a USB port on another device.
132124	The I2C bus was faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132127	The clock module on the card was faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132128	The Phase-Locked Loop (PLL) was faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132131	The Digital Signal Processor (DSP) was faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132137	Chips (including CPLD, RTC, EEPROM, and temperature control chip) were faulty.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132146	The PoE power supply on the device was faulty.	Replace the faulty PoE power supply and check whether the corresponding clear alarm is displayed. If not, go to 2. Replace the faulty PoE DIMM and check whether the corresponding clear alarm is displayed. If not, go to 3. Collect alarm information and configuration information, and then contact technical support personnel.
132147	The indicator was faulty.	Collect alarm information and configuration information, and then contact technical support personnel.
132176	The PHY chip remains at a low temperature.	Check whether the alarm with the error code 132128 is displayed. If not, that is, no PLI failure occurs, no action is required. If so, the PLI is out of lock because the PHY chip remains at a low temperature, and the device will restart. No action is required.
132185	The internal IIC module of the device was faulty.	Wait for a period to check whether the fault is rectified. If not, replace the faulty component or the card.
132199	A fault occurred on the internal channel of the MCU component on the PoE device.	Wait for a period to check whether the fault is rectified. If not, replace the faulty component or the card.
132200	The device silicon crystal was affected by the external environment, resulting in an uncorrectable error. An error that cannot be rectified by ECC (that is, multiple bit ECC errors) occurred on the storage units (memory and flash memory) of the device. If an instruction error or a file system error occurred, the device cannot operate properly.	Wait for a period to check whether the fault is rectified. If not, replace the faulty component or the card.
132201	A CPU DDR fault occurred and the DDR multi-bit error occurred 60 times on the device within one hour. When the DDR multi-bit error occurred 100 times on the device within one hour, the device is restarted and the restart reason is recorded.	Wait for a period to check whether the fault is rectified. If not, replace the faulty component or the card.
132212	An internal error occurred in the CPU cache. The device detected a multi-bit error in the CPU cache and will restart.	After the fault occurs, the device restarts automatically. If this alarm is displayed multiple times, replace the faulty component or device.
132217	Some uplink optical interfaces become unavailable. GPON optical modules and other optical modules are installed on these uplink optical interfaces. Two or more GPON optical modules are installed on these uplink optical interfaces.	Determine which uplink optical interfaces need to be used based on the networking. Remove optical modules from the uplink optical interfaces that do not need to be used.
132218	The chip of the 0.9 V voltage is abnormal.	Restart the device. If the alarm persists, replace the device in the specified slot.
132223	The read and write operations are frequently performed in the partition, damaging storage components. The bad block rate of the SystemMain (nsysmain) partition exceeded the alarm threshold 2%, so the available storage space is low.	Restart the device. Ten seconds later, check whether the alarm persists. If so, go to 2. Run the format flash: command to format the flash. Ten seconds later, check whether the alarm persists. If so, go to 3. Contact technical support personnel to replace the device or flash component.
132224	The read and write operations are frequently performed in the partition, damaging storage components. The bad block rate of the SystemBack (nsysbak) partition exceeded the alarm threshold 2%, so the available storage space is low.	Restart the device. Ten seconds later, check whether the alarm persists. If so, go to 2. Run the format flash: command to format the flash. Ten seconds later, check whether the alarm persists. If so, go to 3. Contact technical support personnel to replace the device or flash component.
132225	The read and write operations are frequently performed in the partition, damaging storage components. The bad block rate of the SystemData (nsysdata) partition exceeded the alarm threshold 2%, so the available storage space is low.	Restart the device. Ten seconds later, check whether the alarm persists. If so, go to 2. Run the format flash: command to format the flash. Ten seconds later, check whether the alarm persists. If so, go to 3. Contact technical support personnel to replace the device or flash component.
132226	The read and write operations are frequently performed in the partition, damaging storage components. The bad block rate of the SystemFile (NVRP or nand root file system) partition exceeded the alarm threshold 2%, so the available storage space is low.	Restart the device. Ten seconds later, check whether the alarm persists. If so, go to 2. Run the format flash: command to format the flash. Ten seconds later, check whether the alarm persists. If so, go to 3. Contact technical support personnel to replace the device or flash component.
132227	The read and write operations are frequently performed in the partition, damaging storage components. The bad block rate of the NVRP partition exceeded the threshold 1.5%, so the available storage space is low.	Restart the device. Ten seconds later, check whether the alarm persists. If so, go to 2. Run the format flash: command to format the flash. Ten seconds later, check whether the alarm persists. If so, go to 3. Contact technical support personnel to replace the device or flash component.
132228	The power consumed by the connected powered device is too high, the total PoE power and the DC output power of the S5720I-10X-PWH-SI-AC exceeds the total power, the device automatically disables the DC power supply function of the 12 V line 1.	Reduce the power consumed by the powered device.
132229	The power consumed by the connected powered device is too high, the total PoE power and the DC output power of the S5720I-10X-PWH-SI-AC exceeds the total power, the device automatically disables the DC power supply function of the 12 V line 2.	Reduce the power consumed by the powered device.
132230	The power consumed by the connected powered device is too high, the total PoE power and the DC output power of the S5720I-10X-PWH-SI-AC exceeds the total power, the device automatically disables the DC power supply function of the 24 V line.	Reduce the power consumed by the powered device.
132231	The power consumed by the connected powered device is too high, the 12 V DC output power of the S5720I-10X-PWH-SI-AC exceeds the alarm threshold 104 W for the 12 V DC output power, the device automatically disables the DC power supply function of the 12 V line.	Reduce the power consumed by the powered device.
132232	The power consumed by the connected powered device is too high, the 24 V DC output power of the S5720I-10X-PWH-SI-AC exceeds the alarm threshold 78 W for the 24 V DC output power, the device automatically disables the DC power supply function of the 24 V line.	Reduce the power consumed by the powered device.
132233	A CPU internal module failed.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132625	The chip does not work normally.	Restart the faulty device and check whether the corresponding clear alarm is displayed. If not, replace the faulty device.
132239	The NOR flash memory is erased frequently. That is, the NOR flash memory is erased 100 times within 24 hours.	Collect alarm information and configuration information, and then contact technical support personnel.
132240	The storage utilization exceeded 80% . This may be because there are many log files on the switch or unnecessary .cc files were not deleted on the switch.	Three methods are available to solve this problem: Run the reset logbuffer command in the user view to delete unnecessary log information from the log buffer. Run the delete /unreserved command in the user view to delete the specified .cc file from the memory. Run the reset recycle-bin command in the user view to delete the files in the specified directory from the recycle bin. NOTE: If the storage utilization increases to 85%, the system automatically clears the recycle bin and deletes unused system software packages, patches, or log files.
132249	The NOR flash memory has reached 90% of its life cycle.	Collect alarm information and configuration information, and then contact technical support personnel.
132281	Card burnt due to high PoE power.	Collect alarm information and configuration information, and then contact technical support personnel.
132282	The specified interface receives preamble error packets.	Run the port serdes-mode command to configure the working Serdes mode of the MultiGE interface.
132283	The specified interface cannot go up due to insufficient frequency.	Check whether the device connected to the interface specified in the alarm can be connected to another interface on the switch. If so, go to step 2. If not, go to step 3. Connect the device to another interface on the switch, and check whether the alarm persists. If so, repeat step 2. If not, no further action is required. Run the port serdes-mode command again to configure the Serdes mode in which the MultiGE interface works. Ensure that the Serdes mode in which the MultiGE interface specified in the alarm should work is specified in the command.

Related Information

Entitytrap_1.3.6.1.4.1.2011.5.25.219.2.2.4 hwBoardFailResume