20010824: ldm nexrad (cont.)

>From: Mike Trexler <address@hidden>
>Organization: NCSU
>Keywords: 200108241801.f7OI19115758 LDM NNEXRAD

Mike,

>No, F27 doesn't work either.  Ok, so don't laugh, but we're running
>5.0.5.

Yikes (he says as the look of panic spreads across his face :-)!

>We're in the process of setting up a new machine to be the
>new ldm server, but in the meantime I am feeding the new machine
>off our old machine.

>We were still subscribing to the WSI nids data
>for RAX and weren't going to kill that feed until the new machine is
>setup.

That would be the approach I would take as well.

>So that's why I was doing all this.  All this to say that it isn't
>really necessary to make the old version work, since with have the
>new machine up and running with the newest versions of everything.

OK, good.

>Next issue: before we completely change over to the new machine,
>I would like to feed data into both machines for a couple of days to
>make sure we don't loss anything in the transition.  Do you have a
>problem with my requesting to be feed from my upstream (FSU) on
>both machines for a couple of days.  This way I can make sure all this
>nexrad stuff is straight without going through the old ldm.

No, we don't have a problem with this, but you have to remember that
you will double the network bandwidth used for that period of time.
If you are close to saturation on your feeds now (I don't have any
reason to suspect or not suspect this, I just feel like I need to 
make the comment), then a double feed will certainly push you over
the edge.  Also, your upstream feed site has to agree to do this.
I don't think that will be a problem, but you never know...

>thanks

Cheers.

Tom