Partitioned RRs with IOS-XR

Load vpnv4.partitioned.rr.xr.init.cfg

#IOS-XE
config replace flash:vpnv4.partitioned.rr.xr.init.cfg 

#IOS-XR
configure
load bootflash:vpnv4.partitioned.rr.xr.init.cfg 
commit replace
y

This is the same as the previous lab, except the RR is moved from R6 to XR1. The CE, XR2, is peered with R6 now.

The L3VPN is fully setup. All PEs are peered with the two RRs. Configure R3 to only accept VPN_A routes and configure XR1 to only accept VPN_B routes.

Answer

Explanation

This lab tests your understanding of applying RT filters in IOS-XR.

As a review, in IOS-XE you can disable the RT filter in three ways:

  1. Configuring the VRF locally, and importing the RT

  2. Configuring the router as an RR

  3. Disabling the RT filter

To configure the IOS-XE router as a RR that selectively accepts VPNv4 updates, you use an RR group.

On IOS-XR, the same three methods are available for disabling the default RT filter:

  1. Configure the VRF locally and import the RT

  2. Configure the router as an RR

  3. Disable the RT filter

To selectively import VPNv4 prefixes on an IOS-XR RR, you simply associate a route-policy with the retain route-target command.

On XR1, we can see that the only VPNv4 routes in the table are for VPN_B:

If we debug bgp update we can see that the VPN_A routes are denied due to the RT filter:

Last updated