IPFPM_1.3.6.1.4.1.2011.5.25.316.3.1 hwIpfpmLossRatioExceed

Description

IPFPM/2/LOSSRATIO_EXCEED: OID [oid] The loss ratio of IPFPM test instance exceeded the upper threshold in continuous five test intervals. ([REPEAT][REPEAT]TestInstanceId=[integer], AchId=[integer], IpfpmMcpSeqNoHigh=[integer], IpfpmMcpSeqNoLow=[integer], [REPEAT]FlowType=[integer], ForwardPktLossRatio=[integer], BackwardPktLossRatio=[integer], InstanceDescription=[octet])

The packet loss ratios of an IP FPM instance exceeded the upper threshold over five consecutive measurement intervals.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.316.3.1	Major	qualityOfServiceAlarm(3)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
TestInstanceId	IP FPM instance ID.
AchId	Atomic closed hop ID. Hop-by-Hop performance statistics collection does not support to generate an alarm based on ACH.
IpfpmMcpSeqNoHigh	32 most significant bits of the statistical period ID.
IpfpmMcpSeqNoLow	32 least significant bits of the statistical period ID.
FlowType	Target flow type.
ForwardPktLossRatio	Packet loss rate for the forward target flow.
BackwardPktLossRatio	Packet loss rate for the backward target flow.
InstanceDescription	IP FPM instance description.

Impact on the System

The packet loss ratios in five consecutive measurement intervals exceed the alarm threshold. The network transmission quality is poor.

Possible Causes

The network bandwidth was insufficient because of abnormal traffic.
The physical link was unstable.

Procedure

Check whether abnormal traffic existed on the network when the trap was generated.
- If abnormal traffic existed on the network, go to Step 2.
- If no abnormal traffic existed on the network, go to Step 3.
Check whether the abnormal traffic was caused by misoperations.
- If the abnormal traffic was caused by misoperations, go to Step 3.
- If the abnormal traffic was not caused by misoperations, go to Step 6.
Delete the misoperation configurations and check whether the trap persists.
- If the trap persists, go to Step 4.
- If the trap is cleared, go to Step 7.
Check whether the link status was stable when the trap was generated.
- If the link status was stable, go to Step 6.
- If the link status was unstable, go to Step 5.
Check the problem that caused the unstable link status, resolve the problem, and check whether the trap persists.
- If the trap persists, go to Step 6.
- If the trap is cleared, go to Step 7.
Collect alarm information and configuration information, and then contact technical support personnel.
End.

Related Information

IPFPM_1.3.6.1.4.1.2011.5.25.316.3.2 hwIpfpmLossRatioRecovery