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

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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.79 hwMplsTunnelHotstandbySwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.79 hwMplsTunnelHotstandbySwitch

Description

LSPM/2/MPLSTUNNELHOTSTANDBYSWITCH:OID [oid] Traffic switched from the primary LSP to the hot-standby LSP.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], TunnelName=[OCTET])

The trap message was output when the primary CR-LSP went Down and traffic was switched to a hot-standby CR-LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.79

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The primary LSP was Down and the backup LSP was in use. The backup mode was HSB.

Procedure

  1. Run the display mpls te tunnel-interface tunnel interface-number 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 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.

    • If the path is successfully calculated, run the display current-configuration interface interface-type interface-number command on the ingress to check the tunnel configurations, including the primary tunnel, protection tunnel, and the protection interface. Check whether the mpls te auto-frr command is configured in the MPLS view. If so, it indicates that Auto FRR is enabled. In this case, you can check the primary tunnel. If not, check whether the mpls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured to identify the primary and backup tunnels.

      After the primary and backup tunnels are checked, you can check the explicit-path command to verify whether the explicit path is configured; check the mpls te affinity property command to verify whether the affinity property is configured.

      Run the display mpls te cspf destination command and configure the parameters of constraints one by one, including the priority (priority setup-priority), bandwidth (bandwidth), explicit path (explicit-path path-name), affinity property (affinity properties), and hop limit (hop-limit hop-limit-number), and you can check whether the 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.
      1. If the explicit path fails to be calculated, check whether the interfaces along the explicit path are in the Up state and are enabled with MPLS and MPLS TE. If the explicit path is successfully calculated, check whether path calculation according to the affinity property and bandwidth is consistent with the explicit path by running the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If CSPF path calculation fails after affinity property is configured, run the mpls te affinity property command in the tunnel view to modify the affinity property of the tunnel, or run the mpls te link administrative group on the interfaces along the tunnel to modify the administrative group property of the link.
      3. If CSPF path calculation fails after bandwidth is configured, run the display mpls te link-administration bandwidth-allocation interface interface-type interface-number command to check whether the bandwidth of each outbound interface along the tunnel is enough. If the bandwidth is enough, it is possible that the tunnel with a higher priority preempts the bandwidth of the current tunnel. Then run the mpls te bandwidth max-reservable-bandwidth and mpls te bandwidth commands in the interface view to increase the bandwidth.
      4. If CSPF path calculation fails because of other constraints, go to Step 6.
      Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUpis generated.
      • If so, go to Stpe 7.
      • If not, go to Step 5.
    • If CSPF path calculation fails, go to Step 5.

  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 restart command in the interface view .
    Then, check whether the alarm 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 router, and contact Huawei technical personnel.
  7. End.
Translation
Download
Updated: 2019-05-06

Document ID: EDOC1000174085

Views: 128963

Downloads: 20

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