Cisco ASR 9000 Series Software Manual page 35

Implementing Layer-3 Multicast Routing on Cisco IOS XR Software
• All PEs must have a unique BGP Route Distinguisher (RD) value. To configure BGP RD value, refer
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide .
Configuration rules for profiles
Rules for Rosen-mGRE profiles (profiles- 0, 3, 11)
• All profiles require VPNv4 or v6 unicast reachability.
• By default, encap 1400-byte size c-multicast IP packet is supported. To support decap or encap larger
packet size, mdt mtu command.
• Loopback configuration is required. Use the mdt source loopback0 command. Other loopbacks can
be used for different VRFs, but this is not recommended.
Rules for Rosen-mLDP profiles (profiles- 1, 9, 12, 13, 17)
• mLDP must be globally enabled.
• VPN-id is mandatory for Rosen-mLDP MP2MP profiles.
• Root node must be specified manually. Multiple root nodes can be configured for Root Node Redundancy.
• If only profile 1 is configured, MVPN must be enabled under bgp.
• For BGP-AD profiles, the remote PE address is required.
Rules for mLDP profiles (profiles- 2, 4, 5, 14, 15)
• MVPN must be enabled under bgp, if only profile 2 is configured.
• Support only for static RP for customer RP.
Rules for inband mLDP profiles (profiles- 6, 7)
• MVPN must be enabled under bgp for vrf-inband profiles.
• Data MDT is not supported.
• Backbone facing interface (BFI) must be enabled on tail PE.
• Source route of SSM must be advertise to tail PE by iBGP.
MLDP inband signaling
MLDP Inband signaling allows the core to create (S,G) or (*,G) state without using out-of-band signaling
such as BGP or PIM. It is supported in VRF (and in the global context). Both IPv4 and IPv6 multicast groups
are supported.
In MLDP Inband signaling, one can configure an ACL range of multicast (S,G). This (S,G) can be transported
in MLDP LSP. Each multicast channel (S,G), is 1 to 1 mapped to each tree in the inband tree. The (S,G) join,
through IGMP/MLD/PIM, will be registered in MRIB, which is the client of MLDP.
MLDP In-band signalling supports transiting PIM (S,G) or (*,G) trees across a MPLS core without the need
for an out-of-band protocol. In-band signaling is only supported for shared-tree-only forwarding (also known
as sparse-mode threshold infinity). PIM Sparse-mode behavior is not supported (switching from (*,G) to
(S,G).
Label Switched Multicast (LSM) Multicast Label Distribution Protocol (mLDP) based Multicast VPN (mVPN) Support
Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide, Release 5.1.x
35