In the topology below we’re still running iBGP between R8 and R7, and the goal is to run EIGRP as the internal customer routing protocol. We’ll be redistributing EIGRP into the BGP process that is then crossed over VPNv4.
First we’ll create EIGRP domains on each customer site. R7<–>R9 and R8<–>R10 EIGRP adjacencies will be formed in VRF A. Below will have R7 and R9 but R8 and R10 will be identical.
R9 will have a normal EIGRP configuration advertising all networks (0.0.0.0).
And R7 will have a similar configuration except it will setup the EIGRP config in VRF A
The interface connected to R9 has already been assigned VRF A and has an IP applied. Because of this the neighbor adjacency comes up. Note- we’re not creating an adjacency with R3 which is part of the P network, hence the smaller network statement on R9, our PE.
The adjacency can be seen with a ‘show ip eigrp vrf A neighbor’.
The configuration for iBGP over the MPLS domain is already setup between R7 and R8, and that can be seen with a simple ‘show ip bgp summary’. In addition, our VRF already has the Route Distinguisher and Route Targets imported and exported, as seen below:
So now to advertise EIGRP routes over the BGP tunnel, we just need to redistribute between the two routing protocols.
EIGRP into BGP:
BGP into EIGRP:
Note this needs to be completed under ‘address-family ipv4 vrf A’.
Now- when checking the global routing table of R10 (across iBGP and MPLS domain), we see that the Loopback for R9 is in the routing table.
This can also be seen from the BGP VPNv4 table – ‘show ip bgp vpnv4 all’
Note- these routes are showing up as internal routes instead of external for both routing protocols.
For EIGRP this allows feasibility condition to be spread across sites.