[57768] in North American Network Operators' Group
RE: Fiber cut?
daemon@ATHENA.MIT.EDU (Steve Gibbard)
Tue Apr 22 00:43:28 2003
Date: Mon, 21 Apr 2003 21:42:39 -0700 (PDT)
From: Steve Gibbard <scg@gibbard.org>
To: "McBurnett, Jim" <jmcburnett@msmgmt.com>
Cc: "Mike (meuon) Harrison" <meuon@highertech.net>, nanog@merit.edu
In-Reply-To: <390E55B947E7C848898AEBB9E507706041E764@msmdcfs01.msmgmt.com>
Errors-To: owner-nanog-outgoing@merit.edu
On Mon, 21 Apr 2003, McBurnett, Jim wrote:
> A small ISP at one of our small cities is claiming a fiber cut took
> them offline..
This is NANOG, and this is pretty basic, so this is probably the wrong
forum for this explanation. That said, if a small ISP gets taken off line
by a fiber cut, it's far more likely to be somewhere between the major
backbone and the ISP (a circuit which from the ISP's perspective may be
controlled by the major backbone), than it is that the fiber cut will
actually isolate the major backbone's POP. The major backbones at this
point have a fair amount of redundancy built in, while the circuit from
the major backbone to the ISP is likely to be a single circuit on a single
path.
Still, even in that environment, most circuit outages are not fiber cuts.
> I can't buy it that it goes from ATlanta to San Fran in 1 hop....
>
> Trace to www.advi.net
> 10 12.122.12.50 0ms 10ms 10ms TTL: 0 (ggr1-p380.attga.ip.att.net probable bogus rDNS: No DNS)
> 11 192.205.32.126 10ms 10ms 0ms TTL: 0 (att-gw.sf.uu.net probable bogus rDNS:
> 12 Request timed out
Not to mention that they'd have to have discovered faster light. ;)
-Steve
