[28550] in North American Network Operators' Group
Re: DACS blamed for MCI / CSX train problems last week
daemon@ATHENA.MIT.EDU (Mohamed Hirse)
Mon May 8 04:30:41 2000
Date: Mon, 8 May 2000 04:24:30 -0400 (EDT)
From: Mohamed Hirse <madlion@justin.net>
To: Sean Donelan <sean@donelan.com>
Cc: nanog@merit.edu
In-Reply-To: <20000506030005.14699.cpmta@c004.sfo.cp.net>
Message-ID: <Pine.LNX.4.05.10005080421530.1540-100000@justin.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On 5 May 2000, Sean Donelan wrote:
>
> According to Computerworld, the MCI outage affecting CSX rail lines
> last week was caused by DACS problems.
>
> http://www.computerworld.com/home/print.nsf/all/000505DCCE
>
> This isn't the first DACS problem nor is MCI the only carrier affected
> by DACS problems. Bell Atlantic had a multi-day DACS problems, I've
> experienced 18+ hour MCI DACS problems in the past. What is it about
> DACS systems which seem to lead to such catastrophic problems? How
> can you put an entire train system out of operation due to a single
> piece of equipment?
A start would be if carriers architecture their network to be redundant
and self healing.
Mo
>
>
>
