Date: Sun, 16 Feb 1997 20:06:28 -0700 (MST) From: Charles Mott <cmott@srv.net> To: Marc Slemko <marcs@znep.com> Cc: chat@freebsd.org Subject: Re: CRL <--> MCI at pacbell NAP Message-ID: <Pine.BSF.3.91.970216195910.1548B-100000@darkstar> In-Reply-To: <Pine.BSF.3.95.970216192438.6083C-100000@alive.znep.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Feb 1997, Marc Slemko wrote: > Part of a traceroute to wcarchive: > > 9 pacbell-nap-atm.SanFrancisco.mci.net (204.70.1.202) 48.998 ms 50.476 ms 49.367 ms > 10 pacbell-nap-atm.SanFrancisco.mci.net (204.70.1.202) 53.675 ms 47.162 ms 61.408 ms > 11 pb-nap.crl.net (198.32.128.20) 1513.402 ms * * > 12 * wcarchive.cdrom.com (165.113.58.253) 483.625 ms * > > Not so hot; can't get more than 1 kbyte/sec from wcarchive when normally > I can get over 200. <sigh> > > Anyone have any idea whose fault it is (looks like CRL to me, but could > be something else at the NAP) and when it will be fixed? Guess I could > manually route around it but that's annoying. Very interesting. The networking expert I know says this can result from a router advertising an incorrect "cost" number. If this parameter, whatever it is, is set incorrectly, a huge amount of traffic can be drawn into a small pipe. Generally speaking you hear phrases like, "it was real bad, we very quickly fixed the problem". Another possibility is that a major link is down and they are going through a T1 backup path. It is also apparently pretty easy to mess up BGP configuration. In any event, you might want to send some e-mail the backbone provider(s). Often noc@.... works prety well. (noc = network operations center). A whois may also give some e-mail addresses. Charles Mott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970216195910.1548B-100000>