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

[IDD #HTV-540274]: Registration for Unidata IDD participation

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: [IDD #HTV-540274]: Registration for Unidata IDD participation
  • Date: Sun, 08 Mar 2015 16:51:36 -0600
Hi Kevin,

re:
> Good afternoon!
> I am configuring an ldm site and would like to register for participation in 
> the Unidata IDD.
> 
> Site Name = Cornell Laboratory of Ornithology
> LDM Administrator:
> Name = Kevin Webb
> Phone Number = 607-254-2103
> Email Address = address@hidden
> LDM Hostname = BUBO.ORNITH.CORNELL.EDU
> Desired Feedtypes = NEXRAD2, CONDUIT

Very good.  I just verified that there is both forward and reverse DNS
for your machine:

% nslookup BUBO.ORNITH.CORNELL.EDU
Server:         192.168.72.2
Address:        192.168.72.2#53

Non-authoritative answer:
Name:   BUBO.ORNITH.CORNELL.EDU
Address: 128.84.13.0

% nslookup 128.84.13.0
Server:         192.168.72.2
Address:        192.168.72.2#53

Non-authoritative answer:
0.13.84.128.in-addr.arpa        name = bubo.ornith.cornell.edu.

Reverse DNS is required to have because sites relaying data typically
create ALLOW rules based on fully qualified machine names.

FYI:
Another department in Cornell is already receiving the CONDUIT feed you
want, so it would be best to feed CONDUIT from them.

Here is an example ~ldm/etc/ldmd.conf REQUEST line for CONDUIT data:

REQUEST     CONDUIT   ".*"  idd.nrcc.cornell.edu

The NEXRAD Level 2 radar data in the NEXRAD2 datastream you can REQUEST from
one or more top level IDD relay machines:

idd.meteo.psu.edu
idd.taum.edu
idd.unidata.ucar.edu

An example ~ldm/etc/ldmd.conf REQUEST line would look like:

REQUEST     NEXRAD2   ".*"  idd.meteo.psu.edu

We suggest that you make redundant feed REQUESTs for each datastream.
For instance, replicate the REQUEST lines in your ~ldm/etc/ldmd.conf file:

REQUEST     NEXRAD2   ".*"  idd.meteo.psu.edu
REQUEST     NEXRAD2   ".*"  idd.tamu.edu

The same thing is true for CONDUIT:

RREQUEST     CONDUIT   ".*"  idd.meteo.psu.edu
REQUEST      CONDUIT   ".*"  idd.nrcc.cornell.edu

The first thing you should do is verify that your machine is ALLOWed
to REQUEST the data you want from the upstream hosts mentioned above:

<as 'ldm' on bubo.ornith.cornell.edu>

notifyme -vl- -f CONDUIT -h idd.nrcc.cornell.edu
notifyme -vl- -f NEXRAD2 -h idd.meteo.psu.edu
notifyme -vl- -f NEXRAD2 -h idd.tamu.edu
notifyme -vl- -f NEXRAD2 -h idd.unidata.ucar.edu

If you are ALLOWed on the upstream host, your 'notifyme' invocation will return
a line that looks like:

Mar 08 22:46:28 notifyme[30018] NOTE: NOTIFYME(idd.meteo.psu.edu): OK

NB: you will have to kill the 'notifyme' invocations with a CTRL-C.

re:
> Thank you.

No worries.  Please let us know if you run into any snags.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: HTV-540274
Department: Support IDD
Priority: Normal
Status: Closed