L2L3-VPN-MCAST-MIB: View SNMP OID List / Download MIB

VENDOR: JUNIPER

Home	MIB: L2L3-VPN-MCAST-MIB
Download as:		SNMPv2-CONF, SNMP-FRAMEWORK-MIB, SNMPv2-SMI, MPLS-TC-STD-MIB, JUNIPER-EXPERIMENT-MIB, JUNIPER-SMI, INET-ADDRESS-MIB, SNMPv2-TC		Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash). Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded. The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.

Object Name	OID	Type	Access	Info
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		no-access	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		no-access	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.
jnxL2L3VpnMcastPmsiTunnelAttributeFlags	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.1	octet string	no-access	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)
jnxL2L3VpnMcastPmsiTunnelAttributeType	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.2	jnxl2l3vpnmcastprovidertunneltype	no-access	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.
jnxL2L3VpnMcastPmsiTunnelAttributeLabel	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.3	mplslabel	no-access	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.
jnxL2L3VpnMcastPmsiTunnelAttributeId	1.3.6.1.4.1.2636.5.11.1.1.1.1.1.4	octet string	no-access	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.
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.
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.