[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 11:18:16 -0600
Hi,

re:
> Thank you for such detailed instructions:

No worries.

re:
> I checked the config files (netcheck.conf ; ldmd.conf) for both machines
> and the upstream sites are:
> upstream:lightning.alden.com
> upstream:unidata.ssec.wisc.edu
> 
> and downstream sites are:
> downstream:atm.geo.nsf.gov
> downstream:metlab1.met.fsu.edu

The entries in netcheck.conf are used for monitoring an LDM, but the
entries do not necessarily reflect machines that you are REQUESTing
from or ALLOWing to REQUEST from you, so this information is not
enough.

Here is what you should do:

<as 'ldm'>

- to get a list of your REQUEST(s) to upstream sites:

cd ~ldm
grep -i ^request etc/ldmd.conf

- to get a list of all connections, both upstream and downstream

netstat -T | grep ESTAB | grep ldm

The listings for downstream feed connections will look different
from upstream REQUESTs.  Here is a snippit from one of our machines:

 ...
tcp        0      0 conduit.unidata.ucar.:33318 conduit.ncep.no:unidata-ldm 
ESTABLISHED 
tcp        0      0 conduit.unidata:unidata-ldm oliver.unidata.ucar.e:36404 
ESTABLISHED 
tcp        0      0 conduit.unidata:unidata-ldm atlas.niu.edu:55566         
ESTABLISHED 
tcp        0      0 conduit.unidata.ucar.:33278 conduit.ncep.no:unidata-ldm 
ESTABLISHED 
 ...

In this abbreviated listing, the two REQUESTs to upstream machines are:

tcp        0      0 conduit.unidata.ucar.:33318 conduit.ncep.no:unidata-ldm 
ESTABLISHED 
tcp        0      0 conduit.unidata.ucar.:33278 conduit.ncep.no:unidata-ldm 
ESTABLISHED 

and the two connections from downstream machines are:

tcp        0      0 conduit.unidata:unidata-ldm oliver.unidata.ucar.e:36404 
ESTABLISHED 
tcp        0      0 conduit.unidata:unidata-ldm atlas.niu.edu:55566         
ESTABLISHED

If you were running a current version of the LDM (both castor and pollux are 
running
LDM v6.11.6 while current LDM releases are v6.13.x), you could use the LDM 
utility
'uldbutil' to list out all of the active connections to sites you are feeding.

re:
> If you can point me to LDM/IDD contacts, I'll start a conversation with them.

We still need a correct list before we can point you in the correct direction.

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.