JUNIPER-LDP-MIB

All MIBs › JUNIPER-LDP-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2004--0-8-

Category: MPLS and Traffic Engineering, Protocol: MPLS, Routing Protocols, Technology: Routing, Vendor: Juniper

Description: Defines managed objects for Label Distribution Protocol (LDP) sessions, LSPs, and label bindings on Juniper Networks MPLS platforms.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is JUNIPER-LDP-MIB?

JUNIPER-LDP-MIB is a Juniper Networks enterprise MIB extending the standard LDP (Label Distribution Protocol) MIB draft to provide Juniper-specific visibility into MPLS label-switched path (LSP) sessions, label bindings, and session state on Juniper routing platforms. It exposes session-level data including router IDs, session up/down interfaces, and reasons why an LSP or session went down, along with statistics counters for LDP activity. This is a protocol/software-status MIB used to monitor MPLS control-plane health -- confirming LDP sessions with neighboring routers stay up and diagnosing exactly why a session or LSP failed when it does, which is critical for MPLS network troubleshooting. It explicitly extends the IETF LDP MIB draft, so it is meant to be used alongside that base standard rather than as a replacement. Typical deployment is service-provider or enterprise MPLS backbone routers running LDP for label distribution. Engineers can download the JUNIPER-LDP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-LDP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Juniper router (MPLS/LDP-enabled)

Monitoring Examples

An administrator would poll jnxLdpStatsTable/jnxLdpStatsEntry (indexed by jnxLdpInstanceId) to track LDP session activity per routing instance, and would check jnxLdpSesDownReason and jnxLdpSesDownIf when a neighbor session drops, immediately identifying which interface and cause (e.g., hold-timer expiry) triggered the failure. Similarly, jnxLdpLspDownReason combined with jnxLdpLspFec and jnxLdpLspFecLen would reveal which specific label-switched path failed and for which forwarding-equivalence-class prefix. jnxLdpRtrid and jnxLdpInstanceName help correlate events to the correct LDP instance and router identity in multi-instance deployments.

What Can Be Monitored

LDP session up/down status
session down reason and interface
LSP down reason and FEC
LDP instance statistics
router ID / instance identification

Imported Objects

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressPrefixLength
InetAddressType

From JUNIPER-MPLS-LDP-MIB

jnxMplsLdpSesState

OBJECT-TYPE

From JUNIPER-SMI

jnxLdpTraps	OBJECT-IDENTITY
jnxMibs	OBJECT-IDENTITY

From MPLS-VPN-MIB

MplsVpnName

From SNMPv2-SMI

Counter64
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using jnxLdpIngressOctets OID:

Select a Juniper router (MPLS/LDP-enabled) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type jnxLdpIngressOctets into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of octets of traffic originated on this box, forwarded over the current LDP FEC. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxLdp	1.3.6.1.4.1.2636.3.14			The MIB modules extends the LDP mib draft.
jnxLdpTrapVars	1.3.6.1.4.1.2636.3.14.1
IP jnxLdpLspFec	1.3.6.1.4.1.2636.3.14.1.1	IpAddress	accessible-for-notify	The LSP FEC in IP address format.
IP jnxLdpRtrid	1.3.6.1.4.1.2636.3.14.1.2	IpAddress	accessible-for-notify	The router id of the sending router.
INT jnxLdpLspDownReason	1.3.6.1.4.1.2636.3.14.1.3	INTEGER	accessible-for-notify	The reason why the LSP went down. Can be one of the following: the topology changed, the neighbor withdrew the label, the neighbor went down, the filter changed, the BFD session went down, lsping down, or the reason is unknown.
INT jnxLdpSesDownReason	1.3.6.1.4.1.2636.3.14.1.4	INTEGER	accessible-for-notify	The reason why the session transitioned to nonexistent state. Can be one of the following: unknown reason, hold time expired, connection time expired, all adjacencies down, received bad tlv, received bad pdu, connectionn error, connection reset, received notification from peer, received unexpected end-of-file, authentication key was changed, error during initialization, graceful restart was aborted or cli command.
NUM jnxLdpSesDownIf	1.3.6.1.4.1.2636.3.14.1.5	InterfaceIndexOrZero	accessible-for-notify	This variable is the snmp index of the interface relevant to the session-down event. If no interface can be correlated to the session-down, then it is the interface associated with one of the neighbors.
INT jnxLdpLspFecLen	1.3.6.1.4.1.2636.3.14.1.6	INTEGER	accessible-for-notify	The length in bits of the LSP FEC prefix.
NUM jnxLdpSesUpIf	1.3.6.1.4.1.2636.3.14.1.7	InterfaceIndexOrZero	accessible-for-notify	This variable is the interface index of one of the neighbors associated with this session.
MPL jnxLdpInstanceName	1.3.6.1.4.1.2636.3.14.1.8	MplsVpnName	accessible-for-notify	Name of the VPN instance.
jnxLdpStatsTable	1.3.6.1.4.1.2636.3.14.2		not-accessible	Table of statistics of Ldp FECs.
jnxLdpStatsEntry	1.3.6.1.4.1.2636.3.14.2.1		not-accessible	Entry containing statistics information about a particular LDP FEC.
U32 jnxLdpInstanceId	1.3.6.1.4.1.2636.3.14.2.1.1	Unsigned32	not-accessible	LDP instance.
IPt jnxLdpFecType	1.3.6.1.4.1.2636.3.14.2.1.2	InetAddressType	not-accessible	Type of this LDP FEC.
IP jnxLdpFec	1.3.6.1.4.1.2636.3.14.2.1.3	InetAddress	not-accessible	LDP FEC.
ADR jnxLdpFecLength	1.3.6.1.4.1.2636.3.14.2.1.4	InetAddressPrefixLength	not-accessible	LDP FEC length (in bits).
INT jnxLdpFecStatisticsStatus	1.3.6.1.4.1.2636.3.14.2.1.5	INTEGER	read-only	Indicates the status of traffic statistics for this FEC. For penultimate hop FECs traffic statistics can be disabled. For such FECs, the following objects will have the value '0'.
C64 jnxLdpIngressOctetsEx	1.3.6.1.4.1.2636.3.14.2.1.6	Counter64	read-only	The number of octets of traffic originated on this box, forwarded over the current LDP FEC. The number reported is not realtime and may be subject to several minutes delay. The delay is controllable by ldp statistics gathering interval, which by default is 5 minutes.
C64 jnxLdpIngressPackets	1.3.6.1.4.1.2636.3.14.2.1.7	Counter64	read-only	The number of packets of traffic originated on this box, forwarded over the current LDP FEC. The number reported is not realtime and may be subject to several minutes delay. The delay is controllable by ldp statistics gathering interval, which by default is 5 minutes.
C64 jnxLdpTransitOctets	1.3.6.1.4.1.2636.3.14.2.1.8	Counter64	read-only	The number of octets of traffic destined to this FEC, originated on a different box, forwarded over the current LDP FEC. The number reported is not realtime and may be subject to several minutes delay. The delay is controllable by ldp statistics gathering interval, which by default is 5 minutes.
C64 jnxLdpTransitPackets	1.3.6.1.4.1.2636.3.14.2.1.9	Counter64	read-only	The number of packets of traffic destined to this FEC, originated on a different box, forwarded over the current LDP FEC. The number reported is not realtime and may be subject to several minutes delay. The delay is controllable by ldp statistics gathering interval, which by default is 5 minutes.
jnxLdpTrapPrefix	1.3.6.1.4.1.2636.4.4.0
NTF jnxLdpLspUp	1.3.6.1.4.1.2636.4.4.0.1			The SNMP trap that is generated when an LSP comes up.
NTF jnxLdpLspDown	1.3.6.1.4.1.2636.4.4.0.2			The SNMP trap that is generated when the LSP goes down.
NTF jnxLdpSesUp	1.3.6.1.4.1.2636.4.4.0.3			The SNMP trap that is generated when the value of 'jnxMplsLdpSesState' enters the 'operational(5) state.
NTF jnxLdpSesDown	1.3.6.1.4.1.2636.4.4.0.4			The SNMP trap that is generated when the value of 'jnxMplsLdpSesState' leaves the 'operational(5) state. The value of jnxLdpSesDownIf is one of the neighbor's interface. It is the interface associated with the last neighbor when jnxLdpSesDownReason is allAdjacenciesDown (3).

RFC description

Extends LDP (Label Distribution Protocol) management with Juniper-specific monitoring for MPLS LSP events and session status.

Start monitoring Juniper router (MPLS/LDP-enabled) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download JUNIPER-LDP-MIB