Contents

HH3C-MPLSSLSP-MIB· 1

About this MIB· 1

MIB file name· 1

Root object 1

Tabular objects· 1

hh3cMplsSlspBaseInfo· 1

hh3cMplsSlspExtInfo· 1

Notifications· 1

hh3cMplsSlspDown· 1

hh3cMplsSlspUp· 3

hh3cMplsSlspLabelDup· 3

HH3C-MPLSSLSP-MIB

About this MIB

Use this MIB to notify static LSP traps.

MIB file name

hh3c-mplsslsp.mib

Root object

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cMplsSlsp(230)

Tabular objects

hh3cMplsSlspBaseInfo

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cMplsSlspBaseInfo (1.3.6.1.4.1.25506.2.230.1.1.1)	accessible-for-notify	OCTET STRING	OCTET STRING (0..127)	Static LSP basic information	As per the MIB.

hh3cMplsSlspExtInfo

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cMplsSlspExtInfo (1.3.6.1.4.1.25506.2.230.1.1.2)	accessible-for-notify	OCTET STRING	OCTET STRING (0..127)	Static LSP extended information	As per the MIB.

Notifications

hh3cMplsSlspDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.230.0.1	Static LSP down	Error	Major	1.3.6.1.4.1.25506.2.230.0.2(hh3cMplsSlspUp)	OFF

Notification triggers

This notification might be generated when the following events occur:

1.     MPLS disabled on an interface.

2.     Route change.

3.     Inbound interface Down.

4.     Outbound interface Down.

5.     Static LSP configuration updated.

6.     Others.

System impact

·     Service interruption will occur on services that use the static LSP for traffic forwarding.

·     No negative impact will occur on services that do not use the static LSP for traffic forwarding.

Status control

ON

CLI: Use the snmp-agent trap enable mpls-private slsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable mpls-private slsp-up-down command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.2.230.1.1.1 (hh3cMplsSlspBaseInfo)	Static LSP basic information	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.230.1.1.2 (hh3cMplsSlspExtInfo)	Static LSP extended information	N/A	OCTET STRING	As per the MIB.

Recommended action

To resolve this issue:

1.     Execute the display mpls interface command to check interface information.

If the alarm was generated at the ingress of the static LSP, check the outgoing interface. If the alarm was generated at the egress of the static LSP, check the incoming interface. If the alarm was generated at the transit node of the static LSP, check both the incoming interface and outgoing interface.

In the command output, verify that the corresponding interface exists and the interface status is Up.

¡     If the interface status is not Up, check and correct the interface configuration, and then go to step 2.

¡     If the corresponding interface is not displayed in the command output, it indicates that MPLS is not enabled on the interface. Enable MPLS on the interface and then go to step 2.

2.     Execute the display ip routing-table ip-address command at the ingress node, and check whether a valid route exists.

¡     If yes, go to step 3.

¡     If not, check the route configuration and ensure that the next hop address is reachable. Then, go to step 4.

3.     Execute the display mpls lsp command at the ingress node to check whether a dynamic LSP with the same prefix as the static LSP is configured.

¡     If yes, disable the dynamic LSP and go to step 4.

¡     If not, go to step 5.

4.     Check whether the alarms have been cleared.

¡     If yes, the issue has been resolved.

¡     If not, go to step 5.

5.     Collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsSlspUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.230.0.2	Static LSP up	Recovery	Major	N/A	OFF

 

Notification triggers

This notification is generated when a static LSP comes up.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable mpls-private slsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable mpls-private slsp-up-down command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.2.230.1.1.1 (hh3cMplsSlspBaseInfo)	Static LSP basic information	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.230.1.1.2 (hh3cMplsSlspExtInfo)	Static LSP extended information	N/A	OCTET STRING	As per the MIB.

Recommended action

No action is required.

hh3cMplsSlspLabelDup

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.230.0.3	The incoming label of the static LSP is already used by a static PW or static CRLSP.	Error	Major	N/A	OFF

Notification triggers

1.     MPLS is enabled and then a static LSP is configured with an incoming label that has been used by an existing static PW or static CRLSP.

2.     A static LSP is configured with an incoming label that has been used by an existing static PW or static CRLSP, and then MPLS is enabled.

System impact

The incoming label request failed.

Status control

ON

CLI: Use the snmp-agent trap enable mpls-private label-duplicate command.

OFF

CLI: Use the undo snmp-agent trap enable mpls-private label-duplicate command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.2.230.1.1.1 (hh3cMplsSlspBaseInfo)	Basic information of the static LSP	N/A	OCTET STRING	As per the MIB.
1.3.6.1.4.1.25506.2.230.1.1.2 (hh3cMplsSlspExtInfo)	Extended information of the static LSP	N/A	OCTET STRING	As per the MIB.

Recommended action

To resolve this issue:

1.     Delete the configuration for the occupied label to release the label.

2.     Request an unused label.

3.     If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help.