RE: 20150516: Nexrad 2: idd.unidata.ucar.edu Access

We are just curious as to what the difference is for your server to receive LDM 
data, from what we believe to understand as being similar upstreams of borth 
the ROC Node and TOC Node, and our connection. I interpret in your previous 
email you were implying you were seeing high latency at both thos Nodes. Am I 
correct in this interpretation?

We've heard little back from our Contacts with NOAA and are a bit weary of 
attempting to move our primary feeds back over to TOC and ROC. Would you have 
any recommendations on how we might be able to test things on our end?

James Olson
Jr. Network Administrator
(O) 828-350-2415
After-Hour: 866-372-7110


-----Original Message-----
From: Unidata User Support [mailto:address@hidden] 
Sent: Saturday, May 16, 2015 6:45 PM
To: James Olson
Cc: Hunter Goosmann; address@hidden
Subject: 20150516: Nexrad 2: idd.unidata.ucar.edu Access


Hi James,

re:
>Hi, I'm with the ERC (Education and Research Consortium of the Western 
>Caro=
>linas) We're one of the top tier level 2 providers. We're currently 
>have dr= astic latency issues with both of our upstream. Anywhere from 
>10-20 minute = latency of data on one and 40 minute latency of data on 
>the other. Unfortun= ately there's not much we can do about the 
>upstream issues until Monday mor= ning. It was suggested to us that we 
>may have access to the idd.unidata.ica= r.edu ldm server that could be 
>used temporarily until we can speak to the p= eople incharge of our 
>upstream ldm servers on Monday. It appears we have ar= e allowed to 
>pull from the server, but just want to make sure it's alright = we do 
>so. My Boss Hunter Goosmann said if any sort of payment is required t= 
>o do this just speak with him. It's extremely urgent we get our latency 
>iss= ues resolved as we have a number of customers currently effected by this 
>is= sue as well.

nws-ldm[12].hpcc.ercbroadband.org are both ALLOWed to REQUEST NEXRAD2 from 
idd.unidata.ucar.edu AND are both already making REQUESTs for this and other 
feeds.  This should indicate that the latecnies you are experiencing are either 
caused by the connection(s) to the NWS top level sites, or by network issues 
close to your location.

Latencies we are seeing for the times of your high latencies strongly suggest 
that the problem is at or close to the NWS top level source machines.

I hope that this helps...

Cheers,

Tom Yoksas
Unidata User Support
--
********************************************************************** <
Unidata User Support                              UCAR Unidata Program <
(303)497-8643                                            P.O. Box 3000 <
address@hidden                             Boulder, CO 80307 <
---------------------------------------------------------------------- <
Unidata Web Support               http://www.unidata.ucar.edu/support  <
----------------------------------------------------------------------
< NOTE: All email exchanges with Unidata User Support are recorded in the 
Unidata inquiry tracking system and then made publicly available through the 
web.  If you do not want to have your interactions made available in this way, 
you must let us know in each email you send to us.