IPFPM_1.3.6.1.4.1.2011.5.25.316.3.1 hwIpfpmLossRatioExceed

Trap Buffer Description

The loss ratio of IPFPM test instance exceeded the upper threshold in continuous five test intervals. (TestInstanceId=[InstanceId], AchId=[AchId], IpfpmMcpSeqNoHigh=[SeqNoHigh], IpfpmMcpSeqNoLow=[SeqNoLow], FlowType=[FlowType], ForwardPktLossRatio=[ForPktLossRatio], BackwardPktLossRatio=[BackPktLossRatio],InstDesc=[InstDesc])

The packet loss rate of an IP FPM instance exceeded the upper threshold over five consecutive statistical periods.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	hwIpfpmLossRatioExceed
Trap OID	1.3.6.1.4.1.2011.5.25.316.3.1
MIB	HUAWEI-IPFPM-MIB
Alarm ID	0x09d72009
Alarm Name	hwIpfpmLossRatioExceed
Alarm Type	qualityOfServiceAlarm
Raise or Clear	Raise
Match trap	IPFPM_1.3.6.1.4.1.2011.5.25.316.3.2 hwIpfpmLossRatioRecovery

Trap Buffer Parameters

Parameter	Description
InstanceId	IP FPM instance ID
AchId	Atomic closed hop ID
SeqNoHigh	32 most significant bits of the statistical period ID
SeqNoLow	32 least significant bits of the statistical period ID
FlowType	Target flow type
ForPktLossRatio	Packet loss rate for the forward target flow
BackPktLossRatio	Packet loss rate for the backward target flow
InstDesc	Specify description of test instance

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.316.1.1.7.1.2	hwIpfpmMcpFlowType	hwIpfpmMcpInstId hwIpfpmMcpAchId
1.3.6.1.4.1.2011.5.25.316.1.2.4.1.10	hwIpfpmMcpForwardLossRatio	hwIpfpmMcpInstId hwIpfpmMcpAchId hwIpfpmMcpSeqNoHigh hwIpfpmMcpSeqNoLow
1.3.6.1.4.1.2011.5.25.316.1.2.4.1.17	hwIpfpmMcpBackwardLossRatio	hwIpfpmMcpInstId hwIpfpmMcpAchId hwIpfpmMcpSeqNoHigh hwIpfpmMcpSeqNoLow
1.3.6.1.4.1.2011.5.25.316.1.1.5.1.2	hwIpfpmMcpInstDesc	hwIpfpmMcpInstId

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

Cause 1: The network bandwidth was insufficient because of abnormal traffic.

Cause 2: The physical link was unstable.

Procedure

1. 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.

2. 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.

3. 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.

4. 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.

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.

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

7. End.