[j-nsp] Spine & leaf

adamv0025 at netconsultings.com adamv0025 at netconsultings.com
Wed Jun 27 17:54:25 EDT 2018

> Of David Sinn
> Sent: Wednesday, June 27, 2018 7:55 PM
> > On Jun 27, 2018, at 8:40 AM, Thomas Bellman <bellman at nsc.liu.se> wrote:
> >
> > On 2018-06-26 21:38, David Sinn wrote:
> >
> >> OSPF scales well to many multiples of 1000's of devices.
> >
> > Is that true even for Clos (spine & leaf) networks, and in a single
> Yes for multi-tiered Clos, as that was the original ask and where my
> is coming from.  However, it is not in a single area.  But if you are
doing a
> multi-tiered then the areas can fall out fairly naturally from the
> > My understanding, solely based on what others have told me, is that
> > the flooding of LSAs in a Clos network can start to overwhelm routers
> > already at a few hundred devices, as each time e.g. a spine sends out
> > an LSA, all of the other spines will hear that from each of the
> > leaves, all more or less simultaneously.  And since the OSPF protocol
> > limits lifetimes of LSAs to 1 hour, you will get a constant stream of
> Even Quagga/FRR has some measure of skew in the refresh interval to insure
> that the re-advertisements aren't all clumped into one batch of updates
> a given node.  And even having a really bad day where you loose power to a
> good number of devices that basically all start up at the same time
> cause measure-able congruence of updates.  The skew in type-1's as the
> boxes randomly bring up adjacencies and re-advertise their reachability
> you a good spread across the refreshes over time which generally grows
> time.  So while there is a continual background, even a single core PPC
> on commodity boxes can handle it with multiple of the available white-box
> OS's.
Haven't you guys heard of DNA LSAs to get rid of the flooding? -this is de
facto standard in SP core networks.
Also if you are having troubles keeping a reasonable number of IGP routes
there's the hiding of transit-only networks RFC 6860 (all you really need
are just the RIDs)? 


::carrier-class solutions for the telecommunications industry::

More information about the juniper-nsp mailing list