[j-nsp] NG-MVPN + Anycast RP

[Amos Thong]

Hi Marco,  
 
We are running Anycast RP in an NG-MVPN routing instance. 
Something to note : 
- we collapse the sender PE router and RP into several routers. 
- The RPs are of the same ip address ( therefore anycast ) and hanging off a lo.1 which we put in the NG-MVPN  separated from lo.0 which use for other non RP function. - The RR ( a juniper in our case ) need to be M-CAST NLRI aware to do the MVPN signaling. To turn it on you need "family inet-mvpn signaling". - In the NG-MVPN the BGP route type 5 , 6  replaces the traditional PIM signaling.  It is basically  PIM in disguish of BGP.  RegardsAmos -----Original Message-----

From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Marco
Marzetti

Sent: Sunday, November 1, 2015 4:27 AM

To: juniper-nsp at puck.nether.net

Subject: [j-nsp] NG-MVPN + Anycast RP

 

Hello,

 

Is PIM-based Anycast RP (RFC4610) supposed to work in an
NG-MVPN routing instance?

 

I mean, let's just say that a PE receives a BGP route type
6 from another router and installs the equivalent PIM join in the control
plane.

Is this PE supposed to relay (actually send) that join to
the other PEs in its rp-set through PIM?

 

An hypothetical configuration would look like:

 

instance-type vrf;

interface ge-0/0/1.2

interface lo0.2;

route-distinguisher 192.0.2.1:2;

provider-tunnel {

    rsvp-te {

       
label-switched-path-template {

           
c2-template;

        }

    }

}

vrf-import vpn-c2-import;

vrf-export vpn-c2-export;

vrf-table-label;

protocols {

    pim {

        rp {

            local {

               
family inet {

                   
address 192.0.2.254;

                   
priority 10;

                   
anycast-pim {

                       
rp-set {

                            address 192.0.2.2;

                       
}

                       
local-address 192.0.2.1;

                   
}

                }

            }

        }

        interface
all {

            mode
sparse;

            version
2;

        }

    }

    mvpn {

    }

}