JUNIPER-VPN-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsJUNIPER-VPN-MIB

Organization: IETF Provider Provisioned VPNs WG

Last Updated: 2010-10-15

Category: Technology: VPN, VPN and Security, Vendor: Juniper

Description: Juniper Networks MIB for managing Layer 2 and Layer 3 VPN service instances and forwarding tables on Juniper PE routers.

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-VPN-MIB?

JUNIPER-VPN-MIB is a Juniper Networks enterprise MIB for managing and monitoring Layer 2 and Layer 3 VPN service instances (including locally switched L2 circuits) on Juniper provider-edge (PE) routers. It exposes configuration and inventory objects describing configured and active VPNs, including per-VPN type, name, and administrative row status, along with index-allocation counters for interfaces, pseudowires, and route targets. Its monitoring focus is software/service status rather than hardware: an administrator tracks how many VPNs are configured versus actively up (jnxVpnConfiguredVpns vs jnxVpnActiveVpns), and whether individual VPN instances remain in an active row status, revealing provisioning errors or VPN instances that failed to come up. It extends and works alongside industry-standard VPN MIBs (e.g., PPVPN/L3VPN MIB family) for full VPN management on Juniper equipment. It is deployed on Juniper MX/PE routers in service-provider networks offering L2VPN/L3VPN services to customers. Engineers can download the JUNIPER-VPN-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-VPN-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 MX-series PE routers
  • Juniper routers providing L2VPN/L3VPN services

Monitoring Examples

An operator would compare jnxVpnConfiguredVpns to jnxVpnActiveVpns to spot VPN instances that are provisioned but not operationally active. Walking jnxVpnTable/jnxVpnEntry lets the admin inspect jnxVpnType, jnxVpnName, and jnxVpnRowStatus for each VPN, where a row status other than active indicates a failed or incomplete VPN instantiation. jnxVpnNextIfIndex, jnxVpnNextPwIndex, and jnxVpnNextRTIndex track internal index allocation for interfaces, pseudowires, and route targets, useful for diagnosing index exhaustion in very large VPN deployments. jnxVpnMIBNotifications would issue traps when VPN state changes occur.

What Can Be Monitored

  • configured VPN count
  • active VPN count
  • per-VPN type and name
  • per-VPN row status
  • pseudowire/interface/route-target index allocation
Imported Objects

From IF-MIB

InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From JUNIPER-SMI

jnxMibsOBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-SMI

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

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using jnxVpnPwPacketsSent OID:

Select a Juniper MX/PE router (L2VPN/L3VPN service instances) 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 jnxVpnPwPacketsSent 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 packets that have been sent over this Pseudo-Wire. 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

RFC description

Manages provider-provisioned VPNs including L2 circuits, VPLS, and various VPN types on Juniper networks.

Start monitoring Juniper MX/PE router (L2VPN/L3VPN service instances) 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-VPN-MIB