06-11-2009 03:04 PM - edited 03-06-2019 06:13 AM
Looking at the correct way to redistribut EIGRP and Static routes into BGP. Please see below config.
ip route 86.43.157.69 255.255.255.255 2.153.42.29 254
router eigrp 90
passive-interface default
no passive-interface g0/0
no auto-summary
netork 2.153.83.0 0.0.0.255
netork 2.153.84.0 0.0.0.255
netork 2.153.85.0 0.0.0.255
netork 2.153.86.0 0.0.0.255
netork 2.153.87.0 0.0.0.255
router bgp 65500
no synchronization
bgp log-neighbor-changes
neighbor 86.43.157.37 remote-as 5466
no auto-summary
Please advise
C
Solved! Go to Solution.
06-11-2009 05:09 PM
What Jon suggests, indeed works. However, it dumps all of your statics and IGP routes into BGP, unless you filter what's being redistributed.
Another method is to use network statements within the BGP router configuration. This redistributes routes only already in the IP routing table that match the network statement. I.e., it might be little clearer what networks you want BGP to advertise.
(NB: I don't work with BGP that often, and I'm doing this from memory. Anyone that notices a mistake, please post a correction - thanks.)
e.g.
router bgp 65500
.
.
network 2.153.83.0 mask 255.255.255.0
network 2.153.84.0 mask 255.255.255.0
network 2.153.85.0 mask 255.255.255.0
network 2.153.86.0 mask 255.255.255.0
network 2.153.87.0 mask 255.255.255.0
network 86.43.157.69 mask 255.255.255.255
Often when working with BGP, we want to avoid route churn that might be caused by IGP routes coming and going. Also, we might want to only advertise a aggregate prefix for an address block. Either/both can be accomplished by using a BGP network statement that matches a static route which covers the addresses used by your IGP.
e.g.
ip route 2.153.83.0 255.255.255.0 null 0 200
ip route 2.153.84.0 255.255.252.0 null 0 200
router bgp 65500
.
.
network 2.153.83.0 mask 255.255.255.0
network 2.153.84.0 mask 255.255.252.0
network 86.43.157.69 mask 255.255.255.255
06-11-2009 03:23 PM
Colm
Simply add in the following 2 redistribute statements -
router bgp 65500
no synchronization
bgp log-neighbor-changes
neighbor 86.43.157.37 remote-as 5466
redistribute eigrp 90
redistribute static
no auto-summary
You can influence which routes are redistributed with route-maps and you can specifiy a metric for each redistribute statement but the above would be enough.
Jon
06-11-2009 05:09 PM
What Jon suggests, indeed works. However, it dumps all of your statics and IGP routes into BGP, unless you filter what's being redistributed.
Another method is to use network statements within the BGP router configuration. This redistributes routes only already in the IP routing table that match the network statement. I.e., it might be little clearer what networks you want BGP to advertise.
(NB: I don't work with BGP that often, and I'm doing this from memory. Anyone that notices a mistake, please post a correction - thanks.)
e.g.
router bgp 65500
.
.
network 2.153.83.0 mask 255.255.255.0
network 2.153.84.0 mask 255.255.255.0
network 2.153.85.0 mask 255.255.255.0
network 2.153.86.0 mask 255.255.255.0
network 2.153.87.0 mask 255.255.255.0
network 86.43.157.69 mask 255.255.255.255
Often when working with BGP, we want to avoid route churn that might be caused by IGP routes coming and going. Also, we might want to only advertise a aggregate prefix for an address block. Either/both can be accomplished by using a BGP network statement that matches a static route which covers the addresses used by your IGP.
e.g.
ip route 2.153.83.0 255.255.255.0 null 0 200
ip route 2.153.84.0 255.255.252.0 null 0 200
router bgp 65500
.
.
network 2.153.83.0 mask 255.255.255.0
network 2.153.84.0 mask 255.255.252.0
network 86.43.157.69 mask 255.255.255.255
06-11-2009 05:09 PM
Accidental double post.
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