[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: Tue, 10 Mar 2015 16:03:34 -0600
Hi Kevin,

re:
> Thank you for your response.

No worries.

re:
> If I get an error from the closest upstream provider for a
> particular datatype, should I make an attempt to get authorization
> from them or should I just stream data from any upstream site
> that responds 'OK' to a notifyme request?

In the case where the upstream site is in your same institution, it is MUCH
better to contact the LDM/IDD administrator of the site: idd.nrcc.cornell.edu.

Our records indicate that the LDM/IDD administrator of Cornell/NRCC is:

Bill Noon <address@hidden>

A quick search of the Cornell/NRCC web site lists a different address for
Bill:

http://www.nrcc.cornell.edu/page_personnel.html

William A. Noon, Computer Systems Analyst
address@hidden

You should send an email to Bill asking that he setup an LDM ALLOW for your
machine, bubo.ornith.cornell.edu.  You could ask Bill to create an ALLOW
for CONDUIT only, but I suggest that it might be more useful in the long
run to request an ALLOW for all IDD datastreams.

Please let us know if you have problems getting the ALLOW from NRCC.

re: example of 'notifyme' test failure to idd.nrcc.cornell.edu
> [ldm@bubo ldm-6.12.7]$ /web/apps/ldm-6.12.7/bin/notifyme -vl- -f CONDUIT -h 
> idd.nrcc.cornell.edu
> Mar 10 20:26:34 notifyme[2365] NOTE: Starting Up: idd.nrcc.cornell.edu: 
> 20150310202634.367 TS_ENDT {{CONDUIT,  ".*"}}
> Mar 10 20:26:34 notifyme[2365] NOTE: LDM-5 desired product-class: 
> 20150310202634.367 TS_ENDT {{CONDUIT,  ".*"}}
> Mar 10 20:26:34 notifyme[2365] INFO: Resolving idd.nrcc.cornell.edu to 
> 132.236.186.91 took 0.001494 seconds
> Mar 10 20:26:34 notifyme[2365] ERROR: NOTIFYME(idd.nrcc.cornell.edu): 7: 
> Authentication error; No match for request
> ^CMar 10 20:26:37 notifyme[2365] NOTE: exiting

I ran the same 'notifyme' invocation from a machine here in the 
unidata.ucar.edu domain,
and we had no problems being ALLOWed by idd.nrcc.cornell.edu.  This should mean 
that
all is needed is for Bill to setup an ALLOW for your machine.

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