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.
Hi James, Sorry for the delayed response, family emergency yesterday. I will update the sitelist doc: http://www.unidata.ucar.edu/projects/idd/sitelist.html to indicate your new machine name and IP. I have you feeding from: sunset.meteor.wisc.edu as a primary contact: Pete Pokrandt address@hidden with flood.atmos.uiuc.edu contact: David Wojtowicz address@hidden and twister.millersv.edu this I believe has changed to twister.millersville.edu (may want to double check with them) doing an ldmping indicates both are up.. contact: Dave Fitzgerald address@hidden as back-ups. As for the lightning feed (NLDN) you will need to contact David Knight at SUNY-Albany contact: address@hidden Please let me know if you encounter any problems, I will make the change here today to reflect the new machine. Thanks for the update! Cheers, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 COMET Case Study Library FX:303-497-8690 University Corp for Atmospheric Research 3300 Mitchell Ln http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 ________________________________________ ______________________ On Mon, 6 Jan 2003, Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden > >cc: address@hidden > >From: James T Brown <address@hidden> > >Subject: ** LDM Server replacement > >Organization: UCAR/Unidata > >Keywords: 200301061741.h06Hfpt16458 > > Unidata Support: > > My LDM server went down last night due to hardware > failure. I will be using this as an opportunity to > upgrade to the latest version of the LDM software > while switching over to a new server this afternoon. > > The machine that failed was listed as: > > cirrus.geo.msu.edu > > > and the new machine will be named: > > accas.geo.msu.edu (35.9.73.98) > > > > Now the fun part, I need to notify those upstream > sites that were feeding me data, but those records > are kept on the machine that died (pretty smart not > to have a hardcopy of the config file readily available). > At any rate, I believe my primary was Wisconsin and my > failover was UIUC. I also believe that I was receiving > NDLD data from Albany. > > Can you confirm this with your records? Do I need > to notify these sites individually with my new hostname > and IP information or can you pass it along for me? > > Thanks. > > -jim > > > > > -- > ========================================================== > James T. Brown > UNIX Systems Administrator > Geography/Fisheries & Wildlife > Michigan State University > > email: address@hidden > > > ------- End of Forwarded Message > >