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

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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).
IP FPM

IP FPM

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. (TestInstanceId=[integer], AchId=[integer], IpfpmMcpSeqNoHigh=[integer], IpfpmMcpSeqNoLow=[integer], 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

  1. The network bandwidth was insufficient because of 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.

IPFPM_1.3.6.1.4.1.2011.5.25.316.3.2 hwIpfpmLossRatioRecovery

Description

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

The packet loss ratios of an IP FPM instance fell below the lower threshold over five consecutive measurement intervals.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.316.3.2

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

Services will not be affected.

Possible Causes

The network transmission quality becomes good, and the packet loss ratios within five consecutive measurement intervals are lower than the clear alarm threshold.

Procedure

  • This trap message is informational only, and no action is required.

IPFPM_1.3.6.1.4.1.2011.5.25.316.3.8 hwIpfpmTlpExceed

Description

IPFPM/2/TLP_EXCEED:OID [oid] The number of board tlp exceeded the threshold. (BoardIndex=[BoardIndex], BoardTlpNumber=[BoardTlpNumber], ThresholdValue=[ThresholdValue])

The number of TLPs configured on a board exceeded the TLP threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.316.3.8

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BoardIndex

Board index

BoardTlpNumber

Number of TLPs configured on a board

ThresholdValue

Number of TLPs allowed by a board

Impact on the System

The number of TLPs configured on a board exceeded the TLP threshold of the board, consuming more board resources. Therefore, the board processing performance is affected.

Possible Causes

The number of TLPs configured on a board exceeded the TLP threshold of the board.

Procedure

  1. Check whether the TLPs on a board are normally configured.

    • If so, go to Step 2.
    • If not, go to Step 3.

  2. Check whether the normally configured TLPs are referenced by services in the DCP view.

    • If so, go to Step 5.
    • If not, go to Step 4.

  3. Delete the TLPs that are incorrectly configured and check whether the trap persists.

    • If so, go to Step 2.
    • If not, go to Step 6.

  4. Delete TLPs that are not referenced by services. Run the display ipfpm dcp command to check the maximum number of TLPs that the board supports. Ensure that the number of TLPs configured on the board is smaller than the maximum number of TLPs that the board supports and check whether the trap persists.

    • If so, go to Step 5.
    • If not, go to Step 6.

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

IPFPM_1.3.6.1.4.1.2011.5.25.316.3.9 hwIpfpmTlpRecovery

Description

IPFPM/2/TLP_RECOVERY:OID [oid] The number of board tlp was under the threshold. (BoardIndex=[INTEGER], BoardTlpNumber=[INTEGER], ThresholdValue=[INTEGER])

The number of TLPs configured on a board fell below the TLP threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.316.3.9

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BoardIndex

Board index

BoardTlpNumber

Number of TLPs configured on a board

ThresholdValue

Number of TLPs allowed by a board

Impact on the System

Services will not be affected.

Possible Causes

The number of TLPs configured on a board fell below the TLP threshold.

Procedure

  • This trap message is informational only, and no action is required.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 4255

Downloads: 6

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