nanog mailing list archives
Re: Long-haul protected services: (was: Re: Bee attack, fiber cut, 7-hour outage)
From: "Bill Stewart" <nonobvious () gmail com>
Date: Fri, 28 Sep 2007 22:06:42 -0700
On 9/21/07, Deepak Jain <deepak () ai net> wrote:
However, when I see "Location of Maintenance: France" and a 5 minute outage for a protected SONET service on a supposedly redundant, high quality International voice/data network... well, let's just say I'm not impressed -- on 36 hrs notice, no less. I can't do anything with respect to an SLA since there is advanced notice, but isn't it reasonable to assume that in this day-and-age running a properly protected T3 isn't *that hard* anymore???? Especially in advance -- you know, shunt the traffic to one your other circuits because, you know, you are supposed to have this massive network.
Typically for a service like that, the carrier would have one or more long-haul rings, either SONET or DWDM with the SONET on top of it or something, interconnected to access rings from a local access carrier at each end, either close to the customer endpoint or possibly back at regional interconnects. The long-haul carrier might not control the local access carrier except through an SLA, so it could be that the local carrier messed up. One hopes that the interconnections between the networks are also at diverse POPs (at least for big countries like France), but it is possible for the interconnections to fail clumsily. The "shunt the traffic to other circuits" approach is naively correct, but I've seen more than one case of "discover that one side of an access ring has failed by shunting the traffic from the other side to do maintenance and having a customer call you a couple of minutes later to report an outage at their headquarters", which is absolutely never supposed to happen, of course :-) What a 5-minute outage sounds like to me is "The early-90s T3-based restoration system recovered the circuit on an end-to-end basis using DACSs instead of SONET restoring it", but I'd be surprised to see than happening at a newer carrier like Vendor L who built most of their network after SONET technology became affordable. ---- Thanks; Bill Note that this isn't my regular email account - It's still experimental so far. And Google probably logs and indexes everything you send it.
Current thread:
- Bee attack, fiber cut, 7-hour outage Sean Donelan (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Deepak Jain (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Chris Boyd (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Valdis . Kletnieks (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Jeff Shultz (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Justin M. Streiner (Sep 21)
- Long-haul protected services: (was: Re: Bee attack, fiber cut, 7-hour outage) Deepak Jain (Sep 21)
- RE: Long-haul protected services: (was: Re: Bee attack, fiber cut, 7-hour outage) michael.dillon (Sep 23)
- Re: Long-haul protected services: (was: Re: Bee attack, fiber cut, 7-hour outage) Bill Stewart (Sep 28)
- Re: Bee attack, fiber cut, 7-hour outage David Lesher (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Wayne E. Bouchard (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Deepak Jain (Sep 21)
- Rings done right (was: Re: Bee attack, fiber cut, 7-hour outage) John Curran (Sep 24)
- Re: Bee attack, fiber cut, 7-hour outage Suresh Ramasubramanian (Sep 21)
- RE: Bee attack, fiber cut, 7-hour outage Frank Bulk (Sep 21)
- Re: Bee attack, fiber cut, 7-hour outage Deepak Jain (Sep 21)