nanog mailing list archives
Re: AT&T NYC
From: alex () yuriev com
Date: Mon, 2 Sep 2002 23:16:51 -0400 (EDT)
Which is exactly what you are doing when you inject nailed routes into bgp. So, why do you need IGP such as OSPF again? AlexTo carry the bgp next-hops around the network? You could add in statics for every next-hop on every router, but this kind of configuration is complex and prone to errors such as loops in relatively minor cases. statically routing every next-hop "does not scale". Not to mention that many of us like the "compare igp metric" portion of the BGP decision tree.
Rubbish again. *Every* interface that you bring up has a connected route. You redistribute those routes into IGP. You redistgribute statics from that router into IGP. Nail those routes into bgp and set internal community on it. network xxx.yyy.zzz.www mask ppp.hhh.ooo.lll route-map set-igp-community.
Having had the displeasure of having to deal with a network which had static routes as its sole igp, I'ld never want to see _that_ again. Thankfully, we managed to merely migrate the customers off that network, rather than even try to pull apart the twisty maze of static routes.
Alex
Current thread:
- Re: AT&T NYC bdragon (Sep 02)
- Re: AT&T NYC Petri Helenius (Sep 02)
- Re: AT&T NYC Stephen J. Wilcox (Sep 02)
- Re: AT&T NYC alex (Sep 02)
- Re: AT&T NYC bdragon (Sep 02)
- Re: AT&T NYC alex (Sep 02)
- Re: AT&T NYC Clayton Fiske (Sep 03)
- Re: AT&T NYC alex (Sep 03)
- Re: AT&T NYC Jesper Skriver (Sep 03)
- Re: AT&T NYC Iljitsch van Beijnum (Sep 03)
- Re: AT&T NYC Jesper Skriver (Sep 03)
- Re: AT&T NYC alex (Sep 02)
- Re: AT&T NYC bdragon (Sep 03)
- Re: AT&T NYC Iljitsch van Beijnum (Sep 03)
- Re: AT&T NYC alex (Sep 03)
- Re: AT&T NYC Iljitsch van Beijnum (Sep 03)
- Re: AT&T NYC alex (Sep 03)