[38859] in Hotline Meeting
unusable network connection to eecs-ath-15.mit.edu
daemon@ATHENA.MIT.EDU (Jerry Burke)
Mon Jul 14 09:46:26 1997
Date: Mon, 14 Jul 1997 09:46:12 -0500
To: hotline@MIT.EDU
From: burke@MIT.EDU (Jerry Burke)
Cc: network@MIT.EDU, hd@MIT.EDU
Hi mhpower
I have forwarded this message off to hotline, they will
verify the machine and the drop and report to whoever
should handle this call, this is an Athena workstation.
Matthew - please report Athena workstation related problems
to "hotline@mit.edu", they can follow up to be certain it is
not the machine, if they determine it is your machine they can
make arrangements to repair it. If they determine it is the
network or the drop they can report it to the necessary service.
Thanks, Jerry
>Date: Sun, 13 Jul 1997 20:30:34 -0400
>From: mhpower@MIT.EDU
>To: net-help@MIT.EDU
>Subject: unusable network connection to eecs-ath-15.mit.edu
>
>Since approximately July 11, the network performance of
>eecs-ath-15.mit.edu has been slow enough to be unusable. When pinging
>from other machines on the subnet or elsewhere on MITnet, the packet
>loss averages over 80% (see attached ping output below); typically, a
>few successive packets will succeed, followed by periods of up to a
>minute or more with no packets succeeding.
>
>The machine eecs-ath-15.mit.edu is connected via UTP to a drop
>labelled "36 781" on the wall beneath the machine. It has been
>connected in the same location and via this same drop for years
>(except that the UTP cable was unplugged and replugged a few times
>after the current problem started, as a check on whether the cabling
>was related to the problem).
>
>The machine is an Athena SPARC Classic; it belongs to Prof. Louis
>Braida. It is located about 8 feet to the left of the 36-781 door. It
>is the only Athena workstation in this office area. There are other
>networked computers in the area, but they are connected via a separate
>local network installed by RLE, and none of them are experiencing
>network performance problems.
>
>The poor network performance level continues even after a reboot.
>
>There have been no software or hardware changes in months. As far as I
>can tell, it just suddenly stopped performing acceptably on July 11.
>Prior to July 11, there were no observed problems with its network
>performance, and on numerous occasions ping had 0% packet loss.
>
>I'd appreciate it if you could check on this network connection.
>
>Matt
>
>
>PING eecs-ath-15.mit.edu (18.62.3.206): 56 data bytes
>64 bytes from 18.62.3.206: icmp_seq=7. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=38. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=39. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=40. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=41. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=42. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=54. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=55. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=56. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=57. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=58. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=59. time=117. ms
>64 bytes from 18.62.3.206: icmp_seq=60. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=69. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=85. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=86. time=230. ms
>64 bytes from 18.62.3.206: icmp_seq=87. time=0. ms
>64 bytes from 18.62.3.206: icmp_seq=88. time=0. ms
>
>----eecs-ath-15.mit.edu PING Statistics----
>100 packets transmitted, 18 packets received, 82% packet loss
>round-trip (ms) min/avg/max = 0/19/230
>
