JNX-L2TP-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › JNX-L2TP-MIB

Organization: Juniper Networks Inc.

Last Updated: 2013-11-21

Category: Protocol: L2TP, Vendor: Juniper

Description: Defines managed objects for Layer 2 Tunneling Protocol (L2TP) sessions and tunnels on Juniper Networks devices.

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 JNX-L2TP-MIB?

JNX-L2TP-MIB is Juniper Networks' proprietary MIB for Layer 2 Tunneling Protocol (L2TP), modeled on the standard L2TP MIB from RFC 3371 but with Juniper-specific index differences for its tunnel and session statistics tables. It exposes monitoring data for L2TP tunnels and sessions terminated or originated on a Juniper router, covering tunnel-level and per-session statistics used in broadband remote access and VPN tunneling deployments. Its focus is on service/software status rather than hardware sensors: administrators use it to confirm how many L2TP tunnels and sessions are currently active and to watch per-tunnel/session statistics counters for signs of instability, since a device supporting L2TP tunneling for subscriber sessions depends on this protocol staying healthy for those users to remain connected. It explicitly derives from and modifies the IETF RFC 3371 L2TP MIB, changing the INDEX fields of the tunnel and session statistics tables while keeping the overall object model similar. It is deployed on Juniper routers acting as LAC/LNS endpoints in broadband access networks (e.g., ISP L2TP-based subscriber tunneling) or L2TP-based VPN termination points. Engineers can download the JNX-L2TP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JNX-L2TP-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 Networks router (LAC/LNS L2TP endpoint)

Monitoring Examples

An operator would monitor Juniper's equivalent of the l2tpTunnelStatsTable and l2tpSessionStatsTable (indexed differently than the RFC 3371 baseline per the module description) to track the number of active tunnels and sessions and their associated packet/error counters. A tunnel showing rising error counts or an unexpected drop in active session count would indicate an L2TP tunnel flapping or subscriber sessions being dropped. Because sample_objects were not provided for this module, exact Juniper-specific object names cannot be confirmed beyond the tunnel/session statistics tables referenced in the module description.

What Can Be Monitored

  • active L2TP tunnel count
  • active L2TP session count
  • per-tunnel statistics counters
  • per-session statistics counters
Imported Objects

From HCNUM-TC

CounterBasedGauge64

From INET-ADDRESS-MIB

InetAddress
InetAddressType
InetPortNumber

From JUNIPER-SMI

jnxL2tpMibRootOBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks
Unsigned32
transmission

From SNMPv2-TC

DateAndTime
RowStatus
StorageType
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using jnxL2tpTunnelStatsControlTxPkts OID:

Select a Juniper Networks router (LAC/LNS L2TP endpoint) 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 jnxL2tpTunnelStatsControlTxPkts 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. This object contains the number of control packets that were transmitted to the tunnel peer. 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 Counter32-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

RFC description

Monitoring for Layer Two Transport Protocol (L2TP) tunnels and sessions on Juniper routers based on RFC 3371.

Start monitoring Juniper Networks router (LAC/LNS L2TP endpoint) 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 JNX-L2TP-MIB