Follow these step-by-step instructions, for general installation
tips for any OEM manufacturer. This TA is aimed specifically at the
HP plaform but the same rules can be applied on any platform.
This includes:
1. Configure the Hardware, ie. open the box.
2. Starting the Installation
3. Installation Query Manager
4. Hard Disk Setup
5. Further Installation Requirements
6. Post Install
7. Additional Software and Maintenance Supplements
8. Networking
9. Additional Patches and Security
10. Skunkware Software
11 Test the processors and memory
12. Compaq EFS Drivers
13. Compaq EFS Supplements
14. Compaq EFS Insight Manager Agents
15. Compaq UPS
16. Add Additional Disks
17. Tape Testing
18. Emergency Recovery Disks
19. Video Configuration
20. Tuning
21. License/Register Your Software
22. Miscellaneous
- Additional Hardware
- Additional Network Services
- Migration Tasks
23. Testing the Server
24. Troubleshooting
For more information, the Getting Started Guide at:
http://www.sco.com/support/docs/openserver/
1. Before installing the OS:
1a. Configure the Hardware
Before starting the installation of the operating system pay
attention to leads and connectors and ensure that they are
sufficiently tightened and the correct Compaq leads are used.
On the inside cover of the Compaq ML Series server there will be
a diagram denoting how the memory should be installed inside the
server. Ensure that these rules are followed and that all memory
used is the same type and speed.
It is suggested to ensure that 64bit slots contain 64bit or 32bit
cards. It is not recommended to put 64bit cards in 32bit slots.
Where possible place 32bit cards in 32bit slots.
Also ensure that, where possible, the PCI cards placed in the
slots inside the server are well spaced apart to spread the load
across the bus.
Where possible, ensure the IDE CDROM is set to MASTER not CABLE
SELECT to ensure that it is detected by the operating system and
that it is using the cable labelled Device 0 in later HP models.
The point is to understand the hardware you have purchased.
For Hardware references see:
HP & SCO Solutions Index:
http://h10018.www1.hp.com/wwsolutions/sco/index.html
The HP ProLiant Server Support Matrix:
http://h71028.www7.hp.com/enterprise/cache/483060-0-0-0-121.html
HP ProLiant SCO Option Matrix:
http://h71028.www7.hp.com/enterprise/cache/498759-0-0-0-121.html
Server and Controller Support Matrix for SCO UNIX Operating
Systems:
http://h71028.www7.hp.com/enterprise/downloads/SCO%20Server%20to%20Controller%20Support%20Matrix.pdf
HP ProLiant host bus adapters:
http://h18004.www1.hp.com/products/servers/proliantstorage/adapters/index.html
If you have a Integrated Lights Out (iLO) or Remote
Intergrated Lights Out (RiLO) Board installed and plan to use it,
then configure it as this will work with SCO products. You will
need a separate IP address available for this Board to connect to
which you can "telnet" or http[s]://<ILO BOARD IP> to.
Please note: This should be a unique device on the network.
You may also wish to set the password of the Administrator.
The initial password should be included on a tag provided with the
server. If not, then press F8 when the server boots to configure
the RiLO or iLO card, when prompted and Edit the Administrator
user and set the password there, or even add a new user.
You can access it then with http://<IP>
Please note that Graphical displays on the Remote Console will
require a license to be entered. However, if you don't need
to use a Graphical console then run "scologin disable" and then
UnixWare7 will only display in text and therefore a RiLO/iLO
license will not be required.
For iLO2 you will need a license for text usage too.
Also, some model's require USB to be enabled before the keyboard
will work. However, in general, disable USB Legacy support.
1b. Download from HP:
Visit HP's web site at http://www.hp.com/support and select your
server, "Download drivers and software" then select your
operating system.
What to download:
i) The Extended Feature Supplement provides drivers and utilities
for your SCO installation. The first flopppy disk contains
the HBA drivers for your installation. The remaining are
floppy disks containing daemons and utilities for monitoring
your hardware to install later.
Get the latest version of the Compaq (HP) EFS which is
supported for this server. Do not just install the latest
EFS because it might not be compatible with your server.
ii) Rompaqs are the firmware revisions of the hardware.
Download the Firmware Maintenance CD and boot from this to
update the firmware of your hardware.
Take note to see if there are later revisions available for
floppy disk or USB Stick Pen that may have been released
after the latest Firmware CD.
To create a USB Flash Disk then you will need a utility to
make your USB Flash Disk bootable, for example HP's SP27608,
to create a DOS bootable disk (once installed you will need
a Windows 98 Boot Disk to pull the System Files from and then
add the SoftPaq ROM (Firmware) UPDATE.EXE or use:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=329290&prodSeriesId=411014&prodNameId=411016&swEnvOID=181&swLang=13&mode=2&taskId=135&swItem=MTX-UNITY-I23839
iii) The Diagnostics can be used to test the hardware should there
be problems with the server down the line and before the
server goes into production, then this is an ideal time to
test the hardware initially.
1c. Firmware:
Upgrade the firmware, if required, of the hardware.
1d. Using SmartStart (for older models):
Please note that the versions of SmartStart will vary and a CD
will be provided in the box with your hardware.
Earlier releases of the product will include SCO operating systems
in the build allowing an automated build. This has been removed
in later releases, forcing a manual build so only the components
required should be installed.
Do not use the Compaq SmartStart "Automatic" feature to install
your server as this is often installed with general configuration
options rather than those specific to your system and additional
software is installed that you may not require.
1e. System Erase (for older models):
Using the Compaq SmartStart CD, perform a System Erase if the
server is new or you are upgrading from a different operating
system.
1f. Configure the Logical Drives:
Use the Compaq SmartStart CD or from the SmartArray BIOS,
configure the logical disks on the controller(s) you may have
installed on your server.
You may want to clear the configuration and save for each
controller(s) on your server.
Ensure that each logical disk array matches the physical drives.
ie. The drives being configured will be physically flashing in
the drive bays of each cage concerned.
It is recommended to have, where possible, a logical volume for
root disk containing the operating system, say 2 x 18GB disks;
a logical volume for the application and maybe the user's $HOME
folders; and a logical volume for the database itself, etc, plus
RAID Hot Spares where appropriate.
Take care not to change the Read/Write ratio, unless required,
for the logical volume. For example, if you change the ratio from
50% to 100% read to make the reads faster, you can expect
significant delays when restoring data from tape or over the
network.
Please note that if you are using the server for a database it is
suggested not to use the Write Back Cache on the controller, even
if you have an extra power supply and an Uninterpretable Power
Supply (UPS). This is because the cache may contain corrupted
data should the server crash during production. In such an event,
corrupted data may be written to the database. Where possible,
use RAID 0+1 to obtain the best performance and robustness for
your installation.
Where possible, have a RAID1 mirrored root disk including swap
and, if possible, put your application and data on a separate
RAID, preferably RAID1 or RAID0+1, separate mirrored logical disk
volume.
Split physical disks, where possible, within logical disk mirrors
over channels to split the writing over the SCSI channels rather
than bottleneck the i/o through one channel.
At the very least, ensure that the application and data
are on separate filesystems other than root.
Many database manufacturers, discourage the use of RAID5 as this
can cause performance problems.
However, RAID 0+1 is the recommended RAID configuration providing
high performance and robustness of your data.
If RAID5 has to be used due to disk capacity then see if ADG,
Advanced Data Guarding, is available as you can loose two disks
at any one time. Take care when testing though, if you have
assigned a hot spare to this logical disk, allow time for the disk
to build before pulling another disk.
It is recommended to leave the Stripe Size at the default of 128K.
It is not recommended to attach a tape device to any channel of a
RAID controller. It is better to control this by a separate SCSI
controller to avoid contention on the data bus which could result
in data loss and corruption regardless of the operating system or
driver in use.
Also, due to the restrictions of "divvy", it is recommended to
have one divvy table applied to each logical volume and not to
have multiple fdisk active partitions on one large logical volume
1g. External Storage:
When possible, storing your data on external storage is preferable
as this provides redundancy in the case of a server failure.
If possible, if you are using an External Cabinet for storage then
consider having a controller using one driver for the root disks,
for example, "ida", and a separate driver for the controller
connecting the External Cabinet, for example "ciss", to prevent
any conflicts.
Note though, for example, a Compaq StorageWorks 4200 cabinet:
Storage Works ID to Slot mapping:
Slot SCSI ID
14 15 (top)
13 14
12 13
11 12
10 11
9 10
8 9
7 8
6 5
5 4
4 3
3 2
2 1
1 0 (bottom)
ID 6 and 7 are used for controller and storage works cabinet
itself. This is useful should the external storage detect a disk
failure as it reports the ID, not the slot.
Please note the fibre channel technology is not available for
OpenServer5.
Using the Compaq SmartStart CD, use the Compaq Array Diagnostics
to ensure the validity of your disks before you start.
Should a failure occur use the Compaq SmartStart CD and choose the
Array Configuration to help you locate the faulty disk.
A report can be saved to floppy disk for future reference.
Please note that for SAS, each disk has it's own channel.
See Also, TA#116222, "How do I quickly determine the cause of a
performance problem using sar?" at http://www.sco.com/ta/116222
1h. System Partition (for older models):
Using the Compaq SmartStart CD create the Compaq System Partition.
Should you see the message that the SmartStart installation has
terminated prematurely then it is likely that you are using a
later version of the Compaq SmartStart CD that didn't come with
the server.
Assuming that the SmartStart partition has installed okay you will
see a choice at boot time to press F1 to boot or F10 key for the
System Partition. When the first menu is displayed, press CTRL-A
to enter "Advanced Mode".
This will provide you with a number of additional options within
the following menus. Use the Test & Diagnose options to test
the validity of your hardware before you start. A report can be
saved to floppy disk for future reference.
Within the Configure Hardware option of the Compaq System
Partition, View and Edit Boards to ensure the controller order of
your hardware. For servers with multiple cards you will need to
ensure that Interrupt Sharing is Enabled in the Advanced Section
of the BIOS, if the BIOS supports it. By default, it is NOT.
1i. BIOS Changes
During the initial boot, if there is an F9 ROM Based Setup Utility
then select it and select the chosen operating system.
Set the Operating System type to SCO OpenServer.
Consider the interrupts to be shared, such as do you want to share
the Network Interface Card(s)(NICs) with each other or share the
SCSI controllers on the same interrupt? Be aware that turning
this option on will result in a number of your interrupts being
re-ordered. For example, is the second serial port going to be
used?
Generally, it is recommended, where possible, not to use
Interrupt Sharing for SCO OpenServer5 but it can be used when it
is not possible to uniquely assign interrupts to devices.
The following is a good example of a message at boot up where an
IRQ conflicts:
WARNING: move_fixed:cannot add 0xF00AA334 to vector 16 - cannot share
WARNING: Handler 0xF00AA334 was not placed on vector 0x00000010
An example of this would be the dual port NC3123 NIC where both
NICs would share the same interrupt. It requires that the BIOS,
Driver and Operating System can understand interrupt sharing well.
Disable ports and cards that are not going to be used to save on
the resources available and, where possible, assign the highest
unique IRQ value to the Root Controller to give it the highest
priority.
The Compaq MPS Mode default for OpenServer is Full Table APIC or
use Auto for later BIOS revisions for full use of IRQ's should
SMP be required.
Determine if any Compaq Dual Network Interface Cards (NICs) can be
swapped to single NIC's. This is because the dual cards are most
effective for load balancing, a feature not supported by the
UnixWare7 operating system. The dual NIC can be used to connect
to a separate network, thus, making the server a network
"router". It can also be used as a backup NIC when another dual
port connects to another network. Therefore, the first port of
the first NIC connects to network 10, the second port of the
second NIC connects to network 20. The second port of the first
NIC is the backup for network 20 and the first port of the second
NIC is the backup for network 10.
eg:
Single Subnet:
Dual Port 1 Dual Port 2
Port 1 - Subnet Port 1 - Backup of Subnet
Port 2 - Disabled Port 2 - Disabled
Two Subnets :
Dual Port 1 Dual Port 2
Port 1 - Subnet 1 Port 1 - Subnet 2
Port 2 - Backup of Subnet 2 Port 2 - Backup of Subnet 1
Turn off the F1 Boot prompt to ensure that when servers are asked
to reboot, it won't wait for someone to press F1 to continue.
Also, if not required, turn off the Automatic Server Recovery
(ASR), Hot Plugable functionality, USB and Virtual Serial Ports &
Physical Serial Ports to save on IRQ's.
It is recommended though, to leave Thermal Shutdown turned on.
If no Compaq System Management tools (ASM) are loaded then the
this will simply turn the machine off in the event of an air
conditioning failure. Whilst this might damage any open files at
the time of power off, this will protect the server itself. If,
the ASM tools are installed onto the operating system then a
shutdown will be initiated before the power is terminated.
Set Disable Wake Up on LAN.
Enter an appropriate Custom Post Message, such as:
Server Name, Server Type, Location
Set HyperThreading: Enable, although you might not wish to use
it, at least it can be enabled in /etc/default/boot with:
http://www.sco.com/ta/126403
Set CPU Optimization: I/O.
If the OS or latest patch supports Dual Core then it will be
enabled by default, assuming SMP has been installed.
Lastly, if you disable the Power On button (ie. a 4 second
depress) to prevent accidental turning off of the server or turn
on the Automatic Power Regulation Saving, if possible, then it is
recommended to "label" the server to make it clear to
Administrators what is and isn't enabled.
2. Starting the Installation:
Use the OpenServer CD or Floppy Disks to boot the operating
system and at the boot (Boot:) prompt enter the any appropriate
boot string to load a new Boot Time Loadable Driver (BTLD) from
the EFS diskettes created.
SCO OpenServer will have a number of Compaq BTLD's available which
you can always update later. For example, OpenServer 5.0.6
contains Compaq EFS drivers 5.34a. Later releases of the EFS
should always be downloaded from http://www.hp.com/support for the
appropriate hardware you are trying to install on.
However, it might be possible that this version of the EFS may not
detect correctly the controller(s) you have.
Therefore, with the EFS BTLD disk, enter the bootstring for the
controller you have.
To see what drivers are available at the Boot: prompt with the
Compaq EFS disk in the floppy drive, enter the command:
: dir fd(61)
For example, the Compaq RAID SmartArray Controller 5300 uses the
Compaq Intelligent Storage Subsystem driver (ciss). So your BTLD
command would read:
: defbootstr link="ciss"
Please note that the default keyboard setting is for the US
Keyboard layout press @ on UK keyboards for a quote ".
See:
TA#105937, "SCO OpenServer installation bootstring options." at
http://www.sco.com/ta/105937
and
TA#109501, "Installing or updating a driver on an installed
OpenServer 5.0.x system from a Boot Time Loadable Device
diskette. " at http://www.sco.com/ta/109501
and
TA#126653, "I cannot install SCO OpenServer 5.0.7 on a Fujitsu
Siemens PRIMERGY TX150-S5 that has no standard legacy floppy
drive attached to it by default, using a BTLD on a floppy disk
via USB floppy drive." at http://www.sco.com/ta/126653
3. Installation Query Manager:
Select the correct Keyboard
Select the appropriate Language. It is recommended to set
"Standard C (English)"
Enter your license details.
Installation type: Fresh
System Name: 8 characters, lower case
Domain Name: Enter your Fully Qualifyed Domain Name
Security Level: To be selected, normally Traditional
Select your Time Zone
Select the Initial System Profile. It is suggested that within
the profile you may wish to remove Power Management and Calendar
options and also to remove IPX but add LAN Manager Client from
Connectivity and Documentation as required.
It is recommended to "defer" the network configuration. The NC3123
Compaq NIC's are a re-badged Intel card and it is recommended with
OpenServer to use Compaq's own "n100c" driver.
For NIC cards other than Compaq is good to let the cards be
Autodetected as you can complete the Gateway and DNS information
at this point.
You may wish to configure the graphics to use the standard SVGA
VESA and turn scologin off and then configure them manually later.
This will save time starting the X Server each time the server
starts into Multi-User Mode until the server's installation has
been completed.
For a normal PS2 Mouse select High Resolution Keyboard.
Select MMDF or SendMail mail configuration. These can be
configured later using "mkdev mmdf" or "mkdev cf" respectively.
Enter your "root" password, when prompted.
4. Hard Disk Setup:
Select "customize" or "fdisk/divvy" (recommended) for partition
setup. For the Compaq ML series you must pick the later as the
"customize" option will overwrite the Compaq System Partition.
During the FDISK part of the configuration, use the rest of the
disk for UNIX and make it ACTIVE.
Please note that for SCSI Disks ignore the Bad Block allocation.
Take the default of 511 for the number of bad block allocation but
ask to make manual adjustments when prompted.
Swap ; The maximum amount of swap allocated will be dependent on
disk size but, unlike, UnixWare7/OpenUNIX 8.0.0 any panic dump
that OpenServer has is not selective. That is, the size of swap
must equal the size of the memory. It is also suggested that
this should be twice memory in case additional memory is added
later. This will be dependant on disk size and additional swap
can be added post-install to another disk added later with the
"swap -a" command. The maximum swap limit which can be defined at
ISL is 4096MB, although more can be allocated within the customise
option, post install 4096MB will be allocated, which you can see
with the "swap -l" command.
However, swap should not really be any greater than 2048MB.
For the root disk, you may not wish to create a partition of
20GB. Consider what root is being used for and how long an 'fsck'
is likely to take if it was required on what is likely to be a
busy file system on your server.
Select 50Mb for the /stand filesystem in case additional kernels
are copied.
You may wish to create a /u filesystem to ensure that any users
created will use a separate filesystem other than root to save
their files or to use as an installation for any applications you
may wish to install later.
5. Further Installation Requirements:
After this the hard disk will be installed with your operating
system and will reboot the server and you will be prompted when
to remove CD's, etc.
6. Post Install:
After the first system boot, boot into Single-User Mode and:
6a. Run "scoadmin -> Software Mgmt -> System -> International
Settings" to ensure the correct locale is set or just
"scoadmin international".
6b. Set the correct date and time by running "asktime".
We will discuss how to use NTP to sync your server's date and
time later
6c. Configuration Files:
- Edit "/etc/default/cleantmp" to add any additional temporary
directories to the list of directories to be cleaned out
automatically by cron.
- Edit "/etc/cleanup" and "/usr/lib/cleantmp" changing
the "atime" parameter to "mtime" otherwise "tmp" directories
won't be cleaned out at all.
- Edit "/etc/issue" and enter your Company name so it appears
when you "telnet" to the server, eg. "Welcome to SCO"
- Edit /etc/default/issue. Eg.
BANNER=SCO OpenServer(TM) Enterprise%r %c (%h) (%t)
- Do you need a /etc/motd? ; Message of the Day to add for when
a user logs into the server.
- Add to /.profile the line:
PS1="`uname -n` # " export PS1
- Monitor your disk space automatically with
TA#104919,"How can I monitor filesystem space automatically?"
6d. Check the "crontabs" in /usr/spool/cron/crontabs and copy
them using:
# mkdir -p /local/cron
# cd /local/cron
# cp /usr/spool/cron/crontabs/* /local/cron
We do this to take a copy of the crontab for administration
purposes. An alternate would be to use the standard
documented method of "crontab -u uucp -e".
Use your favourite editor, for example, for modify the "uucp"
cron and place a hash in the front of the lines there, unless
"uucp" is a function that will be used on this server and copy
the file back using:
# cp /local/cron/uucp /usr/spool/cron/crontabs
Check the changes have been made using:
# crontab -l uucp
#9,9 * * * * /usr/lib/uucp/uudemon.hour > /dev/null
#0 * * * * /usr/lib/uucp/uudemon.poll > /dev/null
#5 23 * * * ulimit 5000; /usr/lib/uucp/uudemon.clean > /dev/null
#8 10,14 * * 1-5 /usr/lib/uucp/uudemon.admin > /dev/null
6e. Where possible remove a disk from the RAID disk array and
monitor what happens to ensure suitable warnings are given
then replace the disk and monitor the RAID re-build.
This will take some time but it is important to understand how
the RAID controller works when a disk goes down and how long
it takes for the repair process to work.
7. Additional Software and Maintenance Supplements:
7a. Additional Software Modules:
First, copy the "stune" file in /etc/conf/cf.d to "stune.orig".
Add any additional SCO modules and licensing (eg. SMP or
Development) by running "custom" and selecting the original
Media CD. License information may be required depending on the
software installed.
Please note that when you install these additional post install
you should add these BEFORE applying Maintenance. If you need
to add these products later it will be necessary to remove
the Maintenance first in Single User Mode, apply the software
then re-apply the Maintenance again, re-link the kernel then
re-boot.
Should any Auto-Tuning be required due to an increase in the
number of user licenses then allow this as you will have the
original "stune" file which you copied above as a reference to
see what changes were made.
Afterwards, you will need to re-link the kernel. This will
either be done depending on the software package selected or by
running:
# /etc/conf/cf.d/link_unix -y
then re-boot the server back into Single User mode using the
command:
# init 6
7b. Patches and Drivers:
At this point, we would be looking to load the Maintenance Pack,
the latest HBA Drivers required, from SCO's web site and any
additional networking drivers.
For ALL versions visit:
http://www.sco.com/support/download.html
For OpenServer 5.0.6:
Apply the RS506A supplement, via "custom" from the RS506A CD
supplied with the media. Apply the Software Manager RS506A fix
first, leave "custom" then run it again to apply the remainder of
the RS506A Supplement.
The RS506A Supplement contains a number of Compaq EFS BTLD
updates.
For example, the Compaq SCSI (cha) which is a re-badged LSI
Symbios controller.
Apply any additional supplements required from this CD.
Ensure that the kernel has been re-linked and re-boot the server
into Single-User Mode, as above.
For OpenServer 5.0.7:
Similar to the above but you will need to install the latest
Maintenance Pack.
After re-booting repeat steps 6 & 7 above to re-test the
processors and memory.
8. Networking:
8a. "netconfig":
Use "netconfig" to configure any additional "n100c" NIC's using
TA#116592, "How do I configure a Compaq network card pair to
act as a redundant (failover) pair on OpenServer 5?" at
http://www.sco.com/ta/116592
8b. Routing to a Gateway:
Define your gateway as detailed in:
TA#113061, "In OpenServer 5.0.6, routed does not start by
default." at http://www.sco.com/ta/113061
After a reboot, make sure you can ping it.
If not, troubleshoot with:
http://www.sco.com/ta/107687
8c. Essential Network Services:
- Next, check Apache and the OnLine Documentation is running,
which should automatically be started from /etc/rc2.d/S95docview:
http://<myserver>:8457
If you wish to start the Apache Web Server then enter:
# apache enable
# apache start
Please note that if you do not wish to use the Web Server to
search for documentation then try the "man" pages, eg:
# man shutdown
or to search for all references to "shutdown", enter:
# man -k shutdown
8d. Domain Name Service (DNS):
In addition, you may wish to define your DNS configuration as
detailed in:
TA#107297, "How do I set up a primary nameserver and nameserver
clients?" at http://www.sco.com/ta/107297
Ensure that the kernel has been re-linked and the server re-booted
into Multi User Mode, as above.
9. Additional Patches and Drivers:
9a. Now, you can visit http://www.sco.com/support and Download
any additional patches or maintenance you need.
SCO Supported customers have the option to use the "patchck"
feature at this point.
Apply the latest patches and drivers for the operating system
found in:
http://www.sco.com/support/download.html
Keep a copy of the patches installed in /local/patches.
9b. Security Supplements:
- As required, download and install the latest individual Security
patches available from:
http://www.sco.com/support/download.html
- In addition, to further improve security, you may wish to run:
# netstat -an
and note the various ports open by TCP/IP inetd.conf services and
services started in /etc/rc2.d. To improve security you may wish
to turn off the services that are not required.
- Configure a .rhosts protocol for allowing "root" or other users
remote access to your server for other Unix servers with user
equivalence:
For more information see: http://www.sco.com/ta/107735
- Using more security connecting technologies such as openssh
(ssh / scp) and secure FTP (sftp) might be preferable than the
the traditional telnet, ftp and rcp.
Also, see TA#114081, "How can I restrict access to my Openserver
5 system over the network?" at http://www.sco.com/ta/114081
and:
http://www.sco.com/ta/115262
- Restrict the use of "root" and control over files, with "chmod":
/etc/default/login - man login
/etc/default/su - man su
9c. Legacy "sysadmsh" (Optional):
In addition, you may wish to install the "sysadmsh" software which
is a legacy System Manager from the SCO Unix 3.2v4.2 release.
This is available from the original OpenServer 5.0.x CD and is
installed via:
custom -> Software -> Install New -> From localhost
-> SCSI CD ROM Drive 0 -> Continue. Choose product to install:
SCO OpenServer Enterprise System UNIX ver 5.0.x ->
SCO OpenServer Enterprise System Utilities ver 5.0.x ->
Optional Utilities ver 5.0.x . ->
sysadmsh
Ensure that "sysadmsh" is the only package selected.
By running "sysadmsh" or "scoadmin accounts" you can set some
sample security options defined below:
sysadmsh -> Accounts -> Defaults -> Password
Min Days between changes 0
Expiration Time 42
Lifetime 180 (6 months)
User Can Choose Own Yes
Checked for obviousness No
sysadmsh -> Accounts -> Defaults -> Logins
User Account 10
Terminals 99
Delay 2
Time 60
CPU 0
sysadmsh -> Accounts -> Defaults -> System
Length of clear text 8 (/etc/default/passwd)
This is the number of characters (*8) in the password that are
significant at login.
For more information see:
http://osr507doc.sco.com/en/OSAdminG/uaD.copyxenix.html#uaC.pwcomp
sysadmsh -> Accounts -> Terminal
Create tty1A and tty2A
10. Skunkware Software:
Skunkware packages are available to download for OpenServer 5
from:
ftp://ftp2.sco.com/skunkware/osr5/vols/
Below is a list of appropriate SkunkWare software that could be
loaded onto a new installation.
Windows:
catdoc - Displays Microsoft Word documents as text
gv / ghostviewer ; a PostScript and PDF Previewer
xlHTML - for viewing Excel spreadsheets
xpdf - for viewing PDF files
Essentials:
* bash - Bash 2.03 - GNU Bourne-Again Shell
* bzip2 - block-sorting file compressor/uncompressor
cdrtools - record audio or data Compact Discs
cpio - GNU Cpio
diffutils - GNU diff, diff3, sdiff and cmp utilities
fileutils - GNU file management utilities, such as cp
findutils - GNU Find Utilities
gzip - GNU Compression Tools
hog - for monitoring memory usage
* less - opposite of more
* lsof - List of Open Files
lynx - character based web browser
Mtools - Utilities to access DOS disks in Unix
* ntp - network time protocol
SarCheck - performance analysis and tuning tool
tar - GNU tar
top - Display top cpu processes
unzip - PK-Zip compatible unzip
vim - Vi IMproved, a programmers text editor
Dependancies:
glib 1.2.8 - Handy Library Of C Utility Functions
gtk+ 1.2.8 - Gimp Toolkit
zip - compatible zip utility
Expecting:
Expect - programmed dialogue
Optional:
NcFTP - Internet file transfer program
Webmin - A powerful web-based administration interface
Wxftp - graphical FTP client
* - already included in OpenServer 5.0.7
See:
TA#114221, "How do I install webmin for OpenServer?" at
http://www.sco.com/ta/114221
TA#115262, "Where can I obtain a Secure Shell (ssh) for
OpenServer?" at http://www.sco.com/ta/115262
TA#114822, "How do I download, compile and install the latest
version of SAMBA for OpenServer?" at
http://www.sco.com/ta/114822
For SAMBA information and troubleshooting see:
http://www.sco.com/ta/119726
For Migration Information see:
http://www.sco.com/ta/111764
TA#113163, "UNIX, Which is the best compression tool to use?"
at http://www.sco.com/ta/113163
11. Processors and Memory:
11a. Test the processors with the technical article (4 processors
max):
TA#111842, "How to check how many CPUs your system is licensed
to use." at http://www.sco.com/ta/111842
11b. Test the memory detected using the command (4GB max):
# memsize
Please note that OpenServer5 has no support for >32-bit physical
memory addresses.
To check exactly what memory OpenServer5 sees run:
# echo boot | crash
Alternatively, for a more comprehensive report enter the following
command at the boot: prompt:
boot: mem=/p/v
12. Compaq EFS BTLD:
The latest EFS (5.770a) is available for download
from the following location;
http://www.hp.com/support
ONLY install the software from the Compaq EFS disks for the
hardware you have.
For the instructions contained to create the appropriate floppy
BTLD disks.
Add the latest BTLD's required for any additional controllers you
have. For example, if you have the "CISS" and "CHA" controllers
when you run "hwconfig -hc". The CISS controller will have a
later EFS version than the CHA. Insert the BTLD floppy and run
the command:
# installpkg
and install the BTLD for the appropriate controller.
Ensure that the kernel has been re-linked and the server re-
booted into Single User Mode, as above.
13. Compaq EFS Supplements:
BEFORE LOADING THE EFS SUPPLEMENT, create the Emergency Floppy
disks, detailed further. This is because the additional EFS
components can cause the kernel image to become too large to fit
onto a floppy disk. You may wish to create an additional set
after the EFS has been loaded.
The remaining Compaq EFS contain useful utilities but it is not
recommended to install them all, but rather only the ones that
will be used as this will place drivers in the kernel for hardware
that you do not have.
To do this place the first of the three Compaq EFS floppies in the
drive and run "custom" and select to Install new software from the
floppy drive. Select the Compaq EFS Supplement but press RETURN on
the supplement to show all the products available. Only pick the
appropriate drivers so as not to install and run drivers and
daemons which are unnecessary in production. Installing
inappropriate utilities can cause performace problems as these
daemons will be probing for hardware you may not have.
Later versions are created as VOL images which can be loaded
directly from "custom".
You will need to install the "ASM" (casm), Health Event Logging
(cevt) and Remote Insight Board (crid) drivers if you wish to use
the Compaq Insight Management tools. The "crid" would be optional
depending on where you were using or had installed a RiLO or ILO
Integrated Lights Out Board.
For example:
Compaq "CISS" Diagnostics utility
Compaq SCSI Management utility
Compaq EFS Documentation
Compaq Ethernet (NIC) Driver (ie. the n100c)
Compaq Intelligent Storage Subsystem Driver
At this point you will be prompted to configure the n100c NIC(s).
See:
TA#110210, "How can I obtain the most current Compaq Extended
Feature Supplement (EFS) for my SCO operating system?" at
http://www.sco.com/ta/110210
Ensure that the kernel has been re-linked and the server re-booted
into Single User Mode, as above.
This should have also added the "cpqciss" component of "mkdev" so
that we can configure additional disks later.
14. Compaq EFS Insight Manager Agents (for older models):
Only install this if the server is to go into a environment
where it is essential to run this tool.
See:
TA#112481, "How do I install the Compaq Insight Manager on
OpenServer?" at http://www.sco.com/ta/112481
Support for OpenServer5 can only be found in the Foundation Packs
supplied with the server. Later models do not have support for
OpenServer5.
15. Compaq UPS:
If you have a Compaq UPS then the software can be installed
using:
TA#113701, "I have installed the Compaq UPS agents but some
of the UPS options are grayed out in the Compaq Insight
Manager" at http://www.sco.com/ta/113701
16. Add Additional Disks, if not done at Installation Time:
- In Single User Mode add additional disks normally using the
command "mkdev". Select the appropriate "mkdev" module for the
type of Compaq controller you have. Normally, this is "mkdev hd"
but in the case of the Compaq "CISS" Controller you must use:
# mkdev cpqciss
and follow the prompts.
See:
TA#118293, "My Compaq OpenServer 5.0.x machine will not
automatically reboot." at http://www.sco.com/ta/118293
After the re-boot, run "mkdev cpqciss" for the second time and
once complete run:
# mkdev fs
to add the filesystems.
- Run "mountall" then "dfspace" to ensure that all the filesystems
are there.
- At this point, it is a good idea to start to physically remove
the disks to ensure that the hardware RAID is working as it
should.
- Once complete, run "divvy -N -P /dev/rroot" to keep a
record of the root filesystem's disk layout.
It is recommended to repeat the procedure for each of any
additional filesystems created.
17. Tape Testing:
If you have tape drive connected then follow the guidelines as
defined in:
TA#110739, "How do I add a Quantum DLT Drive to a Dell
PowerEdge 4200/4300 Server?" at http://www.sco.com/ta/110739
and test a backup solution such as defined in:
TA#116586, "Where can I find a simple backup script to
backup my OpenServer 5 onto a tape on a nightly basis?" at
http://www.sco.com/ta/116586
18. Emergency Recovery Disks:
18a. Copy the following files:
# btmnt -w
# cp /stand/unix /stand/unix.orig
# btmnt -r
# cp /etc/init /etc/init.orig
# cp /etc/default/filesys /etc/default/filesys.orig
18b. Creating the Emergency Disks:
It should be done at this stage before the kernel becomes too
large to fit onto the floppy disk.
There are two choices here, either legacy floppy or CD-ROM
image. There is no support for USB devices.
Create the Emergency Floppies using the command "mkdev fd".
In addition see the following Technical Article for further
information:
TA#112505, "Additional Notes on Emergency Recovery for SCO
OpenServer 5.0.6, 5.0.7 - Including instructions on how to
create Emergency Boot/Root CD's on 5.0.7 " at
http://www.sco.com/ta/112505
TA#114161, "Kernel is too large to fit on a boot diskette,
which causes the creation of emergency boot and root floppies
to fail." at http://www.sco.com/ta/114161
19. Video Configuration:
If there is a specific video adaptor you know of that runs well
with OpenServer then run "scoadmin video" to configure the video
adaptor, otherwise the recommendation would be to leave the
adaptor set to VESA.
To save on system resources you may wish to disable "scologin"
with "scologin disable".
To turn it on again run "scologin enable" and log on or if you
need it occassionally then run simply run "startx" from the
console.
Go into "System Admin" and run the Video Configuration Manager to
check that the correct video settings are defined. For the Compaq
ML range you may need to re-define this.
Turn off all of the unneccessary tty's running on the console,
if you like, to save on memory:
echo "Disabling tty05...tty12 ..."
for i in 05 06 07 08 09 10 11 12
do
echo $i
disable tty${i}
done
Running 'scologin' itself only uses approx 10Mb of RAM, however,
if you start to run the Desktop then CDE takes approx 30Mb of RAM
whereas Panorma or FailSafe only take 10Mb of RAM. However,
running an application like Mozilla can take 200Mb of RAM.
20. Tuning:
20a. Disk Buffering:
By default, OpenServer 5.0.6/7 should not need much tuning,
however, this will depend on the applications and load given.
For example, see:
TA#112723, "How do I set my disk buffering for SCO OpenServer
5 to the optimum values?" at http://www.sco.com/ta/112723
20b. Enable "sar":
Enable "sar" reporting using /usr/lib/sa/sar_enable. See:
TA#114622, "How do I install and run SarCheck?" at
http://www.sco.com/ta/114622
20c. Kernel Tuning:
Increase memory available to exec arguments:
vi /etc/conf/pack.d/kernel/space.c
Be careful when you edit this file. There are two references to
maxexecargs, and it is the second one that you need to edit.
/* maximum size of execargs. */
unsigned int maxexecargs = 250*1024;
See:
TA#105076, "table_grow - exec data table page limit of 25
pages (MAXEXECARGS) exceeded." at http://www.sco.com/ta/105076
Use the following script to tune the kernel as required but the
ones shown below are typical examples. Additional tuning may
be required for any database application running, here is an
example below:
:
echo -n "Tuning kernel parameters ..."
cd /etc/conf/bin
# 2. Processes and Paging (to increase the virtual address
space
# available to the kernel)
./idtune -f SPTMAP 300
# 6. Multi-screens.
./idtune -f TBLNK 300
./idtune -f NSCRN 4
# 7. User and Group Configuration (to increase the number of
# files & processes available)
./idtune -f NOFILES 2048
./idtune -f MAXUP 1024
./idtune -f MAX_PROC 5000
./idtune -f MAX_FLCKREC 2048
./idtune -f FLCKREC 2048
# 17. Miscellaneous system parameters.
./idtune -f MAX_CFGSIZE 4096
# Now re-link the kernel.
echo -n "Re-linking kernel ..."
cd /etc/conf/cf.d
./link_unix -y
You can also disable the Calendar Server, if this feature is
not required to save on system resources as:
# cd /etc/rc0.d
# ./P95calserver stop
# mv P95calserver p95calserver
# cd /etc/rc2.d
# mv P95calserver p95calserver
20d. scodb:
If you wish, you can install the SCO Debugger (scodb) for
kernel debugging. This can be activated using:
TA#113121, "My OpenServer server has panicked with "NOTICE:
growreg - Insufficient memory to allocate 1 page - system
call failed"." at http://www.sco.com/ta/113121
Testing the Server:
------------------
Overnight, you may wish to test the server to it's limits with
the System Certification Test suite available at:
http://www.sco.com/developers/hdk/testsuites/
Follow the 'readme' provided to install the product.
Once installed, run "/home/sct/sct" to start the product in
either GUI (preferrably) or text mode.
If GUI mode is used then you will be able to run the Graphical
tests.
For the networking tests, you will need access to another
server on the LAN for high volume ftp transfer testing.
Use the "Edit" option to change any appropriate settings.
Use the Help -> On Window to launch Mozilla in the GUI version
for more detailed help.
21. License/Register your Software:
# scoadmin license
Add licenses for additional users. When prompted it should not be
necessary to re-tune the server automatically.
Register your software at http://www.sco.com/register and
ensure you have the appropriate number of licenses for the
number of users and database solution you are implementing.
22. Miscellaneous:
22a. Additional Hardware:
- Parallel Port
Add the parallel port, if required, and available as it is not
there by default:
# mkdev parallel
1. Add a parallel port.
2. Parallel Adapter at address 378-37f
For the Olivetti M6-860 and the Compaq Proliant 1500/2500, the
port address may be 3bc-3be (use EISA Configuration or MSD to
check it first).
Select Interrupt 7 (default).
Do not re-link the kernel at this point.
- Run "mkdev cdrom", if required, should the CDROM not be
defined when trying to add additional software.
- Run "mkdev serial" and "mkdev modem", if required.
22b. Additional Network Services:
- Network Time Protocol (NTP):
Configure NTP using:
TA#111921, "How do I configure NTP to synchronize correctly?"
at http://www.sco.com/ta/111921
- DHCP:
- To configure as a simple DHCP Client, use "netcfg"
See: http://www.sco.com/ta/111069
- To configure as a DHCP Server, use "scoadmin address" and
"scoadmin dhcp".
See: http://www.sco.com/ta/110134 or
http://www.sco.com/ta/110170
- Configure Printing:
- Printing ; other than Parallel or Serial Port printing you
can use Network Printing and here you have a choice of
using:
a) HPNP - print to HP Printers or HP JetDirect connected
printers using "/usr/lib/hpnp/hpnpcfg" to port 9100.
For Troubleshooting see: http://www.sco.com/ta/110358
b) SYSV - print to all networked printers using standard
LPD (SYSB) printing on port 515 using "scoadmin printer"
You will need to enable the Remote Printing Daemons.
For Troubleshooting see: http://www.sco.com/ta/119265
c) CuPs - print using the latest CuPs printer drivers
using "scoadmin printer", if CuPs has been installed.
See http://www.sco.com/ta/126211 for more info on CuPs
management.
To switch between SYSV and CuPs printing, see:
http://www.sco.com/ta/126336
- Configure Email:
Configure Email using either:
# scoadmin sendmail
or:
# mkdev mmdf
Depending on the email service selected at Install Time. You
may wish to configure a SmartHost and re-direct "root" email
to a user in your existing email system.
- NFS:
Use "scoadmin filesystem manager"
Please note that some 3rd party NFS products require the "anon"
to be set to "0" in the Advanced section of scoadmin.
Visit http://www.aplawrence.com/SCOFAQ/scotec4.html
For Troubleshooting, see http://www.sco.com/ta/116623
For connecting NFS to a Windows Share please note that the
default in windows when you create a share is an SMB share.
Which would not work. Windows does have a free add-on package
that provides NFS. It is called Windows Services for Unix(SFU):
http://technet.microsoft.com/en-us/interopmigration/bb380242.aspx
If you export your shares using this service then they can be
mounted on Unix.
- NIS:
Information on NIS is available from:
http://osr507doc.sco.com/en/NetAdminG/nisT.initialize.html
22c. Migration Tasks:
To migrate users, printers and data from another server, see:
http://www.sco.com/ta/111764
23. Testing the Server:
- Where possible remove a disk from the disk array and
monitor what happens to ensure suitable warnings are given
then replace the disk and monitor the RAID re-build.
This will take some time but it is important to understand how
the RAID controller works when a disk goes down and how long
it takes for the repair process to work.
24. TroubleShooting:
Common reasons why OpenServer fails to install:
1. Latest HP Rompaq, bios, firmware not loaded on the server.
2. Bios needs to be correctly set to OpenServer settings,
above.
3. Need to disable hyperthreading and ACPI during installation.
4. Need to check CD-ROM configuration - check CD installation
media.
5. Need to disable USB or Virtual Serial Ports during
installation if not required.
6. Make sure the root disk controller is plugged into a 64 bit
PCI slot, where possible.
7. Check all SCSI cables and terminators.
8. Disable other onboard controllers if not needed for
installation.
For example, to disable the load of the ad320 at boot
prompt:
defbootstr disable=ad320 ...
9. Not using the latest EFS from HP and either use the latest
BTLD drivers supported by SCO, which you can find at:
http://www.sco.com/support/download.html
You are now ready to install your application(s) ...
SEE ALSO:
Technical Article 105937, "SCO OpenServer installation bootstring options."
Technical Article 111842, "How to check how many CPUs your system is licensed to
use."
Technical Article 116592, "How do I configure a Compaq network card pair to act as
a redundant (failover) pair on OpenServer 5?"
Technical Article 110210, "How can I obtain the most current Compaq Extended
Feature Supplement (EFS) for my SCO operating system?"
Technical Article 114622, "How do I install and run SarCheck?"
Technical Article 112723, "How do I set my disk buffering for SCO OpenServer 5 to
the optimum values?"
Technical Article 105076, "table_grow - exec data table page limit of 25 pages
(MAXEXECARGS) exceeded."
Technical Article 113121, "My OpenServer server has panicked with "NOTICE:
growreg - Insufficient memory to allocate 1 page - system call failed"."
Technical Article 110739, "How do I add a Quantum DLT Drive to a Dell PowerEdge
4200/4300 Server?"
Technical Article 116586, "Where can I find a simple backup script to backup my
OpenServer 5 onto a tape on a nightly basis?"
Technical Article 113701, "I have installed the Compaq UPS agents but some of the
UPS options are grayed out in the Compaq Insight Manager"
Technical Article 112481, "How do I install the Compaq Insight Manager on OpenServer?"
Technical Article 114221, "How do I install webmin for OpenServer?"
Technical Article 115262, "Where can I obtain a Secure Shell (ssh) for OpenServer?"
Technical Article 114822, "How do I download, compile and install the latest
version of SAMBA for OpenServer?"
Technical Article 113163, "UNIX, Which is the best compression tool to use?"
Technical Article 112505, "Additional Notes on Emergency Recovery for SCO
OpenServer 5.0.6."
Technical Article 111921, "How do I configure NTP to synchronize correctly?"
Technical Article 107297, "How do I set up a primary nameserver and nameserver
clients?"
|
Print Article
E-mail Article
Back to Search Results
