Re: 20000425: Need backup LDM site at Texas Tech (fwd)

>Date:20000426
>Organization: Texas Tech
>Keywords: 200004252141.e3PLf7G14119 Texas Tech

Hi Tim- 


Our records indicate that you were feeding from 

nimbus.atmo.arizona.edu

instead of coriolis.met.tamu.edu.

Nonetheless, I will make these changes to our records.

nimbus could serve as your failover site if the connection is still valid.

Please do a traceroute and a notifyme for nimbus.atmo.arizona.edu

Hi Mike-

Would you please check to see if you still have an allow statement for 

hailshaft.atmo.ttu.edu

Please cc me on all correspondence,


Thanks,

-Jeff
__________
Jeff Weber
Unidata/NWS-COMET Case Study Library
University Corp for Atmospheric Research

address@hidden
PH:303-497-8676   
URL--http://www.unidata.ucar.edu/staff/jweber
________________________________________________

On Tue, 25 Apr 2000, Robb Kambic wrote:

> How about this one.
> 
> Robb...
> 
> ===============================================================================
> Robb Kambic                              Unidata Program Center
> Software Engineer III                    Univ. Corp for Atmospheric Research
> address@hidden                   WWW: http://www.unidata.ucar.edu/
> ===============================================================================
> 
> ---------- Forwarded message ----------
> Date: Tue, 25 Apr 2000 15:59:42 -0600
> From: Unidata Support <address@hidden>
> Reply-To: Tim Doggett <address@hidden>
> To: address@hidden
> Subject: 20000425: Need backup LDM site at Texas Tech
> 
> >To: address@hidden
> >From: Tim Doggett <address@hidden>
> >Subject: Need backup LDM site at Texas Tech
> >Organization: UCAR/Unidata
> >Keywords: 200004252141.e3PLf7G14119
> 
> Hi,
> 
> Our LDM feed from Texas A&M (coriolis.met.tamu.edu) has been choppy for
> awhile now, with latencies exceding 1 hour much of the time.  I have been
> through the set up several times to make sure I haven't messed up, and am
> fairly confident that we are OK in that respect.  I have contacted A&M and
> they feel there might be a firewall issue at hand, but we are not sure.  I
> was wondering if we could get a failover site to test whether the problem
> persists with another data feed.  Additionally, we'd like a fall over site
> anyway, just in case we need a backup.
> 
> I tend to doubt this is going to help much, as the traceroute seems pretty
> direct and relatively fast... and there are times (while relatively rare)
> where the latencies are low.  Also, TAMU is getting the data in a timely
> fashion (at least according to notifyme), so the problem is not furhter up
> the pipeline.  Other than splitting the request into parts based on IP
> address and domain name (which I have done), have you got any other
> suggestions?
> 
> Thanks a bunch.
> 
> -Tim
> -------------------------------------------------------------------------
> Tim Doggett, Ph.D.
> Assistant Professor
> Texas Tech University's Atmospheric Science Group
> e-mail: address@hidden
> phone: (806)742-3477
> fax:      (806)742-1738
> -------------------------------------------------------------------------
> 
>