L2L3-VPN-MCAST-MIB

All MIBs › L2L3-VPN-MCAST-MIB

Organization: IETF Layer-3 Virtual Private Networks Working Group.

Last Updated: 2012-11-05

Category: Standard: IETF, Technology: Multicast, Technology: VPN

Description: IETF MIB for managing multicast in Layer 2 and Layer 3 VPN environments, covering mVPN routing and multicast distribution trees.

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

L2L3-VPN-MCAST-MIB, in this instance, is built to the IETF's multicast-VPN model (per RFC 6513/6514 and the L2VPN/VPLS multicast draft) but implemented with Juniper's private 'jnx' object prefix, indicating it is Juniper's vendor implementation of that standards-based mVPN framework rather than a purely IETF module. It defines objects for PMSI (Provider Multicast Service Interface) tunnel attributes used to signal how multicast traffic is carried across a provider's Layer 2/Layer 3 VPN core, including tunnel type, flags, label, and the interface associated with the tunnel. Its monitoring role is focused on multicast VPN control-plane/software status: an operator can inspect the tunnel attributes to confirm a PMSI tunnel's type and label are correctly signaled and that the tunnel maps to the expected interface, which helps diagnose multicast traffic that fails to reach VPN sites. It has a clear and explicit dependency on IETF RFC 6513/6514 and the L2VPN/VPLS multicast draft standards, adapted into Juniper's private enterprise MIB tree. It is deployed on Juniper MX-series (or similar) provider-edge routers running multicast VPN services for enterprise or carrier customers. Network engineers evaluating or troubleshooting this functionality can download the L2L3-VPN-MCAST-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in L2L3-VPN-MCAST-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 provider edge router
Juniper routers running mVPN services

Monitoring Examples

An operator polls jnxL2L3VpnMcastPmsiTunnelAttributeTable / jnxL2L3VpnMcastPmsiTunnelAttributeEntry to inspect jnxL2L3VpnMcastPmsiTunnelAttributeType and jnxL2L3VpnMcastPmsiTunnelAttributeLabel for a given VPN, confirming the correct PMSI tunnel (e.g., an RSVP-TE P2MP tunnel) is signaled for multicast distribution. Checking jnxL2L3VpnMcastPmsiTunnelIf and jnxL2L3VpnMcastPmsiTunnelPointer against the expected outgoing interface helps identify a misconfigured or missing multicast distribution tree that would explain a customer site not receiving multicast streams.

What Can Be Monitored

PMSI tunnel type
PMSI tunnel label
PMSI tunnel attribute flags
PMSI tunnel interface mapping

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From JUNIPER-EXPERIMENT-MIB

jnxL2L3VpnMcastExperiment

OBJECT-IDENTITY

From JUNIPER-SMI

jnxMibs

OBJECT-IDENTITY

From MPLS-TC-STD-MIB

MplsLabel

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32
experimental

From SNMPv2-TC

RowPointer
RowStatus
TEXTUAL-CONVENTION
TimeInterval
TimeStamp
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
jnxL2L3VpnMcastMIB	1.3.6.1.4.1.2636.5.11.1			This MIB contains common managed object definitions for multicast in Layer 2 and Layer 3 VPNs, defined by [I-D.ietf-l2vpn-vpls-mcast] and RFC 6513/6514. Copyright (C) The Internet Society (2012).
jnxL2L3VpnMcastObjects	1.3.6.1.4.1.2636.5.11.1.1
jnxL2L3VpnMcastPmsiStates	1.3.6.1.4.1.2636.5.11.1.1.1
jnxL2L3VpnMcastPmsiTunnelAttributeTable	1.3.6.1.4.1.2636.5.11.1.1.1.1		not-accessible	This table is for advertised/received PMSI attributes, to be referred to by I-PMSI or S-PMSI table entries
jnxL2L3VpnMcastPmsiTunnelAttributeEntry	1.3.6.1.4.1.2636.5.11.1.1.1.1.1		not-accessible	An entry in this table corresponds to an PMSI attribute that is advertised/received on this router. For BGP-based signaling (for I-PMSI via auto-discovery procedure, or for S-PMSI via S-PMSI A-D routes), they are just as signaled by BGP (RFC 6514 section 5, 'PMSI Tunnel attribute'). For UDP-based S-PMSI signaling for PIM-MVPN, they're derived from S-PMSI Join Message (RFC 6513 section 7.4.2, 'UDP-based Protocol').. Note that BGP-based signaling may be used for PIM-MVPN as well.
OCT jnxL2L3VpnMcastPmsiTunnelAttributeFlags	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.1	OCTET STRING	not-accessible	For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. For BGP-based I/S-PMSI signaling, per RFC 6514 section 5, 'PMSI Tunnel Attribute': The Flags field has the following format: 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ \| reserved \|L\| +-+-+-+-+-+-+-+-+ This document defines the following flags: + Leaf Information Required (L)
JNX jnxL2L3VpnMcastPmsiTunnelAttributeType	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.2	JnxL2L3VpnMcastProviderTunnelType	not-accessible	For BGP-based I/S-PMSI signaling for either PIM or BGP-MVPN, per RFC 6514 section 5, 'PMSI Tunnel Attribute': The Tunnel Type identifies the type of the tunneling technology used to establish the PMSI tunnel. The type determines the syntax and semantics of the Tunnel Identifier field. This document defines the following Tunnel Types: 0 - No tunnel information present 1 - RSVP-TE P2MP LSP 2 - mLDP P2MP LSP 3 - PIM-SSM Tree 4 - PIM-SM Tree 5 - PIM-Bidir Tree 6 - Ingress Replication 7 - mLDP MP2MP LSP For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 does not specify if a PIM provider tunnel is SSM, SM or Bidir, and an agent can use either type 3, 4, or 5 based on its best knowledge.
MPL jnxL2L3VpnMcastPmsiTunnelAttributeLabel	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.3	MplsLabel	not-accessible	For BGP-based I/S-PMSI signaling, per RFC 6514 section 5, 'PMSI Tunnel Attribute': If the MPLS Label field is non-zero, then it contains an MPLS label encoded as 3 octets, where the high-order 20 bits contain the label value. Absence of MPLS Label is indicated by setting the MPLS Label field to zero. For UDP-based S-PMSI signaling for PIM-MVPN, this is not applicable for now, as RFC 6513 does not specify mpls encapsulation and tunnel aggregation with UDP-based signaling.
OCT jnxL2L3VpnMcastPmsiTunnelAttributeId	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.4	OCTET STRING	not-accessible	For BGP-based signaling, as defined in RFC 6514 section 5, 'PMSI Tunnel Attribute'. For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only specifies the 'P-Group' address, and that is filled into the first four octets of this field.
NUM jnxL2L3VpnMcastPmsiTunnelPointer	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.5	RowPointer	read-only	If the tunnel exists in some MIB table, this is the row pointer to it.
NUM jnxL2L3VpnMcastPmsiTunnelIf	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.6	RowPointer	read-only	If the tunnel has a corresponding interface, this is the row pointer to the ifName table.

RFC description

Juniper multicast in Layer 2/3 VPNs including MPLS tunneling and provider tunnels.

Start monitoring Juniper MX-series provider edge router (multicast VPN/PMSI tunnel attributes) 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 L2L3-VPN-MCAST-MIB

What Is L2L3-VPN-MCAST-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description