20030416: 20030415: Real-time data flow (cont.)

>From: Jerrold Robaidek <address@hidden>
>Organization: SSEC
>Keywords:  200302072325.h17NPB625996 IDD UNIWISC unidata2

Hi Jerry,

re: machines that have connected to gold for UNIWISC data

>The ldm on gold has been up since Nov 22

re: following hosts have connected at some time since Nov 22

Unidata controlled machines

Machine                            Status
----------------------------------+-----------------------------------
emo.unidata.ucar.edu               feeds from thelma.ucar.edu
motherlode.ucar.edu                moved to unidata2 20030418
thelma.ucar.edu                    moved to unidata2 20030418

non-Unidata machines

Machine                            Status
----------------------------------+-----------------------------------
f5.aos.wisc.edu                    moved to unidata2 20030417
ldm.comet.ucar.edu                 moved to unidata2 20030413
ldm.meteo.psu.edu                  moved to unidata2 20030417
snow.nrcc.cornell.edu              moved to unidata2 20030418
stokes.metr.ou.edu                 moved to unidata2 20030417
sunny.atmos.washington.edu         moved to unidata2 20030417

The site that has not moved yet is: flood.atmos.uiuc.edu

I will be sending an email to the LDM administrator at Illinois this
afternoon.

So, the move away from gold should be almost over.  For a sanity check,
it would be a good idea if you could jump back onto gold and find out
who is receiving UNIWISC/MCIDAS data.  The easiest way to do this my be
to use netstat:

netstat

Look for entries that end in ".388" or ".ldm" in the Foreign Address
column.  If nobody else has connected to gold, you should only see one
unique machine being fed from gold's LDM.

Tom