DEVM/3/PHY_ERROR_PACKET

Message

DEVM/3/PHY_ERROR_PACKET: [STRING1] detected abnormal packets. ([STRING2])

Description

Packet loss occurred on the physical interface. When the number of upstream or downstream error packets exceeds the threshold, the log is recorded every 15 minutes until the alarm is cleared. The log records only new error packets that are lost within 15 minutes.

Parameters

Parameter Name	Parameter Meaning
STRING1	Interface name.
STRING2	Name and number of error packets on an interface. The value varies according to the interface type. Type of error packets received on an Ethernet interface: Overrun InRangeLength LongPacket Alignment Jabber Fragment Undersized Frame Type of error packets sent by an Ethernet interface: Overflow Underrun System Lost Type of error packets received on the WAN interface: Overrun InRangeLength LongPacket shortpacket Jabber Fragment Type of error packets sent by the WAN interface: Overrun System

Parameter Name

Parameter Meaning

STRING1

Interface name.

STRING2

Name and number of error packets on an interface. The value varies according to the interface type.

Type of error packets received on an Ethernet interface:

Overrun
InRangeLength
LongPacket
Alignment
Jabber
Fragment
Undersized Frame

Type of error packets sent by an Ethernet interface:

Overflow
Underrun
System
Lost

Type of error packets received on the WAN interface:

Overrun
InRangeLength
LongPacket
shortpacket
Jabber
Fragment

Type of error packets sent by the WAN interface:

Overrun
System

Possible Causes

Cause 1: The traffic packet is invalid. For example, the maximum packet length received by the interface is 9600 bytes, but the packet length in the peer traffic is greater than 9600 bytes. In this case, the interface reports the LongPacket statistics log.

Cause 2: The CRC encapsulation of traffic packets is different from that of the device. For example, the packets received by the device do not carry the CRC byte actually but the device removes the CRC byte by default, and the packet length is greater than the maximum length of the received packet on the interface. In this case, the interface reports Jabber statistics logs.

Procedure

1. Run the display this interface command in the interface view to check whether the packet statistics displayed in the interface log are not 0.

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

2. Check whether the physical link is normal and collect the check result.

If the interface is an electrical interface, check whether the network cable is normal.
If the interface is an optical interface, run the display this interface command to check whether the receive optical power of the optical module is within the normal range.
Check whether the configurations on both ends of the interface are consistent.

3. Collect trap, log, and configuration information and contact technical support.

4. End.