No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
IPFPM_1.3.6.1.4.1.2011.5.25.316.3.10 hwIpfpmMultiOneDelayExceed

IPFPM_1.3.6.1.4.1.2011.5.25.316.3.10 hwIpfpmMultiOneDelayExceed

Description

IPFPM/3/MULTI_ONEDELAY_EXCEED: OID [oid] The one-way delay of one link in an IPFPM test instance exceeded the upper threshold over five consecutive statistical periods. (TestInstanceId=[integer], AchId=[integer], IpfpmMcpSeqNoHigh=[integer], IpfpmMcpSeqNoLow=[integer], FlowType=[integer], SourceDCP=[IPADDR], SourceTLP=[integer], DestinationDCP=[IPADDR], DestinationTLP=[integer], OneDelay=[integer])

The one-way delay of a link in an IP FPM instance exceeded the upper threshold over five consecutive statistical periods.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.316.3.10 Minor qualityOfServiceAlarm(3)

Parameters

Name 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

FlowType

Target flow type

SourceDCP

Source DCP

SourceTLP

Source TLP

DestinationDCP

Destination DCP

DestinationTLP

Destination TLP

OneDelay

One-way delay for the target flow

Impact on the System

The network transmission quality is poor.

Possible Causes

  1. Network congestion occurred due to abnormal traffic.
  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.
Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 131635

Downloads: 20

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next