NG-MVPN to Loopback Interface

Figure 1. NG-MVPN Setup Via Loopback Interface

SystemIP is usually used for management purposes and, as such, it might be desired to create services to a separate loopback interface. Due to security concerns, many operators do not want to create services to the systemIP address. See Figure 1 and Figure 2.

The first portion of this feature will allow MVPN routes be advertised with a nexthop specific loopback.

This can be achieved via two methods:

1. Having IBGP session to the loopback interface of the peer, and using the corresponding local loopback for local-address.

2. Having IBGP session to the systemIP but using policies to change the nexthop of the AD route to the corresponding loopback interface.

After the AD routes are advertised via the loopback interface as nexthop, PIM will generate an mLDP FEC for the loopback interface.

The preceding configuration will allow an NG-MVPN to be established via a specific loopback.

Figure 2. Intra-AS Basic Opaque FEC to Loopback Interface

It should be noted that this setup will work in a single area or multi-area through an ABR.