DEVM_1.3.6.1.4.1.2011.5.25.157.2.157.9 hwPhysicalPortCrcPacketErrorRatio

Trap Buffer Description

The CRC-PER(Packet Error Ratio) is rising. (IfIndex=[hwPhysicalPortThrIfIndex],IfName=[hwPhysicalPortThrName],CurrentValue=[hwPhysicalPortCrcPerCurrentValueString],AlarmThreshold=[hwPhysicalPortCrcPerAlarmThresholdString],ResumeThreshold=[hwPhysicalPortCrcPerResumeThresholdString])

The CRC-PER(Packet Error Ratio) 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	hwPhysicalPortCrcPacketErrorRatio
Trap OID	1.3.6.1.4.1.2011.5.25.157.2.157.9
MIB	HUAWEI-PORT-MIB
Alarm ID	0x081300ba
Alarm Name	hwPhysicalPortCrcPacketErrorRatio
Alarm Type	processingErrorAlarm
Raise or Clear	Raise
Match trap	DEVM_1.3.6.1.4.1.2011.5.25.157.2.157.10 hwPhysicalPortCrcPacketErrorRatioResume

Trap Buffer Parameters

Parameter	Description
hwPhysicalPortThrIfIndex	Index of physical port.
hwPhysicalPortThrName	Name of physical port.
hwPhysicalPortCrcPerCurrentValueString	Current bit error rate on a physical interface.
hwPhysicalPortCrcPerAlarmThresholdString	Alarm threshold for the bit error rate on a physical interface.
hwPhysicalPortCrcPerResumeThresholdString	Alarm clearance threshold for the bit error rate on a physical interface.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.157.1.14.1.1.1	hwPhysicalPortThrIfIndex	hwPhysicalPortThrIfIndex
1.3.6.1.4.1.2011.5.25.157.1.14.1.1.2	hwPhysicalPortThrName	hwPhysicalPortThrIfIndex
1.3.6.1.4.1.2011.5.25.157.1.14.1.1.29	hwPhysicalPortCrcPerCurrentValueString	hwPhysicalPortThrIfIndex
1.3.6.1.4.1.2011.5.25.157.1.14.1.1.30	hwPhysicalPortCrcPerAlarmThresholdString	hwPhysicalPortThrIfIndex
1.3.6.1.4.1.2011.5.25.157.1.14.1.1.31	hwPhysicalPortCrcPerResumeThresholdString	hwPhysicalPortThrIfIndex

Impact on the System

If trigger-lsp or trigger-section is configured during the configuration of the CRC error packet rate on a physical interface, the alarm is generated, triggering an LSP or section switching. If trigger-lsp or trigger-section is not configured, services may be interrupted.

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 (CRC mode, scramble mode of interfaces, and clock mode of WAN interfaces) 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 Step 5.

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 Step 6.

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 Step 6.
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 Step 7.
If the alarm is not cleared, go to Step 6.

5.Check the physical link status. Collect the check information.

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

7.End.