MPLS Layer 3 VPN PE-CE EIGRP

Hello Fabio,

Good question, this is something that MPLS VPN does. Here’s an article from Cisco that explains it:

https://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/seipecec.html

the EIGRP routes in Site 1 are carried through the BGP core network as iBGP routes. The EIGRP routes in “Site 1” and “Site 2” are converted to iBGP routes and EIGRP extended community attributes are appended to the iBGP routes. (See Table 1 for a description of these attributes.) The EIGRP extended community attributes are appended to the EIGRP routes when they are redistributed into BGP as iBGP routes, and VPN routing information is redistributed between the PE routers by multiprotocol BGP.

The routes that originate in “Site 1” travel to the PE router that is connected to the CE router in “Site 2” of the VPN and are then converted back to EIGRP routes using the EIGRP extended community attributes. EIGRP routes are treated the same in “Site 1” and “Site 2.” If the route is internal in “Site 1”, it will be internal in “Site 2”, and if the route is external in “Site 1”, it will be external in “Site 2.” All EIGRP metrics are preserved, and EIGRP metric information, along with the autonomous system, tag, and external data, is carried across the VPN over the BGP core network.

EIGRP routes are converted to iBGP routes on the PE router by appending EIGRP extended community attributes. The PE router uses multiprotocol BGP to distribute the VPN routing information using the these extended community attributes. The BGP routes are converted back to EIGRP routes using the extended community attribute information when the iBGP routes reach the PE router that is connected to the destination CE router.

Hope this helps!

Rene

1 Like