This guide is intended for those who manage, operate, or service the
AlphaServer GS160/320 system and the AlphaServer GS80 rack
system. It covers configuration guidelines, operation, system
management, and basic troubleshooting.
COMPAQ and the Compaq logo registered in U.S. Patent and Trademark Office. AlphaServer, OpenVMS,
StorageWorks, and Tru64 are trademarks of Compaq Information Technologies Group, L.P.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in
this document is subject to change without notice.
FCC Notice: The equipment described in this manual generates, uses, and may emit radio frequency
energy. The equipment has been type tested and found to comply with the limits for a Class A digital device
pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio
frequency interference. Operation of this equipment in a residential area may cause interference in which
case the user at his own expense will be required to take whatever measures may be required to correct the
interference. Any modifications to this device—unless expressly approved by the manufacturer—can void
the user’s authority to operate this equipment under part 15 of the FCC rules.
Shielded Cables: If shielded cables have been supplied or specified, they must be used on the system in
order to maintain international regulatory compliance.
Warning! This is a Class A product. In a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.
Achtung! Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb dieses
Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für entsprechende Gegenmaßnahmen
verantwortlich ist.
Attention! Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de créer
des interférences radioélectriques, il appartiendra alors à l'utilisateur de prendre mesures spécifiques
appropriées.
This manual is for managers and operators of Compaq AlphaServer 80/160/320
family systems.
Document Structure
This manual uses a structured documentation design. Topics are organized into
small sections, usually consisting of two facing pages. Most topics begin with an
abstract that provides an overview of the section, followed by an illustration or
example. The facing page contains descriptions, procedures, and syntax
definitions.
This manual has eight chapters, an appendix, and glossary.
Chapter 1, Introduction, gives a general overview of the AlphaServer
•
80/160/320 family.
•
Chapter 2, GS320 System Overview, describes the components of the
GS320 system.
Chapter 3, GS320 System Configuration Rules, provides configuration
•
guidelines for the GS320 system.
•
Chapter 4, GS80 Rack System Overview, describes the components of
the GS80 rack system.
Chapter 5, GS80 Rack System Configuration Rules, provides
•
configuration guidelines for the GS80 system.
•
Chapter 6, Booting and Installing an Operating System, tells how to
boot a supported operating system and how to set boot options.
Visit the Compaq Web site at www.compaq.com for service tools and more
information about the AlphaServer 80/160/320 family systems.
x
Chapter 1
Introduction
The CompaqAlphaServer GS160/320 and GS80 systems are high-performance
server platforms designed for enterprise-level applications. They offer a high
degree of scalability and expandability.
The GS160/320 system uses up to four Alpha microprocessors in each quad
building block (QBB). Two QBBs are paired back-to-back and rotated 180
degrees with reference to each other and then enclosed in a system box. A
system cabinet can hold up to two system boxes.
The GS80 rack system uses up to four Alpha microprocessors in a drawer. Each
rack holds up to two system drawers.
This chapter introduces the AlphaServer GS160/320 and AlphaServer GS80
systems. There are three sections:
AlphaServer GS160/320 and GS80 Systems
•
•
Firmware and Utilities Overview
•
System Architecture
NOTE: When you unpack your system, be sure to save and store all shipping
brackets, pallets, and packing material. You will need this material to
repack the system, if you should decide to relocate it.
Introduction 1-1
1.1 AlphaServer GS160/320 and GS80 Systems
The AlphaServer GS160/320 system and GS80 rack system are separate,
but related, in that they use the same switch technology. The CPU
modules, memory modules, and power modules are also the same. In
the GS160/320 system, the modules are in a system box in a cabinet. In
the GS80 rack system, the modules are in a drawer.
Figure 1–1 AlphaServer GS160 and GS80 Systems
GS80 System
GS160 System
1-2 AlphaServer GS80/160/320 User’s Guide
PK-0654-00
AlphaServer GS160/320 System
The AlphaServer GS160 system cabinet contains up to two system boxes
supporting a maximum of 16 CPU modules.
In an AlphaServer GS320 system, a second system cabinet is used to expand the
system (up to four system boxes containing a maximum of 32 CPU modules).
A power cabinet contains the power components, I/O boxes, and storage.
Additional I/O and storage can be housed in expander cabinets.
AlphaServer GS80 System
The AlphaServer GS80 rack system contains up to two system drawers, I/O, and
storage. Each system drawer supports up to four CPU modules, for a maximum
of eight CPUs per system. Power components are mounted at the bottom of the
rack cabinet.
An expander cabinet can be used to house additional I/O and storage.
System Management Console
The console device, called the system management console (SMC), is a Compaq
Deskpro PC, a DECserver 90M terminal server, and associated hardware and
software. For installation instructions and user information, see the
AlphaServer GS80/160/320 System Management Console Installation and
User’s Guide.
Introduction 1-3
1.2 Firmware and Utilities Overview
Firmware residing in ROM on CPU and other modules in the system
provides commands for booting the operating system, testing devices
and I/O adapters, and other tasks useful in operating and maintaining a
running system. You type commands at the console device.
SRM Console
Systems running the Tru64 UNIX or OpenVMS operating systems are
configured from the SRM console, a command-line interface (CLI). From the
CLI you can enter commands to configure the system, view the system
configuration, and boot the system.
System Control Manager (SCM)
The SCM firmware allows the user to access the system remotely. In addition,
the SCM:
Monitors and notifies the user of power or temperature alert conditions
•
•
Controls initial system power-up
•
Manages hard partitions
LFU (Loadable Firmware Update Utility)
You can boot this utility (with the SRM boot command) whenever you need to
update the SRM console firmware or I/O device firmware. The CD with the
AlphaServer firmware is updated periodically.
1-4 AlphaServer GS80/160/320 User’s Guide
1.3 System Architecture
Each QBB in a GS160/320 system and each QBB (system drawer) in a
GS80 system has a backplane and a switch supporting the CPU
modules, memory modules, and I/O riser modules. Figure 1–2 shows
two QBBs in a single-box system.
Figure 1–2 Sample System Architecture
System Box
To PCI Boxes
To PCI Boxes
CPU
I/OGP
MEM
CPU
I/OGP
MEM
CPUCPUCPU
Switch
MEMMEMMEM
Distribution
Board
CPUCPUCPU
Switch
MEMMEMMEM
PK-0601A-98
The backplane of each QBB (GS160/320 systems) and drawer (GS80 rack
systems) contains the switch that interconnects the CPU modules, memory
modules, and I/O riser modules.
The global port and distribution board provide the interconnect for the QBBs.
In a two-box system, a hierarchical switch is used as the interconnect, in place
of the distribution board.
I/O riser modules connect the PCI boxes to the QBB backplane.
Introduction 1-5
Chapter 2
GS160/320 System Overview
Each system cabinet contains one or two system boxes. The system box houses
two quad building blocks, or QBBs. CPU modules, memory modules, power
modules, and I/O riser modules plug into the QBB backplane.
The power cabinet contains power components, PCI boxes, and storage shelves.
This chapter provides an overview of the system in these sections:
System Characteristics
•
System Box Architecture
•
•
Quad Building Block (QBB) Components
•
Power System
•
PCI I/O
•
Control Panel
GS160/320 System Overview 2-1
2.1 System Characteristics
The illustration shows the BA51A-AA system box. Table 2–1 lists the
system box characteristics. Table 2–2 lists power cabinet and
environmental characteristics.
Figure 2–1 System Box
PK0611
Table 2–1 System Box Characteristics
CharacteristicSpecification
Size
Weight54.55 kg (120 lb) maximum
Maximum heat dissipation2000 w (6,850 Btu/hr)
2-2 AlphaServer GS80/160/320 User’s Guide
535 mm H x 550 mm W x 475 mm D
(21.06 in. x 21.65 in. x 18.7 in.)
Table 2–2 Power Cabinet and System Environmental Characteristics
Power CabinetSpecifications
Electrical
Voltage120/208 VAC (U.S)
380–415 VAC (Europe)
200 VAC (Japan)
Phase3-phase
Frequency50–60 Hz
Maximum input
21 A
current/phase
Heat dissipation
1
9,300 W/31,800 Btu/Hr
Environmental
Temperature
Operating: 5° to 35°C (41 to 95°F)
Not operating: -40° to 66°C (-40° to 151°F)
HumidityOperating: 10% to 90%
Not operating: 10% to 95%
Altitude
Operating: 0 to 3 km (0 to 10,000 ft)
Not operating: 0 to 12.2 km (0 to 40,000 ft)
1
A fully configured system with three system boxes, nine power supplies, two
PCI boxes, and storage shelf.
GS160/320 System Overview 2-3
2.2 System Box Architecture
The system box houses two quad building blocks (QBBs). Each QBB
has a backplane with a switch interconnect that supports up to four
CPU modules, four memory modules, two power modules, two I/O riser
modules, and a global port. Figure 2–2 shows two system boxes
connected by the hierarchical switch. Figure 2–3 shows one system box
and the distribution board.
Figure 2–2 System Box Block Diagram (16-Processor System)
System Box 1
Modem
Operator
Console
PCI Box
Standard
I/O SCM
PCI Box
PCI Box
PCI Box
CPU
CPU CPU CPU
I/OGP
Switch
MEM
CPU
CPU CPU CPU
I/OGP
Switch
MEM
MEMMEMMEM
MEMMEMMEM
System Box 2
Hierarchical
Switch
CPU
PCI Box
PCI Box
PCI Box
PCI Box
CPU CPU CPU
I/OGP
Switch
MEM
CPU
CPU CPU CPU
I/OGP
Switch
MEM
MEMMEMMEM
MEMMEMMEM
2-4 AlphaServer GS80/160/320 User’s Guide
PK-0623-98
The switch on the backplane connects the CPU modules, memory modules, I/O
riser modules, and global port. In an 8-P system, the global ports connect the
QBBs to the distribution board. In a 16-P or a 32-P system, the global ports
connect the QBBs to the hierarchical switch.
Figure 2–3 System Box Block Diagram (8-Processor System)
Operator
Console
Modem
PCI Box
Standard
I/O SCM
PCI Box
PCI Box
PCI Box
System Box
CPU
I/OGP
MEM
CPU
I/OGP
MEM
CPUCPUCPU
Switch
MEMMEMMEM
CPUCPUCPU
Switch
MEMMEMMEM
Distribution
Board
PK-0601-98
GS160/320 System Overview 2-5
2.3 Quad Building Block (QBB) Components
Figure 2–4 shows two QBBs back to back in the system box.
Figure 2–4 System Box QBBs (Top View)
QBB 1 (Front)
Top View
1
2
4
1
QBB 0 (Rear)
2-6 AlphaServer GS80/160/320 User’s Guide
2
3
PK-0612-98
The QBB backplanes are attached to a stiffener and mounted in a system box
enclosure. Each backplane has a differently positioned cutout to accommodate
the global port modules. A global port module is mounted on the front of one
QBB and the other is mounted on the back of the other QBB, putting both
global port modules near the distribution board (or the hierarchical switch)
when the system box is installed in the cabinet.
The callouts in Figure 2–4 point to the location of these components in the
system box:
➊
I/O riser module area. Each QBB supports up to two I/O riser
modules.
➋
CPU module and memory module area. Each QBB holds four CPUs
and four memory modules.
➌
Global port area.
➍
Backplane area.
GS160/320 System Overview 2-7
2.3.1 Backplane
Each QBB backplane is located at the center of the system box. Figure
2–5 shows an unpopulated backplane (no modules installed) as you
would see it from the front of the system box.
Figure 2–5 Backplane (System Box, Front View)
1234345
64343789
2-8 AlphaServer GS80/160/320 User’s Guide
PK0600
The CPU, memory, power, and I/O riser modules plug into the backplane.
Because of the orientation of the QBB backplanes, the modules are situated
differently in the front and rear of the system box. See Section 3.5 for more
information.
The switch interconnect on the backplane allows any processor to access any
memory on the QBB. The backplane also provides power to the modules.
➊Global port module
➋Directory module
➌
CPU module
➍
Memory module
➎
I/O riser modules
➏
Clock splitter module
➐
Power system manager (PSM) module
➑
Main power module
➒
Auxiliary power module
GS160/320 System Overview 2-9
2.3.2 CPU Module
A CPU module comes with an Alpha microprocessor chip with a Bcache, cache control and TAG comparison logic, clock logic, and a DCDC power converter. Also included on the module is logic for
implementing self-test diagnostics. Each module has a Run LED and a
Hot Swap LED.
Figure 2–6 CPU Module
Run LED
Hot Swap
LED
Power
Converter
CPU
Chip
PK0602
2-10 AlphaServer GS80/160/320 User’s Guide
2.3.3 Memory Module
A memory module has eight DIMM slots. See Section 3.7 for memory
configuration guidelines.
Figure 2–7 Memory Module
DIMMs
PK0603
GS160/320 System Overview 2-11
2.3.4 Directory Module
In a GS160/320 system, one directory module is required for each QBB
in a system box. In a two-drawer GS80 system, a directory module is
required in each system drawer. No directory module is needed in a
one-drawer system. The directory module functions as a memory
coherency manager.
Figure 2–8 Directory Module
Directory
DIMMs
2-12 AlphaServer GS80/160/320 User’s Guide
PK0606
2.3.5 Power Modules
Two power modules are installed in the QBB backplane. The main
power module and the auxiliary power module convert 48 VDC to the
various voltages required to power the QBB.
Figure 2–9 Power Modules
Auxiliary Power Module
Main Power Module
PK-0604-99
GS160/320 System Overview 2-13
2.3.6 Power System Manager Module
Each QBB has one power system manager (PSM) module. This module
monitors CPUs, voltages, temperatures, and blower speed in the
cabinet and reports this information to the system control manager
(SCM).
Figure 2–10 Power System Manager Module
PK0607
The PSM module is connected to other PSM modules and the SCM microprocessor (located on the standard I/O module) through the console serial bus
(CSB). The SCM is the master; the PSM can only operate as a slave. The PSM
controls the powering on/off and resetting of all modules within the QBB and of
the QBB itself. The PSM also contains three I
bus channel to each CPU in the QBB. The PSM module retrieves information
from the I
2
C EEROMs residing on the CPUs, memory modules, and the QBB
2
C bus interfaces and a serial I/O
backplane. The PSM uses a serial I/O port connection to communicate with one
CPU module at a time. The PSM can only perform a function as the result of a
request from the SCM.
2-14 AlphaServer GS80/160/320 User’s Guide
2.3.7 Clock Splitter Module
The clock splitter module converts one global signal to identical copies
of a signal that is then distributed to master phase lock loops
associated with the ASICs and the system processors within a QBB. It
also generates independent clock signals for the I/O domain.
Figure 2–11 Clock Splitter Module
PK2222
GS160/320 System Overview 2-15
2.3.8 I/O Riser Module
The I/O riser module is used to connect the QBB backplane to a PCI
box. A “local” I/O riser module is located on the QBB backplane; a
“remote” I/O riser module is in the PCI box.
Figure 2–12 I/O Riser Module
2-16 AlphaServer GS80/160/320 User’s Guide
PK0605
2.3.9 Global Port Module
The global port provides the interconnect to the other QBB(s) through
the distribution board or the hierarchical switch.
Figure 2–13 Global Port Module
Front QBB
Rear QBB
PK-0655-00
GS160/320 System Overview 2-17
2.3.10 Distribution Board
In single-box systems, a distribution board connects the two QBBs
through the global ports.
Figure 2–14 Distribution Board
A1
B1
B0
A0
2-18 AlphaServer GS80/160/320 User’s Guide
PK1244
Figure 2–15 is a block diagram showing the distribution board as the
interconnect between two QBBs.
Figure 2–15 Distribution Board in Single-Box System
System Box
To PCI Boxes
To PCI Boxes
CPU
I/OGP
MEM
CPU
I/OGP
MEM
CPUCPUCPU
Switch
MEMMEMMEM
CPUCPUCPU
Switch
MEMMEMMEM
Distribution
Board
PK-0601A-98
GS160/320 System Overview 2-19
2.3.11 Hierarchical Switch
In two-box systems, a hierarchical switch links the QBBs through the
global ports. The hierarchical switch connects QBBs in three- and
four-box systems also.
Figure 2–16 Hierarchical Switch
System
Box 2
System
Box 4
System
Box 3
2-20 AlphaServer GS80/160/320 User’s Guide
System
Box 1
PK0626
The hierarchical switch links the QBBs in systems having more than one
system box. Figure 2–16 shows cable connectors for each system box (a pair of
connectors for two signal cables routed to each QBB global port in the system).
The hierarchical switch power manager (HPM) module controls power and
monitors the temperature inside the hierarchical switch housing. The HPM
module, along with the PSM modules and PBM modules, report status
information to the SCM.
GS160/320 System Overview 2-21
2.4 Power System
Each system box has a power subrack with up to three 48 VDC power
supplies. Figure 2–17 shows the power system for a 32-P system. See
Section 3.3 for power configuration rules.
Figure 2–17 Power System
System
Box 4
(Brown)
System
Box 3
(Orange)
Orange
Brown
Blue
Green
System
Box 2
(Green)
System
Box 1
(Blue)
Subrack 1
(Blue)
Subrack 2
(Green)
Subrack 3
(Orange)
Subrack 4
(Brown)
AC Input
2
AC Input
1
2-22 AlphaServer GS80/160/320 User’s Guide
PK0615A
Power cables and components are color-coded to ensure proper identification
and easy handling.
NOTE: Color-coded components and power cables must match to ensure proper
power distribution, particularly in hard-partitioned systems.
Figure 2–17 shows each system box and its color-related power subrack and AC
input box. The AC input box also has color-coded circuit breakers. Each AC
input box provides power to the subracks, PCI boxes, and storage shelves.
Power distribution and signal cables are connected from the power subrack to
the QBB backplanes through a power distribution bulkhead. Another cable is
used to provide power to the blower, located at the bottom of the system cabinet,
and the control panel, located in the power cabinet.
Each QBB has its own main power module and auxiliary power module. Each
CPU module has its own power converter that converts the 48 VDC to the
required voltage.
When the main power circuit breaker (CB1) is on and the AC input box is
plugged in, the console serial bus (CSB) has auxiliary power (Vaux), enabling
the system control manager (SCM) to power up the system.
See Section 2.4.1 for more information on the AC input box and circuit breakers.
GS160/320 System Overview 2-23
2.4.1 AC Input Box
A system has two AC input boxes. Figure 2–18 shows the circuit
breakers (CB1–CB11), LEDs (L1–L3), and connectors (J1–J22) on the AC
input box.
Figure 2–18 AC Input Box
J-1J-2J-3
J-4J-5J-6
L1 L2 L3
CB1
J-7
J-12
J-9
J-14
CB5 CB7 CB9CB11CB3
J-15
J-19
J-20J-11 J-13
J-16
J-21
J-18
J-17J-8 J-10
Cabinet
Front
J-22
CB10CB8CB6CB4CB2
Cabinet
Rear
PK-0645-99
2-24 AlphaServer GS80/160/320 User’s Guide
The three LEDs on the AC input box should be lit at all times, indicating that
all three power phases are present in the 3-phase AC input.
Table 2–3 lists the AC input box circuit breakers and the lines they protect.
Table 2–3 AC Input Box Circuit Breakers
Circuit BreakerLine(s) Protected
CB1 (Main)All lines protected.
CB2J1
CB3J2
CB4J3
CB5J4
CB6J5
CB7J6
CB8J7, J8, J9, J10
CB9J11, J12, J13, J14
CB10J15, J16, J17, J18
CB11J19, J20, J21, J22
GS160/320 System Overview 2-25
2.5 PCI I/O
The power cabinet contains at least one PCI master box, and may
contain PCI expansion boxes.
Figure 2–19 PCI Master Box
Front
DVD/CD-ROM
Power Supply LEDsPower Supply LEDs
Rear
Remote I/O
Riser Module
Floppy Drive
Keyboard
Mouse
Remote I/O
Riser Module
COM 2
Serial Port
Local Terminal
Port
Operator
Control
Panel
Parallel
Port
LEDs
CSB Node
ID Switch
CSB
Modem
USB
Ports
Port
2-26 AlphaServer GS80/160/320 User’s Guide
PK0656
A PCI master box has a standard I/O module, a DVD/CD-ROM drive and a
floppy drive as shown in Figure 2–19. PCI expansion boxes provide additional
slots for options. Each PCI power supply has three LEDs: Vaux OK, Power OK,
and Swap OK.
BA54A-AA PCI Box
The BA54A-AA PCI box is a PCI master box. It contains the following
components:
Backplane with a standard I/O module
•
•
Thirteen I/O option slots
DVD/CD-ROM drive
•
•
SCSI disk drive
•
Floppy drive
Ports: one local terminal port, one serial port, one modem port, one parallel
•
port, two USB ports, one keyboard port, one mouse port, one CSB port, and
one control panel port
Two I/O riser slots
•
•
Two power supplies
BA54A-BA PCI Box
The BA54A-BA box is a PCI expansion box and contains the following
components:
Backplane with fourteen option slots
•
Two I/O riser slots
•
•
Two power supplies
GS160/320 System Overview 2-27
2.6 Control Panel
The control panel is located at the top of the power cabinet. It has a
three-position Off/On/Secure switch, three pushbuttons, three status
LEDs, and a diagnostic display.
Figure 2–20 Control Panel
2134
657
9108
PK0621
2-28 AlphaServer GS80/160/320 User’s Guide
The callouts in Figure 2–20 point to these components on the control panel:
➊
Secure LED – When lit, indicates that the keyswitch is in the Secure
position and system is powered on. All pushbuttons and SCM functions
are disabled, including remote access to the system.
➋
Power OK LED – When lit, indicates at least one QBB is powered on and
remote console operations are enabled. The keyswitch is in the On
position.
➌Halt LED – When lit with the Power LED, indicates the system is powered
on, remote console operations are enabled, and the Halt pushbutton is
pressed.
When lit with both Power LED and Secure LED, indicates a powered on
system, disabled remote console operations, and Halt pushbutton is
pressed in.
➍
Diagnostic display indicates system status.
➎
Off switch position – System is powered off and cannot be powered on
remotely.
➏
On switch position – System is enabled to be powered up. A remote system
user can power on or power off the system.
➐Secure switch position – System is powered on and cannot be remotely
powered on or off. All pushbuttons and SCM functions are disabled.
➑
Halt pushbutton – Pressing this pushbutton causes the operating system
to perform a halt, with no captured error information. The system will
automatically reset if the auto_fault_reset environment variable is
enabled.
➒Fault pushbutton – Pressing this pushbutton causes a system reset
without clearing captured error information in the control and status
registers.
➓
Reset pushbutton – Pressing this pushbutton causes a system reset that
clears captured error information.
GS160/320 System Overview 2-29
2.6.1 Control Panel LEDs
Figure 2–21 shows the various control panel LED status indications.
Figure 2–21 Control Panel LED Status
Control Panel LEDsStatus
SecurePower
OK
On
Off
Halt
System powered on; remote console disabled; pause mode.
System powered on; remote console disabled.
System powered on; remote console enabled; remote console
halt or Halt button depressed.
System powered on; remote console enabled.
System powered off for any of the following reasons:
o No AC power available
o Keyswitch in Off position
o Keyswitch in On position but system powered off by remote
console or power/temperature failure
PK-0622-99
2-30 AlphaServer GS80/160/320 User’s Guide
Chapter 3
GS160/320 System Configuration Rules
This chapter provides configuration rules for the following:
•
GS160 System Cabinet
•
GS320 System Cabinets
•
Power Cabinet
System Box
•
•
QBB Color Code
•
Memory Configurations
•
Memory Interleaving Guidelines
PCI Boxes
•
•
PCI Box Slot Configuration
•
Expander Cabinet
GS160/320 System Configuration Rules 3-1
3.1 GS160 System Cabinet
Figure 3–1 shows the front view of the system cabinet and the power
cabinet. One system cabinet houses either one system box or two
system boxes. In a one-box system, a distribution board connects the
two QBBs. In a two-box system, a hierarchical switch connects the
QBBs.
Figure 3–1 GS160 System
System
Box 2
System
Box 1
3-2 AlphaServer GS80/160/320 User’s Guide
PK0614
About the System Cabinet
The cabinet contains the following components:
Vertical mounting rails
•
Wrist strap for static discharge protection
•
GS160 Configuration Rules
•
System box 1 (see Figure 3–1) is mounted in the lower half of the cabinet,
above the blower.
System box 2 is mounted in the upper half of the cabinet, over system box 1.
•
GS160/320 System Configuration Rules 3-3
3.2 GS320 System Cabinets
Figure 3–2 shows the front view of the system cabinets. Two system
cabinets house either three system boxes or four system boxes. A
hierarchical switch is used to connect the QBBs.
Figure 3–2 GS320 System
System
Box 4
System
Box 3
System
Box 2
System
Box 1
PK0615
3-4 AlphaServer GS80/160/320 User’s Guide
GS320 System Configuration Rules
In system cabinet 1, system box 1 (see Figure 3–2) is mounted in the lower
•
half of the cabinet, above the blower. System box 2 is mounted in the upper
half of the cabinet, above system box 1.
In system cabinet 2, system box 3 is mounted in the lower half of the
•
cabinet; system box 4, the upper half of the cabinet.
GS160/320 System Configuration Rules 3-5
3.3 Power Cabinet
One power cabinet is required for all systems. The power cabinet
houses the control panel, AC input boxes, power supplies, PCI I/O
boxes, and storage.
Figure 3–3 Power Cabinet Configuration (32-P System)
System
Box 4
(Brown)
System
Box 3
(Orange)
Orange
Brown
Blue
Green
System
Box 2
(Green)
System
Box 1
(Blue)
Subrack 1
(Blue)
Subrack 2
(Green)
Subrack 3
(Orange)
Subrack 4
(Brown)
AC Input
2
AC Input
1
3-6 AlphaServer GS80/160/320 User’s Guide
PK0615A
Power System Requirements
Each system box requires a power subrack.
•
•
Each power subrack has three power supplies. The third power supply is
always redundant. See Section 3.3.1 for power supply slot assignments.
Two AC input boxes are required.
•
Cables, AC input boxes (including AC circuit breakers), power subracks, and
system boxes are color-coded at cable connections to ensure proper cabling.
Figure 3–3 shows the color coding scheme for a 32-P system.
PCI boxes and storage shelves are installed in the upper half of the power
cabinet.
GS160/320 System Configuration Rules 3-7
3.3.1 Power Supply Slot Assignments
Figure 3–4 show the power supply slot assignments in each power
subrack.
Figure 3–4 Power Supply Slot Assignments
Power
Subrack
1
123
R
R
Power
Subrack
2
123
R
Power
Subrack
3
123
R
Power
Subrack
R
4
indicates redundant power supply slot.
123
Blue
Green
Orange
Brown
Power
Cabinet
Bulkhead
Power
Cabinet
Bulkhead
AC Input 2
AC Input 1
PK-0624-99
3-8 AlphaServer GS80/160/320 User’s Guide
Power Supply Configuration Rules
Power subracks are always mounted in the same power cabinet location,
•
regardless of the number of system boxes.
Power supply slot assignments remain the same in all systems, regardless
•
of the number of system boxes.
•
A redundant power supply slot is always the last slot to be used in a
subrack.
GS160/320 System Configuration Rules 3-9
3.4 System Box
The system box contains two QBBs. Figure 3–5 shows a fully populated
QBB as seen from the front of the cabinet. Figure 3–6 shows the second
QBB at the rear of the cabinet.
Figure 3–5 System Box QBB (Cabinet Front)
Memory 2Memory 0
DirectoryCPU 3CPU 1
I/O Riser
I/O Riser
Signal Cable
Clock
Splitter
Memory 3Memory 1
CPU 2CPU 0
PSM
3-10 AlphaServer GS80/160/320 User’s Guide
Main
Power
Auxiliary
Power
PK0610
System Box Configuration Rules
A system box has two QBBs.
•
•
A QBB supports up to four CPU modules.
•
A QBB supports up to four memory modules.
•
A QBB has up to two I/O riser modules; each I/O riser module connects to
one PCI box.
A system box supports up to four PCI boxes.
•
Figure 3–6 System Box QBB (Cabinet Rear)
Memory 3
Clock
Splitter
Global Port - Odd
(Connected to front QBB)
Auxiliary
Power
Main
Powe r
PSM
CPU 0
CPU 2
Memory 1
Powe r
Connectors
I/O Riser
I/O Riser
CPU 1CPU 3
Memory 0
Memory 2
Directory
Global Port - Even
(Connected to back QBB)
PK2228
GS160/320 System Configuration Rules 3-11
3.5 QBB Color Code
Figure 3–7 and Figure 3–8 show the center bar color code for module
placement in the QBB. Note that CPU and memory slots are colorcoded to ensure the correct placement of each module.
Figure 3–7 QBB Center Bar Color Code (Cabinet Front)
Directory
(White)
Memory 3
Clock
Splitter
(Green)
CPU 3
(Blue)
(Gray)
Memory 2
(Gray)
Memory 1
CPU 2
(Blue)
CPU 1
(Blue)
(Gray)
Memory 0
(Gray)
(Orange)
CPU 0
(Blue)
PSM
Main
Powe r
(Yellow)
Auxiliary
Powe r
(Red)
3-12 AlphaServer GS80/160/320 User’s Guide
PK0628
Figure 3–8 QBB Center Bar Color Code (Cabinet Rear)
(Yellow)
Auxiliary
Powe r
(Red)
Main
Powe r
CPU 0
(Blue)
PSM
(Orange)
Memory 0
(Gray)
CPU 2
(Blue)
Memory 1
(Gray)
CPU 1
(Blue)
Memory 3
(Gray)
Clock
Splitter
(Green)
Memory 2
(Gray)
CPU 3
(Blue)
Directory
(White)
Global
Por t 1
Global
Por t 0
PK2229
GS160/320 System Configuration Rules 3-13
3.6 Memory Configurations
A memory module has eight DIMM slots. Two arrays (Array 0 and
Array 1), consisting of four DIMMs, can be installed on each module. A
directory DIMM is required for each array in systems having more than
four processors. Directory DIMMs are installed on the directory
module.
On a memory module, DIMMs are divided into two groups of four called
•
arrays.
A memory module must be populated on an array-by-array basis; that is,
•
groups of four DIMMs must be installed.
•
DIMMs in an array must be the same size and type.
•
DIMM sizes include 256 Mbyte, 512 Mbyte, and 1 Gbyte.
There are two types of DIMMs: single density (SD) and double density (DD).
Density does not affect interleaving.
•
•
One directory module DIMM is required for each memory array in systems
with more than one QBB.
The type and number of DIMMs installed in the directory module is based
•
on the number of memory arrays populated and the physical size of the
memory arrays. See the table below.
A larger DIMM type may always be used in place of the minimum required
•
DIMM type.
Directory DIMM TypeMemory Array SizePart Number
0 256 MB54-25019-AA
1 1 GB54-25023-AA
2 2 GB54-25023-BA
3 2 GB54-25023-CA
4 4 GB54-25023-DA
GS160/320 System Configuration Rules 3-15
3.7 Memory Interleaving Guidelines
Table 3–1 Interleaving Memory Modules
Memory InterleavingGuidelines
4-wayThe default interleave. One memory module with
one array populated (or most mixes not discussed
below).
8-wayOne memory module with two arrays populated.
Preferred method: Two memory modules with one
array populated on each module.
16-wayTwo memory modules, each with two arrays
populated.
Preferred method. Four memory modules with one
array populated on each module.
32-wayFour memory modules with two arrays populated on
each module.
3-16 AlphaServer GS80/160/320 User’s Guide
Memory Interleaving Guidelines
The larger the interleaving factor, the better the system performance.
•
•
Avoid mixing memory sizes; this limits interleaving capability and
potential bandwidth.
GS160/320 System Configuration Rules 3-17
3.8 PCI Boxes
A QBB supports up to two PCI boxes. A cable connects the QBB “local”
I/O riser to the “remote” I/O riser in the PCI box. There are two I/O
ports on a local I/O riser. Each I/O port is used to connect to one
remote I/O riser. Figure 3–10 shows QBB0 connected to PCI box 0 and
PCI box 1.
Figure 3–10 Sample I/O Subsystem
PCI Box 0PCI Box 1
PCI Bus
PCA
Chip
PCI Bus
PCA
PCI Bus PCI Bus
Remote I/O
Riser 1
1032
Local I/O RiserLocal I/O Riser
Chip
Remote I/O
Riser 0
PCI Bus
QBB0
PCA
Chip
PCI Bus
PCA
PCI Bus PCI Bus
Remote I/O
Riser 1
Chip
Remote I/O
Riser 0
PK-0652-99
3-18 AlphaServer GS80/160/320 User’s Guide
The I/O subsystem consists of the local I/O interface (QBB) and the remote I/O
interface (PCI box) connected by I/O cables.
A system can have up to 16 PCI boxes. To identify PCI boxes in a system, a
node ID is set using the node ID switch located on the rear panel of each PCI
box (see Figure 3–11).
GS160/320 System Configuration Rules 3-19
3.9 PCI Box Slot Configuration
Each QBB can have two I/O risers supporting up to two PCI boxes. A
cable connects a local I/O riser (in the QBB) to a remote I/O riser (in the
PCI box). Each PCI box can have up to two remote I/O risers in place.
Cable connectors for the two remote I/O risers are shown as Riser 0 and
Riser 1 in Figure 3–11. PCI slots and logical hoses are listed in Table 3–
2.
Figure 3–11 PCI Slot Locations
6754 32115647132Slot
RiserRiser 0
3-20 AlphaServer GS80/160/320 User’s Guide
PK-0643-99
PCI Slot Configuration Guidelines
I/O riser 0 must be installed.
•
•
The standard I/O module is always installed in riser 0-slot 1.
•
Install high-powered modules in slots with one inch module pitch (all slots
Additional PCI boxes and storage devices are housed in an expander
cabinet. The same cabinet is used to expand GS160/320 systems and
GS80 systems. Figure 3–12 shows five different PCI and BA356 storage
configurations.
Figure 3–12 BA356 Storage Device Configurations
BA356 (1)
BA356 (1)
BA356 (2)
BA356 (2)
BA356 (3)
BA356 (3)
BA356 (4)
BA356 (4)
BA356 (5)
BA54A PCI (1)
BA356 (6)
BA54A PCI (2)
BA356 (7)
Default
BA356 (8)
Configuration
BA356 (1)
BA356 (2)
BA356 (3)
BA356 (4)
BA356 (5)
BA54A PCI (1)BA54A PCI (2)
BA356 (1)
BA356 (2)
BA356 (3)
BA356 (4)
BA54A PCI (1)
Configuration
Default
BA356 (1)
BA356 (2)
BA54A PCI (3)
BA54A PCI (1)
BA54A PCI (2)
BA356 (1)
BA54A PCI (4)
BA54A PCI (3)
BA54A PCI (1)
BA54A PCI (2)
3-22 AlphaServer GS80/160/320 User’s Guide
PK-0646-99
Chapter 4
GS80 Rack System Overview
In the rack system, the BA52A system drawer has a QBB containing a
backplane, CPU modules, memory modules, power modules, and I/O riser
modules.
This chapter provides an overview of the BA52A drawer in these sections:
•
Rack System Characteristics
System Drawer Architecture
•
•
System Drawer Modules
GS80 Rack System Overview 4-1
4.1 Rack System Characteristics
Table 4–1 lists system drawer characteristics. Table 4–2 lists power and
environmental specifications for the rack system.
Figure 4–1 System Drawer
PK-0633-99
Table 4–1 System Drawer Characteristics
CharacteristicSpecification
Size
Weight45 kg (100 lb) maximum
Maximum heat dissipation1500 w (4910 Btu/hr)
4-2 AlphaServer GS80/160/320 User’s Guide
40 cm H x 45 cm W x 65 cm D (15 in. x 18 in. x
25 in.)
Table 4–2 Rack System Characteristics
Electrical
Voltage120 VAC (U.S.)
220–240 VAC (Europe)
200–240 VAC (Japan)
PhaseSingle
Frequency50–60 Hz
Maximum input
current/circuit
Maximum power
consumption
Environmental
Temperature
HumidityOperating: 10% to 90%
AltitudeOperating: 0 to 3 km (0 to 10,000 ft)
16 A (U.S.)
12 A (Europe)
13 A (Japan)
2.4 – 2.8 KVA (U.S.)
5.2 – 5.7 KVA (Europe)
4.8 – 5.7 KVA (Japan)
Operating: 5° to 35°C (41 to 95°F)
Not operating: -40° to 66°C (-40° to 150°F)
Not operating: 10% to 95%
Not operating: 0 to 12.2 km (0 to 40,000 ft)
GS80 Rack System Overview 4-3
4.2 System Drawer Architecture
The system drawer houses a QBB consisting of a backplane that
supports four CPU modules, four memory modules, two power modules
and two I/O riser modules. These modules are identical to those used in
the box systems. The global port is part of the backplane. In a twodrawer system, the drawers are linked by a distribution board.
Figure 4–2 Two-Drawer Block Diagram
System Drawer 1
PCI Box
PCI Box
PCI Box
PCI Box
CPU
I/OGP
MEM
CPUCPUCPU
Switch
MEMMEMMEM
System Drawer 2
CPU
I/OGP
MEM
CPUCPUCPU
Switch
MEMMEMMEM
Distribution
Board
PK-0630-99
4-4 AlphaServer GS80/160/320 User’s Guide
The switch that interconnects the CPU modules, memory modules, and I/O riser
modules is built into the system drawer backplane.
In a two-drawer system, the system drawers are linked together through the
global ports and the distribution board. A directory module is required in each
system drawer in a two-drawer system.
GS80 Rack System Overview 4-5
4.3 System Drawer Modules
The modules plug into the system drawer backplane. Figure 4–3 shows
a fully populated backplane. Figure 4–4 shows the backplane with no
modules.
Figure 4–3 System Drawer Modules
3
2
1
2
1
4
4
1
2
1
2
5
7
6
PK0619
4-6 AlphaServer GS80/160/320 User’s Guide
The CPU, memory, power, and I/O riser modules plug into the backplane
located at the bottom of the system drawer. Callouts in Figure 4–3 point to the
location of the following system drawer modules:
➊
CPU module
➋
Memory module
➌
Directory module
➍Power modules
➎Power system manager (PSM) module
➏I/O riser modules
➐
Clock splitter module
Figure 4–4 System Drawer Backplane
3
2
1
2
1
4
1
2
1
2
5
7
6
PK-0632-99
GS80 Rack System Overview 4-7
Chapter 5
GS80 Rack System Configuration Rules
This chapter provides configuration rules for the following:
•
Rack
•
Rack Power System
GS80 Rack System Configuration Rules 5-1
5.1 Rack
A rack houses a maximum of two system drawers.
Figure 5–1 Rack
COMPAQ
AlphaServer GS80
Companion Printer
LA75
digital
PK-0635-99
5-2 AlphaServer GS80/160/320 User’s Guide
About the Rack Cabinet
The cabinet contains the following components:
One or two system drawers
•
Control panel (see Section 2.6 for details on the control panel)
•
•
AC input box
•
Power subrack with power supplies
Vertical mounting rails
•
•
Stabilizer
•
Wrist strap for static discharge protection
Rack Variants
The H9A20 RETMA cabinet has three variants:
• H9A20-CA, North American (120V)
•
H9A20-CB, European (220–240V)
•
H9A20-CC, North American and Japanese (200–240V)
GS80 Rack System Configuration Rules 5-3
5.2 Rack Power System
Figure 5–2 shows a two-drawer rack power system: two AC input boxes
and two H7504 power subracks at the bottom of the cabinet. Each
subrack holds three power supplies. The system drawer power cables
connect to the power subrack.
Figure 5–2 Two-Drawer Rack Power System
Power Supply Positions
123
Drawer 2
R
Power Subrack 2
H7504 (2)
R
Power Subrack 1
Redundant Power
R
Supply Location
5-4 AlphaServer GS80/160/320 User’s Guide
H7504 (1)
AC Input Box 2
AC Input Box 1
Drawer 1
PK-0638-99
About the Power System
Each system drawer requires one power subrack.
•
•
Each system drawer requires two power supplies.
•
Each power subrack holds up to three power supplies. The third power
supply is used for redundancy.
GS80 Rack System Configuration Rules 5-5
Chapter 6
Booting and Installing an
Operating System
This chapter provides basic operating instructions, including powering up the
system and booting the operating system.
Sections in this chapter are:
Powering Up the System
•
•
Setting Boot Options
Booting Tru64 UNIX
•
•
Installing Tru64 UNIX
•
Booting OpenVMS
•
Installing OpenVMS
Booting and Installing an Operating System 6-1
6.1 Powering Up the System
To power up the system, set the keyswitch to On, or power up the
system remotely. The SCM power-up display is shown at the system
management console and the control panel, followed by the SRM
power-up display.
6.1.1 SCM Power-Up Display
Example 6–1 SCM Power-Up Display
SCM_E0> power on➊
Powering on PCI Box 0
Powering on PCI Box 1
QBB-0 Powering ON
~I~ Testing OCP Switch passed
Power ON Phase INIT➌
QBB-1 Powering ON
QBB-2 Powering ON
QBB-3 Powering ON
➋Messages denoted by ~I~ are informational and do not indicate a serious
event. Other types of messages include:
*** – Diagnostic format indicating an error has occurred.
### – Diagnostic format indicating a warning.
~E~ – An error has occurred; power-up continues, but the affected resource
is dropped.
~W~ – An error has occurred; power-up continues, and the affected
resource is questionable.
➌
During the Phase INIT (initialization phase) SROM code is loaded into
each CPU in the system and communication between the power system
manager (PSM) and the CPU is established. Phase 0 follows with local
QBB testing.
~I~ QbbConf(gp/io/c/m)=fbbfffff Assign=ff SQbb0=00 PQbb=00 SoftQbbId=fedcba98
~I~ SysConfig: 37 13 07 19 07 12 c7 13 37 13 f7 11 f7 13 37 13
SCM_E0>
QBB1 now Testing Step-6
QBB1 now Testing Step-7
QBB1 now Testing Step-8
QBB1 now Testing Step-9
QBB1 now Testing Step-A
QBB2 now Testing Step-6
QBB2 now Testing Step-7
QBB3 now Testing Step-6
QBB3 now Testing Step-7
QBB3 now Testing Step-8
QBB3 now Testing Step-9
QBB3 now Testing Step-A.
QBB0 now Testing Step-6
QBB1 Step(s)-A B Tested
QBB2 Step(s)-7 8 9 A B Tested
QBB3 Step(s)-A B Tested.
QBB0 now Testing Step-7.
QBB0 now Testing Step-8..
QBB0 now Testing Step-9...
QBB0 now Testing Step-A..
QBB0 now Testing Step-7.
QBB0 now Testing Step-8...
QBB0 now Testing Step-9..
QBB0 now Testing Step-A..
QBB0 now Testing Step-7.
QBB0 now Testing Step-8...
QBB0 now Testing Step-9...
QBB0 now Testing Step-A..
QBB0 now Testing Step-B..
QBB0 unloading console across port0 from PCI Box-1
Console COM1 from master PCI Box-0
~I~ SysConfig: 37 13 07 19 07 12 c7 13 37 13 f7 11 f7 13 37 13
Retrieving FRU information for Shared RAM...
SCM_E0>
QBB0 now Testing Step-E..
Power On Complete
Returning to system COM1 port
➍
Phase 1. The primary CPU, selected by the SCM in phase 0, tests each
➐
➑
QBB in the system.
➎
Phase 2. Secondary CPUs are tested to ensure cache coherency.
➏Phase 3. The tests ensure that each CPU can access each memory array in
the system.
➐
Phase 4. The primary CPU unloads the PAL/console code from the flash
ROM on the standard I/O module into memory.
➑Control of the remainder of power-up is passed to the console firmware.
See Section 6.1.2.
Booting and Installing an Operating System 6-5
6.1.2 SRM Power-Up Display
Following the initial SCM power-up and the five test phases, the SRM
console takes control of the remaining portion of system power-up.
Example 6–2 SRM Power-Up Display
System Primary QBB0 : 0
System Primary CPU : 0 on QBB0
Par hrd/sft CPU Mem IOR3 IOR2 IOR1 IOR0 GP QBB Dir PS Temp
QBB# 3210 3210 (pci_box.rio) Mod BP Mod 321 (:C)
(-) 0/30 ---P PP --.- --.- Px.x P1.0 P P P PPP 26.5
(-) 1/31 -P-P PP --.- --.- --.- --.- P P P PPP 29.0
(-) 2/32 --P- --P- --.- --.- --.- --.- P P P PP- 25.0
(-) 3/33 ---P -P-- --.- --.- Px.x P0.0 P P P PP- 27.0
system = QBB 0 1 2 3 + HS➌
QBB 0 = CPU 0 + Mem 0 1 + Dir + IOP + PCA 0 + GP (Hard QBB 0)
QBB 1 = CPU 0 2 + Mem 0 1 + Dir + IOP + PCA + GP (Hard QBB 1)
QBB 2 = CPU 1 + Mem 1 + Dir + IOP + PCA + GP (Hard QBB 2)
QBB 3 = CPU 0 + Mem 2 + Dir + IOP + PCA 0 + GP (Hard QBB 3)
shared RAM version is 1.3
hose 24 has a standard I/O module
starting console on CPU 0
initialized idle PCB
initializing semaphores
initializing heap
initial heap 2c0c0
memory low limit = 1f2000
heap = 2c0c0, 1ffc0
initializing driver structures
initializing idle process PID
initializing file system
initializing timer data structures
lowering IPL
➊
➋
6-6 AlphaServer GS80/160/320 User’s Guide
➊
A snapshot of the system environment is displayed. See Section 8.7.3 for
more information.
➋
PALcode is loaded and started.
➌The size of the system is determined and mapped. This system has four
QBBs and five CPUs.
Continued on next page
Booting and Installing an Operating System 6-7
Example 6–2 SRM Power-Up Display (Continued)
CPU 0 speed is 731 MHz
create dead_eater
create poll
create timer
create powerup
access NVRAM
QBB 0 memory, 1 GB
QBB 1 memory, 1 GB
QBB 2 memory, 512 MB
QBB 3 memory, 512 MB
total memory, 3 GB
copying PALcode to 103ffe8000
copying PALcode to 201ffe8000
copying PALcode to 301ffe8000
probe I/O subsystem
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1
bus 1, slot 0 -- dva—Floppy
bus 0, slot 1 -- pka—QLogic ISP10x0
bus 0, slot 2 -- vga—ELSA GLoria Synergy
bus 0, slot 3 -- pkb—QLogic ISP10x0
bus 0, slot 15 -- dqa—Acer Labs M1543C IDE
bus 0, slot 15 -- dqb—Acer Labs M1543C IDE
probing hose 1, PCI
bus 0, slot 5 -- ewa—DE500-BA Network Controller
probing hose 24, PCI
probing PCI-to-ISA bridge, bus 1
bus 1, slot 0 -- dvb—Floppy
bus 0, slot 1 -- pkc—QLogic ISP10x0
bus 0, slot 15 -- dqc—Acer Labs M1543C IDE
bus 0, slot 15 -- dqd—Acer Labs M1543C IDE
probing hose 25, PCI
starting drivers
*** keyboard not plugged in...
entering idle loop
initializing keyboard
*** keyboard not plugged in...
starting console on CPU 4
initialized idle PCB
initializing idle process PID
lowering IPL
CPU 4 speed is 731 MHz
create powerup
starting console on CPU 6
initialized idle PCB
initializing idle process PID
lowering IPL
CPU 6 speed is 731 MHz
create powerup
starting console on CPU 9
initialized idle PCB
initializing idle process PID
lowering IPL
➍
➎
➏
6-8 AlphaServer GS80/160/320 User’s Guide
Continued on next page
Example 6–2 SRM Power-Up Display (Continued)
CPU 9 speed is 731 MHz
create powerup
starting console on CPU 12
initialized idle PCB
initializing idle process PID
lowering IPL
CPU 12 speed is 731 MHz
create powerup
initializing pka pkb pkc ewa dqa dqb dqc dqd
initializing GCT/FRU at 1f2000
AlphaServer Console X5.7-6290, built on Feb 4 2000 at 01:41:06
P00>>>
➍
Distributed memory is sized and mapped.
➎
The I/O subsystem is mapped.
➏
Each secondary CPU starts the console, is initialized and ready to join the
multiprocessor environment.
➐
The SRM console prompt is displayed.
➐
Booting and Installing an Operating System 6-9
6.2 Setting Boot Options
v
X
from a RIS server.
You can set a default boot device, boot flags, and network boot
protocols for Tru64 UNIX or OpenVMS using the SRM set command
with environment variables. Once these environment variables are set,
the boot command defaults to the stored values. You can override the
stored values for the current boot session by entering parameters on
the boot command line.
The SRM boot-related environment variables are listed below and described in
the following sections:
bootdef_dev
boot_file
boot_osflags
ei*0_inet_init or
ew*0_inet_init
ei*0_protocols or
ew*0_protocols
Defines a default boot device.
Specifies a default file name to be used for booting when
no file name is specified by the boot command.
Defines parameters to enable specific functions during the
boot process.
Determines whether the interface’s internal Internet
database is initialized from nvram or from a network
server (through the bootp protocol). Set this environment
ariable if you are booting Tru64 UNI
Defines a default network boot protocol (bootp or mop).
6.2.1 Bootdef_dev
The bootdef_dev environment variable specifies one or more devices
from which to boot the operating system. When more than one device is
specified, the system searches in the order listed and boots from the
first device.
Enter the show bootdef_dev command to display the current default boot
device. Enter the show device command for a list of all devices in the system.
6-10 AlphaServer GS80/160/320 User’s Guide
The syntax is:
set bootdef_dev boot_device
boot_device
Example
In this example, two boot devices are specified. The system will try booting
from dkb0 and, if unsuccessful, will boot from dka0.
P00>>> set bootdef_dev dkb0, dka0
NOTE: When you set the bootdef_dev environment variable, it is recommend-
The name of the device on which the system software has
been loaded. To specify more than one device, separate the
names with commas.
ed that you set the operating system boot parameters as well, using the
set boot_osflags command.
6.2.2 Boot_file
The boot_file environment variable specifies the default file name to be
used for booting when no file name is specified by the boot command.
The syntax is:
set boot_filefilename
Example
In this example, a boot file is specified for booting OpenVMS from the
InfoServer. APB_0712 is the file name of the APB program used for the
initial system load (ISL) boot program.
P00>>> set boot_file apb_0712
Booting and Installing an Operating System 6-11
6.2.3 Boot_osflags
The boot_osflags environment variable sets the default boot flags and,
for OpenVMS, a root number.
Boot flags contain information used by the operating system to determine some
aspects of a system bootstrap. Under normal circumstances, you can use the
default boot flag settings.
To change the boot flags for the current boot only, use the flags_value argument
with the boot command.
The syntax is:
set boot_osflagsflags_value
The flags_value argument is specific to the operating system.
Tru64 UNIX Systems
Tru64 UNIX systems take a single ASCII character as the flags_value
argument.
Load operating system software from the specified boot device
a
(autoboot). Boot to multiuser mode.
Prompt for the name of a file to load and other options (boot
i
interactively). Boot to single-user mode.
Stop in single-user mode. Boots /vmunix to single-user mode and stops
s
at the # (root) prompt.
D Full dump; implies “s” as well. By default, if Tru64 UNIX crashes, it
completes a partial memory dump. Specifying “D” forces a full dump at
system crash.
6-12 AlphaServer GS80/160/320 User’s Guide
OpenVMS Systems
OpenVMS systems require an ordered pair as the flags_value argument:
root_number and boot_flags.
root_numberDirectory number of the system disk on which OpenVMS files
are located. For example:
boot_flags
root_number
0 (default)[SYS0.SYSEXE]
1[SYS1.SYSEXE]
2[SYS2.SYSEXE]
3[SYS3.SYSEXE]
The hexadecimal value of the bit number or numbers set. To
specify multiple boot flags, add the flag values (logical OR).
For example, the flag value 10080 executes both the 80 and
10000 flag settings. See Table 6–1.
Root Directory
Table 6–1 OpenVMS Boot Flag Settings
Flags_ValueBit NumberMeaning
10Bootstrap conversationally (enables you to
modify SYSGEN parameters in SYSBOOT).
21Map XDELTA to a running system.
42Stop at initial system breakpoint.
83Perform diagnostic bootstrap.
104Stop at the bootstrap breakpoints.
205Omit header from secondary bootstrap image.
807Prompt for the name of the secondary bootstrap
file.
1008Halt before secondary bootstrap.
1000016Display debug messages during booting.
2000017Display user messages during booting.
Continued on next page
Booting and Installing an Operating System 6-13
Example
In the following Tru64 UNIX example, the boot flags are set to autoboot the
system to multiuser mode when you enter the boot command.
P00>>> set boot_osflags a
In the following OpenVMS example, root_number is set to 2 and boot_flags is set
to 1. With this setting, the system will boot from root directory SYS2.SYSEXE
to the SYSBOOT prompt when you enter the boot command.
P00>>> set boot_osflags 2,1
In the following OpenVMS example, root_number is set to 0 and boot_flags is
set to 80. With this setting, you are prompted for the name of the secondary
bootstrap file when you enter the boot command.
P00>>> set boot_osflags 0,80
6.2.4 ei*0_inet_init or ew*0_inet_init
The ei*0_inet_init or ew*0_inet_init environment variable determines
whether the interface’s internal Internet database is initialized from
nvram or from a network server (through the bootp protocol).
Legal values are nvram and bootp. The default value is bootp. Set this
environment variable if you are booting Tru64 UNIX from a RIS server.
To list the network devices on your system, enter the show device command.
The Ethernet controllers start with the letters “ei” or “ew,” for example, ewa0.
The third letter is the adapter ID for the specific Ethernet controller. Replace
the asterisk (*) with the adapter ID letter when entering the command.
The syntax is:
set ei*0_inet_init value or
set ew*0_inet_init value
Example
P00>>> set eia0_inet_init bootp
6-14 AlphaServer GS80/160/320 User’s Guide
6.2.5 ei*0_protocols or ew*0_protocols
The ei*0_protocols or ew*0_protocols environment variable sets
network protocols for booting and other functions.
To list the network devices on your system, enter the show device command.
The Ethernet controllers start with the letters “ei” or “ew,” for example, eia0.
The third letter is the adapter ID for the specific Ethernet controller. Replace
the asterisk (*) with the adapter ID letter when entering the command.
The syntax is:
set ei*0_protocols protocol_value or
set ew*0_protocols protocol_value
The options for protocol_value are:
mop (default)Sets the network protocol to mop (Maintenance Operations
Protocol), the setting typically used with the OpenVMS
operating system.
bootp
bootp,mopWhen both are listed, the system attempts to use the mop
Example
P00>>> show device
.
.
.
eia0.0.0.1001.0 EIA0 08-00-2B-3E-BC-B5
eib0.0.0.12.0 EIB0 00-00-C0-33-E0-0D
eic0.0.0.13.0 EIC0 08-00-2B-E6-4B-F3
.
.
.
P00>>> set eia0_protocols bootp
P00>>> show eia0_protocols
eia0_protocols bootp
Sets the network protocol to bootp, the setting typically used
with the Tru64 UNIX operating system.
protocol first, regardless of which is listed first. If not
successful, it then attempts the bootp protocol.
Booting and Installing an Operating System 6-15
6.3 Booting Tru64 UNIX
Tru64 UNIX can be booted from a DVD or CD-ROM on a local drive,
from a local SCSI disk, or from a server.
Example 6–3 Booting Tru64 UNIX from a Local SCSI Disk
block 0 of dka0.0.0.1.0 is a valid boot block
reading 13 blocks from dka0.0.0.1.0
bootstrap code read in
base = 2e6000, image_start = 0, image_bytes = 1a00
initializing HWRPB at 2000
initializing page table at 17fbda000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Tru64 UNIX boot - Wed Sep 8 20:59:58 EDT 1999
Loading vmunix ...
Loading at 0xfffffc0000430000
Sizes:
text = 4800560
data = 903872
bss = 1412480
Starting at 0xfffffc00007790d0
Loading vmunix symbol table ... [1330800 bytes]
Alpha boot: available memory from 0x93de000 to 0x3180000000
Digital Tru64 UNIX V4.0G-1 (Rev. 1398); Thu Oct 21 13:34:00 EDT 1999
physical memory = 24572.00 megabytes.
available memory = 24140.65 megabytes.
using 94344 buffers containing 737.06 megabytes of memory
Master cpu at slot 0.
➋
6-16 AlphaServer GS80/160/320 User’s Guide
Example 6–3 Booting Tru64 UNIX from a Local SCSI Disk (Continued)
Firmware revision: 5.6-6930
PALcode: Digital Tru64 UNIX version 1.60-1
Compaq AlphaServer GS320 6/731
.
.
.
Digital Tru64 UNIX Version V4.0
login:
Example 6–3 shows a boot from a local SCSI drive. The example is abbreviated.
For complete instructions on booting Tru64 UNIX, see the Tru64 UNIXInstallation Guide.
Perform the following tasks to boot a system:
Power up the system. The system stops at the SRM console prompt,
1.
P00>>>.
Set boot environment variables, if desired. See Section 6.2.
2.
Install the boot medium. For a network boot, see Section 6.3.1.
3.
4.
Enter the show device command ➊ to determine the unit number of the
drive for your device.
Enter the boot command ➋ and command-line parameters (if you have not
5.
set the associated environment variables). In Example 6–3, boot device and
boot flags
➌ have already been set.
Booting and Installing an Operating System 6-17
6.3.1 Booting Tru64 UNIX Over the Network
To boot the system over the network, make sure the system is
registered on a Remote Installation Services (RIS) server. See the
Tru64 UNIX document entitled Sharing Software on a Local Area
Network for registration information.
Example 6–4 RIS Boot
P00>>> show device➊
dka0.0.0.1.1 DKA0 RZ2DD-LS 0306
dka100.1.0.1.1 DKA100 RZ2DD-LS 0306
dka200.2.0.1.1 DKA200 RZ1CB-CS 0844
dkb0.0.0.3.1 DKB0 RZ25 0900
dqa0.0.0.15.0 DQA0 TOSHIBA CD-ROM XM-6302B 1012
dva0.0.0.1000.0 DVA0
eia0.0.0.4.1 EIA0 00-00-F8-09-90-FF
eib0.0.0.2002.1 EIB0 00-06-2B-00-25-5B
pka0.7.0.1.1 PKA0 SCSI Bus ID 7
pkb0.7.0.3.1 PKB0 SCSI Bus ID 7
P00>>> set eia0_protocols bootp
P00>>> set eia0_inet_init bootp➌
P00>>> boot eia0➍
.
➋
6-18 AlphaServer GS80/160/320 User’s Guide
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.