PORT/2/hwIfMonitorBadBytesErrorRising_active

Message

PORT/2/hwIfMonitorBadBytesErrorRising_active: The bytes of error packets reach the upper threshold. (hwIfMonitorIndex=[hwIfMonitorIndex], hwIfMonitorBadBytesErrorStatistics=[hwIfMonitorBadBytesErrorStatistics], hwIfMonitorBadBytesErrorThreshold=[hwIfMonitorBadBytesErrorThreshold], hwIfMonitorBadBytesErrorInterval=[hwIfMonitorBadBytesErrorInterval], hwIfMonitorName=[hwIfMonitorName])

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

Description

The number of bytes of received error packets exceeded the alarm threshold within a specified period.

Parameters

Parameter Name	Parameter Meaning
hwIfMonitorIndex	Index of physical port.
hwIfMonitorBadBytesErrorStatistics	Statistics about bytes of error packets.
hwIfMonitorBadBytesErrorThreshold	Maximum number of bytes of error packets.
hwIfMonitorBadBytesErrorInterval	Period within which the number of bytes of received error packets is counted.
hwIfMonitorName	Name of physical port.

Possible Causes

Line signals were unstable.

Procedure

1.When link attenuation is too high, replace the optical fiber and check whether the alarm is cleared.

If the alarm is cleared, go to End.
If the alarm is not cleared, go to step 2.

2.Check the transmit optical power of the remote end in the NMS. If the transmit optical power of the remote end is abnormal, replace the LPU at the remote end, and check whether the alarm is cleared.

If the alarm is cleared, go to End.
If the alarm is not cleared, go to step 3.

3.Replace the LPU at the local end for which the alarm is generated, and check whether the alarm is cleared.

If the alarm is cleared, go to End.
If the alarm is not cleared, go to step 4.

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