20000302: ldm on linux

>From: Tom Priddy <address@hidden>
>Organization: University of Kentucky
>Keywords: 200003021359.GAA00836 LDM Linux

Tom,

>We've brought up ldm on a new linux system. No data is coming in. Do
>we need to provide you certain info (ie machine name, etc) to get
>that to work.

The upstream machine(s) that are to feed you need to be informed about
the machine that is to be fed.  Since you should only have one machine
getting an IDD feed from external sources, you should turn off ingestion
on the current machine when you switch to the new one.  Some things to make
sure of before contacting your upstream sites are:

o you followed Linux-specific instructions for the LDM build
o your machine satisfys both forward and reverse name lookup:

  nslookup fully_qualified_machine_name
  nslookup machine_ip_address

  The nslookup using the machine name must return back the correct IP
  address; the nslookuup using the IP address must return back the
  exact same machine name.

If you don't know your upstream contact information, you can find it
on the Site Contact web page:

Unidata HomePage
http://www.unidata.ucar.edu
  Internet Data Delivery (IDD)
   http://www.unidata.ucar.edu/projects/idd
     Current Operational Status
     http://www.unidata.ucar.edu/projects/idd/iddgeneral.html#status
       IDD site contact list
       http://www.unidata.ucar.edu/projects/idd/sitelist.html

Please CC us on these communications.

>We also have ldm working on our unix machine. Must
>we bring down the unix ldm before the linux ldm can operate?/ktp

Given the volume of data flowing through the IDD, it is wise to have
only one feed into a campus, much less a department.  When you inform
your upstream feed site(s) about the new machine you want fed, it is
most likely that they will turn off feeds to your old machine.  You
could request that they don't do this until you tell them that the new
machine is fully up and running, but I caution you that if you let the
dual feeds go, you will start having network congestion problems.

Tom Yoksas