Contents

MPLS-LDP-STD-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

mplsLdpInitSessionThresholdExceeded· 1

mplsLdpSessionUp· 2

mplsLdpSessionDown· 4

 

 

MPLS-LDP-STD-MIB

About this MIB

LDP is the core of MPLS and defines the messages and processing procedures involved in the label distribution process.

The Label Distribution Protocol (LDP) dynamically distributes FEC-label mapping information between LSRs to establish LSPs. LSPs can be established between two adjacent LSRs or terminate at the egress node of the network, so that all intermediate nodes in the network use label switching.

MPLS-LDP-STD-MIB is a public MIB defined by RFC 3815.

MIB file name

rfc3815-mpls-ldp-std.mib

Notifications

mplsLdpInitSessionThresholdExceeded

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.4.0.1	The number of session initialization messages exceeds the limit.	Error	Major	N/A (N/A)	ON

 

Notification triggers

Wrong LDP session parameter configuration will cause LDP to send initialization messages multiple times. This notification is generated when the number of session initialization messages exceeds the value (not 0) of the mplsLdpEntityInitSessionThreshold object.

System impact

All services based on this LDP session will be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable ldp command.

OFF

CLI: Use the undo snmp-agent trap enable ldp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.4.1.2.3.1.11 (mplsLdpEntityInitSessionThreshold)	During the session establishment with an LDP peer, if the number of session initialization messages sent by the LDP entity exceeds the maximum value defined by the mplsLdpInitSessionThresholdExceeded object, the LDP entity will send notifications.	1.3.6.1.2.1.10.166.4.1.2.3.1.1 (mplsLdpEntityLdpId) 1.3.6.1.2.1.10.166.4.1.2.3.1.2 (mplsLdpEntityIndex)	Integer32	0..100

 

Recommended action

To resolve this issue:

1.Check the configuration for LDP session parameters:

  - Verify that the keepalive hold time is not 0 on the remote device. Value 0 is not valid. Use a non-zero value for this parameter.

  - Verify that the label advertisement mode is not Downstream On Demand (DoD) on the remote device. H3C does not support the DoD mode. Set the label advertisement mode to Downstream Unsolicited (DU) on the remote device.

  - Check the loop detection configuration on the remote device. If loop detection is enabled, the PV limit cannot be 0. If loop detection is disabled, the PV limit must be 0.

2.If the issue persists, contact H3C Support.

mplsLdpSessionUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.4.0.3	The session state changes to operational.	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when the value of the mplsLdpSessionState object changes to operational(5). This value indicates that the LDP session is established successfully.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable ldp command.

OFF

CLI: Use the undo snmp-agent trap enable ldp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.4.1.3.3.1.2 (mplsLdpSessionState)	LDP session state.	1.3.6.1.2.1.10.166.4.1.2.3.1.1 (mplsLdpEntityLdpId) 1.3.6.1.2.1.10.166.4.1.2.3.1.2 (mplsLdpEntityIndex) 1.3.6.1.2.1.10.166.4.1.3.2.1.1 (mplsLdpPeerLdpId)	INTEGER	nonexistent(1) , initialized(2) , openrec(3) , opensent(4) , operational(5))
1.3.6.1.2.1.10.166.4.1.3.3.1.8 (mplsLdpSessionDiscontinuityTime)	Time when the LDP session is up.	1.3.6.1.2.1.10.166.4.1.2.3.1.1 (mplsLdpEntityLdpId) 1.3.6.1.2.1.10.166.4.1.2.3.1.2 (mplsLdpEntityIndex) 1.3.6.1.2.1.10.166.4.1.3.2.1.1 (mplsLdpPeerLdpId)	Timeticks	Standard MIB values.
1.3.6.1.2.1.10.166.4.1.3.4.1.1 (mplsLdpSessionStatsUnknownMesTypeErrors)	Number of unknown messages detected by the LSR during the session.	1.3.6.1.2.1.10.166.4.1.2.3.1.1 (mplsLdpEntityLdpId) 1.3.6.1.2.1.10.166.4.1.2.3.1.2 (mplsLdpEntityIndex) 1.3.6.1.2.1.10.166.4.1.3.2.1.1 (mplsLdpPeerLdpId)	Counter32	Standard MIB values.
1.3.6.1.2.1.10.166.4.1.3.4.1.2 (mplsLdpSessionStatsUnknownTlvErrors)	Number of unknown TLVs detected by the LSR during the session.	1.3.6.1.2.1.10.166.4.1.2.3.1.1 (mplsLdpEntityLdpId) 1.3.6.1.2.1.10.166.4.1.2.3.1.2 (mplsLdpEntityIndex) 1.3.6.1.2.1.10.166.4.1.3.2.1.1 (mplsLdpPeerLdpId)	Counter32	Standard MIB values.

 

Recommended action

No action is required.

mplsLdpSessionDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.2.1.10.166.4.0.4	The session state is not operational.	Error	Major	1.3.6.1.2.1.10.166.4.0.3 (mplsLdpSessionUp)	ON

 

Notification triggers

This notification is generated when the value of the mplsLdpSessionState object is not operational.

Possible reasons for the down state of a session include:

interface not operational.

MPLS disabled on interface.

LDP disabled on interface.

LDP auto-configure disabled on interface.

VPN instance changed on interface.

LDP instance deleted.

targeted peer deleted.

L2VPN disabled targeted peer.

TE tunnel disabled targeted peer.

session protection disabled targeted peer.

OSPF Remote LFA disabled targeted peer.

IS-IS Remote LFA disabled targeted peer

process deactivated.

failed to receive the initialization message.

graceful restart reconnect timer expired.

failed to recover adjacency by NSR.

failed to upgrade session by NSR.

closed the GR session.

keepalive hold timer expired.

hello hold timer expired.

session reset.

TCP connection down.

received a fatal notification message.

internal error.

memory in critical state.

transport address changed on interface.

MD5 password changed

Auto targeted peer deleted

Modify LDP local LSR ID

LDP process stopped

System impact

All services based on the LDP session will be interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable ldp command.

OFF

CLI: Use the undo snmp-agent trap enable ldp command.

Object

OID (object name)	Description	Index	Type	Value range
1.3.6.1.2.1.10.166.4.1.3.3.1.2 (mplsLdpSessionState)	Session state.	mplsLdpEntityLdpId mplsLdpEntityIndex mplsLdpPeerLdpId	INTEGER	nonexistent(1) , initialized(2) , openrec(3) , opensent(4) , operational(5))
1.3.6.1.2.1.10.166.4.1.3.3.1.8 (mplsLdpSessionDiscontinuityTime)	System time when a counter of the LDP session suffered a discontinuity.	mplsLdpEntityLdpId mplsLdpEntityIndex mplsLdpPeerLdpId	Timeticks	Standard MIB values.
1.3.6.1.2.1.10.166.4.1.3.4.1.1 (mplsLdpSessionStatsUnknownMesTypeErrors)	Number of unknown messages detected by the LSR during the session.	mplsLdpEntityLdpId mplsLdpEntityIndex mplsLdpPeerLdpId	Counter32	Standard MIB values.
1.3.6.1.2.1.10.166.4.1.3.4.1.2 (mplsLdpSessionStatsUnknownTlvErrors)	Number of unknown TLVs detected by the LSR during the session.	mplsLdpEntityLdpId mplsLdpEntityIndex mplsLdpPeerLdpId	Counter32	Standard MIB values.

 

Recommended action

To resolve this issue:

Take proper actions according to the reason displayed for the session down state. Table 1 shows the recommended actions.

Reasons for session down and the solutions

Reason for session down

Solution

 

interface not operational

Verify that the link state of the interface is normal and the interface has a correct IPv4 or IPv6 address configured.

 

MPLS disabled on interface

Use the mpls enable command to enable MPLS on the interface in interface view.

 

LDP disabled on interface

Use the mpls ldp enable command to enable LDP on the interface in interface view.

 

VPN instance changed on interface

Use the ip binding vpn-instance command in interface view to edit the interface and VPN instance association.

 

LDP instance deleted

Use the vpn-instance command in LDP view to recover the LDP capability of the specified VPN instance.

 

targeted peer deleted

Use the target-peer command in LDP view to reconfigure the targeted peer.

 

L2VPN disabled targeted peer

See the action for the pwDeleted notification node.

 

TE tunnel disabled targeted peer

Use the display interface tunnel command to view the TE tunnel interface state. If the state is not Up, see the mplsTunnelDown notification node for the recommended action.

Use the display mpls ldp interface command to view the MPLS and LDP configuration on the interface. If the configuration does not exist, execute the mpls enable and mpls ldp enable commands in interface view.

 

session protection disabled targeted peer

Use the session protection command in LDP view to recover the session protection configuration.

 

OSPF Remote LFA disabled targeted peer

OSPF calculated that the PQ node address of the remote LFA has changed, so it deleted the corresponding targeted peer. This is a normal operation when the network topology changes and no action is required.

 

IS-IS Remote LFA disabled targeted peer

IS-IS calculated that the PQ node address of the remote LFA has changed, so it deleted the corresponding targeted peer. This is a normal operation when the network topology changes and no action is required.

 

process deactivated

The process is waiting for automatic session recovery to be performed after the LDP process is upgraded.

As a best practice, execute the non-stop-routing command in LDP view to enable NSR to reduce the impact of process upgrading.

 

failed to receive the initialization message

Execute the ping -a local-address -c count (more than 100) destination-address command to test the link status. If packet loss occurs, collect alarm information and configuration data, and then contact the technical support for help.

The local-address and destination-address are the LSR ID of the local device and destination device, respectively.

To view the LSR ID of a device, execute the display mpls ldp parameter command on the device.

 

graceful restart reconnect timer expired

Execute the ping -a local-address -c count (more than 100) destination-address command to test the link status. If packet loss occurs, collect alarm information and configuration data, and then contact the technical support for help.

The local-address and destination-address are the LSR ID of the local device and destination device, respectively.

To view the LSR ID of a device, execute the display mpls ldp parameter command on the device.

 

failed to recover adjacency by NSR

Execute the display ha service-group ldp command. If the value of the State field is Realtime Backup, it indicates that the data backup has completed. Make sure the state is Realtime Backup and then perform a primary/backup switchover.

 

failed to upgrade session by NSR

Execute the display ha service-group ldp command. If the value of the State field is Realtime Backup, it indicates that the data backup has completed. Make sure the state is Realtime Backup and then perform a primary/backup switchover.

 

closed the GR session

Execute the ping -a local-address -c count (more than 100) destination-address command to test the link status. If packet loss occurs, collect alarm information and configuration data, and then contact the technical support for help.

The local-address and destination-address are the LSR ID of the local device and destination device, respectively.

To view the LSR ID of a device, execute the display mpls ldp parameter command on the device.

 

keepalive hold timer expired

Execute the ping -a local-address -c count (more than 100) destination-address command to test the link status. If packet loss occurs, collect alarm information and configuration data, and then contact the technical support for help.

The local-address and destination-address are the LSR ID of the local device and destination device, respectively.

To view the LSR ID of a device, execute the display mpls ldp parameter command on the device.

 

hello hold timer expired

Make sure the link is stable, for example, by changing the link or troubleshooting link faults.

 

session reset

The session is reset manually and will be reestablished automatically. No action is required.

 

TCP connection down

Execute the ping -a local-address -c count (more than 100) destination-address command to test the link status. If packet loss occurs, collect alarm information and configuration data, and then contact the technical support for help.

 

received a fatal notification message

Identify the specific error information in the message and then take actions accordingly.

 

internal error

LDP internal error. Collect alarm information and configuration data, and then contact Technical Support for help.

 

memory in critical state

Memory has a level-3 alarm. Collect alarm information and configuration data, and then contact Technical Support for help.

 

transport address changed on interface

Use the mpls ldp transport-address command in interface view to reconfigure the interface's LDP transport address.

 

MD5 password changed

Use the display this command in LDP view to view the value for the md5-authentication field. Make sure the two ends of the session have the same MD5 authentication password configured.

 

Auto targeted peer deleted

Use the display this command in LDP view to view the accept target-hello configuration:

If the accept target-hello configuration does not exist, check whether it is deleted mistakenly.

If the configuration is accept target-hello prefix-list prefix-list-name, use the display ip prefix-list name prefix-list-name command to check whether this IP prefix list permits the remote LSR ID. Edit the IP prefix list if needed to make sure it permits the remote LSR ID.

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

 

Modify LDP local LSR ID

This operation will cause the session to go down, which is a normal process. Wait for the session to come up again.

 

LDP process stopped

Execute the display current-configuration configuration ldp command to view the LDP configuration. If LDP configuration exists in the output, the LDP process is stopped abnormally. In this case, collect alarm information and configuration data, and then contact Technical Support for help. If the LDP configuration does not exist, check whether it is deleted mistakenly.

The following information indicates that LDP configuration exists:

<Sysname> display current-configuration configuration  ldp

#

mpls ldp

#

return

The following information indicates that LDP configuration does not exist:

<Sysname> display current-configuration configuration  ldp

#

return