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

[IDD #ICA-648762]: COAMPS and NOGAPS data

Hi Brice,

re:
> Technically, we are not supposed to transmit IP addresses in the clear.
> However, since this is a system that is accessible from the Internet -
> 198.122.138.134 would be our standard LDM contact.

OK. This machine should now be able to request the FNMOC feed from
either of the following toplevel IDD relay nodes that we maintain:

idd.cise-nsf.gov
idd.unidata.ucar.edu

Please try the following and return the results:

<as 'ldm' on 198.122.138.134>
notifyme -vl- -f FNMOC -h idd.cise-nsf.gov
notifyme -vl- -f FNMOC -h idd.unidata.ucar.edu

> I'll have to look into the rtstats.  We don't report anything
> at this time because we haven't been on anyone's 'open' net,
> just to selected NASA and NOAA sites.

I understand.  I would be useful to us if you did report stats
from the machine receiving the FNMOC feed.  By the way, in case
reporting stats other than for FNMOC is a issue, you can include
the '-f FNMOC' flag on the ~ldm/etc/ldmd.conf 'exec' for 'rtstats':

exec   "rtstats -f FNMOC -h rtstats.unidata.ucar.edu"

> Per our user's (the Spaceflight Meteorology Group, i.e. Brian,
> Paul, Doris, et al) requirements, our firewall is open on port
> 388 and controlled by the ldmd.conf(s).

Excellent.

> So ldmping and notifyme will work;

I tried this from one of the nodes in our idd.unidata.ucar.edu cluster
and found that it did not work for us:

notifyme -vl- -h 198.122.138.134
Apr 30 22:46:58 notifyme[28454] NOTE: Starting Up: 198.122.138.134: 
20090430224658.217 TS_ENDT {{ANY,  ".*"}}
Apr 30 22:46:58 notifyme[28454] NOTE: LDM-5 desired product-class: 
20090430224658.217 TS_ENDT {{ANY,  ".*"}}
Apr 30 22:46:58 notifyme[28454] ERROR: NOTIFYME(198.122.138.134): 7: Access 
denied by remote server
^CApr 30 22:47:01 notifyme[28454] NOTE: exiting

Presumably you will need to configure your firewall to allow our
LDM requests.

> I use ldmping for testing the circuit now from our development
> systems.  The firewall also allows 388 traffic out without restriction.
> 
> So let me know what gets set up and I will make sure that the
> appropriate entries be made on our end.  And if you can tell me
> what systems will be contacting or replying to ours it would help me
> to mod my firewall filters so that I don't get a lot of
> 'who the heck is this?' messages from it.

OK.  Here is a list of names/IPs for machines that we would appreciate
being allowed port 388 access through your firewall:

oliver.unidata.ucar.edu  - 128.117.156.17
emo.unidata.ucar.edu     - 128.117.140.63
yakov.unidata.ucar.edu   - 128.117.156.86
laraine.unidata.ucar.edu - 128.117.140.62

Thanks in advance for allowing these machines..

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