JUNIPER-RSVP-MIB :: jnxRsvpSessionMplsOctets

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JUNIPER-RSVP-MIB › jnxRsvpSessionMplsOctets

jnxRsvpSessionMplsOctets

Module: JUNIPER-RSVP-MIB

OID (symbolic): JUNIPER-RSVP-MIB::jnxRsvpSessionMplsOctets

OID (numeric): 1.3.6.1.4.1.2636.3.30.1.1.1.11

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: The number of MPLS octets that have been forwarded over this RSVP Session. The number reported is not realtime, may subject to several minutes delay. The delay is controllable by mpls statistics gathering interval, which by default is once every 5 minutes. If mpls statistics gathering is not enabled, this number will not increment. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of jnxRsvpSessionDiscontinuityTime.

What is jnxRsvpSessionMplsOctets?

This object counts the MPLS octets forwarded over this RSVP session, though the number isn't real-time and can lag by several minutes because it depends on the MPLS statistics-gathering interval, which defaults to every 5 minutes; it won't increment at all if that gathering is disabled. Admins use it to measure traffic volume carried by a specific traffic-engineered LSP. For example, a flat octet count across polls could simply mean statistics gathering is turned off, not that the LSP is idle.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.30.1.1.1.11
snmpwalk -v2c -c public <target> JUNIPER-RSVP-MIB::jnxRsvpSessionMplsOctets

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.30.1.1.1.11.1
snmpget -v2c -c public <target> JUNIPER-RSVP-MIB::jnxRsvpSessionMplsOctets.1

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

How to Use in IPNetwork Monitor

Select a Juniper Networks MPLS-capable router (RSVP session monitoring) 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 jnxRsvpSessionMplsOctets 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 MPLS octets that have been forwarded over this RSVP Session. 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.30jnxRsvpMIBJUNIPER-RSVP-MIB
1.3.6.1.4.1.2636.3.30.1jnxRsvpOperationJUNIPER-RSVP-MIB
1.3.6.1.4.1.2636.3.30.1.1jnxRsvpSessionTableJUNIPER-RSVP-MIB
1.3.6.1.4.1.2636.3.30.1.1.1jnxRsvpSessionEntryJUNIPER-RSVP-MIB
1.3.6.1.4.1.2636.3.30.1.1.1.11jnxRsvpSessionMplsOctetsJUNIPER-RSVP-MIB