Hello Manami
First of all, it is difficult to dive right into a topology that has many different things going on at the same time. It is also difficult to troubleshoot by reviewing ten different configuration files without having the devices available to issue show and other verification commands. For this reason, I suggest you begin by creating topologies that build-up to this big one. For example:
- Begin by creating a topology with two PEs, two CEs, and one P and practice route leaking without adding anything else.
- Next, you can add an RR to the mix and see how that goes. Get it working and do extensive experimentation first, before you go on to the next step.
- Next you can disable IPv4 unicast and enable only VPNv4 address family on the same topology.
- Next add two more CEs and try some more complex route leaking scenarios
- Finally, build the whole topology and apply everything at the same time.
Doing it this way will ensure that you understand each concept and have implemented it successfully before incorporating it into a topology with additional features. It takes a long time, but it is the most effective. The important thing to understand is that the goal is not to make this particular topology work but to gain an understanding of the processes involved. Some lessons that will help you along the way include:
Rene doesn’t have a lesson where the RR is being implemented in an MPLS environment, but it should be helpful for you to apply. Some help for using an RR only for VPNv4 is found below:
router bgp 1
no bgp default ipv4-unicast
address-family ipv4
no neighbor x.x.x.x activate
address-family vpnv4
neighbor x.x.x.x route-reflector-client
This configuration will disable IPv4 unicast and will activate the RR for VPNv4 only.
Finally, about the “twist”, you can only import and export routes for the whole AS. If you want to limit traffic to a particular host, you will have to use ACLs.
I hope this has been helpful!
Laz