UUNet core router problems

Article View: ott.online

Article #153

#153

From: Ralph Doncaster
Date: Wed, 01 Jul 1998 00:00

59 lines
3268 bytes

UUnet's Cisco 7513 198.133.49.2, used for peering in Toronto with Bell (and
many others) is running a high CPU load and is dropping packets.
Bell's router connected via FDDI to 198.133.49.2 is 205.207.238.202.


The following were done simultaneously at approx 22:30 from 206.47.27.174
(inside bell's network)

Reply from 198.133.49.2: bytes=32 time=31ms TTL=247
Reply from 198.133.49.2: bytes=32 time=20ms TTL=247
Request timed out.
Request timed out.
Reply from 198.133.49.2: bytes=32 time=42ms TTL=247
Reply from 198.133.49.2: bytes=32 time=21ms TTL=247
Request timed out.
Reply from 198.133.49.2: bytes=32 time=20ms TTL=247
Request timed out.
Reply from 198.133.49.2: bytes=32 time=22ms TTL=247
Reply from 198.133.49.2: bytes=32 time=29ms TTL=247
Reply from 198.133.49.2: bytes=32 time=50ms TTL=247
Request timed out.
Reply from 198.133.49.2: bytes=32 time=21ms TTL=247
Reply from 198.133.49.2: bytes=32 time=22ms TTL=247
Reply from 198.133.49.2: bytes=32 time=28ms TTL=247
Request timed out.
Request timed out.
Reply from 198.133.49.2: bytes=32 time=46ms TTL=247
Reply from 198.133.49.2: bytes=32 time=21ms TTL=247
Reply from 198.133.49.2: bytes=32 time=20ms TTL=247
Reply from 198.133.49.2: bytes=32 time=29ms TTL=247
Reply from 198.133.49.2: bytes=32 time=60ms TTL=247

Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=44ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=19ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=22ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=22ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=21ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248
Reply from 205.207.238.202: bytes=32 time=20ms TTL=248

--
Ralph Doncaster, Doncaster Consulting Inc   email: ralph@doncaster.on.ca

Technical Details

Message-ID: <3599A842.601791AA@sympatico.ca>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10aaae,ac36f95024667caa,start
X-Google-Attributes: gid10aaae,public
X-Google-Thread: 105a5a,ac36f95024667caa,start
X-Google-Attributes: gid105a5a,public
From: Ralph Doncaster <nospam@sympatico.ca>
Subject: UUNet core router problems
Date: 1998/07/01
Message-ID: <3599A842.601791AA@sympatico.ca>
X-Deja-AN: 367626432
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
NNTP-Posting-Date: Tue, 30 Jun 1998 23:08:34 EDT
Content-Type: text/plain; charset=us-ascii
Organization: DCI
Newsgroups: ott.online,can.infohighway