05-27-2010 10:59 AM - edited 03-04-2019 08:36 AM
I have dual MPLS networks connected to two different TELCO’s running BGP to the provider. I am running EIGRP internally. I have all of the redistribution working and have the routers preferring the EIGRP routes learned internally over a BGP route using the weight command on my BGP routing. My question involves the redistribution of EIGRP into BGP. I know I have to set some type of seed metric to get BGP to redistribute the EIGRP route into its routing protocol. I am currently setting the default metric but I wonder if that is the best place. I only want to adjust the metric to redistributed routes so I don’t want to affect all of my internal EIGRP routes. Should I leave it the way it is or set the metric in the redistribute command under BGP? If I leave it like it is am I just affecting the local EIGRP network? Do those metric’s trickle out to my other devices? As an example a Layer 3 switch that is only running EIGRP but does not have the default metric set. The router that is running both protocols learns internal routes via EIGRP from the layer 3 switch but the layer 3 switch only knows about the BGP routes from redistribution.
router eigrp 50
redistribute bgp 65001
network 1.1.1.0 0 0.0.0.255
network 2.2.2.2 0.0.0.0
default-metric 1000 100 250 100 1500
distance eigrp 15 170
no auto-summary
!
router bgp 65001
bgp log-neighbor-changes
neighbor 12.1.1.1 remote-as 7018
!
address-family ipv4
redistribute eigrp 50 route-map redistribute-eigrp
neighbor 12.1.1.2 activate
neighbor 12.1.1.2 weight 40000
neighbor 12.1.1.2 soft-reconfiguration inbound
no auto-summary
no synchronization
network 1.1.1.0 mask 255.255.255.0
network 2.2.2.2 mask 255.255.255.255
exit-address-family
06-04-2010 12:12 PM
Ok setting it on the redistribute command will not work. What about setting it on the route-map and not putting in a default metric on EIGRP?
Also as far as setting a metric for BGP routes going into EIGRP I am not doing that now and I am getting all of my EBGP routes into EIGRP.
06-04-2010 12:29 PM
Hello Bill,
>> Also as far as setting a metric for BGP routes going into EIGRP I am not doing that now and I am getting all of my EBGP routes into EIGRP.
>> router eigrp 50
redistribute bgp 65001
network 1.1.254.0 0.0.1.255
default-metric 1000000 100 250 100 1500
distance eigrp 15 170
no auto-summary
it applies to BGP routes if you remove the bolded line, you will not be able to see BGP routes imported in EIGRP
is it clear now?
Hope to help
Giuseppe
06-04-2010 12:33 PM
I thought the default-metric command was needed to get EIGRP routes in
to BGP not BGP routes into EIGRP.
I am tyring to avoid using the default-metric command and only manipulate the routes that I want to send into BGP.
06-04-2010 02:04 PM
Hello Bill,
>> I thought the default-metric command was needed to get EIGRP routes in
to BGP not BGP routes into EIGRP.
No, it is the opposite you have a correct configuration simply you have thought you needed to set the seed metric in the source protocol instead of the destination protocol.
>> I am tyring to avoid using the default-metric command and only manipulate the routes that I want to send into BGP.
From a practical point of view it will not make any difference: either you use default-metric settings with 5 seed values (for EIGRP) or you can use a set metric + 5 seed values inside the route-map that is invoked by the redistribute bgp command line (as in my examples some posts ago), this will act as a route filter and it will also provide the necessary seed metric compatible to destination protocol
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide