Re: LDM NEXRD2 feeds (fwd)

Hi Jason, 

Exploring options here....

I believe you are getting NEXRD2 on the same LDM machine as other data.

After some discussion it is thought we may be able to solve this issue if
you had access to another machine we could run the LDM on and use it
solely for NEXRD2 data. This may reduce the RECLASS statements and
therefore reduce the bottleneck at NCDC. I will know more when I get some
of the logs from NCDC, but just thought I would bounce this possibility 
off you to see if it is even an option...

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 Thu, 27 Sep 2001, Jason Levit wrote:

> 
>   Hi Jeff,
> 
>   NCDC is needing to use pqsend to push their sites to us due to firewall
> issues on their side.  Since their LDM machines reside behind a firewall,
> they have their own internal IP addresses (198.162.x.x), and the packets
> are rerouted via a fixed firewall IP.  It appears LDM requires a true IP
> address to use the standard "allow" in the ldmd.conf file.
> 
>   Jason
> 
> ----------------------------------------------------------------------------
> Jason J. Levit, N9MLA                  Research Scientist,
> address@hidden             Center for Analysis and Prediction of Storms
> Room 1022                            University of Oklahoma
> 405/325-3503                         http://www.caps.ou.edu/
>