HP D7171A - NetServer - LPr User manual

HP NetServer
SCO UNIX Installation Guide
NOTICE: The information in this document was last updated for the HP NetServer Navigator CD-ROM version
L.19.00. If you don't have the L.19.00 version CD-ROM and you're obtaining this document from the HP NetServer
web site as a reference to install an operating system, be sure to also check the HP NetServer web site for the latest
available drivers.
©Copyright Hewlett-Packard Company
August 28, 2000.
Introduction
This document presents very important information that you need to install SCO UNIX.
The first section of this document is a list of helpful tips on NOS installation, the second
section is a step-by-step installation guide.
NOTE: Hewlett-Packard has more than one Disk Array Controller (DAC) for the
NetServer product family. In this document the term "HP Disk Array" refers to
the EISA and PCI Disk Array Controller models C3609A and C3610A,
respectively. The term "HP NetRAID" refers to the HP NetRAID and NetRAID-
1 PCI Adapters models D4943A and D4992A, respectively. The term “HP
NetRAID 1Si refers to model number D2140A. The term “HP NetRAID 3Si”
refers to model number D5955A. The term “HP Embedded RAID” refers to the
built in RAID controller on the HP NetServer LH 3 and LH 4.
The HP NetServer E 30 does not support either DAC.
The HP NetServer E 40 , E 45 and E 50 support the HP NetRAID DACs only.
The HP NetServer E 60 only the HP NetRAID 1Si and HP NetRAID 3Si.
SCO MPX 3.0 does not work correctly on multiprocessor systems using the Intel
Pentium Pro, Pentium II or Pentium III processor (e.g. the NetServer LC II, LC 3,
LD Pro, LH Pro, LH II, LH 3, LH 4, LPr, LX Pro, LXe Pro, LXr Pro and LXr
8000).
SCO Open DeskTop 3.0, OpenServer 3.0, and MPX 3.0 are not supported on the
NetServer LC 3, LH 3, LH 4, LXr 8000, and LXr8500.
SCO OpenServer 5.0.x is supported on the NetServer E60, E 800 LPr, LC2000,
LC3, LH3, LH3000, LH4, LXr 8000 and LXr8500

Table of Contents
Section 1. General Tips
Introduction
CaSe SeNsItIvE
Start Counting At Zero
Set Up All Cards In ECU or BIOS Setup Utility
Installation To Disk Arrays
Installation Media
Swap Space
Additional File Systems
Configuring Mouse
Configuring Video for Unix
BTLD Tips
Driver Names for HP-Supplied Controllers
Troubleshooting
N1 and N2 Diskettes
Common Errors
The System Hangs without any Error Messages
Serialization Fails
Section 2. Installation Guide
Large Memory Access
SCSI Extended Translation Setting
MPS Table Setting On NetServer LS and LX for SCO MPX
Logical Disk Size for the HP Disk Array and the HP NetRAID Controllers
HP Disk Array Controller Logical Disk Addressing
HP NetRAID Controller Logical Disk Addressing
HP NetRAID Controller Utilities
Booting from the Embedded Scsi Controller
Drivers for HP Network Cards Available on HP NetServer CD-ROM
Manually Configure the Network Speed on the HP J3171A and D5013A NIC
Installing Multiple NICs
Adding a DAC as a Secondary Controller to an IDE System
Installing SCO UNIX 3.2v4.2, SCO ODT 3.0, OpenServer 3.0, and MPX 3.0
Installing SCO OpenServer 5.0.x

Section 3. On-Line Information and Software Sources
Section 1. General Tips
Introduction
The following subsections discuss problems that you may encounter when installing SCO
UNIX 3.2v4.2, Open Desktop (ODT) 3.0, OpenServer 3.0, MPX 3.0, and OpenServer
5.0.x.
SCO UNIX installation procedures include installing SCO UNIX files, loading all
required drivers (including BTLD (Boot Time Loadable Driver) packages), and linking
information to the kernel.
As a rule, select fully configurable, rather than automatic, initialization.
CaSe SeNsItIvE
All version of UNIX are very case sensitive and you need to be absolutely sure that you
type in the commands exactly as instructed. Almost all UNIX commands are in lower
case so if you are unsure try lower case first.
Start Counting At Zero
In almost all cases a UNIX system will start counting at ZERO. Therefore, SCSI
Controller 0 is the first controller, SCSI Channel 0 is the first channel, Hard Disk 0 is the
first hard disk, etc.
Set Up All Cards In ECU or BIOS Setup Utility
SCO UNIX likes to have all cards and disk drives configured in CMOS to work properly.
SCO can actually read the system configuration information. This means that before you
try to configure SCO to use a particular adapter card in the system go in and make sure
that it is set up in the ECU or BIOS setup utility. Even if it is an ISA adapter without a
config file go into the ECU and add a "Generic ISA Adapter" and assign the appropriate
resources such as DMA, Memory, and IRQ to match the settings of the card. (There is a
config file for a Generic ISA Adapter on the NS#2 diskette or Navigator CD-ROM. Add
it as a non-HP board).
Installation To Disk Arrays
Installation to a logical drive, on a disk array, larger than 2048 MB is not recommended.
For SCO versions 5.0.x, larger drives are possible but for backwards compatibility and
ease of system administration logical drives smaller than 2 GB are recommended for your
root drive. Utility Partition Access Disabled

During SCO UNIX installation, access to the Utility Partition built by the Configuration
Assistant is disabled. Select "Skip" if Configuration Assistant asks you to build the
Utility Partition.
Installation Media
The following installation media is required in addition to the main product CD-ROM or
tape to install SCO UNIX.
For UNIX 3.2.4.2: N1, N2, and M1 diskettes, and the HP Drivers Diskette.
For ODT 3.0 and OpenServer 3.0: N1, N2, and the Release Supplement diskettes, and the
HP Drivers Diskette.
For MPX 3.0: MPX 3.0.0j, APIC 1.1 from the AHS 3.4.0 distribution, and SLS
UOD393E (or later) "Performance Supplement" diskettes. You may also want to use
SLS UOD421A (or later) to get the latest APIC driver which supports MPS Specification
1.4.
For OpenServer 5.0: The Boot Disk, the Release Supplement 5.0.0d (or later) diskettes,
and the AHS 5.2.0 (or later) BTLD for the latest arad and alad SCSI drivers, and the HP
Drivers Diskette.
For OpenServer 5.0.2: The Boot Disk, and the AHS 5.2.0 (or later) BTLD for the latest
arad and alad SCSI drivers, and the HP Drivers Diskette.
For OpenServer 5.0.4: The Boot Disk, the Release Supplement 5.0.4c, and the HP
Drivers Diskette.
For OpenServer 5.0.5: The Bootable CD-ROM, the Release Supplement 5.0.5a, and the
HP Drivers Diskette.
For OperServer 5.0.6: The Bootable CD-ROM and the HP drivers Diskette.
Swap Space
You may wish to increase the swap space from the default provided. UNIX uses the
swap space to swap the least-recently used pages in and out of memory. If you have the
disk space available, you might consider using the default, or doubling the size of the
physical memory, whichever is greater.
Additional File Systems
Selecting "/u file system", or some other file system in Release 5.0.x, sets up a separate
file system in addition to the root file system. If you select an additional file system, you
will then be asked to allocate disk space between your root and your additional file
system.

Be sure to leave enough space in your root file system for installing future applications.
Remember that any application files that you place in your /u file system reduce the space
left for user data files.
A scratch division is an area that FSCK (file system check) uses to record data in case of
a problem. It is probably safer to accept a scratch division, so that FSCK can function
properly if you ever need it.
Configuring a Mouse
All HP NetServers have a PS/2 style mouse. This is also know as a mini-DIN or
keyboard mouse. If you want to configure such a mouse as part of the operating system
installation, choosing "Low resolution Keyboard mouse" is the safest choice for
specifying mouse type. If this is not correct, it can always be changed after the system is
up and running.
Configuring Video for UNIX
When configuring the video for UNIX, standard VGA is the safest choice. You can enter
the correct video driver after the system is up and running. The following video chips are
used in the HP NetServers:
E 30: S3 Trio 64V+, 1MB or 2MB video memory
E 40, LC II, LC 3, LH 3, LH 4, LPr, LXr 8000: Cirrus Logic CL-GD5446, 1MB or 2MB
video memory
E 45, E 50: Cirrus Logic CL-GD5446, 2MB video memory
E 60: ATI Rage IIc AGP video card, 4MB video memory
LC Plus, LD Pro, LH, LH Plus, LH Pro and LH II: Trident TVGA9000I, 512KB video
memory
LS, LX Pro, LXe Pro, LXr Pro: Cirrus Logic CL-GD5424, 512KB or 1MB video
memory
LC 2000, LH 3000 LH 6000, LT 6000r: ATI Rage II c on board card, 2MB video
memory
E 800: ATI Rage XL on board card, 4MB video. Driver and install guide can be copied
from Navigator CD SCO Driver diskette
The wrong video driver can produce blank or unreadable screen displays at the higher
(greater than 640 x 480 VGA) resolutions.

BTLD Tips
The HP NetServers use the BTLD for the internal SCSI controllers. The BTLD is a
driver that can be link-edited into the UNIX system kernel during the booting process.
The link-editing is done by boot (HW) after the driver is loaded into memory, but before
the kernel is started. The HP NetServer Manager CD creates a diskette containing the
SCO UNIX BTLDs.
For the UNIX 3.2v4.2 and 3.0 products, you need an HP disk controller driver diskette
that is created by the HP NetServer Navigator CD. This diskette contains the alad, arad,
amird, and mdac drivers.
For OpenServer 5.0.x, the SCSI controller drivers are built into the SCO product. HP
recommends that you use the latest arad and alad drivers that SCO ships. These drivers
are available from SCO on their AHS 5.2.0 (or later) BTLD disk. HP only ships the
drivers for the HP Disk Array Controller (mdac), the HP NetRAID Controller (amird),
the Adaptec alad driver (use alad325 on the link line), the Adaptec blad driver for SCSI
Ultra 2 (use blad325 on the link line) and the Symbios slha driver (use symha on the link
line), but not the Adaptec arad driver, on the driver diskettes that are created by the HP
NetServer Navigator CD.
Driver Names for HP-Supplied Controllers
The following table lists the names of required drivers for the HP-supplied controllers.
NetServer Controller Package Name
E 30,40,45,50 AHA2910 alad or alad325
E 60 AHA7895 alad or alad325
E 800 Symbios 895 slha
LC Plus AIC7770 arad
LC II,3 AIC7880 alad or alad325
LD Pro AIC7880 alad or alad325
LH AIC7855 alad or alad325
LH Plus, LH Pro AIC7880 alad or alad325
LH II AIC7880 alad or alad325
LH 3, LH 4, LPr Symbios 53C895 symha
LH 3000 Symbios 895 slha

LH 3000 AIC7870 alad325
LH 6000 Symbios 895 slha
LH 6000 AIC7870 alad325
LT 6000r Symbios 895 slha
LS AIC7870 alad or alad325
LX, LXe, LXr
Pro
AIC7880 alad or alad325
LXr 8000 Symbios 53C896 slha
All HP Disk Array mdac
All HP NetRAID amird
NOTE: HP currently does not support ultra SCSI mode on the AIC7880
controllers when they are connected to the HP Storage System 6. Ultra SCSI
mode is supported for disks installed in the HP NetServer cabinet and in the HP
NetServer Rack Storage System 8 and 12.
Troubleshooting
SCO OpenServer is very specific about the hardware configuration it expects when
installing. The following limitations apply:
The root hard disk and the install device should both be on the primary SCSI channel.
The root hard disk must be SCSI ID 0. The first SCSI tape drive must be SCSI ID 2.
The first SCSI CD-ROM drive must be SCSI ID 5, or for an IDE CD-ROM use the
CD-ROM as the master device.
The correct SCSI ID is especially important if you are installing from the tape or CD-
ROM drive. If you have a complicated hardware configuration, install SCO
OpenServer using only the minimum system required to install. All additional
hardware can be added afterwards.
N1 and N2 Diskettes
SCO OpenServer comes on floppies, QIC525 tape, or CD-ROM. All versions prior to
OpenServer 5.0.5 require booting the system off the N1 Installation diskette, and perhaps
using the N2 diskette, to build a rudimentary UNIX system as part of the installation
process. OpenServer 5.0.5 has a bootable CD-ROM for installation.

Any error that occurs when you first boot off the N1 diskette is a hardware problem.
Either some piece of hardware is bad or there is a serious hardware configuration error.
Fix this problem before trying to install SCO OpenServer.
When booting off the N1 diskette, always use the link command to link the appropriate
SCSI driver into the system (alad for the E 30, E 40, E 45, E 50, E 60, LC II, LC 3, LD,
LH, LS, or LX; symha for the LH 3, LH 4, LPr, LXr 8000, or LXr 8500). Refer to the
SCO Installation Manual for how to use the link command and the SCO OpenServer
drivers disk for the various NetServers. This driver is not permanently linked into the
kernel until the end of the SCO OpenServer installation.
Most installation errors will occur after inserting the N2 diskette.
Common Errors
The following is a list of error messages and solutions.
WARNING: HD: NO ROOT DISK CONTROLLER
This usually indicates that the NetServer SCSI driver (e.g. alad) was not linked into the
system. One way this can happen is when the installation reaches the point where you
have the following choices:
1. Continue with Installation
2. Install additional packages and you chose 1.
This is the wrong choice when you are adding a BTLD driver such as alad to the
system. You must choose 2 to complete the installation of the alad driver. This may
also happen if the root hard drive is not on the primary SCSI channel.
ALAD: ADAPTER 0 ERROR: SELECTION TIMEOUT
This error could occur if the root hard disk SCSI ID is some value other than 0. The boot
HD must be SCSI ID 0. This could also occur if the hard disk is on the wrong channel in
systems that have the dual channel SCSI.
ALAD: ADAPTER 0 ERROR: SELECTION TIMEOUT: COULDNOT EXTRACT
FILES FROM /DEV/...
The ... in the error message indicates that device that you are using to install SCO
OpenServer. For example, it will be: /dev/Stp0 if you are installing from the QIC525
tape. This message says that SCO OpenServer could not access the device. Check that
the device is working. Check that the SCSI ID is correct. Using any SCSI ID other than
the ones previously listed will not work.

The System Hangs without any Error Messages
This is probably a SCSI bus problem. Check the SCSI setup for errors. Make sure all the
SCSI devices are seen on boot up. One symptom of a SCSI bus termination error is that
some devices are not seen on boot up. Check for bad SCSI devices, bad SCSI
connectors, bad termination, duplicate SCSI IDs.
Serialization Fails
Once you have verified that you have entered the correct serial number/activation key,
check the permissions on the /tmp directory (l -d/tmp). The /tmp directory should have
the following permissions: drwxrwxrwt.
If the permissions differ, enter the following command: chmod 1777 /tmp.
Section 2. Installation Guide
Large Memory Access
SCO UNIX 3.2v4.2, Open DeskTop 3.0, OpenServer 3.0, and MPX 3.0 are limited to 512
MB of physical memory (RAM). The system will ignore any memory above 512 MB.
SCO OpenServer 5.0.0 and 5.0.2 can access 512 MB of physical memory (RAM) without
any patches. The systems can access up to 4 GB of memory by installing the SCO Large
Server Supplement. OpenServer 5.0.0 requires Large Server Supplement version 1.0.0.
OpenServer 5.0.2 requires Large Server Supplement version 1.1.0. OpenServer 5.0.4,
and later, supports 4 GB of memory without requiring patches.
When installing OpenServer 5.0.0 or 5.0.2 on systems with more than 2048 MB (2 GB)
of memory you will need to limit the memory search during the installation process. To
limit the search add the following string to the boot line you use to start the system
installation:
mem=1m-1024m
After the system is installed you can set the correct memory size in the file
“/etc/default/boot”. See the man page for “boot” for the syntax of this file.
There is a defect in OpenServer 5.0.0 and 5.0.2 that causes the system to report a negative
memory size on systems with more than 2 GB of memory. This defect does not appear to
cause operational problems but it may cause problems for shell scripts that use the
“memsize” command.
SCSI Extended Translation Setting
The SCSI extended translation setting for disks with a capacity larger than 1 GB should
be set to ‘disabled’ for all versions of SCO UNIX, Open DeskTop, and OpenServer 3.0.
For OpenServer 5.0.x you can use SCSI extended translation. (Run the EISA

Configuration Utility, or the AIC SCSI BIOS utility <Ctrl>-A, or <Ctrl>-C for Symbios
BIOS utility to set this parameter.)
MPS Table Setting On NetServer LS and LX for SCO MPX
For the HP NetServer LS and LX with multiprocessors, you must set the MPS
configuration parameter to the correct MPS Table setting.
1. Run the EISA Configuration Utility.
2. Move to the MPS Table selection.
3. Select the MPS table value 1.1 for SCO MPX 3.0. You may use MPS table value 1.4
if you install SCO patch /SLS/uod421a (available on SCO's FTP site).
Select MPS table value 1.4 for SCO OpenServer 5.0.x.
Logical Disk Size for the HP Disk Array Controller and the HP
NetRAID Adapter
During system configuration, the DAC configuration utility on the HP NetServer
Navigator CD-ROM helps you set logical disk size in the disk array configuration
process. If the boot drive is on the disk array controller, set the logical disk size to 2048
MB or less.
HP Disk Array Controller Logical Disk Addressing
The logical disks configured on the HP Disk Array controller are all addressed as LUN
(logical unit number) 1. The individual logical disks are addressed through the SCSI ID
field in the SCO "mkdev" command. For example, the first logical disk is SCSI ID 0,
LUN 1 and the second logical disk is SCSI ID 1, LUN 1.
HP NetRAID Controller Logical Disk Addressing
The logical disks configured on the HP NetRAID controller are all addressed as SCSI ID
0. The individual logical disks are addressed through the LUN (logical unit number)
field in the SCO "mkdev" command. For example, the first logical disk is SCSI ID 0,
LUN 0 and the second logical disk is SCSI ID 0, LUN 1.
HP NetRAID Controller Utilities
Two utility programs are installed on the system when the HP NetRAID driver is
installed. The first utility is the HP NetRAID controller monitor program "amirdmon".
Amirdmon is started when the system enters multi-user mode. The second utility is the
controller configuration program "megamgr". Megamgr can be run when the system
administrator needs to reconfigure the HP NetRAID controller.