[44428] in North American Network Operators' Group

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

RE: Followup British Telecom outage reason

daemon@ATHENA.MIT.EDU (Daniel Golding)
Mon Nov 26 11:51:46 2001

From: "Daniel Golding" <dgolding@sockeye.com>
To: "Christian Kuhtz" <christian@kuhtz.com>,
	"S" <sdsolomo@iupui.edu>, <nanog@merit.edu>
Date: Mon, 26 Nov 2001 11:51:08 -0500
Message-ID: <GKEFKKIKGCMICPKBAEIMEEHHCEAA.dgolding@sockeye.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <NJEGKKENPOCEEBFPGGCMEEGDCCAA.christian@kuhtz.com>
Errors-To: owner-nanog-outgoing@merit.edu


This used to be the cc train, then later the S train. However, the S train
has never been as stable as cc, and it has become increasingly less stable
over time, with too many new features rolling in.

I'd be curious as to exactly which CEF bugs bit them. The introduction of
greater MPLS functionality seems to have given CEF a nasty bit of
destabilization.

- Daniel Golding

> -----Original Message-----
> From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
> Christian Kuhtz
> Sent: Sunday, November 25, 2001 12:57 AM
> To: S; nanog@merit.edu
> Subject: RE: Followup British Telecom outage reason
>
>
>
>
> > you are right.  But in an era of focusing on the box, vendors are
> > forgetting that solid software and knowledgable support are just as
> > important.
> >
> > Possibly slow down a bit on rolling all those new features and widgets
> > into the software.... Make the software do what it should,
> reliably.. then
> > put the new stuff in there.
> >
> > ie.. bug scrub a train, per chassis.  Make it solid.. then put the toyz
> > in.
>
> easier said than done when everybody wants every fancy new feature 110%
> solid and yesterday.
>
>


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