From: Brian on
We have a customer setup on a small MPLS network. The MPLS backbone
uses bgp, and the customer uses eigrp. Whenever the customer changes
or has a failure in their network, the default route that was learned
via bgp drops out and doesn't come back. It is overwritten by a higher
cost default route from their eigrp network.

Any ideas on how to make sure that the preferred or lowest cost route
is always used?

Thanks,
Brian
From: John Agosta on

"Brian" <blncrew(a)gmail.com> wrote in message
news:0332cde5-db33-44d1-a5de-c24af8caf111(a)c10g2000vbr.googlegroups.com...
> We have a customer setup on a small MPLS network. The MPLS backbone
> uses bgp, and the customer uses eigrp. Whenever the customer changes
> or has a failure in their network, the default route that was learned
> via bgp drops out and doesn't come back. It is overwritten by a higher
> cost default route from their eigrp network.
>
> Any ideas on how to make sure that the preferred or lowest cost route
> is always used?
>
> Thanks,
> Brian


Your description of the problem could be more detailed.
However, you may need to tweak the admin distance for the BGP route which
gets redistributed into the EIGRP domain to make that particular route look
prefered ........


From: Brian on
On Feb 24, 1:49 pm, "John Agosta" <jago...(a)wideopenwest.com> wrote:
> "Brian" <blnc...(a)gmail.com> wrote in message
>
> news:0332cde5-db33-44d1-a5de-c24af8caf111(a)c10g2000vbr.googlegroups.com...
>
> > We have a customer setup on a small MPLS network. The MPLS backbone
> > uses bgp, and the customer uses eigrp. Whenever the customer changes
> > or has a failure in their network, the default route that was learned
> > via bgp drops out and doesn't come back. It is overwritten by a higher
> > cost default route from their eigrp network.
>
> > Any ideas on how to make sure that the preferred or lowest cost route
> > is always used?
>
> > Thanks,
> > Brian
>
> Your description of the problem could be more detailed.
> However, you may need to tweak the admin distance for the BGP route which
> gets redistributed into the EIGRP domain to make that particular route look
> prefered ........

We are having an ongoing problem with BGP to EIGRP redistribution on
a
particular VPN within our MPLS Network and would like a quote on
technical support from your company.

The devices involved include 2x Cisco 7200 NPE-G1s acting as PE, and
two
Cisco 2800 Series acting as CE.

CE1 - EIGRP - announces default route
PE1 - EIGRP redistributed into an VPNV4 BGP TABLE
PE2 - VPNV4 BGP is redistributed into a EIGRP process to the customer
CE2 - EIGRP

The route is visible in the EIGRP Database on CE1 and PE1 and in the
BGP
tables on PE1 and PE2.

Unfortunately, this only happens when the customer flaps the route
behind CE1 (they test their failover to another MPLS network) -- when
this happens, the route drops off of the EIGRP database at PE2 and
therefore never makes it to CE2. To resolve the issue, a "CLEAR IP
ROUTE VRF VRFNAME 0.0.0.0 0.0.0.0" command is issued and the route
reappears in both the EIGRP database of PE2 and in the route tables of
CE2