MPLS-TE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMPLS-TE-MIB

Organization: Multiprotocol Label Switching (MPLS) Working Group

Last Updated: 2000-11-21

Category: MPLS and Traffic Engineering

Description: Provides SNMP management for MPLS Traffic Engineering, allowing retrieval and monitoring of traffic flows and tunnel configurations.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring MPLS-TE-MIB with a free 30-day trial of IPNetwork Monitor.

What Is MPLS-TE-MIB?

MPLS-TE-MIB is a vendor-neutral IETF-derived MIB module that defines management objects for MPLS Traffic Engineering, covering the configuration and status of TE tunnels (LSPs) as specified in RSVP-TE and CR-LDP extension drafts referenced in its module description. It exposes tunnel-level configuration and operational objects in mplsTunnelTable/mplsTunnelEntry, including tunnel index/instance, ingress and egress LSR identifiers (mplsTunnelIngressLSRId, mplsTunnelEgressLSRId), tunnel name, and whether a tunnel is configured versus actively signaled (mplsTunnelConfigured, mplsTunnelActive). Its monitoring value is centered on the operational software/control-plane status of traffic-engineered paths across an MPLS network: verifying whether a specific tunnel is up and carrying traffic (mplsTunnelActive), which TE distribution protocol signaled it (mplsTunnelTEDistProto), and whether hop-count limits (mplsTunnelMaxHops) are being respected, which is essential for diagnosing a failed or suboptimal LSP. It builds on and complements the base MPLS LSR/label MIBs and the underlying RSVP/CR-LDP signaling protocols referenced in its description, rather than standing alone, and operators bringing up a new TE deployment commonly keep an MPLS-TE-MIB reference nearby to confirm which of these companion modules a given object depends on. It is deployed on MPLS-enabled provider-edge and core routers from any vendor implementing MPLS-TE, where network operations teams monitor tunnel state to ensure traffic-engineered paths remain established as designed.

IPNetwork Monitor allows you to monitor SNMP objects defined in MPLS-TE-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

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer
  • MPLS-enabled routers (provider-edge and core)

Monitoring Examples

An operator would poll mplsTunnelTable/mplsTunnelEntry, keyed by mplsTunnelIndex and mplsTunnelInstance, and check mplsTunnelActive against mplsTunnelConfigured for a tunnel identified by mplsTunnelIngressLSRId and mplsTunnelEgressLSRId to confirm whether a configured LSP is actually up and signaled. A tunnel showing mplsTunnelConfigured true but mplsTunnelActive false would indicate the TE tunnel failed to establish, prompting investigation into path constraints or a failure along the LSP; mplsTunnelName provides the human-readable label used to identify the tunnel during troubleshooting.

What Can Be Monitored

  • TE tunnel configured vs. active state
  • tunnel ingress/egress LSR identity
  • TE signaling/distribution protocol
  • tunnel max-hop constraint
  • tunnel name/identification
Imported Objects

From IF-MIB

InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddressIPv4
InetAddressIPv6

From MPLS-LSR-MIB

MplsBitRate
MplsBurstSize
MplsLSPID

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

DisplayString
RowPointer
RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using mplsTunnelPrimaryTimeUp OID:

Select a device implementing MPLS-TE-MIB 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 mplsTunnelPrimaryTimeUp 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. It reports how long the primary instance of this MPLS TE tunnel has been continuously active. 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 TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the value resets to a low number unexpectedly, since that indicates the primary tunnel path went down and came back up (a failover event). Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Management Information Base for MPLS Traffic Engineering (RFC 3814); provides configuration and operational objects for MPLS TE tunnels and LSPs.

Start monitoring Vendor-neutral IETF standard (MPLS-enabled provider-edge/core router, Traffic Engineering) 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-TE-MIB