[44728] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Network Operations Luminaries?

daemon@ATHENA.MIT.EDU (Brett Frankenberger)
Mon Dec 10 23:47:12 2001

Message-Id: <200112110352.VAA15720@rbfux.rbfnet.com>
To: lucifer@lightbearer.com (Joel Baker)
Date: Mon, 10 Dec 2001 21:52:17 -0600 (CST)
From: "Brett Frankenberger" <rbf@rbfnet.com>
Cc: nanog@merit.edu
In-Reply-To: <20011210154925.A11426@lightbearer.com> from "Joel Baker" at Dec 10, 2001 03:49:25 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu


> 
> Interesting. I wonder if we're discussing two separate events. The one I
> knew of supposedly involved a regex with a misplaced .*, which seems like
> a fairly fundamentally different lesson. Both valuble, though...

I was downstream from 2551 at the time of their, um, big event.  A
botched regex that led to external BGP routes being redistributed into
OSPF is what sources that I considered reliable explained to me as the
cause.  Reports on the length of the outage varied, but I think
official reports were from the time of the initial failure until their
core was stable, because my network was down well over 24 hours, and I
seem to recall the "official" times as shorter.

As for the previous question in this thread, 12.1 that I'm currently
running treats "no red bgp subn route-m <name>" the same as "no red
bgp" (for any value of <name>, including values that don't match what's
already there).  I have no reason to believe that the 11.x that Netcom
was presumably running at the time was any different.

     -- Brett

home help back first fref pref prev next nref lref last post