Intergraph InterServe 8000 User Manual

InterServe 8000

Late-Breaking News

November 1998
DHA023060

Copyright

 1998 Intergraph Computer Systems. All rights reserved. This document contains information protected by copyright, trade secret,
and trademark law. This document may not, in whole or in part, be reproduced in any form or by any means, or be used to make any
derivative work, without written consent from Intergraph Computer Systems.

Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subdivision (c)(1)(ii) of the
rights in technical data and computer software clause at DFARS 252.227-7013. Unpublished rights are reserved under the copyright
laws of the United States.

Intergraph Computer Systems, Huntsville AL 35894-0001

Notice

Information in this document is subject to change without notice and should not be considered a commitment by Intergraph Computer
Systems. Intergraph Computer Systems shall not be liable for technical or editorial errors in, or omissions from, this document.
Intergraph Computer Systems shall not be liable for incidental or consequential damages resulting from the furnishing or use of this
document.

All warranties given by Intergraph Computer Systems about equipment or software are set forth in your purchase contract. Nothing
stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such
warrantites.

Trademarks

Intergraph Computer Systems and the Intergraph Computer Systems logo are registered trademarks of Intergraph Computer Systems.
InterServe is a trademark of Intergraph Computer Systems.

Other brands and product names are trademarks of their respective owners.

General

Setting Up Your System for the First Time

When setting up your system for the first time, you should do so as follows:

1. Set up the basic system hardware as described in the system documentation. However, do

not connect any external peripherals to the system’s SCSI ports.

2. Start the system and complete operating system Setup as described in the system
documentation.

3. Use the Windows NT Disk Administrator program to assign drive letter C to the primary
system disk drive.

4. Connect any external peripherals to the system’s SCSI ports.

5. Configure the system as described in the system documentation.

This ensures that any system devices which require access to drive C, and which assume that
drive C is the primary system disk drive, do not operate incorrectly or cause any operating
system errors.

1

See Disk Administrator Help for instructions on assigning a drive letter.

Systems with More Than 2 GB of Memory

Because of an operating system limitation, an InterServe 8400 with more than 2 GB of
memory ships with only 2 GB configured for use, although all memory ordered is installed in
the system. After completing Windows NT Setup, you must set the system’s BIOS to use all
of the system’s memory.

If you reinstall the operating system, you must set the system’s BIOS to limit memory use to 2
GB before starting installation. After completing Windows NT Setup, you must reset the
system’s BIOS to use all of the system’s memory.

NOTE The system’s BIOS must be at revision E (8330E.ROM) or greater.

To set the system’s BIOS to limit or not limit memory use:

1. Restart the system and, when prompted, press

2. In the BIOS Setup menu, select Advanced.

3. In the Advanced menu, select Use Only 2GB of Memory.

DELETE to run the BIOS Setup program.

2

4. Do one of the following, as appropriate:

−

Change the value to Enabled to limit memory use to 2 GB.

−

Change the value to Disabled to use all of the system’s memory.

5. Save the change and exit from BIOS Setup.

6. Restart the system.

You can also reset the BIOS to Optimal to use all of the system’s memory. See the System
Setup document delivered with the system for more information on the system’s BIOS.

NOTE The System Properties dialog (under Start/Settings/Control Panel/System) shows only 2 GB of

memory on systems with more than 2 GB of memory enabled. To verify the correct amount of
memory, check the Memory tab of the Windows NT Diagnostics dialog (under
Start/Programs/Administrative Tools).

Three-Button Primax Mouse

If your system was delivered with a three-button Primax mouse, you may see a message that

says “MouseWare has detected a new Wheel Mouse....” and asks if you want to configure the

new device. If this happens, select No. If you experience any other anomalies while using the
Primax mouse, reinstall the mouse driver found on the Windows NT software CD-ROM.

Logitech Wheel Mouse

If your system was delivered with a Logitech wheel mouse, you can find information on using
it by right-clicking the mouse icon in the taskbar tray, or by going to Start/Settings/Control
Panel/Mouse and clicking Help in the toolbar.

If the wheel on the mouse does not function, or if you experience any other anomalies while
using the wheel mouse, install the
using InterSite Version Manager.

LMOUSE driver software from the Intergraph System CD

Resetting a Hung ISM Card

An InterSite Server Monitor (ISM) card (also called Server Monitor Module [SMM] or
Emergency Management Card [EMC]) in an InterServe 8000 may hang if system power is
turned off, then on again quickly, using the system’s keyswitch.

To determine if the server’s ISM card is hung:

See the Anomalies and Open Problems\Emergency Management Card\EMC Communication
section of the

README.TXT file delivered with the ISM software kit. This section describes

how to identify a hung ISM card, and how to attempt to reset the card without a physical reset.

To physically reset the ISM card:

1. Shut down the server and turn off system power. Be sure to turn off the server’s breaker
switch.

2. Open the server to get to the ISM card. See the documentation delivered with the server
and with InterSite Server Monitor for more information.

3. Unplug the white J1 connector between the battery pack and the ISM card.

CAUTION Gently pull the connector loose. Do not use a metal object to separate the connector from the

socket, and do not pull on the wires in the connector, or damage may result.

4. Reconnect the J1 connector to its socket.

5. Replace the server’s right side panel.

6. Turn on system power.

3

ISM Server Reset Options on a System Without Redundant Power Supplies

On an InterServe 8000 without redundant power supplies, InterSite Server Monitor (ISM)
software does not support the following Server Reset Options:

u

If the Server Poweroff option is selected, the server reboots.

u

If the Server Powerup option is selected, a 3414 or a 3415 error message and a
description of the error displays in the Window Pane of the LANDesk Server Manager
Console. This error message is expected, and may be ignored.

NOTE You cannot power up a local or remote server which does not contain redundant power

supplies.

u

If the Server Reset option is selected, a 3414 or a 3415 error message and a description of
the error displays in the Windows Pane of the LANDesk Server Manager Console. This
error message is expected, and may be ignored.

Generally, the Warm Boot option will suffice to reboot or reset a remote server. However, if
you wish to use the Server Reset option, you must edit the
file in the system’s Windows NT directory. Change the options at the end of the

HOBBSRV.HDW file to appear as follows:

SYSTEM32\DRIVERS\HOBBSRV.HDW

4

Hard Reset 1
Power Switch 0
Line Power OK 0
Auxilliary Power 0
Remote Temperature Probe 1
Console Redirection 0

After editing the
effect. If a powerdown command is issued, a 3401 error message will display, stating that the
server hardware does not support power control.

HOBBSRV.HDW file, you must reboot the server to make the changes take

Installing and Using Power Console

On a server with an InterRAID disk array, you should install the MegaRAID Power Console
software. You should also add a shortcut to Power Console to the Windows NT Startup menu
(Start/Programs/Startup). Power Console provides valuable information about the health of
the RAID disk array, and can help you pinpoint any problems that may occur in disk array
operation. Power Console can even help predict disk array problems before they occur,
allowing you to take action before problems become critical.

Power Console installation is described in the System Setup document delivered with the
system. Power Console is described in the InterRAID documentation delivered with the
system. See Windows NT Help for information on adding a shortcut to the Start menu.

Third Channel for Secondary RAID Controllers

When expanding an InterServe 8000 to use the third channel of any secondary RAID
controllers, the internal cables extend from the PCI slots to the third-channel ports as follows:

u

Attach the internal third-channel cable from the RAID controller in PCI slot 5 to the third­channel port above PCI slot 5.

u

Attach the internal third-channel cable from the RAID controller in PCI slot 6 to the third­channel port above PCI slot 6.

u

Attach the internal third-channel cable from the RAID controller in PCI slot 7 to the third­channel port above PCI slot 7.

NOTE The primary RAID controller (in PCI slot 4) is a two-channel controller.

See the System Reference for information on PCI slot assignments, and the InterRAID
documentation for information on RAID expansion.

Intel PRO/100B Adapter Self-Test Failure

If an Intel PRO/100B network adapter is installed in any of PCI slots 4 through 12, it may fail
the loopback portion of the self-test. However, if you finish configuring the adapter for use,
the adapter works correctly after you restart the system.

Inserting a Power Supply

When inserting a power supply into a running InterServe 8000 (for example, when replacing a
failed power supply), push the supply completely into the system. If the supply does not
power on, simply pull the power supply out, wait at least 45 seconds, and push it back into
place. The DC OK LED on the back of the power supply illuminates to indicate that the
power supply has powered on.

Windows NT 4.0

Installing the Adaptec SCSI Controller Driver

5

If you reinstall the Windows NT 4.0 operating system, be sure to reinstall the driver for the
onboard Adaptec SCSI controller (2940

To install the 2940

1. When prompted, press

2. When prompted, press

3. When prompted, select Other from the list of devices presented.

4. Follow the prompts to install the driver from the 2940
presented with a list of Adaptec SCSI controllers, select the entry for Windows NT 4.0.

NOTE After installing the 2940SCSIDRV driver, you should repeat these steps to install the SYSMSCI

driver (for a non-RAID system) or the MEGARAID driver (for a RAID system), as appropriate.

SCSIDRV driver during Setup:

S to bypass detection of mass storage devices.
S to specify a mass storage device other than those listed.

SCSIDRV) from backup diskette during Setup.

SCSIDRV backup diskette. When

Installing the Write Cache Utility

The Write Cache Utility, a Windows NT service that runs at system startup, was installed on
the system before shipment. This utility enables write-caching on each hard disk drive not
attached to a RAID controller. This improves the performance of RAID-capable disk drives
in a non-RAID environment.

6

If you reinstall the Windows NT 4.0 operating system, be sure to reinstall the Write Cache
Utility. See the
the utility.

README.TXT file on the WRTCACHEUTIL diskette for instructions on installing

Installing QFE Software

Quick-Fix Engineering (QFE) update software contains fixes for operating system problems or
limitations. If a system requires Quick-Fix Engineering (QFE) update software, it is installed
on the system before it leaves the factory. If QFE update software is installed on the system, a
QFE backup diskette is delivered with the system. You can also create a QFE backup diskette
using InterSite Version Manager.

If you reinstall the Windows NT 4.0 operating system, and the Windows NT 4.0 Service Pack
3 software, be sure to reinstall the QFE update software as well. Install the QFE update
software after you reinstall Service Pack 3 software. QFE update software contains post­Service Pack 3 fixes.