MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch

Trap Buffer Description

Main LSP of Tunnel switches to backup LSP in HSB. (TunnelId=[TunnelId], LocalLspId=[LocalLspId], IngressLsrId=[IngressLsrId], EgressLsrId=[EgressLsrId], TunnelAdminStatus=[TunnelAdminStatus], TunnelOperStatus=[TunnelOperStatus])

Traffic switched from the primary CR-LSP to a hot-standby CR-LSP after the primary CR-LSP went Down.

Trap Attributes

Trap Attribute Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

TNLHSBSWITCH

Trap OID

1.3.6.1.4.1.2011.5.25.121.2.1.9

MIB

HUAWEI-MPLS-EXTEND-MIB

Alarm ID

This is an event trap and does not involve alarm ID.

Alarm Name

This is an event trap and does not involve alarm name.

Alarm Type

This is an event trap and does not involve alarm type.

Raise or Clear

This is an event trap and does not involve alarm generation or clearance.

Match trap

-

Trap Buffer Parameters

Parameter Description

TunnelId

Primary tunnel ID.

LocalLspId

LSP ID of the primary tunnel.

IngressLsrId

Ingress LSR ID of the primary tunnel.

EgressLsrId

Egress LSR ID of the primary tunnel.

TunnelAdminStatus

Indicates the management status of the tunnel.

TunnelOperStatus

Indicates the operating status of the tunnel.

VB Parameters

VB OID VB Name VB Index

1.3.6.1.4.1.2011.5.25.121.1.1.1.7

hwMplsTunnelAdminStatus

hwMplsTunnelIndex

hwMplsTunnelInstance

hwMplsTunnelIngressLSRId

hwMplsTunnelEgressLSRId

1.3.6.1.4.1.2011.5.25.121.1.1.1.8

hwMplsTunnelOperStatus

hwMplsTunnelIndex

hwMplsTunnelInstance

hwMplsTunnelIngressLSRId

hwMplsTunnelEgressLSRId

Impact on the System

Services will not be affected.

Possible Causes

The primary CR-LSP goes Down and the hot-standby CR-LSP is Up.

Procedure

1. Check the configurations of the tunnel interface, RSVP, and IGP, and check whether the bandwidth of the entire link meets the requirements.

  • If an explicit path is configured, check whether the interface along the path is faulty hop by hop.
  • If yes, go to step 2
  • If no, go to Step 3
  • If no explicit path is configured, check whether an explicit path that meets the configuration requirements exists. If such an explicit path exists, go to Step 3.

2. Rectify the link fault.

  • If yes, go to step 5
  • If no, go to Step 3

3. Run the display mpls te tunnel-interface last-error command to view the error information.

  • If the following error information is displayed:
  • If "ENUM_TEM_LSPFSM_EVENT_QUERYROUTE_FAIL" is displayed, the ingress is enabled with CSPF but CSPF fails to calculate a path. Check whether the explicit path is correctly configured, whether the IGP protocol is enabled with MPLS TE, and whether the route configuration is correct.
  • If yes, go to step 5
  • If no, go to Step 4
  • Display "Receive Error-Node(192.168.1.2) at ENUM_TEM_LSPFSM_STATE_SETUPING state.", it indicates that the configuration of the tunnel node 192.168.1.2 is incorrect. In this case, you need to check whether the TE and RSVP-TE configurations on the node are correct.
  • If yes, go to step 5
  • If no, go to Step 4
  • Display "Sig. reports connect timeout at ENUM_TEM_LSPFSM_STATE_SETUPING state."RSVP-TE is not enabled on the downstream interface or node of the tunnel.
  • If yes, go to step 5
  • If no, go to Step 4
  • The message "Crlsp receive Sig." is displayed.ResvTear at ENUM_TEM_LSPFSM_STATE_SETUPING state.", a downstream link or node of the tunnel is faulty and needs to be checked.
  • If yes, go to step 5
  • If no, go to Step 4
  • For other types of errors, go to Step 4.
  • If no error message is displayed, go to step 4.

4. Collect log and configuration information, and contact technical support personnel.

5. The procedure ends.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >