Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: AT&T NYC

  • From: Stephen J. Wilcox
  • Date: Mon Sep 02 14:36:53 2002


On Mon, 2 Sep 2002, Petri Helenius wrote:

> "Stephen J. Wilcox" wrote:
> > 
> > On Mon, 2 Sep 2002, Petri Helenius wrote:
> > 
> > >
> > > bdragon@gweep.net wrote:
> > > > With link-state, one interface flap can mean doing SPF on every route.
> > >
> > > Only if you learned every one of your routes from different neighbor.
> > > If you have two exits and 100000 routes, you calculate twice and
> > > apply the results to the prefixes.
> > >
> > > Note that this does not apply to a proprietary, "hybrid", semi-link
> > > state protocol marketed with name "EIGRP" where all routes need
> > > per-prefix calculation. (OSPF and IS-IS work fine)

but.. with SPF you need to run the algorithm on all paths for each flap and then
see what that does to your routes

with eigrp you only need to apply the algorithm to any route on the link that
flapped and then only on the attached router (which will propogate much like bgp
if it requires other routers to recalculate)

yes thats bad if yuo have 100000 routes but you shouldnt have! assuming a
smaller routing table yuo get quicker convergence and much much less CPU
requirement on your rotuers

Steve

 > 
> Pete
> 
> 
> > Steve
> > 
> > >
> > > Pete
> > >
> 





Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.