Contents

iii

Chapter 3 GS160/320 System Configuration Rules

Chapter 4 GS80 Rack System Overview

Chapter 5 GS80 Rack System Configuration Rules

Chapter 6 Booting and Installing an Operating System

iv

v

Glossary

Index

Examples

Figures

vi

Tables

vii

viii

Preface

Intended Audience

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.

???Chapter 7, Operation, gives basic operating instructions.

???Chapter 8, Using the System Control Manager, describes the function and operation of the system control manager.

ix

???Appendix A, Jumpering Information, calls out jumpers and their functions.

Documentation Titles

Table 1 AlphaServer 80/160/320 Family Documentation

Information on the Internet

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 Compaq AlphaServer 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.1AlphaServer 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

PK-0654-00

1-2 AlphaServer GS80/160/320 User???s Guide

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.2Firmware 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.3System 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

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.1System 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

2-2 AlphaServer GS80/160/320 User???s Guide

Table 2???2 Power Cabinet and System Environmental Characteristics

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.2System 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)

2-4 AlphaServer GS80/160/320 User???s Guide

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)

Modem

System Box

GS160/320 System Overview 2-5

2.3Quad 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)

2-6 AlphaServer GS80/160/320 User???s Guide

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

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.2CPU Module

A CPU module comes with an Alpha microprocessor chip with a B- cache, cache control and TAG comparison logic, clock logic, and a DC- DC 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

Power

Run LED

Hot Swap

LED

PK0602

2-10 AlphaServer GS80/160/320 User???s Guide

2.3.3Memory 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.4Directory 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

PK0606

2-12 AlphaServer GS80/160/320 User???s Guide

2.3.5Power 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.6Power 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 micro- processor (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 I2C bus interfaces and a serial I/O bus channel to each CPU in the QBB. The PSM module retrieves information from the I2C EEROMs residing on the CPUs, memory modules, and the QBB 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.7Clock 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.8I/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

PK0605

2-16 AlphaServer GS80/160/320 User???s Guide

2.3.9Global 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

PK1244

2-18 AlphaServer GS80/160/320 User???s Guide

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

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

System

Box 1

PK0626

2-20 AlphaServer GS80/160/320 User???s Guide

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.4Power 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

PK0615A

2-22 AlphaServer GS80/160/320 User???s Guide

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.1AC 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-7 J-9 J-16 J-18

J-1 J-2 J-3 J-8 J-10 J-15 J-17

Cabinet

Front

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

GS160/320 System Overview 2-25

2.5PCI I/O

The power cabinet contains at least one PCI master box, and may contain PCI expansion boxes.

Figure 2???19 PCI Master Box

2-26 AlphaServer GS80/160/320 User???s Guide

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.6Control 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

8 9 10

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.1Control Panel LEDs

Figure 2???21 shows the various control panel LED status indications.

Figure 2???21 Control Panel LED Status

OK

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

On

Off

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.1GS160 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

3-2 AlphaServer GS80/160/320 User???s Guide

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.2GS320 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.

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.3Power 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.

PK0615A

3-6 AlphaServer GS80/160/320 User???s Guide

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.1Power Supply Slot Assignments

Figure 3???4 show the power supply slot assignments in each power subrack.

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

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)

GS160/320 System Configuration Rules 3-11

3.5QBB 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 color- coded to ensure the correct placement of each module.

Figure 3???7 QBB Center Bar Color Code (Cabinet Front)

PK0628

3-12 AlphaServer GS80/160/320 User???s Guide

Figure 3???8 QBB Center Bar Color Code (Cabinet Rear)

PK2229

GS160/320 System Configuration Rules 3-13

3.6Memory 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.

Figure 3???9 Memory Module and Directory Module

PK-0651-99

3-14 AlphaServer GS80/160/320 User???s Guide

Memory Configuration Guidelines

???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.

GS160/320 System Configuration Rules 3-15

3.7Memory Interleaving Guidelines

Table 3???1 Interleaving Memory Modules

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.8PCI 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

QBB0

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.9PCI 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

PK-0643-99

3-20 AlphaServer GS80/160/320 User???s Guide

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 except riser 0-slot 5, riser 0-slot 6, riser 1-slot 5, and riser 1-slot 6).

???Install high-performance adapters across multiple bus/hose segments to get maximum performance.

???VGA graphics options must be installed in riser 0-slot 2 or riser 0-slot 3.

CAUTION: Installing a full-length module next to the standard I/O module requires extra care due to cabling on the standard I/O module.

Logical Hoses

You can have a maximum of four logical hoses per PCI box. Logical hose numbers are assigned by the firmware. Logical hoses are numbered from 0 to 63.

Table 3???2 PCI Slots and Logical Hoses

GS160/320 System Configuration Rules 3-21

3.10 Expander Cabinet

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

3-22 AlphaServer GS80/160/320 User???s Guide

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.1Rack 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

4-2 AlphaServer GS80/160/320 User???s Guide

Table 4???2 Rack System Characteristics

GS80 Rack System Overview 4-3

4.2System 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 two- drawer system, the drawers are linked by a distribution board.

Figure 4???2 Two-Drawer Block Diagram

PCI Box

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.3System 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

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

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.1Rack

A rack houses a maximum of two system drawers.

Figure 5???1 Rack

COMPAQ

AlphaServer GS80

LA75 Companion Printer

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.2Rack 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

1 2 3

Drawer 2

PK-0638-99

5-4 AlphaServer GS80/160/320 User???s Guide

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.1Powering 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.1SCM Power-Up Display

Example 6???1 SCM Power-Up Display

QBB-0 Powering ON

~I~ QbbConf(gp/io/c/m)=fbbfffff Assign=ff SQbb0=00 PQbb=00 SoftQbbId=fedcba98

.............................................................................

.........................................................................

SCM_E0> ......................................

6-2 AlphaServer GS80/160/320 User???s Guide

~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.

Continued on next page

Booting and Installing an Operating System 6-3

Example 6???1 SCM Power-Up Display (Continued)

6-4 AlphaServer GS80/160/320 User???s Guide

Example 6???1 SCM Power-Up Display (Continued)

???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.2SRM 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

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)

Continued on next page

6-8 AlphaServer GS80/160/320 User???s Guide

Example 6???2 SRM Power-Up Display (Continued)

CPU 9 speed is 731 MHz create powerup

starting console on CPU 12 initialized idle PCB

???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.2Setting Boot Options

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:

6.2.1Bootdef_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 The name of the device on which the system software has been loaded. To specify more than one device, separate the names with commas.

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- ed that you set the operating system boot parameters as well, using the set boot_osflags command.

6.2.2Boot_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_file filename

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.3Boot_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_osflags flags_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.

aLoad operating system software from the specified boot device (autoboot). Boot to multiuser mode.

iPrompt for the name of a file to load and other options (boot interactively). Boot to single-user mode.

sStop in single-user mode. Boots /vmunix to single-user mode and stops at the # (root) prompt.

DFull 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_number Directory number of the system disk on which OpenVMS files are located. For example:

boot_flags 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.

Table 6???1 OpenVMS Boot Flag Settings

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.4ei*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.5ei*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:

Booting and Installing an Operating System 6-15

6.3Booting 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 UNIX Installation Guide.

Perform the following tasks to boot a system:

1.Power up the system. The system stops at the SRM console prompt, P00>>>.

2.Set boot environment variables, if desired. See Section 6.2.

3.Install the boot medium. For a network boot, see Section 6.3.1.

4.Enter the show device command ??? to determine the unit number of the drive for your device.

5.Enter the boot command ??? and command-line parameters (if you have not 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.1Booting 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

.

6-18 AlphaServer GS80/160/320 User???s Guide

Systems running Tru64 UNIX support network adapters, designated ew*0 or ei*0. The asterisk stands for the adapter ID (a, b, c, and so on).

1.Power up the system. The system stops at the SRM console prompt, P00>>>.

2.Set boot environment variables, if desired. See Section 6.2.

3.Enter the show device command ??? to determine the unit number of the drive for your device.

4.Enter the following commands. Example 6???4 assumes you are booting from eia0. If you are booting from another drive, enter that device name instead.

P00>>> set eia0_protocols bootp P00>>> set eia0_inet_init bootp

The first command ??? enables the bootp network protocol for booting over the Ethernet controller. The second command ??? sets the internal Internet database to initialize from the network server through the bootp protocol.

5.Enter the boot command ??? and command-line parameters (if you have not set the associated environment variables). In Example 6???4 the boot command sets the system to boot automatically from eia0.

For complete instructions on booting Tru64 UNIX over the network, see the

Tru64 UNIX Installation Guide.

Booting and Installing an Operating System 6-19

6.4Installing Tru64 UNIX

Tru64 UNIX is installed from the DVD/CD-ROM drive connected to the system.

Example 6???5 Tru64 UNIX Installation Display

Initializing system for Tru64 UNIX installation. Please

wait...

*** Performing CDROM Installation

Loading installation process and scanning system hardware.

This procedure installs Tru64 UNIX onto your system. You will be asked a series of system configuration questions. Until you answer all questions, your system is not changed in any way.

During the question and answer session, you can go back to any previous question and change your answer by entering: history You can get more information about a question by entering: help

6-20 AlphaServer GS80/160/320 User???s Guide

There are two types of installations:

oThe Default Installation installs a mandatory set of software subsets on a predetermined file system layout.

oThe Custom Installation installs a mandatory set of software subsets plus optional software subsets that you select. You can customize the file system layout.

The Tru64 UNIX Shell option puts your system in single-user mode with superuser privileges. This option is provided for experienced Tru64 UNIX system administrators who want to perform file system or disk maintenance tasks before the installation.

The Installation Guide contains more information about installing Tru64 UNIX.

1)Default Installation

2)Custom Installation

3)Tru64 UNIX Shell

Enter your choice:

??? Boot the operating system from the DVD/CD-ROM drive connected to the system.

??? Follow the Tru64 UNIX installation procedure displayed after the installation process is loaded.

???If your system console is a VGA monitor, the X Server is started and an Installation Setup window is displayed. Click on the fields in the Installation Setup window to enter your responses to the installation procedure.

???If your system console is a serial terminal, a text-based installation procedure is displayed, as shown in Example 6???5. Enter the choices appropriate for your system.

See the Tru64 UNIX Installation Guide for complete installation instructions.

Booting and Installing an Operating System 6-21

6.5Booting OpenVMS

OpenVMS is booted from a local SCSI disk drive or from a DVD/CD- ROM drive on the InfoServer.

Example 6???6 Booting OpenVMS from a Local Disk

(boot dka0.0.0.1.0 -flags 0,0)

block 0 of dka0.0.0.1.0 is a valid boot block reading 924 blocks from dka0.0.0.1.0 bootstrap code read in

base = 2c4000, image_start = 0, image_bytes = 73800 initializing HWRPB at 2000

initializing page table at 2bfbc6000 initializing machine state

setting affinity to the primary CPU jumping to bootstrap code

OpenVMS (TM) Alpha Operating System, Version B7.2-1H1

6-22 AlphaServer GS80/160/320 User???s Guide

Example 6???6 shows a boot from a local disk. The example is abbreviated. For complete instructions on booting OpenVMS, see the OpenVMS installation document.

1.Power up the system. The system stops at the SRM console prompt, P00>>>.

2.Set boot environment variables, if desired. See Section 6.2.

3.Install the boot medium. For a network boot, see Section 6.2.4.

4.Enter the show device command ??? to determine the unit number of the drive for your device.

5.Enter the boot command and command-line parameters (if you have not set

the associated environment variables.). In Example 6???6, the boot command with the -flags option ??? causes the system to boot from [SYS0.EXE] on device DKA0.

Booting and Installing an Operating System 6-23

6.5.1Booting OpenVMS from the InfoServer

You can boot OpenVMS from a LAN device on the InfoServer. The devices are designated EI*0 or EW*0. The asterisk stands for the adapter ID (a, b, c, and so on).

Example 6???7 InfoServer Boot

base = 200000, image_start = 0, image_bytes = 70400 initializing HWRPB at 2000

initializing page table at 3ffee000 initializing machine state

setting affinity to the primary CPU jumping to bootstrap code

6-24 AlphaServer GS80/160/320 User???s Guide

1- Find Services

2- Enter known Service Name

Enter an Option ID value: 2

Enter a Known Service Name: ALPHA_V71-2_SSB

OpenVMS (TM) Alpha Operating System, Version V7.1-2

1.Power up the system. The system stops at the P00>>> console prompt.

2.Insert the operating system DVD/CD-ROM into the drive connected to the InfoServer.

3.Enter the show device command ??? to determine the unit number of the drive for your device.

4.Enter the boot command and any command-line parameters ???. In Example 6???7 the device is EIA0. APB_0712 is the file name of the APB program used for the initial system load (ISL) boot program.

The InfoServer ISL program displays a menu ???.

5.Respond to the menu prompts ???, using the selections shown in this example.

For complete instructions on booting OpenVMS from the InfoServer, see the OpenVMS installation document.

Booting and Installing an Operating System 6-25

6.6Installing OpenVMS

After you boot the operating system DVD or CD-ROM, an installation menu is displayed on the screen. Choose item 1 (Install or upgrade OpenVMS Alpha). Refer to the OpenVMS installation document for information on creating the system disk.

Example 6???8 OpenVMS Installation Menu

OpenVMS (TM) Alpha Operating System, Version V7.1-2??? Copyright ?? 1999 Digital Equipment Corporation. All rights reserved.

Installing required known files...

Configuring devices...

****************************************************************

You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM.

You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk.

Please choose one of the following:

1)Install or upgrade OpenVMS Alpha Version V7.1-2

2)Display products that this procedure can install

3)Install or upgrade layered products

4)Show installed products

5)Reconfigure installed products

6)Remove installed products

7)Execute DCL commands and procedures

8)Shut down this system

6-26 AlphaServer GS80/160/320 User???s Guide

???The OpenVMS operating system DVD/CD-ROM is booted.

???Choose option 1 (Install or upgrade OpenVMS Alpha). To create the system disk, see the OpenVMS installation document.

Booting and Installing an Operating System 6-27

Chapter 7

Operation

This chapter gives basic operating instructions. Sections include:

???SRM Console

???Displaying a Tru64 UNIX or OpenVMS Configuration

???Setting SRM Environment Variables

???Setting SRM Console Security

???Setting Automatic Booting

???Changing the Default Boot Device

???Soft Partitioning

???Hard Partitioning

Operation 7-1

7.1SRM Console

The SRM console is located in an EEROM on the standard I/O module. From the console interface, you set up and boot the operating system, display the system configuration, and perform other tasks. For complete information on the SRM console, see the AlphaServer GS80/160/320 Firmware Reference Manual.

7.1.1SRM Command Overview

Table 7???1 summarizes the most frequently used SRM console commands; Table 7???2 gives the command notation formats; and Table 7???3 shows special characters used on the command line.

Table 7???1 Summary of SRM Commands

7-2 AlphaServer GS80/160/320 User???s Guide

Table 7???1 Summary of SRM Commands (Continued)

Operation 7-3

Table 7???2 Notation Formats for SRM Console Commands

7-4 AlphaServer GS80/160/320 User???s Guide

Table 7???3 Special Characters for SRM Console

Operation 7-5

Table 7???3 Special Characters for SRM Console (Continued)

7.1.2Setting the Control Panel Message

When the operating system is running, the control panel displays the console revision. It is useful to create a customized message if you have a number of systems and you want to identify each system by a node name. Use the set ocp_text command.

Example 7???1 Set Ocp_Text Command

SCM_E0> set ocp_text nodenamealpha

power on......

.

.

SCM_EF> sho ocp Line0: nodenamealpha Line1: Power ON

Line2: Cpu-10 Mem-6 Pci-6

Line3: Keyswitch-ON

7-6 AlphaServer GS80/160/320 User???s Guide

7.2Displaying the System Configuration

View the system hardware configuration from the SRM console. It is useful to view the hardware configuration to ensure that the system recognizes all devices, memory configuration, and network connections.

Use the following SRM console commands to view the system configuration.

Additional commands to view the system configuration are described in the

AlphaServer GS80/160/320 Firmware Reference Manual.

show boot* Displays the boot environment variables.

show config Displays the logical configuration of interconnects and buses on the system and the devices found on them.

show device Displays the bootable devices and controllers in the system.

show fru Displays the physical configuration of FRUs (field-replaceable units).

show memory Displays configuration of main memory.

7.2.1Show Boot Command

Use the show boot* command to list the boot environment variables.

booted_dev booted_file booted_osflags

Operation 7-7

7.2.2Show Config Command

Use the show config command to display the entire logical configuration. Example 7???3 shows a GS80 system configuration.

Example 7???3 Show Config

7-8 AlphaServer GS80/160/320 User???s Guide

???Firmware. Version numbers of the SRM console, OpenVMS PALcode, and

Tru64 UNIX PALcode.

???QBB0. Components listed include the quad switch and the following modules: CPUs, memory modules, directory module, IOP module, and global port. Chip revision numbers are also listed. Component information for each QBB in the system is displayed.

???PCI I/O information, PCI Box 0. In this example, QBB0 is connected to PCI Box 0 and PCI box 3 (see ???).

QBB0 I/O port 0 is linked to remote I/O riser 0 located on the right side of PCI box 0. Logical hose numbers are 0 and 1.

QBB0 I/O port 1 is linked to remote I/O riser 1 located on the left side of PCI box 0. Logical hose numbers are 2 and 3.

???PCI I/O information, PCI Box 3. QBB0 is also connected to PCI box 3.

QBB0 I/O port 0 is linked to remote I/O riser 0 located on the right side of PCI box 3. Logical hose numbers are 4 and 5.

QBB0 I/O port 1 is linked to remote I/O riser 1 located on the left side of PCI box 3. Logical hose numbers are 6 and 7.

Continued on next page

Operation 7-9

Example 7???3 Show Config (Continued)

7-10 AlphaServer GS80/160/320 User???s Guide

???The total system memory size is reported.

QBB0 has 8 Gbytes in a 32-way interleave; QBB1 has 4 Gbytes in a 16-way interleave.

???Standard I/O modules in the system. In this example, PCI box 0, 1, and 3 each has a standard I/O module. The primary standard I/O module is located in PCI box 0. Hose and IOP connections are also listed.

???System memory shown by board, set, array, and size. See Section 3.7 for more information.

Continued on next page

Operation 7-11

Example 7???3 Show Config (Continued)

7-12 AlphaServer GS80/160/320 User???s Guide

Example 7???3 Show Config (Continued)

???PCI Box, Riser, Slot. Each PCI box in the system is identified by a number (0 to F hexadecimal). A system can have a maximum of 16 PCI boxes. The physical location of options in the PCI box are identifed by the remote I/O riser (0 or 1), and slot number in the PCI box.

???Option. Options are listed. Note that the standard I/O module occupies slot 1, on hose 0, riser 0, PCI box 0.

???Hose. PCI devices connect to logical hoses in the PCI box. A logical hose number identifies the logical hose for each device. The firmware assigns the logical hose number (0 to 63). Each PCI box has a maximum of four logical hose numbers.

???Bus. The remote I/O riser PCI bus will always be numbered 0. Buses behind device bridges are numbered 1, 2, 3, etc.

???Slot. This is the logical slot ID number of each device or controller.

???Function. On multi-function devices, the function ID is displayed.

???Name. Device names are listed.

???This next section of the show config output lists I/O devices by logical order. The logical Slot number for each option appears in the first column.

???The Option name appears next.

???Hose 0, Bus 0, PCI. In this example, the standard I/O module is logical Slot 1 on PCI Bus 0, Hose 0. See ??? for a different presentation of this information.

???The devices shown logically are the controllers and devices connected to the controllers. COMPAQ BB00921B91 and RRD46 are SCSI drives attached to controller pka0.

Continued on next page

Operation 7-13

Example 7???3 Show Config (Continued)

Continued on next page

7-14 AlphaServer GS80/160/320 User???s Guide

Example 7???3 Show Config (Continued)

???Looking back at the information presented under ??? helps the user locate the physical PCI slot of each device listed in the logical PCI device output. For example, to find where the DEC KZPSA, Hose 3, Bus 0, PCI device is located, see 3 in the Hose column ???, identify the option by name, and see that it is in PCI box 0, riser 1, slot 6.

???The console prompt is displayed.

Operation 7-15

7.2.3Show Device Command

Use the show device command to display the bootable devices. DK = SCSI drive; DQ = IDE drive; DV = diskette drive; EI or EW = Ethernet controller; PK = SCSI controller.

7-16 AlphaServer GS80/160/320 User???s Guide

Table 7???4 Device Naming Conventions

Operation 7-17

7.2.4Show Memory Command

The show memory command displays the main memory configuration.

P00>>>

7-18 AlphaServer GS80/160/320 User???s Guide

???The total system memory size is reported.

???Each memory board (or module) in the QBB is listed. Boards are numbered from 0 to 3. Each QBB can have up to four memory boards.

???Each memory board has two sets (arrays) of DIMMs installed. A set is numbered 0 or 1. Each set consists of four DIMMs.

???In this example, all DIMMs have the same density (4 GB) and are in a 32- way interleave. The first array on board 0 is board 0, set 0, and is referred to as array 0; the second array on board 0 is board 0, set 1, and is referred to as array 4, and so forth.

???The size, or density of the array.

???The starting address of the array.

???Identifies each QBB in the system.

???The total available memory in the QBB.

7.3Setting SRM Environment Variables

You may need to set several SRM console environment variables and built-in utilities to configure systems running the Tru64 UNIX or OpenVMS operating systems.

Set environment variables at the P00>>> prompt.

???To check the setting for a specific environment variable, enter the show envar command, where the name of the environment variable is substituted for envar.

???To reset an environment variable, use the set envar command, where the name of the environment variable is substituted for envar.

For more information on environment variables, see the AlphaServer GS80/160/320 Firmware Reference Manual.

Operation 7-19

7.4Setting SRM Console Security

You can set the SRM console to secure mode to prevent unauthorized personnel from modifying the system parameters or otherwise tampering with the system from the console.

When the SRM is set to secure mode, you can use only two console commands:

???The boot command, to boot the operating system

???The continue command, to resume running the operating system if you have inadvertently halted the system

The console security commands are as follows:

These commands put the console into secure mode.

Exits secure mode.

Turns off console security for the current session.

AlphaServer GS80/160/320 User???s Guide

7.4.1Setting Tru64 UNIX or OpenVMS Systems to Auto Start

The SRM auto_action environment variable determines the default action the system takes when the system is power cycled, reset, or experiences a failure.

On systems that are factory configured for Tru64 UNIX or OpenVMS, the factory setting for auto_action is halt. The halt setting causes the system to stop in the SRM console. You must then boot the operating system manually.

For maximum system availability, auto_action can be set to boot or restart.

???With the boot setting, the operating system boots automatically after the SRM init command is issued or the Reset button is pressed.

???With the restart setting, the operating system boots automatically after the SRM init command is issued or the Reset button is pressed, and it also reboots after an operating system crash.

To set the default action to boot, enter the following SRM commands:

P00>>> set auto_action boot

P00>>> init

7.5Changing the Default Boot Device

You can change the default boot device for Tru64 UNIX or OpenVMS with the set bootdef_dev command.

With the Tru64 UNIX or OpenVMS operating systems, you can designate a default boot device. You change the default boot device by using the set bootdef_dev SRM console command. For example, to set the boot device to the IDE CD-ROM, enter commands similar to the following:

P00>>> show bootdef_dev bootdef_dev dka400.4.0.1.1

P00>>> set bootdef_dev dqa500.5.0.1.1 P00>>> show bootdef_dev

bootdef_dev dqa500.5.0.1.1

Operation 7-21

7.6Soft Partitioning

Soft partitioning allows you to run multiple instances of an OpenVMS operating system on one hardware system. Soft partitions are created by setting environment variables that define the number of partitions, as well as the CPU modules, I/O risers, memory size, and size of shared memory. Also, one partition is assigned to receive error interrupts. See the OpenVMS Alpha Galaxy Guide and GS80/160/320 Firmware Reference Manual for more information.

About Soft Partitioning

???Only the OpenVMS operating system supports soft partitioning.

???Each partition is maintained by the system management console.

???Each soft partition must have at least one CPU module, one memory module, an I/O riser module, and a PCI box with a standard I/O module.

???Each soft partition requires a standard I/O module with resident SRM firmware in order to boot an operating system copy (or instance).

???Two I/O risers in a QBB cannot be split between partitions.

???CPU and memory resources can be shared across partitions; I/O is bound to a particular partition.

You define what resources are allocated to each partition by setting SRM environment variables. Table 7???5 lists the environment variables used to create soft partitions. After you have assigned the environment variable values, issue the lpinit command to initialize the partitions defined.

7-22 AlphaServer GS80/160/320 User???s Guide

Table 7???5 SRM Environment Variables for Soft Partitions

Operation 7-23

At the SRM console prompt, you set values for one environment variable to define the number of soft partitions in the system, one to set the memory mode, and two for each partition that define the CPU and I/O modules in each partition. The lpinit command completes the procedure.

Example 7???6 Defining Soft Partitions

7-24 AlphaServer GS80/160/320 User???s Guide

???The number of soft partitions is set to 3.

???The set lp_io_mask0 1 command defines QBB0 (and its I/O risers) as residing in partition 0.

???Set lp_cpu_mask0 f assigns CPUs 0???3 to partition 0. The set lp_mem_size0 6GB command assigns 6 GB of memory to partition 0.

???Set lp_ io_mask1 6 defines QBB1 and QBB2 (and its I/O risers) as residing in partition 1. The set lp_cpu_mask1 cf0 command assigns CPUs 4???7, 10, 11 to partition 1. The set lp_mem_size1 16GB command assigns 12 GB of memory to partition 1.

???The set lp_ io_mask2 8 defines QBB3 (and its I/O risers) as residing in partition 2. Set lp_cpu_mask1 f300 assigns CPUs 8, 9, 12-15 to partition 2. Set lp_mem_size1 10GB assigns 10 GB of memory to partition 2.

???The set lp_shared_mem_size 4GB command assigns 4 GB of memory to be shared by all partitions.

???Set lp_error_target 0 assigns partition 0 to receive and process the error interrupts.

???The lpinit command completes the procedure and partitions the system.

As a final result of the commands entered in Example 7???6, you will have the following soft partition setup:

Operation 7-25

7.7Hard Partitioning

Hard partitioning allows you to run multiple operating systems on one hardware system. Table 7???6 lists the SCM environment variables used to create hard partitions. After entering the SCM commands, set the control panel switch to Off and then to On to create the hard partitions.

Table 7???6 SCM Environment Variables for Hard Partitions

In Example 7???7, a GS160 system is hard partitioned into 2 partitions with:

???QBB 0 and QBB 1 in partition 0, and,

???QBB 2 and QBB 3 in partition 1

Example 7???7 Defining Hard Partitions

SCM_E0> set hp_count 2

SCM_E0> set hp_qbb_mask0 3

SCM_E0> set hp_qbb_mask1 c

7-26 AlphaServer GS80/160/320 User???s Guide

Partitioning a system is done at the QBB level: You can have a maximum of eight partitions. In hard partitioning mode:

???System partitions are independent.

???Each partition requires its own configuration tree.

???Hardware isolation is required.

???Address spaces are disjointed.

???Failures are isolated to a specific partition.

Operation 7-27

Chapter 8

Using the System Control Manager

The system control manager (SCM) communicates with microprocessors on the console serial bus (CSB) to monitor and manage the system. The SCM also provides remote server management functions.

This chapter explains the operation and use of the SCM. Sections are:

???Console Serial Bus Subsystem

???System Control Manager

???SCM COM1 Operating Mode

???Console Device Setup

???Entering the SCM

???SRM Environment Variables for COM1

???SCM Command-Line Interface

???Troubleshooting Tips

For more information on SCM commands, see the AlphaServer GS80/160/320 Firmware Reference Manual.

Using the System Control Manager 8-1

8.1Console Serial Bus Subsystem

The console serial bus (CSB) links microprocessors throughout the system, forming a monitoring and control subsystem managed by the system control manager (SCM). The SCM microprocessor is located on the standard I/O module in the master PCI box. Figure 8???1 shows a block diagram of the CSB, the microprocessors (or ???managers???), and the SCM. Also shown is a redundant SCM available as a standby console.

Figure 8???1 CSB Block Diagram

8-2 AlphaServer GS80/160/320 User???s Guide

The SCM communicates with the PCI backplane managers (PBMs), the hierarchical switch power manager (HPM), and the QBB power system managers (PSMs) distributed throughout the CSB subsystem. The subsystem has a power source separate from the rest of the system called auxiliary voltage (Vaux). Vaux enables the subsystem to be turned on from a remote site when the main system breaker is on and the system is plugged in.

Using the System Control Manager 8-3

8.2System Control Manager Overview

With the SCM, you can monitor and control the system (reset, power on/off, halt) without using the operating system. You can enter SCM commands at a local or remote console device. You also manage hard partitions using the SCM.

The SCM:

???Controls the control panel display and writes status messages on the display.

???Detects conditions that require alerts, such as excessive temperature, fan failure, and power supply failure. On detection, SCM displays messages on the OCP, pages an operator, and sends an interrupt to the SRM, which then passes the interrupt to the operating system or an application.

???Retrieves and passes information about a system shutdown to the SRM console at the next power-up. SRM displays a message regarding the last shutdown.

???Provides a command-line interface (CLI) for the user to control the system. From the CLI the user can power the system on and off, halt or reset the system, and monitor the system environment.

???Passes error log information to shared RAM so that this information can be accessed by the system.

???Handles power supply hot swap.

???Manages hard partitions using HP_* environment variables.

???Shared RAM on every standard I/O module in the system is kept coherent by the master SCM. This allows every SCM console and copy of the operating system in a hard-partitioned system to see the same configuration information.

8-4 AlphaServer GS80/160/320 User???s Guide

SCM Firmware

SCM firmware resides on the standard I/O module in flash memory. If the SCM firmware should ever become corrupted or obsolete, you can update it manually using the Loadable Firmware Update Utility. The microprocessor can also communicate with the system power control logic to turn on or turn off power to the rest of the system.

The SCM is powered by an auxiliary 5V supply. You can gain access to the SCM as long as AC power is available to the system (through the wall outlet) and the control panel keyswitch is in the On position. Thus, if the system fails, you can still access the SCM and gather information about the failure.

PSMs, PBMs, and HPMs

The power system managers (PSMs), PCI backplane managers (PBMs), and hierarchical switch power manager (HPM) are the ???slaves??? of the master SCM. The SCM gathers all environmental data from the slaves. The PSMs, PBMs, and HPM perform the following:

???Monitors environmental sensors

???Monitors voltages, power supplies, and fans

???Shuts down a subsystem (QBB or PCI box) if a fatal condition (temperature reaches a fatal limit or a power failure occurs) is detected

Configuration, Error Log, and Asset Information

The SCM provides additional functionality to read and write configuration and error log information to FRU error log devices. All reading and writing of the FRU EEPROMs is done by the slaves under the direction of the SCM.

Using the System Control Manager 8-5

8.3SCM COM1 Operating Modes

The SCM can be configured to manage different data flow paths defined by the com1_mode environment variable. In through mode (the default), all data and control signals flow from the system COM1 port through the SCM to the active external port. You can also set bypass modes so that the signals partially or completely bypass the SCM. The com1_mode environment variable can be set from either SRM or the SCM. See Section 8.7.1.

8-6 AlphaServer GS80/160/320 User???s Guide

Through Mode

Through mode is the default operating mode. The SCM routes every character of data between the internal system COM1 port and the active external port, either the local port or the modem port. If a modem is connected, the data goes to the modem. The SCM filters the data for a specific escape sequence. If it detects the default escape sequence, ???<Esc><Esc>scm???, it enters the SCM CLI.

Figure 8???2 illustrates the data flow in through mode. The internal system COM1 port is connected to one port of the DUART chip, and the other port is connected to an external modem port, providing full modem controls. The DUART is controlled by the SCM microprocessor, which moves characters between the two UART ports. The local port is always connected to the internal UART of the microprocessor. The escape sequence signals the SCM to enter the CLI. Data issued from the CLI is transmitted between the SCM microprocessor and the active port that enters the SCM.

NOTE: The internal system COM1 port should not be confused with the external COM1 serial port on the standard I/O module. The internal COM1 port is used by the system software to send data either to the COM1 port on the system or to the SCM modem port if a modem is connected.

Local Mode

You can set a local mode in which only the local channel can communicate with the system COM1 port. In local mode the modem is prevented from sending characters to the system COM1 port, but you can still enter the SCM from the modem.

Using the System Control Manager 8-7

8.3.1Bypass Modes

For modem connection, you can set the operating mode so that data and control signals partially or completely bypass the SCM. The bypass modes are snoop, soft bypass, and firm bypass.

Figure 8???3 Data Flow in Bypass Mode

8-8 AlphaServer GS80/160/320 User???s Guide

Figure 8???3 shows the data flow in bypass mode. Note that the internal system COM1 port is connected directly to the modem port.

NOTE: You can connect a console device to the modem port in any of the bypass modes.

The local console device is still connected to the SCM and can still enter the SCM to switch the COM1 mode if necessary. In any of the bypass modes, when the system loses power, it defaults to snoop mode.

Snoop Mode

In snoop mode data partially bypasses the SCM. The data and control signals are routed directly between the system COM1 port and the external modem port, but the SCM taps into the data lines and listens passively for the SCM escape sequence. If it detects the escape sequence, it enters the SCM CLI.

The escape sequence is also passed to the system on the bypassed data lines. If you decide to change the default escape sequence, be sure to choose a unique sequence so that the system software does not interpret characters intended for the SCM.

In snoop mode the SCM is responsible for configuring the modem for dial-in as well as dial-out alerts and for monitoring the modem connectivity.

Because data passes directly between the two UART ports, snoop mode is useful when you want to monitor the system but also ensure optimum COM1 performance.

Soft Bypass Mode

In soft bypass mode all data and control signals are routed directly between the system COM1 port and the external modem port, and the SCM does not listen to the traffic on the COM1 data lines. The SCM is responsible for configuring the modem and monitoring the modem connectivity. If the SCM detects loss of carrier, it switches automatically into snoop mode. If you have set up the dial- out alert feature, the SCM pages the operator if an alert is detected and the modem line is not in use.

Soft bypass mode is useful if management applications need the COM1 channel to perform a binary download, because it ensures that SCM does not accidentally interpret some binary data as the escape sequence.

Continued on next page

Using the System Control Manager 8-9

After downloading binary files, you can set the com1_mode environment variable from the SRM console to switch back to snoop mode or other modes for accessing the SCM, or you can hang up the current modem session and reconnect it.

Firm Bypass Mode

Firm bypass mode effectively disables the SCM. All data and control signals are routed directly from the system COM1 port to the external modem port. The SCM does not configure or monitor the modem, and the SCM dial-in and call- out features are disabled. Firm bypass mode is useful if you want the system, not the SCM, to fully control the modem port and you want to disable SCM remote management features. You can switch to other modes, if necessary, by resetting the com1_mode environment variable from the SRM console.

Hard Bypass Mode

Hard bypass mode is set by a jumper on the standard I/O module. If this jumper is set, then all other modes are prohibited and the SCM is only accessible from the local port.

8-10 AlphaServer GS80/160/320 User???s Guide

8.4Console Device Setup

You can use the SCM from a console device connected to the system or a modem hookup. As shown in Figure 8???4, local connection is made from the local port ???. You connect remotely from a modem connected to the modem port ???.

Figure 8???4 Setups for SCM (PCI Box)

1

2

PK-0650-99

Note: Both the local port and the modem port are set at: 1 start bit, 8 data bits, 1 stop bit, no parity.

Local port defaults: baud rate is 9600, flow control is soft.

Modem port defaults: baud rate is 57600, flow control is hard.

Using the System Control Manager 8-11

8.5Entering the SCM

Type an escape sequence to invoke the SCM from the SRM console. You can enter SCM from a modem, or from a local console device. From a VGA monitor, you can enter SCM commands from the SRM console.

???You can enter the SCM from the local console device regardless of the current operating mode.

???You can enter the SCM from the modem if the SCM is in through mode, snoop mode, or local mode. In snoop mode the escape sequence is passed to the system and displayed.

Entering from a Console Device

Invoke the SCM from a console device by typing the following default escape sequence (six plus signs):

<Esc><Esc>scm

To exit, enter the quit command. This action returns you to whatever you were doing before you invoked the SCM. In the following example, the quit command returns you to the system COM1 port.

SCM_E0> quit

Returning to COM1 port

Entering SCM Commands from a VGA Console

From the SRM console, enter:

P00>>> SCM <CLI_command>

8-12 AlphaServer GS80/160/320 User???s Guide

8.6SRM Environment Variables for COM1

Several SRM environment variables allow you to set up the COM1 port for use with the SCM. Default values are read from shared RAM and set to whatever the SCM values are at console boot time.

Using the System Control Manager 8-13

8.7SCM Command-Line Interface

The system control manager supports setup commands and commands for managing the system. See Table 8???1. For an SCM commands reference, see the AlphaServer GS80/160/320 Firmware Reference Manual.

Table 8???1 SCM Commands

8-14 AlphaServer GS80/160/320 User???s Guide

Table 8???1 SCM Commands (Continued)

Using the System Control Manager 8-15

Command Conventions

Follow these conventions when entering SCM commands:

???Enter enough characters to distinguish the command.

NOTE: The reset and quit commands are exceptions. You must enter the entire string for these commands to work.

???For commands consisting of two words, enter the entire first word and at least one letter of the second word. For example, you can enter disable a for disable alert.

???For commands that have parameters, you are prompted for the parameter.

???Use the Backspace key to erase input.

Power-Up Messages

???A *** message is a diagnostic error format displayed when an error is detected by SROM or XSROM code. Power-up continues depending on the type of error and system configuration.

???A ### message is a diagnostic warning format detected by SROM or XSROM code. System power-up continues, and the resource remains available for use.

???An ~E~ message indicates a more severe error has been detected; power-up continues, but the affected resource is dropped.

???A ~W~ message indicates an error has been reported to the SCM by a ???slave??? microprocessor (PSM, PBM, or HPM). Power-up continues, but the affected resource is questionable.

???A ~I~ message is informational only, and indicates no error condition.

8-16 AlphaServer GS80/160/320 User???s Guide

8.7.1Defining the COM1 Data Flow

Use the set com1_mode command from SRM or SCM to define the COM1 data flow paths.

You can set com1_mode to one of the following values:

Example

SCM_E0> set com1_mode snoop

Using the System Control Manager 8-17

8.7.2Displaying the System Status

The SCM status command displays the current SCM settings. Table 8???2 explains the status fields.

SCM_E0> show status

System Management Settings

Table 8???2 Status Command Fields

8-18 AlphaServer GS80/160/320 User???s Guide

Table 8???2 Status Command Fields (Continued)

Using the System Control Manager 8-19

8.7.3Displaying the System Environment

The SCM show system command provides a snapshot of the system environment.

SCM_E0> show system

SCM_E0>

???In a partitioned system, the number shown in this column identifies the hard partition that each QBB is a member of.

???The hard QBB and soft QBB numbers are listed. Location in the system determines hard QBB numbers; the system firmware assigns soft QBB numbers.

???CPU self-tests are reported. Note that there are four CPUs in each of the four QBBs. In this example, all 16 CPUs have passed self-test as indicated by a P.

???Memory self-tests are reported. The 16 memory modules have passed self- test.

???Remote I/O riser map for each QBB.

8-20 AlphaServer GS80/160/320 User???s Guide

For QBB0:

Px.x indicates that a remote I/O riser is present (P), but no I/O mapping (x.x) has been determined.

P2.0 indicates that a hose from local I/O riser 2, port 2, (IOR2) is connected to PCI box 2, remote I/O riser 0.

Pf.1 indicates that a hose from local I/O riser 1, port 1 (IOR1) is connected to PCI box F, remote I/O riser 1.

Pf.0 indicates that a hose from local I/O riser 1, port 0 (IOR0) is connected to PCI box F, remote I/O riser 0.

???Global port module self-test results.

???QBB backplane test results.

???Directory module self-test results.

???Power supply test results.

???Power supply temperature readings.

???HSwitch. The model number of the H-switch is displayed. In this example the model number is HPM40.

???Type. The HPM40 is a 4-port H-switch.

???Cables. In the example, H-switch ports 0 through 3 are enabled (P); H- switch ports 4 through 7 are not present (???). Other indicators are V (valid),

*(present), and F (failed).

???Temp. Displays the temperature inside the H-switch housing.

???PCI Cab. This map shows the presence or absence of devices in each PCI box in the system. Each PCI box has a maximum of four PCI hoses (two hoses (0 and 1) on remote I/O riser 0 and two hoses (0 and 1) on remote I/O riser 1.

In this example, PCI box 10 has a standard I/O module (S) in riser 0, hose 0, slot 1, and two low-powered devices (L) in riser 0, hose 1, slots 4 and 6.

A device is labeled according to its power usage: L is low-powered, M is medium-powered, and H is high-powered.

Continued on next page

Using the System Control Manager 8-21

???RIO. Remote I/O modules. * indicates the presence of a remote I/O module; ??? indicates its absence. In the example, PCI box 10 has one remote I/O riser, I/O riser 0, installed.

???PS. PCI box power supplies 2 and 1. A P indicates a power supply is powered on and passed self-test; a ??? indicates no power supply is installed. Other indications include:

p, power supply passed self-test and is powered off

*, power supply is present, but no pass/fail status yet

F, power supply failed

???Temp. Displays the temperature on the PCI backplane.

8.7.4Power On and Off, Reset, and Halt

The SCM power {on, off}, halt {in, out}, and reset commands perform the same functions as the buttons on the control panel.

Power On and Power Off

The SCM power on command powers the system on, and the power off command powers the system off. The Power button on the control panel, however, has precedence.

???If the system has been powered off with the Power button, the SCM cannot power the system on. If you enter the power on command, the message ???Power button is OFF??? is displayed, indicating that the command will have no effect.

???If the system has been powered on with the Power button, and the power off command is used to turn the system off, you can toggle the Power button to power the system back on.

8-22 AlphaServer GS80/160/320 User???s Guide

Halt In and Continue

The halt in command halts the operating system. The continue command releases the halt.

Issuing the continue command will restart the operating system even if the Halt button is latched in.

Reset

NOTE: The environment variable, auto_quit, must be enabled for the reset command to return to the console or operating system.

The SCM reset command restarts the system. The console device exits SCM and reconnects to the server???s COM1 port.

SCM_E0> reset

Returning to COM port

Using the System Control Manager 8-23

8.7.5Configuring Remote Dial-In

Before you can dial in through the SCM modem port or enable the system to call out in response to system alerts, you must configure the system for remote dial-in.

Example 8???1 Dial-In Configuration

Querying the modem port...modem detected

Initializing modem...passed

Modem port initialized

NOTE: The following modems require the initialization strings shown here. For other modems, see your modem documentation.

8-24 AlphaServer GS80/160/320 User???s Guide

???Enables remote access to the SCM modem port.

???Sets the password (in the example, ???wffirmare???) that is prompted for at the beginning of a modem session. The string cannot exceed 14 characters and is not case sensitive. For security, the password is not echoed on the screen. When prompted for verification, type the password again.

???Sets the modem initialization string. The string is limited to 31 characters and can be modified depending on the type of modem used.

The SCM automatically configures the modem's flow control according to the setting of the SRM com1_flow environment variable. The SCM also enables the modem carrier detect feature to monitor the modem connectivity.

After the initialization string is set, it is copied to the SCM???s EEPROM to allow the SCM to reinitialize the modem in the case of a system power cycle.

???The init command is entered to initialize the modem.

???At this point, the modem is configured for remote dial-in.

Dialing In

Once the remote session is connected, the password must be entered to access the SCM CLI. The following example shows the screen output when a modem connection is established.

atdt915085551212 CONNECT 9600

Password: **********

Access granted

Modem escape sequence verified

SCM_E0>

1.At the SCM_E0> prompt, enter SCM CLI commands to monitor and control the system. Use the show status command to check the current manage- ment settings and the channel the modem connection is currently using.

2.When you have finished a modem session, enter the hangup command to cleanly terminate the session and disconnect from the server.

Using the System Control Manager 8-25

8.7.6Configuring Alert Dial-Out

Set a few parameters to configure alert dial-out. The dial string and alert string are set to send a message to a remote operator. When an alert condition is triggered, the dial string is sent first, followed by the alert string. Once the two strings are set, alert dial-out is enabled and the new parameters should be verified. The elements of the dial string and alert string are shown in Table 8???3.

You must configure remote dial-in for the dial-out feature to be enabled.

To set up the dial-out alert feature, enter the SCM from the local console device.

Example 8???2 Alert Dial-Out Configuration

8-26 AlphaServer GS80/160/320 User???s Guide

???Sets the string to be used by the SCM to dial out when an alert condition occurs. The dial string must include the appropriate modem commands to dial the number.

???Sets the alert string that is transmitted through the modem when an alert condition is detected. Set the alert string to the phone number of the modem connected to the remote system. The alert string is appended after the dial string, and the combined string is sent to the modem.

???Alert dial-out is enabled.

???Issue the test alert command to test the alert dial-out settings.

???Now issue the show status command to verify settings. Note that the alert pending value is YES (???), indicating the test alert was successful.

???Once the dial-out settings are verified, the pending alert should be cleared by entering the clear alert command.

Paging services vary, so you need to become familiar with the options provided by the paging service you will be using. The SCM supports only numeric mes- sages.

NOTE: If you do not want dial-out paging enabled at this time, enter the disable alert command after you have tested the alert dial-out function. Alerts continue to be logged, but no paging occurs.

Alert Conditions Reported to a Remote Operator

Using the System Control Manager 8-27

Table 8???3 Elements of Dial String and Alert String

8-28 AlphaServer GS80/160/320 User???s Guide

8.7.7Resetting the Escape Sequence

The SCM set escape command allows the user to change the escape sequence. The default escape sequence is ???<Esc><Esc>scm???.

The new escape sequence can be any printable character string, not to exceed six characters. Use the show status command to verify the new escape sequence.

SCM_E0> set escape Escape Sequence: foofoo SCM_E0> show status

.

.

.

RMC Escape Sequence: foofoo

Using the System Control Manager 8-29

8.8Troubleshooting Tips

Table 8???4 lists possible causes and suggested solutions for symptoms you might see.

Table 8???4 SCM Troubleshooting

8-30 AlphaServer GS80/160/320 User???s Guide

Table 8???4 SCM Troubleshooting (Continued)

Using the System Control Manager 8-31

Appendix A

Jumpering Information

This appendix contains jumpering information for the PCI backplane, the hierarchical switch power manager (HPM), and the standard I/O module.

A.1 PCI Backplane Jumpers

Table A???1 lists PCI backplane jumpers and their functions. These two jumpers are not normally installed.

Table A???1 PCI Backplane Jumpers

Jumpering Information A-1

A.2 HPM Jumpers

Table A???2 lists hierarchical switch power manager (HPM) jumpers and their functions. The HPM module has three 2-position jumpers, none of which are normally installed.

Table A???2 HPM Jumpers

A.3 Standard I/O Module Jumpers

Table A???3 lists standard I/O module jumpers and their functions. The jumper station is three-pronged and the installed position is indicated by a silkscreen connection.

Table A???3 Standard I/O Module Jumpers

A-2 AlphaServer GS80/160/320 User???s Guide

Glossary

Glossary-1

Glossary-2

Glossary-3

Glossary-4

Glossary-5

Warm-swap state One of the power states of the system in which power is removed from a specified QBB but other segments of the system remain fully powered. In this state only the power going to the specified QBB is removed so that the QBB can be serviced. See also Hot-swap, Cold-swap, and AC off states.

Glossary-6

Index-1

Index-2

Index-3