Intergraph InterServe 800 SL User manual

InterServe 800
Late-Breaking News
June 1998
DHA027720

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.

1
General
Disk Activity LED on non-RAID Systems
On non-RAID systems, the RAID disk array status LED does not light to show non-RAID disk
activity. When the system is powered off, this LED is not lit. This differs from the activity of
this LED as described in the System Setup document.
System BIOS Notes
Please note the following items related to the system’s BIOS:
u The troubleshooting information in the System Setup document contains a list of beep
codes and error messages. These beep codes are not used by the current InterServe 800
system board. If your system powers on but does not display any video, check for proper
installation of the memory modules and the video display adapter.
u The BIOS Setup options Floppy Access Control and IDE Hard Disk Access Control (used
to write-protect these devices) have no effect under Windows NT. Windows NT does not
use the BIOS for peripheral device access.
u Immediately after installing a Symbios SCSI adapter card, you must run the Symbios
SCSI Configuration Utility (PCI_CFG.EXE) to disable SCAM on the SCSI adapter card,
and to change the Adapter Boot Order to include the SCSI adapter card. The correct boot
order is as follows:
Boot Order Bus / Device Description
0 0 / 60 Internal SCSI channel
1 0 / 61 External SCSI channel
2 Varies / Varies Symbios SCSI adapter card
The bus and device numbers for the card depend on the slot in which the card is installed.
Enabling the MegaRAID Audible Alarm
On an InterServe 800 with an AMI MegaRAID disk controller, the controller’s audible alarm
is disabled by default. You can configure the InterSite Watchdog program to alert you to
RAID problems such as disk failures. If you want to enable the controller’s audible alarm,
you can do so using the MegaRAID BIOS Configuration Utility or Power Console. For more
information, see Watchdog Help and the InterRAID documentation delivered with the system.

2
Third Channel for Secondary RAID Controllers
When expanding an InterServe 800 to use the third channel of any secondary RAID
controllers, the internal cables extend from the PCI slots to the third-channel ports above the
I/O panel. Attach the internal third-channel cable from one of the additional RAID controllers
to one of the third-channel ports. Repeat this for each of up to four additional RAID
controllers.
NOTE The primary RAID controller (in PCI slot 1) is a two-channel controller.
See the System Reference for information on PCI slot assignments, and the InterRAID
documentation for information on RAID expansion.
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 800 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 doing a physical
reset.
To physically reset the ISM card:
1. Shut down and power off the server. Be sure to turn off the server’s breaker switch.
2. Open the server to get at 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 800 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 SYSTEM32\DRIVERS\HOBBSRV.HDW
file in the system’s Windows NT directory. Change the options at the end of the
HOBBSRV.HDW file to appear as follows:
Hard Reset 1
Power Switch 0
Line Power OK 0
Auxilliary Power 0
Remote Temperature Probe 1
Console Redirection 0
After editing the HOBBSRV.HDW file, you must reboot the server to make the changes take
effect. If a powerdown command is issued, a 3401 error message will display, stating that the
server hardware does not support power control.
Operating System Support for USB Peripherals
Your system includes Universal Serial Bus (USB) ports to which you can connect USB
peripherals. Windows NT 4.0 does not currently support USB peripherals. Microsoft will
add support for USB peripherals to a future Windows NT release.

4
Windows NT 4.0
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.