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

20031024: New System at UNI

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: 20031024: New System at UNI
  • Date: Fri, 24 Oct 2003 10:41:02 -0600
>From: "Patrick O'Reilly" <address@hidden>
>Organization: UNI
>Keywords: 200310241337.h9ODbAOb017830 IDD node

Patrick,

>We here at UNI have acquired a new system through a Unidata grant.  The plan
>for this system, among other things, is to become a relay node on the IDD,
>instead of a leaf node, which our machine, blizzard.storm.uni.edu, is now.
>The machine won't be ready for a week or two, but I wanted to get this in
>motion and figure out the who-what-when-where-why-how of the change as far
>as Unidata is concerned.

I am not quite sure of what you are asking, but here is what I can
offer:

- get the machine setup with all of the available OS patches (make sure
  that this includes the recent patch for OpenSSH).

- make sure that you have a complete development environment inststalled

- make sure that DNS is setup to provide forward and reverse name lookup
  for the new machine

- if you are behind a firewall, make sure that the firewall is setup to
  allow bidirectional traffic through port 388

- download the latest LDM version (currently LDM-6.0.14), and build it
  from source and install it.  Make sure that you set it up to report
  real time statistics back to the UPC.  Make sure that all requests
  for data are made by machine name, not IP address (wherever possible)

- have your new machine feed off or your current LDM node to exercise
  your LDM installation

- if your new LDM is supposed to take over from your existing node, send
  email to all of your upstream feed sites so that they upgrade their
  allow lines in their ldmd.conf files and stop and restart their LDMs

As far as your machine acting as an IDD relay node, we would then monitor
the connectivity of the machine and decide where it would fit nicely
into the IDD.

Given the "beefy" nature of your machine, you might consider making
data available from it using THREDDS technologies (OpenDAP and McIDAS-ADDE).
We can talk more about this later since it is not something you would
do immediately.

>The system is a Dell Precision 650, dual 3 GHz
>Xeon Processors, 2 GB memory, 250 GB hard drive, RedHat 9.  Thanks!

Nice!

Tom

>From address@hidden Fri Oct 24 11:46:29 2003

Exactly what I was looking for. Thanks Tom!

Patrick