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.53 hwMplsTunnelBesteffortDown

MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown

Description

The best-effort 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 best-effort LSP of the tunnel changes to Down.

Attributes

Attributes

Description

Alarm or Event

Alarm

Trap Severity

Error

Mnemonic Code

hwMplsTunnelBesteffortDown

Trap OID

1.3.6.1.4.1.2011.5.25.121.2.1.53

Alarm ID

0x00f10047

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp

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.

hwMplsTunnelDownReason

Indicates the reason why a tunnel goes Down.

hwMplsTunnelDownLSRId

Indicates the LSR ID of the error node on a tunnel.

hwMplsTunnelDownIfAddrType

Indicates the IP address type of the error interface on a tunnel.

hwMplsTunnelDownIfAddr

Indicates the IP address of the error interface on 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 best-effort LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the best-effort LSP of the tunnel and another backup LSP is configured, traffic will be switched to the other backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: Other.

Cause 2: Static LSP Down.

Cause 3: Static CR-LSP Down.

Cause 4: The out interface of the RSVP LSP ingress is down.

Cause 5: The resource of RSVP LSP is preempted.

Cause 6: RSVP message timeout.

Cause 7: RSVP neighbor lost.

Cause 8: The bypass-tunnel is down or is unbinded with main tunnel, as bypass-tunnel is in used.

Cause 9: CSPF fails to compute.

Cause 10: User shutdown.

Procedure

  • Cause 1: Other.
    1. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 2: Static LSP Down.
    1. Check whether the configurations for the current tunnel interface, RSVP, an IGP, link connectivity, and bandwidth for links along the tunnel are correct.

      • If a configuration is incorrect, correct the configuration and commit the new configuration. Then check whether the tunnel is Up. If the tunnel goes Up, the alarm is cleared. If the tunnel is still Down, go to Step 4.
      • If all configurations are correct and the alarm persists, go to Step 2.

    2. Run the display mpls te tunnel-interface last-error command to check error information.

      • Check possible causes for error information before proceeding to the next step:
        • "Cspf failed to calculate a path for Tunnel": CSPF is enabled on the ingress but CSPF fails to calculate a path for the tunnel. Check whether configurations for explicit paths are correct, whether IS-IS TE or OSPF TE has been enabled, and whether routing configurations are correct.
          • If a configuration is incorrect, correct the configuration. Then the alarm is cleared.
          • If all configurations are correct and the alarm persists, go to Step 3.
        • "Routing Problem:Bad EXPLICIT_ROUTE object." or "Routing Problem:Bad initial subobject.": The ingress is not enabled with CSPF and is configured with an incorrect explicit path. Configure a correct explicit path for the tunnel.
          • If this error information is displayed, correct the configuration. Then, the alarm is cleared.
          • If all configurations are correct and the alarm persists, go to Step 3.
        • "Routing Problem:No route available toward destination.": CSPF is not enabled on either the ingress or any transit node, or an incorrect explicit path or an unreachable route to the destination address is configured. Correctly reconfigure the explicit path or an IGP.
          • If this error information is displayed, correct the configuration. Then, the alarm is cleared.
          • If all configurations are correct and the alarm persists, go to Step 3.
        • "Service preempted": Tunnel resources are preempted. Reconfigure the setup and holding priorities on the tunnel interface.
          • If this error information is displayed, correct the configuration. Then, the alarm is cleared.
          • If all configurations are correct and the alarm persists, go to Step 3.
        • "Admission Control failure": The ingress is enabled with CSPF but its downstream nodes is not. Along an explicit path, CSPF counts the bandwidth: the bandwidth of the ingress is sufficient; but the link bandwidth of downstream nodes is insufficient. Check the explicit path and bandwidth configurations.
          • If this error information is displayed, correct the configuration. Then, the alarm is cleared.
          • If all configurations are correct and the alarm persists, go to Step 3.
        • If other errors occurs, go to Step 4.
      • If no error information is displayed, go to Step 3.

    3. Run the display mpls lsp statistics command to check whether the number of LSPs exceeds the upper limit. If the number of LSPs exceeds the upper limit, delete unwanted LSPs and check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 3: Static CR-LSP Down.
    1. Check whether the configurations for the current tunnel interface, RSVP, an IGP, link connectivity, and bandwidth for links along the tunnel are correct.

      • If a configuration is incorrect, correct the configuration and commit the new configuration. Then check whether the tunnel is Up. If the tunnel goes Up, the alarm is cleared. If the tunnel is still Down, go to Step 4.
      • If the alarm persists, go to Step 2.

    2. Run the display mpls te tunnel-interface last-error command to check error information.

      • Check possible causes for error information before proceeding to the next step:
        • "Cspf failed to calculate a path for Tunnel": CSPF is enabled on the ingress but CSPF fails to calculate a path for the tunnel. Check whether configurations for explicit paths are correct, whether IS-IS TE or OSPF TE has been enabled, and whether routing configurations are correct.
          • If the configuration is corrected, the alarm is cleared.
          • If the alarm persists, go to Step 3.
        • "Routing Problem:Bad EXPLICIT_ROUTE object." or "Routing Problem:Bad initial subobject.": The ingress is not enabled with CSPF and is configured with an incorrect explicit path. Configure a correct explicit path for the tunnel.
          • If the configuration is corrected, the alarm is cleared.
          • If the alarm persists, go to Step 3.
        • "Routing Problem:No route available toward destination.": CSPF is not enabled on either the ingress or any transit node, or an incorrect explicit path or an unreachable route to the destination address is configured. Correctly reconfigure the explicit path or an IGP.
          • If the configuration is corrected, the alarm is cleared.
          • If the alarm persists, go to Step 3.
        • "Service preempted": Tunnel resources are preempted. Reconfigure the setup and holding priorities on the tunnel interface.
          • If the configuration is corrected, the alarm is cleared.
          • If the alarm persists, go to Step 3.
        • "Admission Control failure": The ingress is enabled with CSPF but its downstream nodes is not. Along an explicit path, CSPF counts the bandwidth: the bandwidth of the ingress is sufficient; but the link bandwidth of downstream nodes is insufficient. Check the explicit path and bandwidth configurations.
          • If the configuration is corrected, the alarm is cleared.
          • If the alarm persists, go to Step 3.
        • If other errors occurs, go to Step 4.
      • If no error information is displayed, go to Step 3.

    3. Run the display mpls lsp statistics command to check whether the number of LSPs exceeds the upper limit. If the number of LSPs exceeds the upper limit, delete unwanted LSPs and check whether the alarm is cleared. If the alarm persists, go to Step 4.
    4. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 4: The out interface of the RSVP LSP ingress is down.
    1. Check the configuration and status of the current tunnel interface. If the outbound interface is incorrectly configured, reconfigure it correctly. After this, if the alarm persists, go to the next step.
    2. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 5: The resource of RSVP LSP is preempted.
    1. Change the setup and holding priorities on the tunnel interface.
    2. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 6: RSVP message timeout.
    1. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 7: RSVP neighbor lost.
    1. Check configurations and statues of all downstream nodes of the ingress. Correct the configuration if there is an error. After this, if the alarm persists, go to the next step.
    2. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 8: The bypass-tunnel is down or is unbinded with main tunnel, as bypass-tunnel is in used.
    1. Run the display mpls te tunnel-interface command to check the status of the bypass tunnel. If a problem occurs, solve it and check whether the bypass tunnel is Up.

      • If the tunnel is Up and the alarm is cleared, go to Step 3.
      • If the alarm persists, go to Step 2.

    2. Run the display mpls te tunnel verbose command to check the binding between the primary and bypass tunnel. If a problem occurs, solve it. If the alarm persists, go to the next step.
    3. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 9: CSPF fails to compute.
    1. CSPF is enabled on the ingress but CSPF fails to calculate a path for the tunnel. Check whether configurations for explicit paths are correct, whether IS-IS TE or OSPF TE has been enabled, and whether routing configurations are correct.
    2. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
  • Cause 10: User shutdown.
    1. Run the undo shutdown command in the tunnel interface view.
    2. Collect the alarm information, log information, and configuration information, and then Collect alarm information and configuration information, and then contact technical support personnel..
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039527

Views: 79814

Downloads: 21

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