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

[NOAAPORT #PYS-247015]: Missing Noaaport Data

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: [NOAAPORT #PYS-247015]: Missing Noaaport Data
  • Date: Wed, 13 Aug 2014 13:14:03 -0600
Hi Randy,

re: what version of the TDS are you running
> Looks like i'm running 4.0.8...time for an upgrade i guess.

I would say yes.

re:
> Ok, that makes sense that there will be changes after NOA
> upgrades their downlink.

And after additions to CONDUIT that should be upcoming sometime
in the fall (I don't know what these will be, but you can bet
that some are related to HRRR output).

re: our not receiving your real-time stats is likely due to your firewall

> I bet our guys are blocking it.

I agree.

re:
> you should noaapxcd.it-protect.com.

OK.  The only machines listed in our real-time stats pages that have
'protect' in their name are at NSSL.

Just to be sure that is how your machine(s) should report, please check
the hostname setting.  This would be in:

~ldm/etc/ldmadmin-pl.conf for older versions of the LDM (e.g., 6.8.1)
~ldm/etc/registry.xml     for new versions of the LDM (e.g., 6.11.x, 6.12.x)

re:
> It's definitely behind a firewall.

Yes, aren't we all.  Most .edu firewalls, however, are not setup to block
outbound traffic.  Pretty much all .mil, an increasing number of .gov and
some .com firewalls, on the other hand, are setup to block outbound traffic.

re:
> So i should ask them to open port 388 outbound only?

If our not receiving your real-time stats is being caused by the firewall
configuration there, and if you would like to report the stats so that
we can help you (learn to) troubleshoot problems so you don't have to
reply on us, then yes, I suggest that you should request that outbound
traffic to port 388 should not be blocked.  If it is desired to keep this
pretty locked down, I would ask that it be opened for port 388 on
machines in the unidata.ucar.edu domain.  This includes the 128.117.140,
128.117.156, and 128.117.149 subnets.

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: PYS-247015
Department: Support NOAAPORT
Priority: Normal
Status: Closed