NGN-MVPN in JUNOS. IP multicast has been serving the need in the field since long time. The only thing is it totally depends on the IGP for the failover. MPLS has been growing in deployment in the field and providing robust technology or application like Layer 3, Layer 2 VPNs as well as VPLS kind of services and MPLS Traffic engineering to achieve the faster failover. It will be great to have same kind of behavior for the multicast traffic and NGN MVPN with RSVP extension for point to multipoint LSP provides the labeled multicast capability. In following base topology we have multicast source connected to the PE1 router and have two interested receiver connected to the PE2 and PE3 router. 1. Base topology   3. IBGP MVPN signaling  4. IGP and BGP redistribution under routing-instance/VRF  5. PIM Join and BGP Routes:   7. MP-BGP NENMVPN specific routes:  8. PMSI (kind of Default MDT)  9.S-PMSI BGP signaling (Route Type-3 & Type-4)  10. S-PMSI (kind of Data MDT)  Condition to generate Type-5: 1. PE Router should be RP and should be receiving PIM source register messages from source DR. 2. PE should be running MSDP with RP in customer environment to receive Source Active messages. 3. PE should be a DR for the interface connected to upstream router or source. Type-7 and Type-4: Type-7 will be generated by receiver PE after it receives the Type-5 routes from source PE. Type-7 can be sent in absence of Type-5 in case of SSM deployment. Similarly Type-4 will be generated by receiver PE after it receives the Type-3 from source PE to build Selective Tree or Selective PMSI (S-PMSI). MVPN summary: 1. Types MVPN: There are multiple types of MVPNs. Two of them are based on draft Rosen which uses the PIM or BGP as signalling protocol but PIM as a data plane. Other two types are called NGN MVPN which uses the MPLS labeling in data plane, we can use RSVP or mLDP protocol to distribute labels. In NGN MVPN control information is exchanged using BGP. 2. In both Rosen based MVPN you need to enable the PIM in service provider core. 3. In draft Rosen there are two types of tunnel: Default and Data MDT. 4. In NGN MVPN also we have two type of tunnel, Inclusive PMSI (I-PMSI, its similar to Default MDT) & Selective PMSI (S-PMSI, its similar to Data MDT built to only interested receivers). 5. Type 4 (Used in S-PMSI), Type 6 and Type 7 are generated by receiver PE. 6. Type 3 and Type 5 are generated by source PE. 7. JUNOS source PE sends individual path messages for each spoke or receiver and expect the same number of RESV messages. A P2MP LSP is identified by a combination of <P2MP ID, Tunnel ID, Ext Tunnel ID> from P2MP SESSION object and tunnel sender address and LSP ID of P2MP SENDER_TEMPLATE object. This Sub-group fields from S2L SUB-LSPs along with above mentioned parameters define the state of a particular leaf Feb 25 12:25:01.160726 RSVP send Path 192.168.1.200->200.200.200.2 Len=264 ge-0/0/0.0 Feb 25 12:25:01.160753 Session13 Len 16 192.168.1.200(port/tunnel ID 33134 Ext-ID 192.168.1.200) Proto 0 Feb 25 12:25:01.160906 Sender12 Len 20 P2MP Sender 192.168.1.200(port/lsp ID 1, branch ID 2) SubGrpOrg ID 0xc0a801 8. PMSIs can be dynamic or statically configured. 9. Route reflectors can be used to address scaling in ISP network. 10. There is no VPN label or multicast traffic in MPLS is not dual tag traffic, it uses the context based label, in other words PMSI MPLS label is bind to appropriate routing-instance or VRF. 11. As there is no VPN label, there is no PHP behavior in NGN-MVPN MPLS forwarding. 12. In case of dual homing of source PE with same source address, two different source PE will advertise same source and group information to receiver PE, receiver PE then use UMH procedure to elect the source based on highest RID of source PE by default. 13. To generate source information route or Type 5, source PE should receiver source information, it can be achieve by making source PE as RP of receiver or running MSDP. 14. In case of SSM deployment in NGN MVPN, receiver PE will advertise type 7 with out waiting or receiver Type 5 as in case of SSM, source information is already present in PIM/IGMP joins. 15. Draft Rosen 6 is ASM model and Draft Rosen 7 is used for SSM model. 16. Benefit of MVPN with RSVP TE is to have FRR/protection capabilities of millisecond as compare to traditional MVPN and mLDP. 17. RSVP-TE allows more control of network path. Other JUNOS knobs for MVPN: Under PIM: accept-remote-source Under protocol mvpn: MVPN Mode: rpt-spt mode unicast-umh-election <<< Used in multihoming of NGMVPN to select one designated forwarder. receiver-site sender-site For NGMVPN Extranet: set routing-instance <instance-name> routing-options auto-export Use VT interface: set routing-instance <instance-name> interface vt-x/y/z.w multicast troubleshooting and verification commands: You might have to capture the following commands multiple time to locate the incrementing counters. show pim interface instance <instance-name> | no-more show pim join extensive instance <instance-name> | no-more show pim rps details instance <instance-name> | no-more show pim neighbor instance <instance-name> | no-more show multicast route extensive instance <instance-name> | no-more show route table <instance-name>.inet.0 | no-more show route table <instance-name>.inet.1 | no-more show route table <instance-name>.mvpn.0 | no-more show mpls lsp p2mp | no-more show mpls lsp p2mp extensive | no-more show mpls lsp | no-more show rsvp session p2mp | no-more show rsvp session p2mp extensive | no-more show bgp summary | no-more |