20010910: nexrad floater feed on new NMSU machine

>From: Michael Trexler <address@hidden>
>Organization: NCSU
>Keywords: 200109061611.f86GBx103724 LDM NNEXRAD FNEXRAD

Mike,

>Things are going better now with the data feeds,

Does this mean that your problem was a firewall configuration one?

>but I'm still having
>one very puzzling problem, this time about the nexrad floaters.  A
>little history...
>
>Originally, when I set up the new machine (measol), I was feeding it
>from our old machine (meaculpa) which was running a really old ldm.
>Under this scheme I fed through the Millersville floaters to measol
>(using the header NMC3) and everything was great.

So, your upstream feed site had an allow line in ldmd.conf for the
FNEXRAD feed for your meaculpa.

>Ok, so then I began
>to try to feed directly off of my upstream radar feed (Illinois) using
>the same thing.  Well, now I can't get the floaters to come through.

On the surface, this sounds like your upstream feed site does not have
an allow for measol.

>So, I tried using FNEXRAD, which my version of ldm (5.1.2) doesn't
>like.

The translation from name to numeric representation of a feed is done
on your end.  If NMC3 didn't work, FNEXRAD would not either.

>Funny thing about all this is that if I try to get specific
>sites (I'm getting RAX, GSP, and BYX right now) then they come through
>fine.

This must be from the NNEXRAD (aka NEXRAD) feed.

>Or if I open the flood gates to get everything on the NEXRAD
>feed, that works too.  Any ideas?

This sounds like your upstream feed site, flood.atmos.uiuc.edu, doesn't
have an allow for measol for the FNEXRAD feed type, EXCEPT for the fact
that you get an OK on a notifyme for NMC3 from them.

>One more bit of helpful info is what I get from the notifyme:
>
>[14]ldm on measol-> notifyme -v -l- -h flood.atmos.uiuc.edu -f NEXRAD -o
>3600
>Sep 10 21:23:31 notifyme[22669]: Starting Up: flood.atmos.uiuc.edu:
>20010910202331.373 TS_ENDT {{NNEXRAD,  ".*"}}
>Sep 10 21:23:31 notifyme[22669]: NOTIFYME(flood.atmos.uiuc.edu): OK
>Sep 10 21:23:31 notifyme[22669]:      948 20010910202440.229 NNEXRAD
>253  SDUS52 KILM 102018 /pNVLLTX
 ...

This demonstrates the allow for NEXRAD for measol on flood.atmos.uiuc.edu.

>[12]ldm on measol-> notifyme -v -l- -h flood.atmos.uiuc.edu -f NMC3 -o 3600
>Sep 10 21:22:43 notifyme[22666]: Starting Up: flood.atmos.uiuc.edu:
>20010910202243.116 TS_ENDT {{NMC3,  ".*"}}
>Sep 10 21:22:43 notifyme[22666]: NOTIFYME(flood.atmos.uiuc.edu): OK
>
>whereas I get nothing here.

I did the exact same thing from a Unidata machine to flood and got the
same results: an OK but no listing of products.  I tried the same thing
with a other top level LDM machines that should be fanning out the
FNEXRAD feed, and got the same result from them also.

>thanks again!

Can you still get NMC3 products on meaculpa (I will be very surprised
if your answer is yes)?  If not, it means that the FNEXRAD feed is down
and has to be looked into.

Tom