DEVM_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising

Trap Buffer Description

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

The CRC error is rising.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Alert
Mnemonic Code	hwIfMonitorCrcErrorRising
Trap OID	1.3.6.1.4.1.2011.5.25.41.4.1
MIB	HUAWEI-IF-EXT-MIB
Alarm ID	0x081300bc
Alarm Name	hwIfMonitorCrcErrorRising
Alarm Type	processingErrorAlarm
Raise or Clear	Raise
Match trap	DEVM_1.3.6.1.4.1.2011.5.25.41.4.2 hwIfMonitorCrcErrorResume

Trap Buffer Parameters

Parameter	Description
hwIfMonitorIndex	Index of physical port.
hwIfMonitorCrcErrorStatistics	CRC error statistics value.
hwIfMonitorCrcErrorThreshold	CRC error alarm threshold.
hwIfMonitorCrcErrorInterval	CRC error alarm interval time(unit is second),default value is 10s and 0 is an invalid value.
hwIfMonitorName	Name of physical port.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.41.1.7.1.1.2	hwIfMonitorCrcErrorStatistics	hwIfMonitorIndex
1.3.6.1.4.1.2011.5.25.41.1.7.1.1.3	hwIfMonitorCrcErrorThreshold	hwIfMonitorIndex
1.3.6.1.4.1.2011.5.25.41.1.7.1.1.4	hwIfMonitorCrcErrorInterval	hwIfMonitorIndex
1.3.6.1.4.1.2011.5.25.41.1.7.1.1.19	hwIfMonitorName	hwIfMonitorIndex

Impact on the System

Some service data on the interface where the alarm was generated will be lost.

Possible Causes

Cause 1: Transmission distances of optical modules on two directly connected devices were inconsistent with actual transmission distances. As a result, the input optical power of the devices was either too high or too low, causing error codes or packets over the link.

Cause 2: The connector or extension component (such as a flange or concentrator) on the direct cable or link was not connected securely, causing error codes or packets over the link.

Cause 3: The direct optical fiber or cable was not connected securely with devices on both ends, causing error codes or packets over the link.

Cause 4: The direct optical module or power module was not connected securely with devices on both ends, causing error codes or packets over the link.

Cause 5: The transmission network was faulty, causing routers to receive error codes or packets.

Cause 6: The connector or extension component (such as a flange or concentrator) on the direct cable or link aged, causing error codes or packets over the link.

Cause 7: The configurations of interconnected physical layer devices were inconsistent, causing error codes or packets over the link.

Procedure

1.Check that the optical fiber is connected properly. Run the display this interface command in the interface view to check the interface status.

If the interface is Up, go to Step 2.
If the interface is Down, go to End.

2.Check the optical receive power in the display this interface command output.

If the optical receive power is within the allowed range, go to Step 3.
If the optical receive power is not in the allowed range, go to End.

3.Check the link protocol, clock mode and scramble of the local device in the display this interface command output. Then check whether they are consistent with those of the peer device.

If the link layer protocols and clock modes are consistent, go to End.
If the link layer protocols and clock modes are inconsistent, go to Step 4.

4.Set the same link protocol, clock mode and scramble for the local and peer devices. Then check whether the alarm is cleared.

If the alarm is cleared, go to End.
If the alarm is not cleared, go to Step 6.

5.Check the physical link status.

If the alarm is cleared, go to End.
If the alarm is not cleared, go to Step 6.

6.Collect the alarm information, log information, and configuration information, and then contact technical support personnel.