North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: Fiber cut in SJ
- From: Aaron Glenn
- Date: Mon Aug 08 06:50:07 2005
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RwDIo8GzckJlkrNOz/+EJGepQX8V7pPH8J3SL4vZMvQ4vzutt/zvIIZnEM3V3ovSB4rB+MnO7Nm/vTiHrpURcmd6q8vvwnssxgRxoyh2MxidjZhkC+UcP9DUgbE07tN5ZNSoRohhiZ0zIakeGMvS/keYlQ7uwhwG4d0Lw3mx8bs=
On 8/8/05, Michael.Dillon@btradianz.com <Michael.Dillon@btradianz.com> wrote:
>
> > Eight or nine people I had
> > talked to thought they had geographically distinct
> > ring loops that turned out to be on that one cable
> > when the second cut took it down hard.
>
> Perhaps now people will begin to take physical separacy
> seriously and write grooming protocols and SLAs into
> their contracts?
>
> Or was this type of service "good enough"?
What was the actual cost of this outage to operators in SLA credits?
Perhaps it's just a function of economics: it's cheaper to plan for
the 3 fiber cuts per 1000 route miles per year (or whatever the silly
rate was I came across somewhere) and hand out credits than actually
engineer physical redundancy.
But seriously, has anyone quantified what this or similar cuts *actually cost*?
aaron.glenn
|
