IPFPM/2/hwIpfpmTwoDelayExceed_active
Message
IPFPM/2/hwIpfpmTwoDelayExceed_active: The two-way delay of IPFPM test instance exceeded the upper threshold in continuous five test intervals. (TestInstanceId=[InstanceId], AchId=[AchId], IpfpmMcpSeqNoHigh=[SeqNoHigh], IpfpmMcpSeqNoLow=[SeqNoLow], TwoDelay=[DelayValue])
Description
The two-way delay of an IP FPM instance exceeded the upper threshold over five consecutive statistical periods.
Parameters
Parameter Name | Parameter Meaning |
---|---|
TestInstanceId |
IP FPM instance ID |
AchId |
Atomic closed hop ID |
IpfpmMcpSeqNoHigh |
32 most significant bits of the statistical period ID |
IpfpmMcpSeqNoLow |
32 least significant bits of the statistical period ID |
TwoDelay |
Two-way delay for the target flow |
Possible Causes
- Network congestion occurred due to 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 log information and configuration information, and then contact technical support personnel.
- End.