MPLS_LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.91 hwP2mpTeSubLspDown

Trap Buffer Description

P2MP sub-lsp status changes to down. (SessionTunnelId=[SessionTunnelId], LocalLspId=[LocalLspId], IngressLsrId=[IngressLsrId], DestAddr=[DestAddr], TunnelName=[TunnelName], LspRole=[LspRole], P2MPID=[P2mpId], SubLspDownReason=[SubLspDownReason], SubLspDownLSRId=[SubLspDownLSRId], SubLspDownIfAddrType=[SubLspDownIfAddrType], SubLspDownIfAddr=[SubLspDownIfAddr])

P2MP sub-lsp status changes to down.

Trap Attributes

Trap Attribute Description

Alarm or Event

Event

Trap Severity

Warning

Mnemonic Code

P2MP_SUB_LSP_DOWN

Trap OID

1.3.6.1.4.1.2011.5.25.121.2.1.91

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

SessionTunnelId

Tunnel ID.

LocalLspId

Local LSP ID.

IngressLsrId

Ingress LSR ID.

DestAddr

Destination IP address.

TunnelName

Tunnel name.

LspRole

Role of an LSP generating a trap:

  • Primary LSP
  • Modified LSP for the primary LSP.

P2mpId

P2MP flag.

SubLspDownReason

Cause for the sub-LSP Down event.

SubLspDownLSRId

Node on which the sub-LSP went Down.

SubLspDownIfAddrType

Type of an interface on which a sub-LSP went Down.

SubLspDownIfAddr

Address of an interface on which a sub-LSP went Down.

VB Parameters

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.1.1.1.28

hwMplsTunnelLspType

hwMplsTunnelIndex

hwMplsTunnelInstance

hwMplsTunnelIngressLSRId

hwMplsTunnelEgressLSRId

1.3.6.1.4.1.2011.5.25.121.2.2.20

hwMplsP2mpId

-

Impact on the System

Traffic forwarded along the LSP will be interrupted.

Possible Causes

Cause 1: Other.

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: BYPASS is down or by pass is unbinded.

Cause 100: The alarm was cleared.

Procedure

1. Check causes for each sub-LSP that went Down.

  • Locate the cause, and repair the sub-LSP. If the fault is rectified, go to Step 3.
  • If the fault persists and no cause is located, go to Step 2.

2. Collect log information and configuration information, and then contact technical support personnel.

3. End.

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