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

20030428: upgrading LDM to 6.0.10 on sunset (cont.)

>From: Jerrold Robaidek <address@hidden>
>Organization: SSEC
>Keywords: 200304242033.h3OKXk7U023728 LDM IDD NOAAPORT

Hi Jerry,

>I have sunshine.ssec.wisc.edu back up and running with a new
>motherboard, and has been stable for over a month.

Excellent.

>I have put
>LDM-6.0.10 on it and I would like to point unidata2 at it, to free
>sunset.ssec.wisc.edu up to be a back up for other ingestors.

I agree that the LDM on unidata2 should point back to sunset.

>Also, since unidata2 has a primary and alternate for each feed does the
>sunshine need to point at another machine as a back up anymore?

No.  What we are striving for is ingesters send to one machine that
acts as an IDD node.  We can't really control a site from feeding more
than one internal machines from their NOAAPORT ingester, but we are
recommending that they do not.

>I
>configured it, so it is not, but I do not know how you guys prefer
>things to be set up.

unidata2 is the IDD node at SSEC, and as you note, it is already setup
to get its primary data form an SSEC NOAAPORT SDI (to be sunset) and
alternate feeds from other top level IDD nodes (which, in turn, are
also fed from NOAAPORT ingest machine(s).

Did you get a chance to look into the ADDE setup on unidata2?  I just
tried pointing at it for the dataset EAST and got nowhere:

DATALOC LIST EAST

Group Name                    Server IP Address
--------------------         ----------------------------------------
EAST                         UNIDATA2.SSEC.WISC.EDU

<LOCAL-DATA> indicates that data will be accessed from the local data directory.
DATALOC -- done

DSINFO I EAST
DSINFO: Accounting data was not valid
    No Datasets found of Type: IMAGE in Group: EAST
DSINFO -- done
 
Also, we would like to explore the possibility of converting our SDI box
from a NOAAPORT single channel receiver into a GOES ingest machine and
then make the data from it available in the same manner as you are doing
on unidata2.  Our motivation is to provide a redundant source of GOES
imagery so that when the availability of the data on unidata2 is finally
announced (this summer), the machine/network at SSEC will not get swamped.
What we need to do this is:

o GOES SDI ingest software
o information on how you are propagating the data from your SDI GOES
  box to unidata2

Any information you can provide would, as usual, be most appreciated.

Tom