Re: 20030106:LDM Server replacement

Hi Jim, 

LSU, Nebraska, and others are doing just that.

I know it can be done, details....I would need to dig a bit, but will get
some info to you re the dish/ldm tandem config.

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 Tue, 7 Jan 2003, James T Brown wrote:

> Jeff:
> 
> 
> > Sorry for the delayed response, family emergency yesterday.
> 
> No problem with the delay.  I should have been a little more careful
> with my own record keeping.   Thanks for sending out the list of my
> upstream nodes.  I will be sure to contact them with my new IP and
> host information.
> 
> On a somewhat related note.  We also have access to a NOAAPort feed
> (Unisys) here at Michigan, but have yet to fully implement it.  While
> rebuilding the server, I may try to make more use of the NOAAPort 
> stream.  Is it possible to feed streams from NOAAPort and the IDD
> into the same LDM queue?  I have noticed in the past that our NOAAPort
> feed using "pqact" will occasionally drop or hang - when this happens,
> "ldmadmin stop" won't even terminate the process.  Haven't look into
> this enough to determine what the problem is, but just curious how
> many sites are running IDD with NOAAPort as a backup or vice-versa.
> 
> Thanks again.
> 
> 
> -jim
> 
> 
> 
> 
>  
> > 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
> > >
> > >
> 
> -- 
> ==========================================================
> James T. Brown   
> UNIX Systems Administrator
> Geography/Fisheries & Wildlife
> Michigan State University
> 
> email: address@hidden
>