L2L3-VPN-MCAST-MIB

File: L2L3-VPN-MCAST-MIB.mib (8118 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF SNMPv2-TC
SNMP-FRAMEWORK-MIB INET-ADDRESS-MIB MPLS-TC-STD-MIB
JUNIPER-SMI JUNIPER-EXPERIMENT-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
experimental Unsigned32 MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP TEXTUAL-CONVENTION
TruthValue RowPointer RowStatus
TimeStamp TimeInterval SnmpAdminString
InetAddress InetAddressType MplsLabel
jnxMibs jnxL2L3VpnMcastExperiment

Defined Types

JnxL2L3VpnMcastProviderTunnelType  
Types of provider tunnels used for multicast in a l2/l3vpn.
TEXTUAL-CONVENTION    
  INTEGER unconfigured(0), rsvp-p2mp(1), ldp-p2mp(2), pim-ssm(3), pim-asm(4), pim-bidir(5), ingress-replication(6), ldp-mp2mp(7)  

JnxL2L3VpnMcastPmsiTunnelAttributeEntry  
SEQUENCE    
  jnxL2L3VpnMcastPmsiTunnelAttributeFlags OCTET STRING
  jnxL2L3VpnMcastPmsiTunnelAttributeType JnxL2L3VpnMcastProviderTunnelType
  jnxL2L3VpnMcastPmsiTunnelAttributeLabel MplsLabel
  jnxL2L3VpnMcastPmsiTunnelAttributeId OCTET STRING
  jnxL2L3VpnMcastPmsiTunnelPointer RowPointer
  jnxL2L3VpnMcastPmsiTunnelIf RowPointer

Defined Values

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).
MODULE-IDENTITY    

jnxL2L3VpnMcastObjects 1.3.6.1.4.1.2636.5.11.1.1
OBJECT IDENTIFIER    

jnxL2L3VpnMcastPmsiStates 1.3.6.1.4.1.2636.5.11.1.1.1
OBJECT IDENTIFIER    

jnxL2L3VpnMcastPmsiTunnelAttributeTable 1.3.6.1.4.1.2636.5.11.1.1.1.1
This table is for advertised/received PMSI attributes, to be referred to by I-PMSI or S-PMSI table entries
OBJECT-TYPE    
  SEQUENCE OF  
    JnxL2L3VpnMcastPmsiTunnelAttributeEntry

jnxL2L3VpnMcastPmsiTunnelAttributeEntry 1.3.6.1.4.1.2636.5.11.1.1.1.1.1
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.
OBJECT-TYPE    
  JnxL2L3VpnMcastPmsiTunnelAttributeEntry  

jnxL2L3VpnMcastPmsiTunnelAttributeFlags 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.1
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)
OBJECT-TYPE    
  OCTET STRING Size(1)  

jnxL2L3VpnMcastPmsiTunnelAttributeType 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.2
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.
OBJECT-TYPE    
  JnxL2L3VpnMcastProviderTunnelType  

jnxL2L3VpnMcastPmsiTunnelAttributeLabel 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.3
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.
OBJECT-TYPE    
  MplsLabel  

jnxL2L3VpnMcastPmsiTunnelAttributeId 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.4
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.
OBJECT-TYPE    
  OCTET STRING Size(0..37)  

jnxL2L3VpnMcastPmsiTunnelPointer 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.5
If the tunnel exists in some MIB table, this is the row pointer to it.
OBJECT-TYPE    
  RowPointer  

jnxL2L3VpnMcastPmsiTunnelIf 1.3.6.1.4.1.2636.5.11.1.1.1.1.1.6
If the tunnel has a corresponding interface, this is the row pointer to the ifName table.
OBJECT-TYPE    
  RowPointer