[38207] in Hotline Meeting
w20-575-100+ connectivity
daemon@ATHENA.MIT.EDU (Matt)
Tue May 6 14:33:47 1997
To: hotline@MIT.EDU
Cc: fredette@MIT.EDU
Date: Tue, 06 May 1997 14:33:44 EDT
From: Matt <fredette@MIT.EDU>
I'm curious to know why the physical segment of 18.187/16 that serves the
w20-575-100+ machines suffers from such high packet loss to their next hop.
Today, pinging from w20-575-108 to that next hop, W20-RTR-W20-CLUSTER-ETHER,
I see 10% packet loss over 500 packets. This makes the machine difficult
for me to use, since most of my windows are into other machines, and no
doubt causes similar frustration for others.
What's up with this segment? It's not just plain too busy, since pinging
from w20-575-108 to its immediate neighbors sees no loss.
Matt
--
Matt Fredette
fredette@bbnplanet.com, fredette@mit.edu, fredette@theory.lcs.mit.edu
http://www.mit.edu:8001/people/fredette/home.html
"The first time the Rolling Stones played, three people showed up."
> Date: Tue, 04 Mar 1997 16:45:50 EST
> To: hotline@MIT.EDU
> From: Matt <fredette@MIT.EDU>
> Subject: w20-575-104
>
> w20-575-104 is having connectivity problems - I'm seeing big
> delay swings and high packet loss just pinging its next-hop,
> 18.187.0.1 (W20-RTR-W20-CLUSTER-ETHER.MIT.EDU):
>
> [4:35pm] (22) w20-575-104:~ ping 18.187.0.1
> PING 18.187.0.1 (18.187.0.1): 56 data bytes
> 64 bytes from 18.187.0.1: icmp_seq=0 ttl=255 time=42 ms
> 64 bytes from 18.187.0.1: icmp_seq=1 ttl=255 time=2 ms
> ...
> 64 bytes from 18.187.0.1: icmp_seq=230 ttl=255 time=1 ms
> 64 bytes from 18.187.0.1: icmp_seq=231 ttl=255 time=64 ms
> 64 bytes from 18.187.0.1: icmp_seq=232 ttl=255 time=2 ms
>
> ----18.187.0.1 PING Statistics----
> 233 packets transmitted, 217 packets received, 6% packet loss
> round-trip (ms) min/avg/max = 1/49/8908
> [4:39pm] (23) w20-575-104:~
>
> Makes the machine kind of hard to use. Thought you might want
> to know.
>
> Matt
