JUNIPER-LDP-MIB :: jnxLdpIngressOctets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-LDP-MIB › jnxLdpIngressOctets

jnxLdpIngressOctets

Module: JUNIPER-LDP-MIB

OID (symbolic): JUNIPER-LDP-MIB::jnxLdpIngressOctets

OID (numeric): 1.3.6.1.4.1.2636.3.14.2.1.6

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: 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.

What is jnxLdpIngressOctets?

This read-only counter reports the number of octets of traffic that originated on this router and were forwarded over the current LDP FEC, that is, ingress traffic this box injected into the LSP. Because the underlying statistics-gathering interval defaults to 5 minutes, admins should expect this counter to lag real time rather than reflect an instantaneous rate. A steadily rising jnxLdpIngressOctets on a given FEC confirms this router is actively originating and forwarding traffic into that label-switched path.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.14.2.1.6
snmpwalk -v2c -c public <target> JUNIPER-LDP-MIB::jnxLdpIngressOctets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.14.2.1.6.1
snmpget -v2c -c public <target> JUNIPER-LDP-MIB::jnxLdpIngressOctets.1

Start monitoring Juniper router (MPLS/LDP-enabled) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-LDP-MIB::jnxLdpIngressOctets OID value, configure state conditions and alerts, and monitor any Juniper router (MPLS/LDP-enabled) from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.3jnxMibsJUNIPER-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2636.3.14jnxLdpJUNIPER-LDP-MIB
1.3.6.1.4.1.2636.3.14.2jnxLdpStatsTableJUNIPER-LDP-MIB
1.3.6.1.4.1.2636.3.14.2.1jnxLdpStatsEntryJUNIPER-LDP-MIB
1.3.6.1.4.1.2636.3.14.2.1.6jnxLdpIngressOctetsJUNIPER-LDP-MIB