[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20010817: ASU LDM setup
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: Re: 20010817: ASU LDM setup
- Date: Fri, 17 Aug 2001 13:29:21 -0600 (MDT)
Hello Talbot, Welcome aboard! Are you going to be transferring the IP and name of the machine to the new or will we be dealing with a completely new entity? If it is going to change, I suggest keeping the old one up and running until we have the new one running...and you will want to go into your ldmd.conf file and notify all who feed from you and all who you feed from..both primary and failover, and all point to point connects, and notify them of the change and when it will occur. For topo changes like this the more "heads up" we can provide to everyone the better. Soooo, the first thing you will want to do is install the LDM on the new machine. Please see: http://unidata.ucar.edu/packages/ldm/index.html and I suspect you will go with a binary install, unless you desire to muck with the code. So go to LDM Preinstallation Requirements and peruse document, then I would visit LDM Binary Installation Check List and then probably LDM Setup all these are links from the aforementioned URL. These provide step by step instructions on how to load the LDM. I would suggest making copies of your ldmd.conf file and probably your pqact.conf file from your existing machine and transferring them over, this will save you time, and probably some error troubleshooting. There are also many searchable archives for help at the bottom of this page, please feel free to scour them for advice...and as always, when an answer cannot be found please contact address@hidden Thank you and good luck.. I also maintain the topology so please keep me posted as to the new name -if there is going to be one- and when the change will occur. Thanks again, -Jeff ____________________________ _____________________ Jeff Weber address@hidden Unidata Support PH:303-497-8676 NWS-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 Fri, 17 Aug 2001, Unidata Support wrote: > > ------- Forwarded Message > > >To: address@hidden > >From: Talbot Brooks <address@hidden> > >Subject: Shifting data stream > >Organization: UCAR/Unidata > >Keywords: 200108171734.f7HHYQ107330 > > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > --Boundary_(ID_mcjlSALMXaN4spy0vZfv+g) > Content-type: text/plain; charset="iso-8859-1" > > Hi! > > My name is Talbot Brooks and I am the relatively new network administrator > for the Dept. of Geography at Arizona State University. One of our faculty, > Prof. Joe Zehnder, is a recipient of Unidata data streams for NOAAport, > GOES, and NIDS. Currently, our data stream is being handled by a Compaq > Alpha server running Tru64. Recently, we purchased 2 Sun Microsystems 420r > servers. We want to shift the handling of the data stream from the Compaq > to the Sun boxes. I am not terribly familiar with LDM or how the datastream > is handled. Would you be able to help me through this process by outlining > what needs to be done on our end with some pointers to additional > information for each step? > > Thank-you, > > Talbot J. Brooks > Dept. of Geography > Arizona State University > P.O. Box 870104 > Tempe, AZ 85287 > > (480) 965-7832 > > address@hidden > > Visit our web site at: > http://geography.asu.edu > > --Boundary_(ID_mcjlSALMXaN4spy0vZfv+g) > Content-type: text/html; charset="iso-8859-1" > Content-transfer-encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> > <HTML> > <HEAD> > <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = > charset=3Diso-8859-1"> > <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = > 5.5.2653.12"> > <TITLE>Shifting data stream</TITLE> > </HEAD> > <BODY> > > <P><FONT SIZE=3D2>Hi!</FONT> > </P> > > <P><FONT SIZE=3D2>My name is Talbot Brooks and I am the relatively new = > network administrator for the Dept. of Geography at Arizona State = > University. One of our faculty, Prof. Joe Zehnder, is a recipient = > of Unidata data streams for NOAAport, GOES, and NIDS. Currently, = > our data stream is being handled by a Compaq Alpha server running = > Tru64. Recently, we purchased 2 Sun Microsystems 420r = > servers. We want to shift the handling of the data stream from = > the Compaq to the Sun boxes. I am not terribly familiar with LDM = > or how the datastream is handled. Would you be able to help me = > through this process by outlining what needs to be done on our end with = > some pointers to additional information for each step?</FONT></P> > > <P><FONT SIZE=3D2>Thank-you,</FONT> > </P> > > <P><FONT SIZE=3D2>Talbot J. Brooks</FONT> > <BR><FONT SIZE=3D2>Dept. of Geography</FONT> > <BR><FONT SIZE=3D2>Arizona State University</FONT> > <BR><FONT SIZE=3D2>P.O. Box 870104</FONT> > <BR><FONT SIZE=3D2>Tempe, AZ 85287</FONT> > </P> > > <P><FONT SIZE=3D2>(480) 965-7832</FONT> > </P> > > <P><FONT SIZE=3D2>address@hidden</FONT> > </P> > > <P><FONT SIZE=3D2>Visit our web site at:</FONT> > <BR><FONT SIZE=3D2><A HREF=3D"http://geography.asu.edu"; = > TARGET=3D"_blank">http://geography.asu.edu</A> </FONT> > </P> > > </BODY> > </HTML>= > > --Boundary_(ID_mcjlSALMXaN4spy0vZfv+g)-- > > > ------- End of Forwarded Message > >
- Prev by Date: FSL2 Feed
- Next by Date: Re: 20010817: FNEXRAD feed & LSU NOAAPORT
- Previous by thread: FSL2 Feed
- Next by thread: RE: 20010817: ASU LDM setup
- Index(es):