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).
MPLS

MPLS

MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.23 hwBoardMplsPhpResLack

Description

MPLS/4/PHP_RESLACK:OID [OID] PHP labels added failed because of insufficient resource. (Slot=[OCTET])

PHP labels failed to be added due to insufficient resources.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.23

Warning

processingErrorAlarm(4)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot Indicates the slot ID.

Impact on the System

MPLS traffic cannot be transmitted over the corresponding card.

Possible Causes

Cause 1:

The ACL resources are insufficient.

Cause 2:

The MPLS PHP label specified exceeds the upper threshold.

Procedure

  1. Run the label advertise { explicit-null | non-null } command in the MPLS view of the switch directly connected to the local device to enable the egress switch to distribute a label without an explicit null label to the PHP node.
  2. Run the reset mpls ldp command in the user view of the local device to enable LDP globally.

Related Information

None

MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.25 hwBoardMplsFwdResLack

Description

MPLS/4/MPLS_LACK:OID [OID] The MPLS resource usage has reached or exceeded [GAUGE]%. (EntPhysicalIndex=[GAUGE], Slot=[OCTET], ResourceType=[INTEGER])

The usage of MPLS forwarding entries has reached or exceeded the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.25

Warning

equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Indicates the upper threshold of an alarm.
EntPhysicalIndex Indicates the physical entity index.
Slot Indicates the slot ID.
ResourceType Indicates a resource type.
  • 330: mplsvpTable (MPLS VP entry)
  • 331: mplsEntryTable (MPLS_ENTRY and INSEGMENT entries)
  • 332: mplsVcAndSwapLabelTable (VC_AND_SWAP entries)
  • 333: ipTunnelMplsTable (EGR_IP_TUNNEL_MPLS and TUNNEL entries)
  • 578: vfiTable (VFI entries)
  • 579: vxlanvpTable (VXLAN VP entry)

Impact on the System

When the usage of MPLS forwarding entries reaches 85%, the MPLS service cannot be normally transmitted. When the value of ResourceType is 579, the number of VXLAN VP entries exceeds the upper limit, causing abnormal VXLAN service transmission.

Possible Causes

The usage of MPLS forwarding entries has reached or exceeded the upper threshold.

Procedure

  1. Run the display current-configuration command to check detailed device configuration. Delete unnecessary service configuration based on the value of ResourceType in the alarm information.

    • If the value of ResourceType is 330, 579, or 331, check whether the configuration of VPLS, VXLAN, VLL, or PWE3 is redundant.
    • If the value of ResourceType is 332, check whether the configuration of VPLS, VLL, PWE3, L3VPN, MPLS LDP, or MPLS TE is redundant.
    • If the value of ResourceType is 333, check whether the configuration of MPLS LDP or MPLS TE is redundant.
    • If the value of ResourceType is 578, check whether the configuration of VPLS or VXLAN is redundant.

  2. Check whether the alarm is cleared. If not, go to step 3.
  3. Collect log information and configuration information, and then contact technical support personnel. You can collect diagnostic information using the display diagnostic-information command.

Related Information

None

MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume

Description

MPLS/4/MPLS_RESUME:OID [OID] The MPLS resource usage is restored to be lower than [GAUGE]%. (EntPhysicalIndex=[GAUGE], Slot=[OCTET], ResourceType=[INTEGER])

The usage of MPLS forwarding entries has fallen below the lower threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.26

Warning

equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
GAUGE Indicates the lower threshold of an alarm.
EntPhysicalIndex Indicates the physical entity index.
Slot Indicates the slot ID.
ResourceType Indicates a resource type.
  • 330: sourceVpTable (VP and SVP entries)
  • 331: mplsEntryTable (MPLS_ENTRY and INSEGMENT entries)
  • 332: mplsVcAndSwapLabelTable (VC_AND_SWAP entries)
  • 333: ipTunnelMplsTable (EGR_IP_TUNNEL_MPLS and TUNNEL entries)

Impact on the System

Services will not be affected.

Possible Causes

The usage of MPLS forwarding entries has fallen below the lower threshold.

Procedure

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

Related Information

None

MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.46 hwBoardMplsFlowLabelNonSupp

Description

MPLS/4/FLOW_LABEL_NONSUPP:OID [OID] The board does not support MPLS flow label. (Slot=[OCTET])

The device detects a card that does not support the flow label function.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.46

Warning

equipmentAlarm(5)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot Indicates the slot ID.

Impact on the System

The flow label function does not take effect on the detected card.

Possible Causes

The card or device is restarted after the flow label function is enabled on the device. The device detects that the card does not support the flow label function.

Procedure

  1. Check whether services transmitted by this card require the flow label function.

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

  2. Replace the card with one supporting the flow label function. Only the X series cards, LE1D2S04SEC0, LE1D2X32SEC0, and LE1D2H02QEC0 support the flow label function.
  3. This log message is informational only, and no action is required.

Related Information

None

MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.54 hwBoardMplsFwdResFull

Description

MPLS/4/MPLSRESOURCEFULL: OID [OID] The MPLS entry resource has been exhausted. (Slot=[OCTET], ResourceType=[INTEGER])

The MPLS forwarding entry resources have been exhausted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.227.2.1.54

Warning

environmentalAlarm(6)

Parameters

Name Meaning
OID Indicates the MIB object ID of the alarm.
Slot Slot ID.
ResourceType Resource type.
  • 331: mplsEntryTable, corresponding to the MPLS_ENTRY and INSEGMENT entries
  • 332: mplsVcAndSwapLabelTable, corresponding to the VC_AND_SWAP entry
  • 333: ipTunnelMplsTable, corresponding to the EGR_IP_TUNNEL_MPLS and TUNNEL entries

Impact on the System

If the MPLS forwarding entry resources are exhausted, the MPLS and VPN service traffic fails to be forwarded.

Possible Causes

The usage of the MPLS forwarding entry resources reaches or exceeds the upper limit.

Procedure

  1. Run the display current-configuration command to check detailed device configuration. Delete unnecessary service configuration based on the value of ResourceType in the alarm information.

    • If the value of ResourceType is 331, check whether the configuration of VPLS, VLL, PWE3, or VXLAN is redundant.
    • If the value of ResourceType is 332, check whether the configuration of VPLS, VLL, PWE3, L3VPN, MPLS LDP, or MPLS TE is redundant.
    • If the value of ResourceType is 333, check whether the configuration of MPLS LDP or MPLS TE is redundant.

  2. Check whether the clear alarm MPLS_1.3.6.1.4.1.2011.5.25.227.2.1.26 hwBoardMplsFwdResLackResume is reported. If not, go to step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3533

Downloads: 2

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