|
Re: ftp server
1996-04-04 14:31:17
On Thu, 4 Apr 1996, Ken Pendell wrote:
> If index.storsys.ibm.com and its mirrors were all mirrors
> of another site, they could all have the updates at about
> the same time. As it is, there is such a heavy demand that
> the mirrors can't copies of the updates either.
>
> -Ken Pendell
>
We are having problems with the mirror at ftp.cac.psu.edu. The connection
between PSU and IBM has a bottle neck that is slowing the transfer down.
Here is a traceroute:
traceroute index.storsys.ibm.com
traceroute to index.storsys.ibm.com (198.80.6.2), 30 hops max, 40 byte packets
1 (128.118.2.202) 4 ms 4 ms 8 ms
2 (128.118.100.1) 6 ms 4 ms 5 ms
3 psu-ether0-1.cic.net (192.5.159.11) 5 ms 7 ms 6 ms
4 dgc-psu.cic.net (131.103.26.81) 37 ms 39 ms 29 ms
5 dgf-fddi5-0.cic.net (131.103.1.19) 38 ms 35 ms 23 ms
6 cpe1-fddi-0.WillowSprings.mci.net (192.217.0.1) 31 ms 31 ms 32 ms
7 borderx1-hssi2-0.WillowSprings.mci.net (204.70.104.101) 28 ms 45 ms 29 ms
8 core2-fddi-0.WillowSprings.mci.net (204.70.104.49) 147 ms 29 ms 25 ms
9 core1-hssi-4.NorthRoyalton.mci.net (204.70.1.169) 119 ms 26 ms 34 ms
10 border3-fddi-0.NorthRoyalton.mci.net (204.70.98.19) 32 ms 28 ms 47 ms
11 206.157.77.10 (206.157.77.10) 38 ms 38 ms 39 ms
12 t3-1.cnss27.Chicago.t3.ans.net (140.222.27.3) 34 ms 53 ms 35 ms
13 t3-1.cnss96.Denver.t3.ans.net (140.222.96.2) 65 ms 83 ms 69 ms
14 t3-1.cnss8.San-Francisco.t3.ans.net (140.222.8.2) 88 ms 101 ms 84 ms
15 cnss13.San-Francisco.t3.ans.net (140.222.8.197) 98 ms 94 ms 105 ms
16 enss258.t3.ans.net (204.148.44.22) 3201 ms 3234 ms 3398 ms
17 198.80.6.2 (198.80.6.2) 3400 ms 2903 ms 3352 ms
I tried the traceroute about 6:30 am EDT, and similar problems. It looks
like a bottle neck is at enss258.t3.ans.net and it is taking a long time
to get the data through.
John Kalbach Center for Academic Computing
kalbach AT cac.psu DOT edu Penn State University
+1 814 863-7895 Computer Bldg
http://cac.psu.edu/~kalbach/ University Park, PA 16802
|
|
|
