ENTITYEXTTRAP_1.3.6.1.4.1.2011.5.25.31.2.2.12 hwEntityRuntPacketCheckNotify

Description

ENTITYEXTTRAP/3/PKTCHECKERR: OID [oid] Recovery of runt packet has been detected for more than 5000 times. (SlotID=[S TRING], UnitID=[INTEGER], PortID=[STRING])

The system has experienced more than 5000 fault recoveries after receiving Runt packets (undersized packets passing CRC checks).

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.31.2.2.12	Minor	communicationsAlarm(2)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
SlotID	Indicates a slot ID.
UnitID	Indicates a chip ID.
PortID	Indicates a physical port ID on the chip.

Impact on the System

Service forwarding on an interface may be abnormal after the interface receives undersized Runt packets.

Possible Causes

A switch automatically rectifies the fault after receiving Runt packets. The faulty recovery process will cause short service interruption. If such fault recoveries are performed frequently, this alarm is generated.

Procedure

Check the link status on the interface. If the link status is abnormal, replace the network cable or optical fibers on the interface, and then run the display interface interface-type [ interface-number ] command to check Runt packet statistics on the interface. If the Runts field shows that the interface still receives Runt packets, go to step 2.
Check whether any upstream device is sending Runt packets. If such a device is found, analyze the reason why this device sends Runt packets and rectify the fault. If no upstream device is sending Runt packets, go to step 3.
Collect alarm information and configuration information, and then contact technical support personnel.