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

[IDD #PVY-155954]: new ldm server

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 #PVY-155954]: new ldm server
  • Date: Thu, 18 Aug 2011 11:39:48 -0600
Hi Paul,

re:
> We've previously operated an LDM server (tornado.unco.edu/138.86.201.128)
> for the University of Northern Colorado Earth Sciences Program.
> That server is being brought down, to be replaced by server
> nhsmet01.unco.edu/138.86.64.45.

OK.  A quick check of the name/IP of your new machine shows that neither
forward nor reverse DNS exists for it:

% nslookup 138.86.64.45
Server:         128.117.140.62
Address:        128.117.140.62#53

** server can't find 45.64.86.138.in-addr.arpa.: NXDOMAIN

% nslookup nhsmet01.unco.edu
Server:         128.117.140.62
Address:        128.117.140.62#53

** server can't find nhsmet01.unco.edu: NXDOMAIN

This may be due to the machine not actually being up and on the
network yet (a 'ping' to the machine also fails, but responses
to 'ping's can be turned off in firewalls).

re:
> I am replacing Gary Huffines as our local LDM administrator:
> Paul Nutter, 970-351-2398, address@hidden

Very good.  I have updated our records to reflect this change.

re:
> I'm working to start our new LDM configuration with a simple request
> for IDS|DDPLUS feedtype from IDD.unidata.ucar.edu.  For the most part,
> I am following instructions from the LDM workshop I attended in July.

As soon as forward and reverse DNS are available for your machine,
your LDM REQUEST requests will be honored by your upstream host(s).
Our records (which may be out of date) indicate that your upstream
feed hosts used to be: idd.unl.edu and cirrus.al.noaa.gov.  I
can work with the folks at UNL (idd.unl.edu) and CU/CIRES (rainbow.al.noaa.gov)
to insure that feed REQUESTs from you will be ALLOWed.  Again,
this will occur _after_ both forward and reverse DNS are available
for your machine.

re:
> My initial start appears not be be working.  It may be an RPC connection
> that I'll need to discuss with my network administrators.  Yet, with
> this note, I seek to confirm that we have the appropriate upstream
> authorization from Unidata on our new server.

idd.unidata.ucar.edu will ALLOW a feed REQUEST for any/all non-restricted
datastreams from your machine as soon as there is forward and reverse DNS
for your machine.  Please let us know when this has been setup on the UNC
side.

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