L2L3 VPN Multicast MIB
Extracted elements (21)
The MIB modules are designed as a shared foundation to be used by other MIB modules rather than as standalone monitoring tools. This avoids duplication of P-tunnel type and identifier definitions across per-technology MIBs for L2 VPN (RFC 7117) and L3 VPN (RFC 6513) multicast.
The l2L3VpnMcastPmsiTunnelAttributeTable is designed to be used in conjunction with other MIBs such as MPLS-TE-STD-MIB (RFC 3812) via l2L3VpnMcastPmsiTunnelPointer and IF-MIB (RFC 2863) via l2L3VpnMcastPmsiTunnelIf, enabling cross-table lookups for complete P-tunnel configuration and interface information.
Implementations claiming compliance to SNMPv3 MUST include full support for authentication and privacy via the User-based Security Model (USM) with the AES cipher algorithm (RFC 3826).
Implementations MAY also provide support for the Transport Security Model (TSM) in combination with a secure transport such as SSH (RFC 5592) or TLS/DTLS (RFC 6353).
Implementations SHOULD provide SNMPv3 security features, and deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. SNMPv3 with cryptographic security is RECOMMENDED instead.
L2L3-VPN-MULTICAST-MIB defines l2L3VpnMcastPmsiTunnelAttributeTable, where each entry represents the PMSI Tunnel attribute information of a specific P-tunnel on a PE router. The table is indexed by (l2L3VpnMcastPmsiTunnelAttributeType, l2L3VpnMcastPmsiTunnelAttributeId) to uniquely identify a P-tunnel.
L2L3-VPN-MULTICAST-TC-MIB defines two textual conventions: L2L3VpnMcastProviderTunnelType (enumeration of P-tunnel types) and L2L3VpnMcastProviderTunnelId (identifier of a P-tunnel). These TCs are intended for reuse by other MIB modules monitoring or configuring L2L3VpnMCast networks.
l2L3VpnMcastPmsiTunnelAttributeMplsLabel is a read-only MplsLabel object representing the MPLS Label in the PMSI Tunnel attribute. Its value is zero when the P-tunnel has no PMSI Tunnel attribute.
l2L3VpnMcastPmsiTunnelIf is a read-only RowPointer pointing to the corresponding row in ifXTable (RFC 2863) if the P-tunnel has an associated interface entry. It defaults to zeroDotZero when no such entry exists.
l2L3VpnMCastPmsiTunnelLeafInfoRequired is a read-only integer object with values false(0), true(1), or notAvailable(2). When true, it indicates the originating PE requests receivers to send a new Leaf A-D route; notAvailable is used when the P-tunnel has no corresponding PMSI Tunnel attribute.
l2L3VpnMcastPmsiTunnelPointer is a read-only RowPointer that references the corresponding entry in another table (e.g., mplsTunnelTable per RFC 3812) for additional P-tunnel details. It defaults to zeroDotZero when no such entry exists.
L2L3VpnMcastProviderTunnelType enumerates nine P-tunnel types: noTunnelInfo(0), rsvpP2mp(1), ldpP2mp(2), pimSsm(3), pimAsm(4), pimBidir(5), ingressReplication(6), ldpMp2mp(7), and transportTunnel(8). These are aligned with IANA-registered Tunnel Types defined in RFC 6514 Section 5 and RFC 7524 Section 14.1.
Two conformance levels are defined: l2L3VpnMcastCoreCompliance (mandatory objects: l2L3VpnMCastPmsiTunnelLeafInfoRequired and l2L3VpnMcastPmsiTunnelAttributeMplsLabel) and l2L3VpnMcastFullCompliance (adds optional group with l2L3VpnMcastPmsiTunnelPointer and l2L3VpnMcastPmsiTunnelIf).
IANA assigned two OBJECT IDENTIFIER values in the 'SMI Network Management MGMT Codes Internet-standard MIB' registry: l2L3VpnMcastTCMIB (L2L3-VPN-MULTICAST-TC-MIB) at { mib-2 244 } and l2L3VpnMcastMIB (L2L3-VPN-MULTICAST-MIB) at { mib-2 245 }.
The MIB modules define no read-write or read-create objects, so direct SNMP SET attacks cannot alter or create management objects. However, read access to l2L3VpnMcastPmsiTunnelAttributeTable reveals P-tunnel topology information including identifiers composed of source and multicast group IP addresses, and pointers to configuration/performance tables; these should be considered sensitive and access-controlled.
For ingressReplication(6), the Tunnel Identifier is the unicast tunnel endpoint IP address of the local PE: 4 octets in IPv4 and 16 octets in IPv6.
For ldpP2mp(2) and ldpMp2mp(7), the Tunnel Identifier is the P2MP or MP2MP FEC Element per RFC 6388, with a size of 17 octets in IPv4 and 29 octets in IPv6.
For pimSsm(3), pimAsm(4), and pimBidir(5), the Tunnel Identifier is composed of the source IP address and the group IP address: 8 octets in IPv4 and 32 octets in IPv6.
For rsvpP2mp(1), the Tunnel Identifier consists of an Extended Tunnel ID (4 octets IPv4 / 16 octets IPv6), 2 reserved octets set to zero, a Tunnel ID (2 octets), and a P2MP ID (4 octets), totaling 12 octets in IPv4 and 24 octets in IPv6.
For transportTunnel(8), the Tunnel Identifier is a tuple of Source PE Address and Local Number (unique to the source PE per RFC 7524), each 4 octets in IPv4 or 16 octets in IPv6, totaling 8 or 32 octets respectively.
L2L3VpnMcastProviderTunnelId is an OCTET STRING with size constrained to (0|4|8|12|16|17|24|29|32) octets. The actual size depends on address family (IPv4 or IPv6) and the corresponding tunnel type; for example, rsvpP2mp is 12 octets in IPv4 and 24 in IPv6, while ingressReplication is 4 octets (IPv4) or 16 octets (IPv6).