A fire district attaches a township that already standardized on EIGRP at the edge to an MPLS L3VPN PE. Which concern should designers keep in mind at a conceptual level?
Select an answer to reveal the explanation.
Short Explanation
EIGRP on the PE-CE link is fine when the township already speaks it—but watch for routing loops when sites reconnect through the VPN. Site-of-Origin style protections are part of that story. EIGRP at the edge doesn’t delete RD/RT or replace MP-BGP in the core.
Full Explanation
EIGRP can serve as a PE-CE protocol for VRFs when edge domains are already EIGRP-based. Designers must account for loop-prevention behaviors such as Site-of-Origin when multipath or multihomed VPN topologies could reintroduce routes. RD/RT and MP-BGP between PEs remain required for the L3VPN control plane; EIGRP PE-CE does not replace them.