[16371] in North American Network Operators' Group

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

RE: AT&T Outage cause last week.

daemon@ATHENA.MIT.EDU (Goldstein_William@bns.att.com)
Wed Apr 22 11:51:54 1998

From: Goldstein_William@bns.att.com
Date: Wed, 22 Apr 98 11:01:41 -0400
TO: nanog@merit.edu, rjoffe@bbn.com


--openmail-part-031d288f-00000001
Content-Type: text/plain; charset=ISO-8859-1; name="BDY.RTF"
Content-Disposition: attachment; filename="BDY.RTF"
Content-Transfer-Encoding: quoted-printable

There is supposed to be a press conference on this at 2PM today with the=

CEO's of both AT&T and Cisco.  More information on this should come out
at this time.
Bill Goldstein
Senior Internet Specialist
AT&T
wgoldstein@att.com
TEL:(412)642-7288

   ----------
   From:       rjoffe
   Sent:       Monday, April 20, 1998 4:57 PM
   To:         nanog
   Cc:         rjoffe
   Subject:    AT&T Outage cause last week.
   =

   Received: from motown1.bns.att.com (motown1a.bns.att.com
   [135.170.169.236])
      by pawayn01.bns.att.com (8.8.6/1.3) with ESMTP id KAA22750
      for <Goldstein_William/bcs_pawayn01@pawayn01.bns.att.com>; Wed, 22=

   Apr 1998 10:51:37 -0400 (EDT)
   Received: from kcig2.att.att.com (kcig2.att.att.com [135.38.78.195])
   by motown1.bns.att.com (8.7.3/2.5) with ESMTP id LAA14973 for
   <goldstein_william@bns.att.com>; Wed, 22 Apr 1998 11:03:20 -0400
   (EDT)
   Received: (from nuucp@localhost)
      by kcig2.att.att.com (AT&T/GW-1.0) id JAA18780;
      Wed, 22 Apr 1998 09:51:27 -0500 (CDT)
   >Received: by kcgw2.att.com; Wed Apr 22 09:32 CDT 1998
   Received: by kcgw2.att.com; Wed Apr 22 09:32 CDT 1998
   Received: from localhost (daemon@localhost)
      by merit.edu (8.8.7/8.8.5) with SMTP id KAA13040;
      Wed, 22 Apr 1998 10:39:00 -0400 (EDT)
   Received: by merit.edu (bulk_mailer v1.5); Wed, 22 Apr 1998 10:35:42
   -0400
   Received: (from majordom@localhost)
      by merit.edu (8.8.7/8.8.5) id KAA12832
      for nanog-outgoing; Wed, 22 Apr 1998 10:35:42 -0400 (EDT)
   Received: from home.merit.edu (home.merit.edu [198.108.60.42])
      by merit.edu (8.8.7/8.8.5) with ESMTP id KAA12826
      for <nanog@merit.edu>; Wed, 22 Apr 1998 10:35:36 -0400 (EDT)
   Received: (from ljb@localhost) by home.merit.edu (8.8.8/merit-2.0) id=

   KAA16606 for nanog@merit.edu; Wed, 22 Apr 1998 10:35:35 -0400 (EDT)
   Received: from layer9.com (layer9.com [207.240.231.2])
      by merit.edu (8.8.7/8.8.5) with ESMTP id QAA10218
      for <nanog@merit.edu>; Mon, 20 Apr 1998 16:54:32 -0400 (EDT)
   Received: from bbn.com (HST-13.layer9.com [207.240.231.13])
             by layer9.com (8.8.8/8.8.8) with ESMTP
        id NAA13617 for <nanog@merit.edu>; Mon, 20 Apr 1998 13:54:20
   -0700
   Message-ID: <353BB6C2.D6713F0C@bbn.com>
   Date: Mon, 20 Apr 1998 13:57:38 -0700
   From: Rodney Joffe <rjoffe@bbn.com>
   Organization: GTE Internetworking
   X-Mailer: Mozilla 4.05 [en] (WinNT; U)
   MIME-Version: 1.0
   To: nanog@merit.edu
   Subject: AT&T Outage cause last week.
   Content-Transfer-Encoding: 7bit
   Sender: owner-nanog@merit.edu
   Content-Type: text/plain; charset=3Dus-ascii
   --------------------------------------------------
   According to AT&T, in a story just released, the problem was a Cisco
   code problem. It would be interesting to hear what the actual
   software
   cause was, if anyone from Cisco cares to let us know?.../rlj
   =

   =

   - - - AT&T's network failure AT&T Corp. reported
    today that last week's frame relay network failure
    was due to a software-based problem. =

   =

    Last Monday's network failure disrupted service
    nationally for thousands of AT&T's business
    customers for about a day. =

   =

    The cause of the outage was previously attributed
    to the interaction between two frame-relay
    switches, but AT&T now says it was a software
    problem. AT&T Chairman C. Michael Armstrong
    said today the company is working closely with
    Cisco Systems, which provided its switches, on
    ways to fix the problem. =

   =

    The type of network application affected by
    frame-relay service is "any kind of high-speed data
    applications where large amounts of information
    [are] exchanged in quick bursts," Granieri said.
    Querying an inventory database is one example of
    such an application, he said. Reuters contributed
    to this report
   =

   =

   
--openmail-part-031d288f-00000001--


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