MPLS-TE-STD-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsMPLS-TE-STD-MIB

Organization: Multiprotocol Label Switching (MPLS) Working Group

Last Updated: 2004-06-03

Category: MPLS and Traffic Engineering

Description: Manages MPLS Traffic Engineering tunnels, providing configuration and statistics for TE tunnel LSPs that originate, traverse, or terminate on a given LSR (RFC 3812).

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

What Is MPLS-TE-STD-MIB?

MPLS-TE-STD-MIB is a standards-based IETF MIB (RFC 3812) for managing MPLS Traffic Engineering (TE) tunnels on a Label Switching Router, covering configuration and statistics for TE tunnel LSPs that originate, transit, or terminate at the device. Categories exposed include TE tunnel configuration such as paths, hop lists, and reserved bandwidth, along with per-tunnel operational statistics and TE-related notifications. MPLS-TE-STD-MIB SNMP monitoring emphasizes software/protocol state — whether a traffic-engineered tunnel is operationally up, which path it is using, and how much of its reserved bandwidth is actually carried — flagging reroutes or failures along an LSP rather than physical sensor data. It builds directly on core MPLS concepts from MPLS-LSR-MIB and the underlying RSVP-TE/CR-LDP signaling protocols (RFC 3209/3212) referenced in its description. It is deployed on MPLS-enabled core and edge routers in service-provider backbones that use RSVP-TE or CR-LDP for traffic engineering.

IPNetwork Monitor allows you to monitor SNMP objects defined in MPLS-TE-STD-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 core/edge router (LSR)

Monitoring Examples

An operator would poll the per-tunnel configuration and status entries to see whether a given traffic-engineered tunnel is operationally up and which physical hop path it is currently using, revealing whether a primary TE path failed over to a backup route. Tunnel-level statistics would show whether a bandwidth-reserved LSP is actually carrying its expected traffic load, flagging under- or over-utilization against its reservation. No sample object names were captured for this module, so exact table/column identifiers aren't cited here, but a tunnel entry unexpectedly reporting a down or reoptimizing state would alert an admin to a link failure or reroute event along the LSP's path.

What Can Be Monitored

  • TE tunnel operational status
  • tunnel path/hop configuration
  • reserved bandwidth utilization
  • tunnel traffic statistics
  • tunnel reroute/failure events
Imported Objects

From DIFFSERV-MIB

IndexIntegerNextFree

From IF-MIB

InterfaceIndexOrZero
ifCounterDiscontinuityGroupOBJECT-GROUP
ifGeneralInformationGroupOBJECT-GROUP

From INET-ADDRESS-MIB

InetAddressPrefixLength

From MPLS-TC-STD-MIB

MplsBitRate
MplsBurstSize
MplsExtendedTunnelId
MplsLSPID
MplsOwner
MplsPathIndex
MplsPathIndexOrZero
MplsTunnelAffinity
MplsTunnelIndex
MplsTunnelInstanceIndex
TeHopAddress
TeHopAddressAS
TeHopAddressType
TeHopAddressUnnum
mplsStdMIBOBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

RowPointer
RowStatus
StorageType
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using mplsTunnelInstanceUpTime OID:

Select an MPLS-enabled core or edge router 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 mplsTunnelInstanceUpTime 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 the total time this MPLS TE tunnel instance's operational status has been up. 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 tunnel instance went down and came back up (a failover event). Click Finish to create the monitor; you can adjust any parameter later.

See also: mplsTunnelPrimaryUpTime, mplsTunnelTotalUpTime

OIDs

RFC description

MPLS Traffic Engineering standard MIB (RFC 3812) for managing MPLS TE tunnels, LSPs, and traffic engineering parameters.

Start monitoring Vendor-neutral IETF standard (MPLS-enabled core/edge 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-STD-MIB