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 V200R010C00

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).
LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLSPDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLSPDown

Description

LSPM/2/STATICLSPDOWN: OID [oid] Static LSP went Down. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], lspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static LSP was in the Down state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.2

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LspIndex

Indicates the index of the LSP.

InSegmentIndex

Indicates the inSegment index of a static LSP.

OutSegmentIndex

Indicates the outSegment index of a static LSP.

OutIfIndex

Indicates the outbound interface index of a static LSP.

lspName

Indicates the name of a static LSP.

LspStatus

Indicates the status of a static LSP.

OutIfName

Indicates the outbound interface name of a static LSP.

InIfIndex

Indicates the inbound interface index of a static LSP.

InIfName

Indicates the inbound interface name of a static LSP.

DownReason

Indicates the reason that the static LSP down.

Impact on the System

If there is some service using this static LSP, the service is interrupted. If there is not any service using this static LSP, there is no impact.

Possible Causes

1. The interface was Down.

2. The next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.

3. The link was damaged.

Procedure

  1. Run the display mpls interface. If the trap is generated on the ingress of static LSPs, you need to check the information about only the outbound interface; if the trap is generated on the egress of static LSPs, you need to check the information about only the inbound interface; if the trap is generated on the transit of static LSPs, you need to check the information about both the inbound interface and the outbound interface. You need to check whether the corresponding interface is displayed in the command output, and whether the Status field of the interface is Up.

    • If the interface status is not Up, check the interface.

    • If the corresponding interface is not displayed in the command output, it indicates that MPLS is not enabled on the interface. In this case, you need to enable MPLS on the interface. Then, check whether the trap is cleared.
      • If so, go to Step 5.

      • If not, go to Step 2.

    • If the trap is generated on the ingress of static LSPs, go to Step 2.
    • If the trap is generated on the egress or transit of static LSPs, go to Step 4.

  2. Run the display ip routing-table ip-address mask command to check the routing information. Check whether the configured destination addresses, masks, outbound interfaces, and next hops of static LSPs are the same as those in the routing information. Note that if a static LSP is configured by specifying the outbound interface, the address of the outbound interface is used as the next hop. This configuration is used only in a small number of scenarios.

    • If so, go to Step 3.

    • If not, check the configuration of the static LSP route on the ingress and make it strictly match with the route in the RM. Then, check whether the trap is cleared.
      • If so, go to Step 5.

      • If not, go to Step 2.

  3. If the ingress is bound to the tunnel, run the display mpls interface command to check whether the TE Attr field is En. If not, it indicates that MPLS TE is not enabled on the interface. Run the display current-configuration interface interface-type interface-number command to check whether the corresponding tunnel is correctly configured.

    • If the MPLS TE is not enabled, enable MPLS TE on the interface.

    • Run the display current-configuration interface interface-type interface-number command to check whether the corresponding tunnel is correctly configured.
      • If the tunnel is not consistent with the destination address of the static LSP, you need to enter the corresponding tunnel view and run the destination command to modify the destination address of the tunnel.
      • After modifying the configuration of the tunnel, run the mpls te commit command to commit the modification.
      • If the signaling mode is not static, run the mpls te signal-protocol static command to modify the signaling mode of the tunnel.
      If neither preceding operations can locate the fault, go to Step 4.

  4. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 183447

Downloads: 44

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