[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20020320: thelma hardware

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: 20020320: thelma hardware
  • Date: Wed, 20 Mar 2002 14:14:01 -0700
>From: Robert Mullenax <address@hidden>
>Organization: Universal Weather
>Keywords: 200203202010.g2KKA6a26082 hardware

Robert,

>I was just curious.  You said that you got a replacement machine for thelma.

We ordered a replacement for thelma.  Delivery is expected in 1.5 - 2
weeks.

>What hardware did you get and OS

Sun SPARC, Solaris.

>and what will thelma be doing?

Actually, thelma might stay in place.  We (Mike and John, our sysadmins)
did a couple of things to try and isolate the problem what was occurring:
remove the gigabit ethernet card and remove 1 GB of RAM.  After his was
done early yesterday, we have been "wailing" on thelma to try and cause
it to fail.  So far, it is purring along nicely.  We will leave thelma
with its current configuration for several days (up to a week), and then
try adding things back in one-by-one - assuming, of course that it is
still running well.  The first thing that will be done is to add back the
1 GB of RAM (to bring its RAM back to 4 GB).  If that works well, we
will turn disk mirroring back on.  If that works correctly, we will
feel pretty confident that the problem was being caused by the gigabit
ethernet adapter.  If all of this goes smoothly, we will continue to use
thelma as a high volume IDD relay.

Tom