|
Thread Index [isp-bgp] Re: BGP Configuration
On Mon, Jul 19, 2004 at 01:04:08PM +1000, John De La Fuente wrote: > Hi James, > > Many thanks for that. The thought had occurred to me to redistribute to > EIGRP via a sanatized redistribute, however, that would only work for > 'default route only' and partial feeds with default only. If you were to > receive the full BGP feed, would the redistribute still work? In that case, if you are receiving full routes, that means you are now standing on the brave new world of DFZ (Default Free Zone), where your router no longer needs a default. So, for such case you do: ip route 0.0.0.0 0.0.0.0 Null0 254 router ei whatever redist static route-map default-only metric blah bleh blah blerg just need to make sure static default route is Null0'd with a higher admin distance so that if you have a conflicting default route somewhere (i.e. bgp), null route will not take precedence. You can also send a summary route from your border router via EIGRP using ip summary-route 0.0.0.0 0.0.0.0 eigrp <asn> command. Beware, setting up summary-route in EIGRP will flap the adjacency and destabilize your network for a few seconds while eigrp reconverges. (personally i think eigrp sucks, but i am not about to start a religious war :-D ) > > I have implemented what you wrote, and it's working fine. My concern now > is would this still work given my upstream were to no longer generate a > default route, but instead give me the entire BGP feed? In this case, you can use two default routes. One from bgp, one from static null route with high admin distance. Redistribute both bgp and static into eigrp process, but just make sure that you strictly control what you redistribute using prefix-list or access-list under the route-map, since you do not want to accidentally redistribute entire bgp routing table into eigrp (that will be a bad idea..). Making sure that static null route has admin dist of 254 will make BGP default route have preference over static during normal times. When BGP fails, static null route will take precedence, and 'redistribute static' under eigrp process will readvertise the new default route toward the border router. Its either that or you summarize the EIGRP address at the interface going toward your eigrp core. Hope this helps! -J -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james@... Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
Thread Index |
|
