Alcatel-Lucent 7750 SR - Table 24: Supported Configuration Combinations

Virtual Private Routed Network Services
7750 SR OS Services Guide Page 1087
The Alcatel-Lucent implementation supports the following features:
• MVPN membership auto-discovery using BGP
• PE-PE Transmission of C-Multicast Routing using BGP
• IPv4 support
• Use of PIM default and data MDTs as PMSIs
• Inter-AS support with direct VRF connect (option A)
• Backward compatibility with existing Rosen implementation to provide an easy migration
path
MVPN Membership Auto-discovery using BGP
BGP-based auto-discovery is performed by an multicast VPN address family. Any PE that
attaches to an MVPN must issue a BGP update message containing an NLRI in this address
family, along with a specific set of attributes.
The PE router uses route targets to specify MVPN route import and export. The route target may
be the same as the one used for the corresponding unicast VPN, or it may be different. The PE
router can specify separate import route targets for sender sites and receiver sites for a given
MVPN.
The route distinguisher (RD) that is used for the corresponding unicast VPN can also be used for
the MVPN.
When BGP auto-discovery is enabled, PIM peering on the I-PMSI is disabled, so no PIM hellos
are sent on the I-PMSI. C-trees to P-tunnels bindings are also discovered using BGP S-PMSI AD
routes, instead of PIM join TLVs. Configure PIM join TLVs when c-mcast-signaling is set to pim
in the config>service>vprn>mvpn>provider-tunnel>selective>auto-discovery-disable
context.
Table 24 and Table 25 describe the supported configuration combinations. If the CLI combination
is not allowed, the system returns an error message. If the CLI command is marked as “ignored” in
the table, the configuration is not blocked, but its value is ignored by the software.
Table 24: Supported Configuration Combinations
Auto-Discovery Inclusive PIM SSM Action
Yes Yes Allowed
No Yes Not Allowed
Yes or No No Allowed