Contents

HH3C-MPLSSCRLSP-MIB· 1

About this MIB· 1

MIB file name· 1

Root object 1

Scalar objects· 1

hh3cMplsScrlspBaseInfo· 1

hh3cMplsScrlspExtInfo· 1

Notifications· 1

hh3cMplsScrlspDown· 1

hh3cMplsScrlspUp· 3

hh3cMplsScrlspLabelConflict 4

hh3cMplsScrlspLabelDup· 4

HH3C-MPLSSCRLSP-MIB

About this MIB

Use this MIB to manage static CRLSP notifications.

MIB file name

hh3c-mplsscrlsp.mib

Root object

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

Scalar objects

hh3cMplsScrlspBaseInfo

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cMplsScrlspBaseInfo (1.3.6.1.4.1.25506.2.231.1.1.1)	accessible-for-notify	OCTET STRING	OCTET STRING (1..127)	Static CRLSP basic information.	As per the MIB.

hh3cMplsScrlspExtInfo

Object (OID)	Access	Syntax	Value range	Description	Implementation
hh3cMplsScrlspExtInfo (1.3.6.1.4.1.25506.2.231.1.1.2)	accessible-for-notify	OCTET STRING	OCTET STRING (1..127)	Static CRLSP extended information.	As per the MIB.

Notifications

hh3cMplsScrlspDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.231.0.1	A static CRLSP went down.	Error	Major	1.3.6.1.4.1.25506.2.231.0.2 (hh3cMplsScrlspUp)	OFF

Notification triggers

This notification might be generated when the following events occur:

·     MPLS disabled on an interface.

·     MPLS TE disabled on an interface.

·     Route change.

·     Tunnel binding associated with the CR-LSP deleted.

·     Inbound interface Down.

·     Outbound interface Down.

·     Tunnel associated with the static CR-LSP has been shut down.

·     Static CR-LSP configuration update.

·     The bound ring is invalid.

·     Others.

System impact

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

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

Status control

ON

CLI: Use the snmp-agent trap enable te-private scrlsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private scrlsp-up-down command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
(1.3.6.1.4.1.25506.2.231.1.1.1) hh3cMplsScrlspBaseInfo	Static CRLSP basic information.	N/A	OCTET STRING	Standard MIB values.
(1.3.6.1.4.1.25506.2.231.1.1.2) hh3cMplsScrlspExtInfo	Static CRLSP extended information.	N/A	OCTET STRING	Standard MIB values.

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 CRLSP, check the outgoing interface. If the alarm was generated at the egress of the static CRLSP, check the incoming interface. If the alarm was generated at the transit node of the static CRLSP, 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.

¡     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. If MPLS TE is not enabled on the interface, enable MPLS TE on the interface.

2.     Check whether the alarms have been cleared.

¡     If yes, the issue has been resolved.

¡     If not, go to step 3.

3.     Execute the display current-configuration interface tunnel interface-name command on the ingress to verify that the tunnel configuration is correct.

¡     If the configuration is correct, go to step 4.

¡     If the destination address of the corresponding tunnel is different from the destination address of the static CRLSP, enter tunnel interface view and use the destination command to change the tunnel destination address.

¡     If the signaling type of the tunnel is not static, use the mpls te signaling static command to set the tunnel signaling type to static.

4.     If the bandwidth attribute is configured on the static CRLSP, execute the display current-configuration interface interface-name command to check the maximum bandwidth and maximum reserved bandwidth configuration of the outgoing interface.

¡     If the configuration is correct, go to step 5.

¡     If the available bandwidth of the outgoing interface is smaller than the bandwidth required by the static CRLSP, enter the interface view of the outgoing interface. In the interface view, execute the mpls te bandwidth max-reservable-bandwidth command to increase the bandwidth of the outgoing interface.

5.     Check whether the alarms have been cleared.

¡     If yes, the issue has been resolved.

¡     If not, go to step 6.

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

hh3cMplsScrlspUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.231.0.2	A static CRLSP came up.	Recovery	Major	N/A	OFF

Notification triggers

This notification is generated when a static CRLSP comes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private scrlsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private scrlsp-up-down command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
(1.3.6.1.4.1.25506.2.231.1.1.1) hh3cMplsScrlspBaseInfo	Static CRLSP basic information.	N/A	OCTET STRING	Standard MIB values.
(1.3.6.1.4.1.25506.2.231.1.1.2) hh3cMplsScrlspExtInfo	Static CRLSP extended information.	N/A	OCTET STRING	Standard MIB values.

Recommended action

No action is required.

hh3cMplsScrlspLabelConflict

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.231.0.3	SR label conflict	Error	Major	(1.3.6.1.4.1.25506.2.231.0.4) hh3cMplsScrlspLabelDup	OFF

Notification triggers

The requested Segment Routing label has been occupied.

System impact

The label request failed.

Status control

ON

CLI: Use the snmp-agent trap enable te-private scrlsp-lab-conflict command.

OFF

CLI: Use the undo snmp-agent trap enable te-private scrlsp-lab-conflict command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
(1.3.6.1.4.1.25506.2.231.1.1.1) hh3cMplsScrlspBaseInfo	Basic information of the static CRLSP	N/A	OCTET STRING	Standard MIB values.
(1.3.6.1.4.1.25506.2.231.1.1.2) hh3cMplsScrlspExtInfo	Extended information of the static CRLSP	N/A	OCTET STRING	Standard MIB values.

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.

hh3cMplsScrlspLabelDup

Basic information

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

Notification triggers

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

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

System impact

The incoming label request failed.

Status control

ON

CLI: Use the snmp-agent trap enable te-private scrlsp-lab-conflict command.

OFF

CLI: Use the undo snmp-agent trap enable te-private scrlsp-lab-conflict command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
(1.3.6.1.4.1.25506.2.231.1.1.1) hh3cMplsScrlspBaseInfo	Basic information of the static CRLSP	N/A	OCTET STRING	Standard MIB values.
(1.3.6.1.4.1.25506.2.231.1.1.2) hh3cMplsScrlspExtInfo	Extended information of the static CRLSP	N/A	OCTET STRING	Standard MIB values.

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.