In realt terms I don't think anything has changed in this space over 15 years Will and the seperation of different layers is networking 101.
But the root cause pointed at RR, when in fact it was whatever flooded them with lots of extra routes, which is not well explained in the text. Neil. -- Neil J. McRae. [email protected] ________________________________________ From: Will Hargrave [[email protected]] Sent: 06 October 2012 10:55 To: Neil J. McRae Cc: Thomas Mangin; [email protected] Subject: Re: [uknof] Go daddy what happened On 6 Oct 2012, at 05:29, "Neil J. McRae" <[email protected]> wrote: > but even if they didn't have RR how do they get into a situation where a > router starts switching in software. RR is a red herring in this failure > scenario even with full mesh this failure would still have happened. > root cause is somewhere a wad of routes turned a lot of silicon into > something useless. > does anyone know what kit this was? These sorts of designs are common in DC networks now, with increasing use of l3 to the edge. The key thing here is to keep your internet edge/core separated from your DC network. Great preso here from Microsoft: http://www.nanog.org/meetings/nanog55/abstracts.php?pt=MTk0MiZuYW5vZzU1&nm=nanog55 -- Will Hargrave +44 114 303 4444
