[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: failover sites - traceroute files

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: failover sites - traceroute files
  • Date: Mon, 24 Feb 2003 11:33:59 -0700 (MST)
Hi Nancy, 

Oddly, the best route still seems to be to U of A..

(jweber) lenny:/home/jweber 19 % m trace_nimb
 1  router-11786.inre.asu.edu (129.219.174.1)  8 ms  2 ms  1 ms
 2  dmz-gw-ascix1.inre.asu.edu (149.169.254.11)  1 ms  2 ms  1 ms
 3  fwc-inside.asu.edu (209.147.181.12)  2 ms  1 ms  1 ms
 4  asu-isp-gw.inre.asu.edu (209.147.180.1)  2 ms  2 ms  3 ms
 5  209.147.191.134 (209.147.191.134)  23 ms  22 ms  23 ms
 6  virgil.telcom.arizona.edu (192.80.43.21)  74 ms  41 ms  40 ms
 7  tuco.telcom.arizona.edu (192.80.43.33)  40 ms  41 ms  41 ms
 8  woody.telcom.arizona.edu (192.80.43.26)  42 ms  42 ms  40 ms
 9  bullseye.telcom.Arizona.EDU (150.135.250.14)  43 ms *  68 ms
10  nimbus.atmo.arizona.edu (128.196.30.175)  57 ms  62 ms  43 ms


aside from feeding from us:

(jweber) lenny:/home/jweber 17 % m trac_thelma
 1  router-11786.inre.asu.edu (129.219.174.1)  7 ms  1 ms  1 ms
 2  dmz-gw-ascix1.inre.asu.edu (149.169.254.11)  1 ms  1 ms  1 ms
 3  fwc-inside.asu.edu (209.147.181.12)  7 ms  6 ms  2 ms
 4  asu-isp-gw.inre.asu.edu (209.147.180.1)  2 ms  3 ms  2 ms
 5  209.147.191.134 (209.147.191.134)  26 ms  24 ms  23 ms
 6  198.32.11.106 (198.32.11.106)  23 ms  24 ms  23 ms
 7  gin.ucar.edu (128.117.243.33)  29 ms  50 ms  37 ms
 8  mlrb-n243-72.ucar.edu (128.117.243.75)  77 ms *  29 ms
 9  thelma.ucar.edu (192.52.106.21)  29 ms  26 ms  32 ms


But both of these look quite reasonable, and you should not be
experiencing 60 minute latencies with this good of a connection..

Could you check w/your sys admin folks to see if they are "sniffing"
packets via packeteer or packetshaper software...We have found this to
severely degrade performance unless perfectly tuned. We use port 388, so
if they are using this, perhaps they could ease up on port 388..

Willing to try anything, but 10 hops and 50->60 ms is a pretty darn good
connect.

We can try feeding from thelma for a brief period of time to see if that
improves things..

Let ne know..I have an allow for you already on thelma..

Cheers, 

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
COMET Case Study Library                      FX:303-497-8690
University Corp for Atmospheric Research      3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber      Boulder,Co 80307-3000
________________________________________      ______________________

On Thu, 20 Feb 2003, system PRIVILEGED account wrote:

> Jeff,
>   Please reply to me as address@hidden, but I had to be root to use 
> traceroute. 
>  Here are the 4 files, with the second 3 or 4 letters of the filename 
> indicating 
> teh 4 sites, nim - nimbus, thel - thelma, ross - rossby, typh = typhoon
>   
> 
> Thanks,
> Nancy
>