Configuration Example

Figure 1. Core Diversity with Parallel NG-MVPN Services on Parallel IGP Instances

In Figure 1, there are three IGP instances, the default Instance 0, Instance 1, and Instance 2. Each instance will bind to its own loopback interface. For Instance 0, it will be the systemIP system Interface used as loopback. LDP, RSVP and MP-BGP need to run between the corresponding loopback associated with each instance.

For example, for the blue Instance 2, both MP-BGP and LDP need to be configured to its corresponding loopback loopback2 and the next-hop for BGP MVPN-IP4/IPv6 and the VPN-IPv4/IPv6 need to be loopback2.

From a configuration point of view, the following steps need to be taken:

1. For MLDP, configure LDP with local-lsr-id with loopback interface of instance 2 loopback2:

   *A:SwSim14>config>router>ldp# info 
   
         interface-parameters
            interface ‟2ROOT” dual-stack
              ipv4
                local-lsr-id interface-name ‟loopback2”
                 no shutdown
              exit
              no shutdown
            exit
   

2. Enable the source-address for default auto discover as follows:

   *A:Dut-A>config>service>vprn 2
         mvpn auto-discovery default source-address LOOPBack1
         vrf-export ‟vprnexp100”
   *A:Dut-A>config>service>vprn 3
         mvpn auto-discovery default source-address LOOPBack2
         vrf-export ‟vprnexp101”
   

3. Define community vprnXXXX for each VPRN using non-default core-instance and define a policy to tag each VPRN with either a blue or red standard community attribute:

   *A:Dut-A>config>router>policy-options# info
           community "vprn2" members "target:70:70"
           community "vprn3" members "target:80:80"
           policy-statement "vprnexp2"
               entry 10
                   from
                      protocol direct
                   exit
                   action accept
                      community add "vprn2" "red"
                   exit
               exit
           policy-statement "vprnexp3"
               entry 10
                   from
                      protocol direct
                   exit
                   action accept
                      community add "vprn3" "blue"
                   exit
               exit
           exit
   

4. Define a single global BGP policy to change next hop for red/blue MVPNs:

   *A:Dut-A>config>router>policy-options# info
           policy-statement "MVPN_CoreDiversity_Exp"
               entry 10
                   from
                      community "red"
                   exit
                   to
                      protocol bgp-vpn
                   exit
                   action accept
                        next-hop loopback1
                   exit
               exit
               entry 20
                   from
                      community "blue"
                   exit
                   to
                      protocol bgp-vpn
                   exit
                   action accept
                        next-hop loopback2
                   exit
               exit
           exit
   

5. Configure BGP default MVPN export in the group as required:

   configure router bgp group "mvpn" export "MVPN_CoreDiveristy_Exp"
   

6. Configure each VPRN to use proper IGP source address and proper VRF export policy:

   *A:Dut-A>config>service>vprn 2
         mvpn auto-discovery default source-address loopback1
         vrf-export "vprnexp2"
   *A:Dut-A>config>service>vprn 3
         mvpn auto-discovery default source-address loopback2
         vrf-export "vprnexp3"