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

CloudEngine 12800 and 12800E V200R005C00

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_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

Description

The primary LSP of the tunnel changes to Down. (SessionTunnelId=[SessionTunnelId], TunnelInstIndex=[TunnelInstIndex], IngressLsrId=[IngressLsrId], EgressLsrId=[EgressLsrId], mplsTunnelIfName=[mplsTunnelIfName], hwMplsTunnelDownReason=[hwMplsTunnelDownReason], hwMplsTunnelDownLSRId=[hwMplsTunnelDownLSRId], hwMplsTunnelDownIfAddrType=[hwMplsTunnelDownIfAddrType], hwMplsTunnelDownIfAddr=[hwMplsTunnelDownIfAddr], SignalledTunnelName=[SignalledTunnelName])

The primary LSP of the tunnel changes to Down.

Attributes

Attributes

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwMplsTunnelPrimaryDown

Trap OID

1.3.6.1.4.1.2011.5.25.121.2.1.47

Alarm ID

0x09060006

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp

Parameters

Parameter Description

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the InstIndex of the tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

mplsTunnelIfName

Indicates the name of a tunnel.

SignalledTunnelName

Tunnel alias.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.121.1.1.1.29

hwMplsTunnelInterfaceName

hwMplsTunnelIndex

hwMplsTunnelInstance

hwMplsTunnelIngressLSRId

hwMplsTunnelEgressLSRId

1.3.6.1.4.1.2011.5.25.121.2.2.3

hwMplsTunnelDownReason

N/A

1.3.6.1.4.1.2011.5.25.121.2.2.8

hwMplsTunnelDownLSRID

N/A

1.3.6.1.4.1.2011.5.25.121.2.2.10

hwMplsTunnelDownIfIpAddrType

N/A

1.3.6.1.4.1.2011.5.25.121.2.2.9

hwMplsTunnelDownIfIpAddr

N/A

Impact on the System

If traffic is not forwarded along the primary LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the primary LSP of the tunnel and a backup LSP is configured, traffic will be switched to the backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

  • Cause 1: The interface went Down.
  • Cause 2: The configuration of the tunnel was deleted.
  • Cause 3: The link was faulty.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm MPLS_LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check whether a path that meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restartcommand in the interface view .

    Then, check whether the alarm MPLS_LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.

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

  6. Collect the trap information, log information, and configuration of the switch, and contact technical support personnel.
  7. End.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 69764

Downloads: 21

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