OUTAGE: DACS failure in USWEST/spokane
This morning USWEST lost a DACS serving Spokane (and other places in Washington State). That isn't very unusual, but did spark my interest in a continuing pattern of DACS failures around the country. Not only have several telco's we use had DACS failures (usually a power supply), but the mean time to repair (and reprogram) them was over 12 hours. Whatever method of quickly re-loading the repaired DACS configuration doesn't seem to be working, or the operational procedures of several telephone companies are lacking. Generally after 10-12 hours, the telco usually informs us they are manually re-programming the DACS circuit by circuit. Have other network operators seen the same thing from their facility departments or providers? Is this a problem with the DACS vendor, user- interface design, operator procedures, or dumb management? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation
At 04:37 AM 12/27/98 -0600, Sean Donelan wrote:
This morning USWEST lost a DACS serving Spokane (and other places in Washington State).
...
Have other network operators seen the same thing from their facility departments or providers? Is this a problem with the DACS vendor, user- interface design, operator procedures, or dumb management?
After five years of dealing with USworst ... dumb management. Those guys couldn't find a clue in a clue factory. The Colorado Public utilities commisison (CPUC) penalizes them regularly because they can not even operate their telephone services properly. At one time, USwest was quoting 9-week lead-times for residential telephony servce in Black Forest (Colorado Springs, CO, CPUC requirements is two weeks)! If a telephone company can't even do telephony, how do you expect them to do Internet? Our USworst gateway regularly goes <dead> because they can't even keep their routers configured. (strictly personal experiance/opinion, YMMV) ___________________________________________________ Roeland M.J. Meyer - e-mail: mailto:rmeyer@mhsc.com Internet phone: hawk.lvrmr.mhsc.com Personal web pages: http://staff.mhsc.com/~rmeyer Company web-site: http://www.mhsc.com ___________________________________________________ I hold it, that a little rebellion, now and then, is a good thing... -- Thomas Jefferson
On Sun, Dec 27, 1998 at 04:37:32AM -0600, Sean Donelan wrote:
This morning USWEST lost a DACS serving Spokane (and other places in Washington State).
That isn't very unusual, but did spark my interest in a continuing pattern of DACS failures around the country. Not only have several telco's we use had DACS failures (usually a power supply), but the mean time to repair (and reprogram) them was over 12 hours.
Whatever method of quickly re-loading the repaired DACS configuration doesn't seem to be working, or the operational procedures of several telephone companies are lacking. Generally after 10-12 hours, the telco usually informs us they are manually re-programming the DACS circuit by circuit.
Have other network operators seen the same thing from their facility departments or providers? Is this a problem with the DACS vendor, user- interface design, operator procedures, or dumb management? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation
I had DACS failure in the PacHell aehm, PacBell CO in Alameda on X-mas eve. They lost two relay racks because of that and several of my T1s went down. It took them about 3-4 hours to fix everything. All my T1s from PacHell were ok, part of my CLEC T1s failed. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073
participants (3)
-
Roeland M.J. Meyer -
Sean Donelan -
Ulf Zimmermann