Updated on 2024-01-25 GMT+08:00

ALM-135463100 hwIfMonitorCrcErrorRising

Description

The CRC error is rising. (hwIfMonitorIndex=[EntityPhysicalIndex], hwIfMonitorCrcErrorStatistics=[hwIfMonitorCrcErrorStatistics], hwIfMonitorCrcErrorThreshold=[hwIfMonitorCrcErrorThreshold], hwIfMonitorCrcErrorInterval=[hwIfMonitorCrcErrorInterval], EntPhysicalName=[EntPhysicalName], hwIfMonitorAllStatistics=[hwIfMonitorAllStatistics])

The number of CRC error packets received by the interface in a specified period exceeded the upper threshold.

Attribute

AlarmID

Alarm OID

Alarm Severity

Alarm Type

135463100

1.3.6.1.4.1.2011.5.25.41.4.1

Critical

Processing error alarm

Parameters

Name

Meaning

OID

Indicates the MIB object ID of the alarm.

EntityPhysicalIndex

Entity index.

hwIfMonitorCrcErrorStatistics

Real-time statistics of CRC error packets

hwIfMonitorCrcErrorThreshold

Upper threshold for the number of CRC error packets

hwIfMonitorCrcErrorInterval

Configured statistics collection interval

EntPhysicalName

Entity name

hwIfMonitorAllStatistics

Number of packets in real-time statistics

Impact on the System

An interface receives a large number of CRC error packets, which may cause the interface to transit to the Error-Down state.

Possible Causes

The interface receives excessive CRC error packets whose lengths are greater than or equal to 64 bytes in a specified period of time.

Procedure

1. Run the display this command in the interface view to check whether the alarm threshold for error packets is too low.Determine the alarm threshold based on service requirements.

  • If so, go to Step 2.
  • If no, go to Step 3.

2. Run the trap-threshold crc-statistics command in the interface view to set a larger alarm threshold for error packets. Then check whether the alarm is cleared.

  • If yes, no further action is required.
  • If no, go to Step 3.

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

Related Information

None.