CISCO-IETF-MPLS-TE-P2MP-STD-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-IETF-MPLS-TE-P2MP-STD-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2009-09-30

Category: Cisco Devices, MPLS and Traffic Engineering

Description: Covers point-to-multipoint MPLS Traffic Engineering tunnels as defined by the IETF draft standard.

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 CISCO-IETF-MPLS-TE-P2MP-STD-MIB?

CISCO-IETF-MPLS-TE-P2MP-STD-MIB is Cisco's implementation of the IETF standard MIB for managing Point-to-Multipoint (P2MP) MPLS Traffic Engineering tunnels, as defined by RFC 4461 and the RFC 4875 signaling extensions to RSVP-TE. It exposes tables of P2MP TE tunnel configuration and state, including whether a tunnel is configured versus actively signaled/active, branch role, sub-group identifiers, destination leaf endpoints, and total hop counts. It is used to monitor the software/control-plane status of MPLS P2MP tunnels in a service-provider core -- specifically whether a tunnel is up (cmplsTeP2mpTunnelActive vs cmplsTeP2mpTunnelConfigured) and whether all destination branches are correctly established, with notifications available for tunnel state changes. As an "IETF" MIB implemented by Cisco, it explicitly depends on and mirrors the IETF MPLS-TE and P2MP standards (RFC 4461, RFC 4875) and typically coexists with the base MPLS-TE-STD-MIB for point-to-point tunnels. Typical deployment is on Cisco MPLS provider-edge/core routers delivering multicast-like P2MP LSP services such as IPTV distribution or multicast VPN. Engineers can download the CISCO-IETF-MPLS-TE-P2MP-STD-MIB file directly to load it into their MIB browser.

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

  • Cisco MPLS provider-edge/core routers (P2MP TE / multicast VPN deployments)

Monitoring Examples

An operator would poll cmplsTeP2mpTunnelTable (cmplsTeP2mpTunnelEntry) to compare cmplsTeP2mpTunnelConfigured against cmplsTeP2mpTunnelActive for a given tunnel, revealing whether a provisioned P2MP tunnel has actually come up. The cmplsTeP2mpTunnelDestTable lists each destination leaf of the tree, so a leaf missing from that table while cmplsTeP2mpTunnelTotalMaxHops looks normal would indicate a specific branch failed to signal even though the overall tunnel is nominally active. The cmplsTeP2mpTunnelBranchRole and cmplsTeP2mpTunnelP2mpIntegrity objects help diagnose whether a router node is acting as head/branch/leaf and whether the tree's signaling integrity is consistent, while cmplsTeP2mpNotifications would alert operators to tunnel state transitions without polling.

What Can Be Monitored

  • tunnel configured vs active state
  • destination leaf endpoints
  • branch role of node
  • total max hop count
  • P2MP tree signaling integrity
Imported Objects

From CISCO-SMI

ciscoExperimentOBJECT-IDENTITY

From DIFFSERV-MIB

IndexInteger
IndexIntegerNextFree

From IF-MIB

InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From MPLS-LSR-STD-MIB

MplsIndexType

From MPLS-TC-STD-MIB

MplsLabel
MplsPathIndexOrZero

From MPLS-TE-STD-MIB

mplsTunnelEgressLSRIdOBJECT-TYPE
mplsTunnelIndexOBJECT-TYPE
mplsTunnelIngressLSRIdOBJECT-TYPE
mplsTunnelInstanceOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

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

From SNMPv2-TC

RowStatus
StorageType
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using cmplsTeP2mpTunnelDestPathChanges OID:

Select a Cisco MPLS provider-edge/core router (P2MP TE) 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 cmplsTeP2mpTunnelDestPathChanges 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 counts the number of times the actual path for this destination of this P2MP tunnel instance has changed. 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

Manages MPLS Traffic Engineering point-to-multipoint tunnels based on the IETF draft standard.

Start monitoring Cisco MPLS provider-edge/core routers (P2MP TE) 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 CISCO-IETF-MPLS-TE-P2MP-STD-MIB