JnxL2L3VpnMcastPmsiTunnelAttributeEntry |
|
SEQUENCE |
|
|
|
|
jnxL2L3VpnMcastPmsiTunnelAttributeFlags |
OCTET STRING |
|
|
jnxL2L3VpnMcastPmsiTunnelAttributeType |
JnxL2L3VpnMcastProviderTunnelType |
|
|
jnxL2L3VpnMcastPmsiTunnelAttributeLabel |
MplsLabel |
|
|
jnxL2L3VpnMcastPmsiTunnelAttributeId |
OCTET STRING |
|
|
jnxL2L3VpnMcastPmsiTunnelPointer |
RowPointer |
|
|
jnxL2L3VpnMcastPmsiTunnelIf |
RowPointer |
|
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. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
JnxL2L3VpnMcastPmsiTunnelAttributeEntry |
|
|