cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
619
Views
5
Helpful
3
Replies

How to allow different BGP metrics be reflected in the redistribution into EIGRP

Jeff Stephenson
Level 1
Level 1

I have multiple Corporate WAN edge routers (for resiliency) running both BGP (outside) and EIGRP (inside) connected to multiple internal corporate routers.   WAN edge routers have 2 BGP peers, (outside) and multiple equal cost EIGRP peers (inside).

One BGP peer is going into a MPLS cloud and the other BGP peer is going to a Internet Firewall, and is used so the internet can be used as remote WAN network backup.  The Internet Firewall bgp peer has AS Prepends to increase the AD of the learned networks through that path.   Also there are certain policies to only allow certain remote subnets.

This design works well if the remote location loses it's connection to the MPLS cloud.  We discovered that it causes issues if the Corporate router loses it's MPLS circuit/BGP peer. 

Because we are redistributing routes from the common BGP AS into EIGRP with the same metric, traffic is still sent to this router and the some traffic is blacked holed because of the "backup policies".

We have other WAN Edge routers that still have connections to the MPLS cloud and we would prefer traffic take those paths.

How can I get the BGP AS Prepends be reflected in the redistribution to EIGRP?

Attached is a High Lever Visio of my Corporate side network.

Please Help! 

3 Replies 3

Philip D'Ath
VIP Alumni
VIP Alumni

I would expect something like the below to work (metrics made up):

ip as-path access-list 1 permit ^xxx xxx xxx$

route-map bgp-to-eigrp
  match as-path 1

router eigrp xxx
   redistribute bgp 100 route-map bgp-to-eigrp metric 100 1 255 1 1500

If that does work, play with the route-map match criteria.  I often use "match ip address prefix-list ..." but this would not work in your case.

In the route-map you could also try using "match ip next-hop ..." to match the case when the next-hop becomes the ASA.  You could also consider using route tags or communities.

Actually this might work better.

ip as-path access-list 1 permit ^xxx xxx xxx$

route-map bgp-to-eigrp permit 10
  match as-path 1
set metric 100 1 255 1 1500 *** Metric for pre-pended routes
route-map bgp-to-eigrp permit 20
set metric 100 1 255 1 1500 *** Metric for all other routes


router eigrp xxx
   redistribute bgp 100 route-map bgp-to-eigrp

Review Cisco Networking for a $25 gift card