MPLS-VPN-MIB-DRAFT-05

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMPLS-VPN-MIB-DRAFT-05

Organization: Provider Provisioned Virtual Private Networks Working Group.

Last Updated: 2002-10-31

Category: L2VPN/MPLS, MPLS

Description: Manages IETF draft-05 MPLS VPN instance routing and forwarding table objects.

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 MPLS-VPN-MIB-DRAFT-05?

MPLS-VPN-MIB-DRAFT-05 is a vendor-neutral IETF draft-05 MIB module (based on RFC 3031's MPLS architecture) for managing MPLS/BGP Virtual Private Network (VPN) instances, commonly known as VRFs (Virtual Routing and Forwarding tables), on provider-edge routers. It exposes configuration and operational data including which VRFs are configured versus active, which interfaces are attached to a VPN, per-VRF route-count thresholds and route-limit notification settings, and per-interface VPN classification/label-edge-type and routing-distribution-protocol objects. As a monitoring resource it is used to track the software/protocol-level health of VPN routing - the number of configured vs. active VRFs, route-count threshold breaches (potential VRF route-table exhaustion), and interface-to-VPN attachment/classification - rather than hardware sensors, and includes notification objects to alert when a VRF's route count crosses a configured maximum. It is explicitly built on RFC 3031 (MPLS architecture) and depends on underlying MPLS label-switching and BGP MIBs for full context of the VPN's forwarding and route-distribution behavior. It is deployed on provider-edge (PE) routers in MPLS/BGP-based Layer 3 VPN service-provider networks offering multi-tenant VPN connectivity to enterprise customers, consistent with the MPLS-VPN-MIB-DRAFT-05 RFC draft it implements.

IPNetwork Monitor allows you to monitor SNMP objects defined in MPLS-VPN-MIB-DRAFT-05. 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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • MPLS/BGP VPN provider-edge (PE) router

Monitoring Examples

An operator would compare mplsVpnConfiguredVrfs against mplsVpnActiveVrfs to spot a VRF that is configured but not currently active, indicating a provisioning or activation problem, and monitor mplsVpnConnectedInterfaces for unexpected changes in which interfaces are attached to VPNs. Walking mplsVpnIfConfTable/mplsVpnIfConfEntry (indexed by mplsVpnIfConfIndex) to check mplsVpnIfVpnClassification and mplsVpnIfVpnRouteDistProtocol confirms each interface's VPN role and routing-protocol distribution method is correctly set, while mplsVpnVrfConfMaxPossibleRoutes and mplsVpnVrfConfRouteMaxThreshTime govern when a mplsVpnNotifications trap fires for a VRF approaching its route-table capacity limit.

What Can Be Monitored

  • configured vs. active VRF counts
  • interfaces attached to VPNs
  • per-VRF route count vs. maximum threshold
  • interface VPN classification and route-distribution protocol
Imported Objects

From BGP4-MIB

bgp4PathAttrIpAddrPrefixOBJECT-TYPE
bgp4PathAttrIpAddrPrefixLenOBJECT-TYPE
bgp4PathAttrPeerOBJECT-TYPE

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From PPVPN-TC-MIB

VPNId

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
experimental

From SNMPv2-TC

DisplayString
RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using mplsVpnVrfSecIllegalLblVltns OID:

Select a device implementing MPLS-VPN-MIB-DRAFT-05 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 mplsVpnVrfSecIllegalLblVltns 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. Indicates the number of illegally received labels on this VPN/VRF. 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

MPLS/BGP Virtual Private Networks configuration and monitoring.

Start monitoring Vendor-neutral IETF draft standard (MPLS/BGP VPN provider-edge router) 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 MPLS-VPN-MIB-DRAFT-05