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

[IDD #NZC-887525]: LDM at UIB

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 #NZC-887525]: LDM at UIB
  • Date: Mon, 05 May 2014 14:43:16 -0600
Hi Jordi,

re:
> thanks for your help. I'll answer inline so I don't miss any point:

OK.

re: The questions for you now are:
> > - is 130.206.30.86 the correct IP address for your new machine?

> Yes, this is the IP address for the new Eady machine.

OK, you need to work with your networking folks to get forward and
reverse DNS setup for this machine.

re:
> Indeed, we are going to change the DNS to point to this new IP when
> everything's set up.

OK.

re: run some 'notifyme' invocations to see if you are ALLOWed to REQUEST
data from your upstream feed host(s)

> The output for that command was this:
> 
> *eady2:/home/jordi> whoami*
> *ldm*
> *eady2:/home/jordi> notifyme -vl- -f CONDUIT -h idd.unidata.ucar.edu
> <http://idd.unidata.ucar.edu>*
> *May 05 18:57:57 notifyme[8761] NOTE: Starting Up: idd.unidata.ucar.edu
> <http://idd.unidata.ucar.edu>: 20140505185757.567 TS_ENDT {{CONDUIT,
> ".*"}}*
> *May 05 18:57:57 notifyme[8761] NOTE: LDM-5 desired product-class:
> 20140505185757.567 TS_ENDT {{CONDUIT,  ".*"}}*
> *May 05 18:57:57 notifyme[8761] INFO: Resolving idd.unidata.ucar.edu
> <http://idd.unidata.ucar.edu> to 128.117.140.3 took 0.001458 seconds*
> *May 05 18:58:47 notifyme[8761] NOTE: LDM-5 desired product-class:
> 20140505185757.567 TS_ENDT {{CONDUIT,  ".*"}}*
> *May 05 18:58:47 notifyme[8761] INFO: Resolving idd.unidata.ucar.edu
> <http://idd.unidata.ucar.edu> to 128.117.140.3 took 0.001514 seconds*
> 
> It is working correctly, then?

No, it is not.  If the REQUEST that was embodied in a 'notifyme' invocation
was honored (ALLOWed), then you would have seen a line that looks like:

May 05 20:39:44 notifyme[19582] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK

The important part is the 'OK' at the end.  This will tell you that your
REQUEST is ALLOWed on the upstream (idd.unidata.ucar.edu in this case).

re:
> Whenever we change the DNS to point to the
> new address, it should start receiving data?

Yes.  When you get word of the DNS change, you should rerun the
'notifyme' invocations from the machine and verify that the upstream
host is able to use the DNS to convert the IP address that is part
of the REQUEST into a fully-qualified hostname.  That hostname will
then be compared against ALLOWs on the upstream machine to see if
it should honor the feed REQUEST.

re:
> Many thanks for your help.

No worries.

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: NZC-887525
Department: Support IDD
Priority: Normal
Status: Closed