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

20030703: UGa upgrading to latest LDM-6 (cont.)

>From: "Thomas L. Mote" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200307031521.h63FLfLd024002 LDM-6 rtstats

Tom,

>Thanks much. I will make the changes you suggested.
>One additional, albeit minor, question.

OK.

>The system "noaaport" is actually on a private
>fiber optic network that includes my noaaport
>system, cacimbo, plus my Beowulf cluster (running MM5)
>and my web server. This saves the rest of my building
>from being bogged down with lots of local traffic
>among my systems.

Smart move.

>"Noaaport" is set in the hosts file
>to the IP address for the private network while
>"noaaport.ggy.uga.edu" is set to public IP address.
>I assume that under these circumstances, I do not want
>the fully qualified name. Correct?

You are correct.  Presumably 'noaaport' is running an LDM (hence the
request).  Where does it get its data?  I had assumed that the data
from your PDI ingest system being inserted with the "pdinrsd 3333" and
"pdinrsd 3334" entries.  Just curious...

The overriding objectives of the real time statistics are to report
information that could help troubleshoot data reception and feed
problems for an LDM host.  Sites that ingest data from NOAAPORT
reception systems really aren't concerned with a lot of this, but the
reporting can be useful.  This can be seen by comparing the feed trees
listed in the 'topology' links in the web page I pointed you to
earlier:

http://www.unidata.ucar.edu/staff/chiz/rtstats/siteindex.shtml?cacimbo.ggy.uga.edu

with the same kind of links for Unidata-controlled NOAAPORT ingest
machines like atm.geo.nsf.gov and thelma.ucar.edu:

http://www.unidata.ucar.edu/staff/chiz/rtstats/siteindex.shtml?atm.geo.nsf.gov

http://www.unidata.ucar.edu/staff/chiz/rtstats/siteindex.shtml?thelma.ucar.edu

'atm' is itself an ingest machine.  'thelma', on the other hand, ingests
a lot of its data from a NOAAPORT ingest machine, jackie.unidata.ucar.edu.
Having statistics all along the path from injection to reception allows
one to plot differential latencies in the feeds.  This is done by clicking
links in the 'topology' links for a particular feed on a particular host.

Tom

>From address@hidden Thu Jul  3 20:22:19 2003

re: NOAAPORT setup at UGa
>All of the NWSTG traffic is moved via an LDM running on noaaport,
>which is (as you probably guessed) the noaaport system.
>The GOES channels send their files via pdinrsd, which is meant for
>the transfer of large files like the 1km VIS images.
>
>Thanks again.