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

[IDD #BFR-463999]: Hostname change for upstream data feeds

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 #BFR-463999]: Hostname change for upstream data feeds
  • Date: Mon, 22 Apr 2019 08:33:05 -0600
Hi,

re:
> Purdue University currently runs two LDM hosts (castor.rcac.purdue.edu &&
> pollux.rcac.purdue.edu), we are upgrading these machines and would like to 
> change
> hostnames to (nexrad-00.rcac.purdue.edu && nexrad-01.rcac.purdue.edu).

OK.  Please make sure that there is both forward and reverse DNS for
the machines's new names.

re:
> Looking at the documentation, the upstream LDM’s administrators need to allow 
> entries
> for our new LDM hosts.
> 
> https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/configuring.html#upstream%20config

This is correct.

re:
> Can you point me to the steps/procedures to follow?

The first thing you need to do is make sure that there is forward and reverse
DNS for the new machine names

The second thing you need to do is generate a list of all of the upstream 
machines
that you are REQUESTing feed(s) from.

The next thing you need to do is ascertain who the appropriate LDM/IDD contacts
are for those upstreams.  We should be able to help you determine who the
appropriate contacts are, but our ability to determine this is not guaranteed.

The next thing you need to do is inform the LDM/IDD contacts at each upstream
of the machine name change.

The last thing you need to do is to inform the LDM/IDD administrator responsible
for each downstream that you are feeding data to inform them of the need to
change their REQUEST line(s).

All of the above needs to be coordinated so that a smooth transition is 
accomplished.


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: BFR-463999
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.