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

Re: IDD connection requested

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: IDD connection requested
  • Date: Thu, 13 Sep 2001 13:28:28 -0600 (MDT)
Hi Luis, 

Wow, altho it goes much further it is as quick, and probably much more
reliable than telcom.arizona...

As soon as Larry gets meteora stable I suggest we feed you PRIMARILY from
UCSD and use U of A as your failover..as a Devil, I am sure you would
rather feed from UCSD than those darn 'Cats in Tucson anyway...ha ha.

We'll see after meteora gets the green light.

Thank you,

-Jeff
____________________________                  _____________________
Jeff Weber                                    address@hidden
Unidata Support                               PH:303-497-8676 
NWS-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 Wed, 12 Sep 2001, LUIS M FARFAN wrote:

> Jeff,
> 
> attached is the information you requested:
> 
> 
> (ldm) mothra:/usr/user/ldm/logs 40 % /usr/sbin/traceroute 
> nimbus.atmo.arizona.edu
> traceroute to nimbus.atmo.arizona.edu (128.196.30.175), 30 hops max, 
> 40 byte packets
>   1  router-11786.inre.asu.edu (129.219.174.1)  1 ms  1 ms  1 ms
>   2  asu-gw-ascix1.inre.asu.edu (149.169.254.11)  6 ms  11 ms  5 ms
>   3  129.219.253.14 (129.219.253.14)  28 ms  29 ms  25 ms
>   4  virgil-pos6-0-0.telcom.arizona.edu (192.80.43.21)  47 ms  49 ms  40 ms
>   5  angeleyes-fa9-1-virgil.telcom.arizona.edu (192.80.43.37)  50 ms 
> 45 ms  44 ms
>   6  jessie-vlan910-angeleyes.telcom.arizona.edu (192.80.43.30)  51 ms 
> 46 ms  44 ms
>   7  * * *
>   8  * * *
> 
> (ldm) mothra:/usr/user/ldm/logs 42 %
> (ldm) mothra:/usr/user/ldm/logs 42 % /usr/sbin/traceroute meteora.ucsd.edu
> traceroute to meteora.ucsd.edu (132.239.94.91), 30 hops max, 40 byte packets
>   1  router-11786.inre.asu.edu (129.219.174.1)  20 ms  1 ms  1 ms
>   2  asu-gw-ascix1.inre.asu.edu (149.169.254.11)  6 ms  2 ms  1 ms
>   3  129.219.253.14 (129.219.253.14)  21 ms  36 ms  38 ms
>   4  snva-dnvr.abilene.ucaid.edu (198.32.8.1)  54 ms  57 ms  65 ms
>   5  losa-snva.abilene.ucaid.edu (198.32.8.18)  59 ms  63 ms  65 ms
>   6  USC--abilene.ATM.calren2.net (198.32.248.85)  64 ms  64 ms  75 ms
>   7  UCSD--USC.POS.calren2.net (198.32.248.34)  89 ms  93 ms  87 ms
>   8  198.32.248.186 (198.32.248.186)  63 ms  67 ms  93 ms
>   9  nodec-ucsd-gw.ucsd.edu (132.239.255.145)  63 ms  66 ms  60 ms
> 10  meteora.ucsd.edu (132.239.94.91)  61 ms  62 ms  60 ms
> (ldm) mothra:/usr/user/ldm/logs 43 %
> 
> 
> >Hi Luis,
> >I see both ASU and U of A are Abilene participants and connected sites.
> >However, when you performed the traceroute from your ldm machine to nimbus
> >it did not appear to be on Abilene.
> >Could you please perform
> >traceroute nimbus.atmo.arizona.edu
> >again and attach the results
> >and while we are at it lets do it to :
> >meteora.ucsd.edu
> >as well.
> >We may need to bring the network folks at ASU into this thread...
> >Thank you,
> >-Jeff
> -- 
> Luis M Farfan
>