Compaq AlphaServer GS140 User manual

AlphaServer GS140
Getting Started with Logical Partitions
Order Number: EK–TUNLP–SF
This document describes the hardware configuration rules and
the console firmware commands and environment variable
settings needed to run multiple instances of an operating system
on Compaq AlphaServer GS140 systems.

First Printing, May 1999
The information in this publication is subject to change without notice.
COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR
EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING,
PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED
“AS IS” AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE,
GOOD TITLE AND AGAINST INFRINGEMENT.
This publication contains information protected by copyright. No part of this publication may be
photocopied or reproduced in any form without prior written consent from Compaq Computer
Corporation.
© 1999 Digital Equipment Corporation.
All rights reserved. Printed in the U.S.A.
The software described in this guide is furnished under a license agreement or nondisclosure
agreement. The software may be used or copied only in accordance with the terms of the
agreement.
COMPAQ and the Compaq logo are registered in United States Patent and Trademark Office.
Tru64 is a trademark of Compaq Computer Corporation. AlphaServer and OpenVMS are
trademarks of Digital Equipment Corporation. UNIX is a registered trademark in the U.S. and
other countries, licensed exclusively through X/Open Company Ltd.
Microsoft and Windows NT are registered trademarks of Microsoft Corporation.
Other product names mentioned herein may be the trademarks of their respective companies.

iii
Contents
Preface vii
Chapter 1 Introduction
1.1 Reasons for Partitioning 1-2
1.2 Important Considerations for Partitioned Systems 1-4
1.3 Overview of the Partitioning Process 1-6
Chapter 2 Configuration Rules
2.1 Overview of Configuration Requirements 2-2
2.2 Example of a Partitioned System 2-4
2.3 Module Configuration 2-6
2.4 Memory Allocation 2-8
2.4.1 Two Partitions 2-8
2.4.2 Three Partitions 2-10
2.5 DWLPB PCI Card Cages and Hose Connections 2-12
2.6 KFE72-DA Adapters and Attached Console Terminals 2-14
2.7 CD-ROM Drives for Secondary Partitions 2-16
2.8 Attaching Floppy Drives for Secondary Partitions (Optional) 2-18
2.9 Moving One Floppy Drive Between Partitions 2-20
Chapter 3 Environment Variable Settings
3.1 Environment Variables Used 3-2
3.2 Detailed Directions for lp_cpu_mask 3-4
3.3 Detailed Instructions for lp_io_mask 3-8
Chapter 4 Setting Up, Initializing, and Booting Logical
Partitions
4.1 Primary Console: Check Configuration 4-2
4.2 Step 1: Create and Initialize Environment Variables from the
Primary Console 4-6
4.3 Step 2: Initialize Partitions from the Primary Console;
Boot/Install OS in Partition 0 4-8

iv
4.4 Step 3: Set and Initialize Environment Variables,
Boot/Install from Secondary Consoles 4-10
Chapter 5 Tips and Troubleshooting
5.1 Setting auto_action Within Partitions 5-2
5.2 How to Stop a Hung Secondary Partition 5-4
5.2 Halting All Partitions to Reconfigure 5-6
5.3 Correcting Errors in Environment Variables 5-8
5.4 Using Tools to Debug a Partition 5-10
Index
Examples
4-1 Check Configuration from Primary Console 4-2
4-2 Initial Commands from the Primary Console 4-6
4-3 Initializing the Partitions 4-8
4-4 Using the Secondary Consoles 4-10
5-1 Halting a Hung OS Instance in Partition 0 5-4
5-2 Halting a Hung OS Instance in Secondary Partitions 5-4
5-3 All Consoles: Shut Down Operating System 5-6
5-4 Primary Console: Disable Partitions and Reset EVs 5-6
5-5 Correcting a Bad Bit Mask 5-8
Figures
1-1 Maintaining Multiple Instances at Separate Consoles 1-1
1-2 Consolidating Resources by Using Partitioning 1-2
1-3 Reset: Use Caution with Partitioned Systems 1-4
1-4 Overview of Using Logical Partitions 1-6
2-1 Example Configuration (Front View of Cabs) 2-4
2-2 Example Configuration (Rear View of Cabs) 2-5
2-3 Module Configuration 2-6
2-4 Memory Allocation with Two Partitions 2-8
2-5 Memory Allocation with Three Partitions 2-10
2-6 DWLPB PCI Card Cages 2-12
2-7 Hose Numbering Scheme for I/O Modules 2-13
2-8 KFE72-DA Adapters 2-14
2-9 Placement of RRDxx-VA Disks 2-16
2-10 Floppy Drive Connector on KFE72-DA Adapter 2-18
2-11 Relevant Connectors on KFE72s and DWLPBs 2-20

v
3-1 Environment Variables and lpinit Command 3-2
3-2 Construction of Three-Partition CPU Bit Mask 3-4
3-3 Construction of Two-Partition CPU Bit Masks 3-6
3-4 Construction of Three-Partition I/O Bit Masks 3-8
3-5 Construction of Two-Partition I/O Bit Masks 3-9
5-1 Setting auto_action to Halt in Each Partition 5-2
5-2 Debugging One Partition 5-10
Tables
1 Related AlphaServer GS140 Documentation viii
2-1 Requirements for a Three-Partition System 2-2
2-2 Requirements for a Two-Partition System 2-3
3-1 Environment Variables for Logical Partitions 3-3

vii
Preface
Intended Audience
This manual is written for anyone wishing to understand the concepts and
requirements of logical partitions for a Compaq AlphaServer GS140 system, as
well as how to use the console firmware to define them.
Document Structure
This manual uses a structured documentation design. Topics are organized into
small sections for efficient online and printed reference. Each topic begins with
an abstract. You can quickly gain a comprehensive overview by reading only
the abstracts. Next is an illustration or example, which also provides quick
reference. Last in the structure are descriptive text and syntax definitions.
This manual has five chapters, as follows:
•Chapter 1, Introduction, gives an overview of logical partitions.
•Chapter 2, Configuration Rules, describes the hardware you need to run
logical partitions.
•Chapter 3, Environment Variable Settings, describes the environment
variables used to define logical partitions for an operating system.
•Chapter 4, Setting Up, Initializing, and Booting Logical Partitions ,
describes the sequence of console firmware commands you need to use to
enable logical partitioning and boot/install the operating system.
•Chapter 5, Tips and Troubleshooting, gives pointers on how to perform
common operations, correct problems, and run tools to debug a partition.

viii
Documentation Titles
Table 1 lists the books in the AlphaServer GS140 documentation set and
operating system documentation that you may find useful.
Table 1 Related AlphaServer GS140 Documentation
Title Order Number
Hardware User Information and Installation
Operations Manual EK–T8030–OP
Service Information Kit QZ–00RAC–GC
Service Manual (hard copy) EK–T8030–SV
Service Manual (diskette) AK–QKNFB–CA
AK-QUW7B-CA
AK-QUW6B-CA
Reference Manuals
System Technical Manual EK–T8030–TM
System Technical Manual Supplement: CPU EK–T8030–TS
System Technical Manual Supplement: Memory EK–MS7CC–TS
DWLPA/DWLPB PCI Adapter Technical Manual EK–DWLPA–TM
Upgrade Manuals
KN7CG CPU Installation Card EK–KN7CG–IN
MS7CC Memory Installation Card EK–MS7CC–IN
KFTHA System I/O Module Installation Card EK–KFTHA–IN
KFTIA Integrated I/O Module Installation Card EK–KFTIA–IN
AlphaServer 8400 Upgrade Manual EK–T8430–UI
DWLPA/DWLPB PCI PIU Installation Guide EK–DWL84–IN
KFE72 Installation Guide EK–KFE72–IN
Software Manuals
Tru64 UNIX Installation Guide
Tru64 UNIX System Administrator’s Guide
Tru64 UNIX Release Notes
DECevent Installation Guide AA–DECUX–IN

Introduction 1-1
Chapter 1
Introduction
Partitioning is defined as the capability to run multiple copies, or instances, of
an operating system on one hardware system. Each instance is maintained at a
separate console monitor, as shown for two partitions in Figure 1–1. The
AlphaServer GS140 system supports up to three partitions.
Figure 1–1 Maintaining Multiple Instances at Separate Consoles
BX0502C-99
Primary Console
Secondary Console
Tru64 UNIX
running on
1 CPU module
1 2-Gbyte memory
1 KFTHA I/O module
Tru64 UNIX
running on:
2 CPU modules
1 4-Gbyte Memory
2 KFTHA I/O modules

1-2 Getting Started with Logical Partitions
1.1 Reasons for Partitioning
Partitioning can be used for various reasons, including the
consolidation of computing resources into one system or increasing the
efficiency of an existing system.
Figure 1–2 Consolidating Resources by Using Partitioning
BEFORE AFTER
Server
running 24/7
air pollution
monitoring and
simulation for
greater
Los Angeles
Small server
running office
applications
Medium-sized server
running audio-visual design
group
Partition 0
Partition 1
Partition 2
AlphaServer GS140
running 3 instances of
Compaq Tru64 UNIX
using logical partitions
BX-0199-99

Introduction 1-3
With logical partitioning, you can divide computing resources into as many as
three distinct partitions. Partitioning can be used for a variety of reasons,
including:
•Consolidation of several different computing requirements into one
hardware system, thereby reducing floor space requirements, power
consumption, and air conditioning costs. Figure 1–2 shows an example of
how an enterprise whose computing needs are met by three different
systems can accomplish the same work with one system using logical
partitions. Logical partitions can be used to run different applications that
require different configuration and tuning of the operating system.
•Increasing the efficiency of an existing system. For example, a facility may
have one particularly I/O intensive (or compute intensive) application and a
variety of other applications without such demands. With partitioning, you
can allocate the resources needed to provide the two separate environments
required. More I/O (or CPU) modules can be allocated to the I/O (or
compute) intensive application and the other applications limited to a
smaller set of resources, and both environments run at the same time.

1-4 Getting Started with Logical Partitions
1.2 Important Considerations for Partitioned Systems
Here are some important considerations for partitioned AlphaServer
GS140 systems.
Figure 1–3 Reset: Use Caution with Partitioned Systems
P00>>>
Primary Console
Reset
BX-0100F-99
(powerup display)
.
.
.
S
e
c
o
n
d
a
r
y
C
o
n
s
o
l
e
s
Poof!
Running OS
goes
Poof!
Running OS
goes
Don't forget to shut down the
Operating System in all partitions!

Introduction 1-5
There are some important things to be aware of when running multiple
instances of operating systems on separate partitions on AlphaServer GS140
systems:
•Reset Keyswitch Position. Once partitions are up and running separate
instances of the operating system, turning the control panel keyswitch to
the Reset position causes the system to initialize, stopping whatever is
going on in all partitions. To halt operations in an orderly manner,
you must shut down the operating system for each of the partitions
at the appropriate console terminal and then use Reset.
•Init Command. Issuing the init command at the console terminal for any
partition causes a complete reinitialization of all partitions defined for the
system, with results as described for Reset, above. With the init command,
however, the firmware displays a prompt asking you to confirm that you
want to reset all partitions before any action is taken.
•Ctrl/P. At the primary console, you can halt a hung instance of the
operating system by using the Ctrl/P keystroke, returning to the console
prompt. Secondary partitions continue uninterrupted. Ctrl/P does not work
from secondary consoles, but you can stop processing in secondary partitions
by issuing a stop ncommand to halt a CPU from another partition, as
discussed further in Chapter 5.

1-6 Getting Started with Logical Partitions
1.3 Overview of the Partitioning Process
To define logical partitions, you need to check the hardware
configuration, assign modules to partitions as desired, initialize the
partitions, and install the operating system.
Figure 1–4 Overview of Using Logical Partitions
Obtain Required Hardware, Firmware,
and Operating System
(see Chapter 2)
Set Logical Partitioning
Environment Variables
(see Chapter 3)
Set Up, Initialize, and Boot
Logical Partitions
(see Chapter 4)
Troubleshoot as Necessary
(see Chapter 5)
BX-0199A-99

Introduction 1-7
There are hardware, firmware, and software requirements and restrictions to
meet before you can run logical partitions. Chapter 2 describes the major
hardware configuration rules as of this printing. However, you should check the
Systems and Options Catalog for the most up-to-date information on the
hardware, firmware, and software required. The Systems and Options Catalog
also lists hardware that is not supported for partitioned systems and must be
removed from your system before partitions will run. The Systems and Options
Catalog is available on the web at http://www.compaq.com/alphaserver/.
Defining logical partitions involves setting certain environment variables.
Settings for these environment variables are discussed in Chapter 3.
A sequence of console commands must be issued to set environment variables
and to initialize logical partitions before installation of an instance of the
operating system in each partition. These commands are described in
Chapter 4. See also the information on logical partitioning in the Tru64 UNIX
System Administrator’s Guide for information on how to initialize logical
partitions and boot and install the operating system.
Once partitions are up and running separate instances of an operating system,
maintenance and troubleshooting will likely be done from each partition’s
console terminal. For example, a hardware error may cause one instance of the
operating system to crash. If the proper installations have been made, you can
run DECevent from the problem partition to debug.
However, some conditions (such as upgrading your system’s console firmware,
or to include new modules or other hardware) require shutting down each
instance of the operating system and disabling partitions temporarily until the
situation is taken care of. This procedure is described in Chapter 5.

Configuration Rules 2-1
Chapter 2
Configuration Rules
To define logical partitions for AlphaServer GS140 systems, you must have
certain hardware. Other hardware normally supported on AlphaServer GS140
systems are not supported with logical partitions. Check the Systems and
Options Catalog for up-to-date information. This chapter describes the
hardware requirements at the time this manual was printed. Sections include:
•Overview of Configuration Requirements
•Example of a Partitioned System
•Module Configuration
•Memory Allocation
•DWLPB PCI Card Cages and Hose Connections
•KFE72-DA Adapters and Attached Console Terminals
•CD-ROM Disks for Secondary Partitions
•Attaching Floppy Drives for Secondary Partitions (Optional)
•Moving One Floppy Drive Between Partitions (Optional)

2-2 Getting Started with Logical Partitions
2.1 Overview of Configuration Requirements
Here are the minimum and maximum configurations for partitioned
systems.
Table 2–1 Requirements for a Three-Partition System
Partition 0 Partition 1 Partition 2
Min Max Min Max Min Max
CPU
modules111 11 1 1
Memory
module size 512 MB 4 GB 512 MB 4 GB 512 MB 4 GB
Memory
modules 11 11 1 1
I/O modules 1 1 1 1 1 1
DWLPB 1 4 1 4 1 4
KFE72-EA 0 1 N/A N/A N/A N/A
KFE72-DA N/A N/A 1 1 1 1
BA35x 1 See
footnote21See
footnote² 1See footnote²
Disk Drives 2 See
footnote32See
footnote³ 2See footnote³
RRD4x
CD-ROMs 1N/A01 0 1
Floppy40 1 N/A N/A N/A N/A
1Logical partitions support KN7CG (GS140) processors only.
2As many as you need, based on the number of SCSI controllers.
3Depends on the number of StorageWorks shelves in your configuration.
4Only required to run utilities such as the RAID Configuration Utility (RCU). (You can
move one floppy between partitions, if necessary, as described in Section 2.9.)

Configuration Rules 2-3
Table 2–1 lists the minimum requirements and maximum restrictions for three
logical partitions; Table 2–2, for two partitions.
Table 2–2 Requirements for a Two-Partition System
Partition 0 Partition 1
Min Max Min Max
CPU modules115² 1 5²
Memory module
size 512 Mbyte 4 Gbyte 512 Mbyte 4 Gbyte
Memory
modules21515
I/O modules² 1 2 1 2
DWLPB31818
KFE72-EA 0 1 N/A N/A
KFE72-DA N/A N/A 1 1
BA35x41 See footnote 4 1 See footnote 4
Disk Drives52 See footnote 5 See footnote 5
RRD4x CD-
ROMs 1 N/A 1 N/A
Floppy6
1Logical partitions support KN7CG (GS140) processors only.
2The total number of modules connected to the TLSB must not exceed 9 (CPU, I/O, and
memory).
3Configuration depends on number of I/O hoses available.
4The maximum is as many as you need, based on the number of SCSI controllers.
5The maximum depends on the number of StorageWorks shelves in your configuration.
6Only required to run utilities such as the RAID Configuration Utility (RCU). (You can
move one floppy between partitions, if necessary, as described in Section 2.9.)

2-4 Getting Started with Logical Partitions
2.2 Example of a Partitioned System
These illustrations give an overview of some of the interplay between
the number of hardware modules, DWLPB adapters, KFE70/KFE72
adapters, and disks that you will need to consider in configuring your
AlphaServer GS140 system to run logical partitions.
Figure 2–1 Sample Configuration (Front View of Cabs)
BX-0183G-99
BA35x
Disks BA35x
Disks
BA35x
Disks
MEM
CPU CPU
CPU
Main Cabinet Expander Cabinet
RRD4x Disks
BA35x-FA
Personality Card