this is configured on PE routers, however most of our providers for our customers are reporting they do not support it. Aside from buidling DMVPN tunnels over the MPLS network to all my locations, is it possible to configure this solution on our CE routers?
Thanks Guiseppe. I've brought this up before in prior postings for which you replied already. The EIGRP PE-CE was a solution we have tried to push with the providers but they don't do it. I am limited to EIGRP due to our data center configuration. Our spokes use the MPLS eBGP path to our HQ where we have a VPN tunnel for datacenter traffic. However if that fails, the spokes have their own vpn tunnels which can only run eigrp. This is becoming a big problem and I've pushed for solutions, however its become mismash of configs to make this work. Were running 2 instances of EIGRP on the spokes and redistributing from one EIGRP into another so that the advertisement up the backup tunnel to the data center shows up as 170 EIGRP. The HQ VPN tunnel is also running EIGRP. THe spokes and hub talk over eBGP and we redistribute back into EIGRP. Its a mess. The EIGRP PE-CE is the only solution that seems clean and viable however noone wants to do it.
So 1 we can either redistribute between EIGRP to change the admin distance, or run a tunneling solution over the MPLS eBGP network to preserve EIGRP administrative distances.
All sites that have GRE IPSEC tunnels have to run EIGRP as that's what the data center runs. The spokes have backup IPSEC+GRE tunnels to the Data centers and EIGRP runs across this. Data center won't run BGP to customer sites. That's where I am stuck. I can force the EIGRP admin distance to 170 up to the data center by redistributing from EIGRP into EIGRP but again this is messy and redistribution makes me ill. :D
So yea, I'm really stuck right now on what I can do.
I am also trying to somehow tag routes from my backup tunnel at the hub so I can deny those routes at some spokes but not others. Since the MPLS connected router runs EIGRP and BGP trying to figure out how to tag routes on the backup tunnel when they come in, then tage them again when redistributed into BGP from the hub to the spokes. I want to deny these backup routes for some spokes but not others and dont know how.
Sprint supports EIGRP on their Global L3VPN product. Cisco's BGP cost community implementation with EIGRP works pretty well in terms of minimizing routing loops but convergence/transient loop conditions can still be an issue without appropriate filtering when backdoor routes are involved. EIGRP SoO on the PEs was not supported when I worked over there thus requiring you to still utilize route tagging and filtering on the CE side.
This document is an early notification of a behaviour change that will be introduced in IOS XR release 6.5.
IOS XR configuration principles relevant for this article are:
On router platforms all interfaces must be by defaul...
With XR 4.2.0 the ASR9000 is releasing a new line of hardware models. This amongst others is the RSP440, the next generation RSP with faster switch fabric along with Typhoon based Linecards, the next generation network processor.
The Cisco EPN system incorporates a network architecture designed to consolidate multiples services on a single Multiprotocol Label Switching (MPLS) transport network. This network is designed primarily based on Application ...