Digital PDFs

EK-GS320-RM-C01

September 2000

278 pages

Original

4.2MB

Document:	AlphaServer GS80/160/320 Firmware Reference Manual
Order Number:	EK-GS320-RM
Revision:	C01
Pages:	278
Original Filename:

OCR Text

AlphaServer GS80/160/320
Firmware Reference Manual

Order Number: EK-GS320-RM. C01

This manual is for users and field service engineers for Compaq
AlphaServer GS80/160/320 systems. It describes the firmware
interface to these systems.

Compaq Computer Corporation

Revised September 2000
© 2000 Compaq Computer Corporation.
COMPAQ, the Compaq logo, and AlphaServer registered in U.S. Patent and Trademark Office.
OpenVMS, StorageWorks, and Tru64 are trademarks of Compaq Information Technologies Group, L.P.
Portions of the software are © copyright Cimetrics Technology. Linux is a registered trademark of Linus
Torvalds in several countries. UNIX is a registered trademark of The Open Group in the U.S. and other
countries. All other product names mentioned herein may be trademarks of their respective companies.
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
This equipment 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.
Modifications
The FCC requires the user to be notified that any changes or modifications made to this device that are
not expressly approved by Compaq Computer Corporation may void the user's authority to operate the
equipment.
Cables
Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods
in order to maintain compliance with FCC Rules and Regulations.
Taiwanese Notice

Japanese Notice

Canadian Notice
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment
Regulations.
Avis Canadien
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel
brouilleur du Canada.
European Union Notice
Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low
Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
Compliance with these directives implies conformity to the following European Norms (in brackets are
the equivalent international standards):
EN55022 (CISPR 22) - Electromagnetic Interference
EN50082-1 (IEC801-2, IEC801-3, IEC801-4) - Electromagnetic Immunity
EN60950 (IEC950) - Product Safety
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 les mesures spécifiques
appropriées.

Contents

Preface ..................................................................................................................... xiii
Chapter 1
1.1
1.2
1.3
1.4
1.5

System Console Device.......................................................................... 1-2
Remote Console Operations .................................................................. 1-4
Booting an Operating System ............................................................... 1-6
Setting Up and Initializing Partitions .................................................. 1-8
Firmware User Interface Overview .................................................... 1-10

Chapter 2
2.1
2.1.1
2.1.2
2.2
2.3
2.4
2.4.1
2.4.2
2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.6
2.7
2.7
2.8

Hardware Overview

System Overview................................................................................... 2-2
Front and Rear View of a GS80 System ......................................... 2-2
Front and Rear View of a GS160/320 System................................. 2-4
Control Panel ........................................................................................ 2-6
Ports Provided by the Primary PCI ...................................................... 2-8
Quad Building Block (QBB) ................................................................ 2-10
QBB in GS80 Systems .................................................................. 2-10
QBB in GS160/320 Systems.......................................................... 2-12
System Drawers and System Boxes.................................................... 2-14
System Drawers in a GS80 System .............................................. 2-14
System Box in a GS160 System.................................................... 2-16
Two System Boxes in System Cabinet 1....................................... 2-18
System Boxes in System Cabinet 2............................................... 2-20
Hard QBB Numbers............................................................................ 2-22
QBB and PCI Box Connections ........................................................... 2-24
Console Serial Bus .............................................................................. 2-26
System Power-up ................................................................................ 2-28

Chapter 3
3.1

Introduction to the Firmware

Remote Console Operations

Overview of Remote Setup and Operation............................................ 3-2

3.2
3.3
3.4
3.5
3.6
3.6.1
3.6.2
3.7
3.7.1
3.7.2
3.7.2
3.8
3.9
3.10

Remote Operations Command Summary ............................................. 3-4
Displaying Help on SCM Console Commands ...................................... 3-5
Setting Up for a Remote Console .......................................................... 3-6
Dialing in and Invoking SCM ............................................................... 3-8
Transmission Modes ........................................................................... 3-10
Through and Local Mode .............................................................. 3-10
Bypass Modes ............................................................................... 3-12
Displaying System Status ................................................................... 3-14
Show CSB ..................................................................................... 3-14
Show System Command ............................................................... 3-16
Show FRU Command.................................................................... 3-18
Controlling Power to the System ........................................................ 3-20
Leaving the SCM Command-Line Interpreter.................................... 3-21
Terminating the Remote Session ........................................................ 3-22

Chapter 4
4.1
4.2
4.2.1
4.2.2
4.3
4.4
4.4.1
4.4.2
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6
4.7
4.8

Maintaining Partitions at Separate Consoles....................................... 4-2
Hard and Soft Partitions....................................................................... 4-4
Hard Partitions............................................................................... 4-4
Soft Partitions................................................................................. 4-6
Hardware Requirements....................................................................... 4-8
Defining Hard Partitions .................................................................... 4-10
SCM Commands that Define Hard Partitions.............................. 4-10
Detailed Directions for hp_qbb_mask........................................... 4-12
Defining Soft Partitions ...................................................................... 4-14
SRM Commands That Define Soft Partitions............................... 4-14
Detailed Directions for lp_io_mask............................................... 4-16
Detailed Directions for lp_cpu_mask ............................................ 4-18
Detailed Directions for lp_mem_size ............................................ 4-20
Detailed Directions for lp_shared_mem_size................................ 4-22
Lpinit Command........................................................................... 4-24
Soft Partitions Within Hard Partitions .............................................. 4-26
Master and Slave SCMs...................................................................... 4-28
SCM Functionality from Master and Slave SCMs.............................. 4-30

Chapter 5
5.1
5.1.1
5.1.2
5.1.3

Partitions

Booting an Operating System

Preparation ........................................................................................... 5-2
Set os_type Environment Variable ................................................. 5-2
Set Console Environment Variable................................................. 5-3
Set auto_action Environment Variable .......................................... 5-4

5.2
5.2.1
5.2.2
5.3

Selecting a Boot Device ......................................................................... 5-6
Show Device Commands................................................................. 5-8
Boot Environment Variables ........................................................ 5-11
Booting an Operating System ............................................................. 5-12

Chapter 6

SCM Command Reference

6.1
Language Overview .............................................................................. 6-2
6.2
SCM Command Summary .................................................................... 6-4
6.3
SCM Command Description Conventions............................................. 6-5
6.4
Clear Command .................................................................................... 6-6
6.5
Deposit Command................................................................................. 6-6
6.6
Disable Command ................................................................................. 6-8
6.7
El Command.......................................................................................... 6-9
6.8
Enable Command................................................................................ 6-10
6.9
Erase Command.................................................................................. 6-11
6.10
Examine Command............................................................................. 6-12
6.11
Fault Command .................................................................................. 6-14
6.12
Halt Command.................................................................................... 6-14
6.13
Hangup Command .............................................................................. 6-15
6.14
Help Command ................................................................................... 6-16
6.15
Init Command ..................................................................................... 6-17
6.16
Power Command ................................................................................. 6-18
6.17
Quit Command.................................................................................... 6-20
6.18
Reset Command .................................................................................. 6-21
6.19
Set Commands .................................................................................... 6-22
6.19.1
Set Alert Command ...................................................................... 6-22
6.19.2
Set Baud Command ...................................................................... 6-23
6.19.3
Set Com1_Mode ............................................................................ 6-24
6.19.4
Set Dial Command........................................................................ 6-25
6.19.5
Set Escape Command ................................................................... 6-26
6.19.6
Set <environment_variable> Command ....................................... 6-27
6.19.7
Set Flow Command....................................................................... 6-28
6.19.8
Set Init Command......................................................................... 6-29
6.19.9
Set Ocp_text Command ................................................................ 6-30
6.19.10
Set Password Command ............................................................... 6-31
6.20
Show Commands................................................................................. 6-32
6.20.1
Show CSB Command .................................................................... 6-32
6.20.2
Show FRU Command.................................................................... 6-34
6.20.3
Show Nvram Command................................................................ 6-36
6.20.4
Show Status Command................................................................. 6-38
6.20.5
Show System Command ............................................................... 6-40

vii

6.21
6.22

Test Alert Command........................................................................... 6-42
Test &pcn Command........................................................................... 6-42

Chapter 7
7.1
7.2
7.3
7.4
7.4.1
7.4.2
7.4.3
7.5
7.5.1
7.5.2
7.5.3
7.5.4
7.5.5
7.5.6
7.5.7
7.5.8
7.5.9
7.5.10
7.5.11
7.5.12
7.5.13
7.5.14
7.5.15
7.5.16
7.5.17
7.5.18
7.5.19
7.5.20
7.5.21
7.5.22
7.5.23
7.5.24
7.5.25
7.5.26
7.5.27
7.5.28
7.5.29

viii

SRM Command Reference

SRM Command Overview ..................................................................... 7-2
SRM Command Description Conventions............................................. 7-8
SRM Command Language Environment Variables.............................. 7-9
SRM Console Shell Syntax.................................................................. 7-10
I/O Pipes........................................................................................ 7-10
Redirecting Output ....................................................................... 7-10
Background Operator ................................................................... 7-11
SRM Console Commands .................................................................... 7-12
Boot Command.............................................................................. 7-12
Cat Command ............................................................................... 7-16
Clear Command ............................................................................ 7-18
Continue Command ...................................................................... 7-19
Crash Command .......................................................................... 7-20
CSR Command.............................................................................. 7-21
Deposit and Examine Commands................................................. 7-23
Edit Command .............................................................................. 7-26
Exer Command ............................................................................. 7-28
Galaxy Command ......................................................................... 7-32
Gct Command ............................................................................... 7-33
Grep Command............................................................................. 7-34
Halt Command.............................................................................. 7-36
Help or Man Command................................................................. 7-37
Info Command .............................................................................. 7-37
Init Command............................................................................... 7-41
Kill Command............................................................................... 7-42
Kill_diagsCommand...................................................................... 7-43
Lpinit Command........................................................................... 7-44
Ls Command ................................................................................. 7-46
Memexer Command...................................................................... 7-47
Memexer_mp Command ............................................................... 7-48
Migrate Command ........................................................................ 7-49
More Command............................................................................. 7-50
Nettest Command ......................................................................... 7-51
Nvram Script ................................................................................ 7-53
Power Command........................................................................... 7-54
Ps Command ................................................................................. 7-55
Reset Command ............................................................................ 7-56

7.5.30
7.5.31
7.5.32
7.5.33
7.5.34
7.5.35
7.5.36
7.5.37
7.5.38
7.5.39
7.5.40
7.5.41
7.5.42
7.5.43
7.5.44
7.5.45

Rm Command ............................................................................... 7-56
Run BIOS Command .................................................................... 7-57
SCM Command............................................................................. 7-59
Set envar Command...................................................................... 7-60
Show BIOS Command .................................................................. 7-64
Show Configuration Command..................................................... 7-66
Show Device Command ................................................................ 7-74
Show envar Command .................................................................. 7-76
Show FRU Command.................................................................... 7-78
Show Memory Command .............................................................. 7-80
Show PAL and Show Version Commands .................................... 7-82
Show_status Command ................................................................ 7-83
Sys_exer Command....................................................................... 7-84
Test Command.............................................................................. 7-86
Wwidmgr Command ..................................................................... 7-87
Comment (#) ................................................................................. 7-88

Appendix A Boot Options
Appendix B Loadable Firmware Update Utility
B.1
B.2
B.3
B.4
B.5
B.6

Overview
..........................................................................................B-2
Booting LFU..........................................................................................B-4
Display Command.................................................................................B-6
Exit Command ......................................................................................B-8
List Command.......................................................................................B-9
Update Command ...............................................................................B-10

Index
Examples
1–1
3–1
3–2
3–3
3–4
3–5
3–6
3–7
3–8

Booting an Operating System ............................................................... 1-6
Help or ? ................................................................................................ 3-5
Sample Setup for a Remote Console ..................................................... 3-6
Sample Remote Dial-In Dialog.............................................................. 3-8
Set com1_mode through Command .................................................... 3-11
Set com1_mode local Command .......................................................... 3-11
Show CSB Command .......................................................................... 3-14
Show System Command...................................................................... 3-16
Show FRU Command.......................................................................... 3-18

3–9
3–10
3–11
4–1
4–2
4–3
4–4
4–5
4–6
4–7
4–8
4–9
4–10
4–11
5–1
5–2
5–3
5–4
5–5
5–6
5–7
5–8
5–9
B–1
B–2
B–3
B–4
B–5
B–6
B–7
B–8

Power Off Command ........................................................................... 3-20
Using Quit to Return to SRM ............................................................. 3-21
Using the Hangup Command.............................................................. 3-22
Resource Allocation with Soft Partitions .............................................. 4-7
Sample Hard Partition Setup ............................................................. 4-13
Sample lp_io_mask Setup ................................................................... 4-17
Sample lp_cpu_mask Setup ................................................................ 4-19
Example for Constructing lp_mem_size ............................................. 4-20
Examples of lp_mem_size ................................................................... 4-21
Example of Constructing lp_shared_mem_size .................................. 4-22
Examples of lp_shared_mem_size....................................................... 4-23
Show Config Command for a Hard Partition...................................... 4-24
Setting Up Soft Partitions................................................................... 4-25
Soft Partitions Within Hard Partitions .............................................. 4-27
Setting os_type for OpenVMS ............................................................... 5-2
Setting os_type for Tru64 UNIX ........................................................... 5-2
Set Console to Serial ............................................................................. 5-3
Set Console to Graphics ........................................................................ 5-3
Setting the auto_action Environment Variable .................................... 5-4
Show Device Command......................................................................... 5-8
Show Config and Show Device Commands ........................................... 5-8
Viewing and Setting Boot Environment Variables ............................. 5-11
Tru64 UNIX Boot ................................................................................ 5-12
LFU Menu Screen .................................................................................B-2
Booting LFU from the Network ............................................................B-4
Display Command.................................................................................B-6
Exit Command ......................................................................................B-8
List Command.......................................................................................B-9
Update Command for a PCI Device ....................................................B-10
Update Command for the SRM Console .............................................B-10
Update Command for Micros ..............................................................B-10

Figures
1–1
1–2
1–3
1–4
2–1
2–2
2–3

System Management Console ............................................................... 1-2
Managing a System from a Remote Console......................................... 1-4
Using Partitions to Consolidate Resources ........................................... 1-8
Firmware User Interface Components................................................ 1-10
Front and Rear View of a GS80 System................................................ 2-2
System Front and Rear Views (GS160/320).......................................... 2-4
Control Panel ........................................................................................ 2-6

2–4
2–5
2–6
2–7
2–8
2–9
2–10
2–11
2–12
2–13
2–14
2–15
2–16
2–17
2–18
2–19
2–20
3–1
3–2
3–3
4–1
4–2
4–3
4–4
4–5
4–6
4–7
4–8
4–9
4–10
4–12
4–13
6–1

Console and Modem Ports on Standard I/O Module ............................ 2-8
Master PCI Ports .................................................................................. 2-9
GS80 QBB Backplane ......................................................................... 2-10
Elements of a GS80 QBB (System Drawer) ........................................ 2-11
QBB Backplane for GS160/320 Systems............................................ 2-12
Elements of a QBB for GS160/320 Systems........................................ 2-13
System Drawers in a GS80 System .................................................... 2-14
Elements of a System Box (GS160 Rear Orientation) ........................ 2-16
Reverse Side of System Box (Front of System Cabinet 1)................... 2-17
System Boxes in System Cabinet 1..................................................... 2-18
Elements of System Cabinets 1 and 2................................................. 2-20
Front of System Box in System Cabinet 2 .......................................... 2-21
Hard QBB Numbers............................................................................ 2-22
QBB Local I/O Port Numbers.............................................................. 2-24
Sample Cabling to PCI Boxes ............................................................. 2-25
Logic Diagram of the Console Serial Bus............................................ 2-26
Location of Nodes on the Console Serial Bus...................................... 2-28
Overview of Remote Setup and Operation............................................ 3-2
Through and Local Modes................................................................... 3-10
Bypass Modes...................................................................................... 3-12
Maintaining Multiple OS Instances at the SMC .................................. 4-2
Hard Partitions ..................................................................................... 4-4
Soft Partitions ....................................................................................... 4-6
Hardware Requirements for Each Partition......................................... 4-8
SCM Commands for Hard Partitions.................................................. 4-10
Sample QBB Bit Masks....................................................................... 4-12
Soft Partitions ..................................................................................... 4-14
Sample lp_io_mask Bit Masks ............................................................ 4-16
Sample lp_cpu_mask Bit Masks ......................................................... 4-18
Multiple SCMs in a Partitioned System ............................................. 4-28
Systemwide Functionality .................................................................. 4-30
Partition-Dependent Functionality..................................................... 4-31
Overview of SCM Command Language Functionality.......................... 6-2

Tables
1
3–1
4–1
4–2
4–3
5–1

Compaq AlphaServer GS80/160/320 Documentation ............................ xii
SCM Commands Related to Remote Console Management ................. 3-4
SCM Environment Variables for Hard Partitions .............................. 4-11
SRM Environment Variables for Soft Partitions ................................ 4-15
Example of Soft Partitions Within Hard Partitions ........................... 4-26
Boot Devices .......................................................................................... 5-6

5–2
6–1
6–2
6–3
6–4
6–5
7–1
7–2
7–3
7–4
7–5
7–6
A–1
A–2

xii

SRM Console Device Naming Conventions........................................... 5-9
Management Tasks and Related SCM Commands............................... 6-4
SCM Command Description Conventions............................................. 6-5
Alert String Elements ......................................................................... 6-22
Dial String Elements .......................................................................... 6-25
Modem Initialization Strings .............................................................. 6-29
Summary of SRM Console Commands ................................................. 7-2
Notation Formats for SRM Console Commands ................................... 7-5
Special Characters for the SRM Console .............................................. 7-6
SRM Command Description Conventions............................................. 7-8
Environment Variables ....................................................................... 7-60
Device Naming Conventions ............................................................... 7-75
Tru64 UNIX Boot Options ....................................................................A-1
OpenVMS Boot Options ........................................................................A-2

Preface

Intended Audience
This manual is intended for users and field service engineers who use the
AlphaServer GS80/160/320 firmware.

Document Structure
This manual uses a structured documentation design. Topics are organized into
small sections for efficient online and printed reference. Each topic begins with
an abstract. You can quickly gain a comprehensive overview by reading only
the abstract. In conceptual chapters, the next item is an illustration or
example, which also provides quick reference. Next is descriptive text.
The reference chapters follow the format of UNIX man pages. This includes
syntax, arguments, and options (if appropriate), and an example.
This manual has seven chapters and two appendixes, as follows:

•

Chapter 1, Introduction to the Firmware, introduces the AlphaServer
GS80/160/320 firmware and the devices through which it is accessed.

•

Chapter 2, Hardware Overview, gives an overview of the structure and
architecture of the AlphaServer GS80/160/320 systems.

•

Chapter 3, Remote Console Operations, describes the SCM commands that
allow remote access, and how to use the firmware from a remote terminal.

•

Chapter 4, Partitions, describes the SCM commands used to set up hard
partitions and the SRM commands used to set up soft partitions.

•

Chapter 5, Booting an Operating System, tells how to boot an operating
system on AlphaServer GS80/160/320 systems.

•

Chapter 6, SCM Command Reference, describes the SCM commands in
alphabetical order for easy reference.

•

Chapter 7, SRM Command Reference, describes the SRM commands in
alphabetical order for easy reference.

xiii

•

Appendix A, Boot Options, lists the options used with the SRM boot
command for the Tru64 UNIX and OpenVMS operating systems to control
various phases of booting.

•

Appendix B, Updating Firmware, explains how to run the Loadable
Firmware Update (LFU) utility.

Documentation Titles
Title

Order Number

AlphaServer GS80/160/320 Documentation Kit

QA-6GAAA-G8

AlphaServer GS80/160/320 User’s Guide

EK-GS320-UG

AlphaServer GS80/160/320 Firmware Reference Manual

EK-GS320-RM

AlphaServer GS80/160/320 Getting Started with Partitions

EK-GSPAR-RM

AlphaServer G160/320 Installation Guide

EK-GS320-IN

AlphaServer GS80 Installation Guide

EK-GSR80-IN

AlphaServer GS80/160/320 User Information CD (HTML files)

AG-RKSWB-BE

AlphaServer GS80/160/320 User Information CD (translations)

AG-RLVJA-BE

AlphaServer GS80/160/320 Service Documentation Kit

QA-6GAAB-G8

AlphaServer GS80/160/320 Service Manual

EK-GS320-SV

AlphaServer GS80/160/320 Firmware Reference Manual

EK-GS320-RM

AlphaServer GS80/160/320 Service Information CD

AG-RKSZ*-BE

AlphaServer GS160/320 Upgrade Manual

EK-GS320-UP

AlphaServer GS80/160/320 System Management Console
Installation and User’s Guide

EK-GSCON-IN

AlphaServer GS80 Upgrade Manual

EK-GSR80-UP

AlphaServer GS80/160/320 Site Preparation

EK-GS320-SP

xiv

Related Software Documentation
Title

Order Number

Tru64 UNIX Installation Guide

AA-RH8SC-TE

Tru64 UNIX System Management

AA-RH9FC-TE

OpenVMS Alpha Version 7.2-1H1 New Features and Release Notes

AA-RLMUA-TE

OpenVMS Alpha Galaxy and Partitioning Guide

AA-REZQC-TE

Information on the Internet
Visit the Compaq Web site at http://www.compaq.com/site_index.html for
service tools and more information about the system.

Chapter 1
Introduction to the Firmware

This chapter introduces the Compaq AlphaServer GS80, GS160, and GS320
firmware and the devices through which it is accessed. Sections include:

•

System Console Device

•

Remote Console Operations

•

Booting an Operating System

•

Setting Up and Initializing Partitions

•

Firmware User Interface Overview

Introduction to the Firmware 1-1

1.1

System Console Device

A local user or field service engineer interacts with the system
firmware through the system management console.
The system
management console is connected directly to the system. A user may
also communicate with the system remotely through the use of a
modem.

Figure 1–1 System Management Console

AlphaServer GS320

Partition 3
Partition 2
Partition 1

PK-0100C-99

1-2 AlphaServer GS80/160/320 Firmware Reference Manual

During everyday operations, you will not interact with the firmware on an
AlphaServer GS80, GS160, or GS320 system. Once fundamental parameters
have been defined, powering on the system activates the firmware that controls
power-up and boots the operating system, all automatically.
The firmware on an AlphaServer GS80/160/320 system supports six primary
functions:

•

Accessing the system from a local or remote console

•

Booting an operating system

•

Setting up and initializing partitions

•

Setting up system parameters for booting

•

Monitoring environmental conditions

•

Testing the system

The other functions largely revolve around displaying information on the
current state of the system.
All these functions are accessed through either a local or remote console device.
A console device may consist of a serial display monitor and a keyboard, or a
terminal emulator on a PC, UNIX, or VMS workstation attached to the system.
Figure 1–1 shows the system management console monitor with windows for
three partitions open on the monitor screen. In this case, a terminal emulator
displays the screens; the commands typed at each screen direct the firmware to
perform the actions requested.

Introduction to the Firmware 1-3

1.2

Remote Console Operations

Some installations of AlphaServer GS80, GS160, or GS320 systems may
require that the systems be managed by a person remote from the
systems, in another room, building, or many miles away. The firmware
supports such remote maintenance.

Figure 1–2 Managing a System from a Remote Console

beep!
Modem

(To remote terminal
to dial in and troubleshoot)
Alert!
Too hot!
Dial-out to
remote pager

Dial-in to
system modem

Modem

PK-0125A-99

1-4 AlphaServer GS80/160/320 Firmware Reference Manual

The AlphaServer GS80/160/320 systems are large, fast, modular systems.
Some installations require operation 24 hours a day, seven days a week, and
some installations may contain many of these systems. In these cases, it is
reasonable to expect that these systems be monitored by a person remote from
the systems, in another room, another building, or many miles away. The
firmware supports such remote monitoring and management.
The key to remote management of these systems is a function called an alert.
For example, the firmware monitors system conditions such as temperature and
voltage. After setting up the capability for remote console operations, the
firmware can recognize an alert condition, and dial out to an assigned telephone
number, usually a pager, to notify the system manager that an alert condition
exists (Figure 1–2).
The system manager can then use a serial terminal with a modem, or a PC or
workstation with terminal emulation software, to access the remote system that
sent the alert. System control manager (SCM) commands allow a user to
troubleshoot a system from the remote terminal (or, for that matter, the local
console terminal) without interrupting operating system execution. These
commands include various show options that display status and the examine
command to view error registers. If the system has crashed, you can reinitialize
the system to reboot or to power off or reset, at which time you can run software
to display error log information to isolate faulty hardware.
In addition to alerts, the systems, including the firmware and operating system
software, have been carefully designed to keep the operating system running
even though individual CPU, memory, and I/O modules, as well as AC/DC
converters, fail. The remote user can routinely examine the status of the
system and schedule service personnel for maintenance as appropriate.

Introduction to the Firmware 1-5

1.3

Booting an Operating System

Most of the time, GS80/160/320 systems are running user programs
under control of an operating system, either Tru64 UNIX or OpenVMS.
When the operating system is shut down, control returns to the
firmware. The firmware provides the means to boot the operating
system, initially and after shutdown and maintenance.

Example 1–1 Booting an Operating System
P00>>> b dkb4 -fl A –file vmunix
➊
(boot dkb400.4.0.1.2 -file vmunix -flags A)
block 0 of dkb400.4.0.1.2 is a valid boot block
reading 13 blocks from dkb400.4.0.1.2
bootstrap code read in
base = 344000, image_start = 0, image_bytes = 1a00
➋
initializing HWRPB at 2000
initializing page table at 3fffb2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
➌
.
.
.
Digital UNIX Version V4.0 (wfsys6.eng.pko.dec.com) console
login: root
➍
Password:
Last login: Wed Sep 8 23:49:02 on console
.
.
.
sys6>
➎

1-6 AlphaServer GS80/160/320 Firmware Reference Manual

Example 1–1 shows an operator booting the Tru64 UNIX operating system,
using the SRM console command boot (abbreviated as b in the example). The
SRM console firmware runs on the primary processor, selected during power-up,
as described in Chapter 2.

➊

The operator issues the boot command. The boot disk is named directly as
dkb4, the –fl option is used to request boot flag A, which boots the system
disk to multiuser mode for Tru64 UNIX. The –file option specifies the
name of the file to boot.

➋

The HWRPB (hardware restart parameter block) is an area in memory
where parameters are passed between the operating system and the SRM
console. (The HWRPB is discussed in detail in the Alpha Architecture
Manual.)

➌

The SRM jumps to bootstrap code that has been loaded into memory from
the boot device to boot the operating system from the disk named in the
boot command.

➍

The Tru64 UNIX operating system is given control and displays the
prompt for login name and password.

➎

The operator is at the operating system prompt and can initiate operations
to be performed by the operating system.

Introduction to the Firmware 1-7

1.4

Setting Up and Initializing Partitions

The firmware allows you to set up and initialize partitions.

Figure 1–3 Using Partitions to Consolidate Resources
BEFORE
Server
running office
applications

Server
running 24/7
air pollution monitoring
and simulation for
greater Los Angeles

AFTER
Partition 0

AlphaServer GS160
with three partitions

Partition 1

Server generating real-time
displays for Web site
traffic updates

Partition 2
PK-0150-00

1-8 AlphaServer GS80/160/320 Firmware Reference Manual

Multiple copies, or instances, of the Tru64 UNIX and/or OpenVMS operating
systems can be run on AlphaServer GS80, GS160, and GS320 systems. This
partitioning of the system is set up and initialized using the console firmware.
You define the number of partitions and what resources are to be allocated to
each partition.
One of the primary reasons for using partitions is shown in Figure 1–3. The left
side of the figure shows three separate servers, each performing user tasks in a
separate environment. The right side of the figure shows how these same
functions can be performed on one larger server, using partitions.

Introduction to the Firmware 1-9

1.5

Firmware User Interface Overview

A user at a console device has access to two interfaces: the SCM
command language and the SRM command language. The Loadable
Firmware Update (LFU) utility can be loaded from CD-ROM to update
resident firmware.

Figure 1–4 Firmware User Interface Components
Resident on the standard I/O
module

Resident on the standard I/O
module

SCM Monitor

SRM Console

Remote console
access

Define soft
partitions

Define hard
partitions

Boot the operating
system

Loadable Firmware Update Utility (LFU)
Loads updates of firmware. Resident
on CD-ROM, loaded into memory to run on
primary CPU.
PK-0116B-99

1-10 AlphaServer GS80/160/320 Firmware Reference Manual

Figure 1–4 shows the two main user interfaces to the firmware and where the
firmware resides. The figure also shows the Loadable Firmware Update (LFU)
utility, which is loaded from DVD/CD-ROM when necessary to load or update
the firmware.
SCM Monitor Command Language Interface
The system control manager (SCM) command language provides the interface to
firmware that resides on nodes attached to the console serial bus, or CSB (see
Section 2.8). The primary functions of this interface are to allow you to define
and activate remote console services and to define hard partitions.
Remote console access allows a user to respond to an alert condition from a
remote location without halting operating system execution.
Partitions allow the user to run multiple copies or instances of an operating
system within one GS80/160/320 system. Hard partitions indicate that the
boundaries of each partition remain fixed along boundaries defined by system
building blocks called QBBs (see Section 2.4). See Chapter 4 for a discussion of
partitions.
SRM Console Command Language Interface
The SRM console firmware resides in flash EEROM on the standard I/O module
(or modules, if partitions are used). The command language lets you define
whether the operating system is to be booted automatically at system power-up
or by request. This feature applies to all operating systems offered with the
AlphaServer GS80/160/320 systems.
In addition, the SRM console firmware provides the means to set up and
initialize soft partitions, which can be run in conjunction with OpenVMS
Galaxy. Soft partitions allow you to dedicate specific CPUs, memories, and I/O
modules to run separate instances of an operating system. See Chapter 4 for a
discussion of partitions.
A discussion of how the SRM command language affects booting is given in
Chapter 5. The SRM command language interface is described in detail in
Chapter 7.
Loadable Firmware Update (LFU) Utility
The LFU utility allows you to update the firmware components. LFU is on CDROM. The LFU interface is described in Appendix B.

Introduction to the Firmware 1-11

Chapter 2
Hardware Overview

To understand firmware operations and displays for GS80/160/320 systems, it is
helpful to understand the structure and architecture of the hardware.
If you are already familiar with the hardware comprising these systems, skip
over this chapter to the one discussing the firmware you wish to use.
Sections in this chapter include:

•

System Overview
-

Front and Rear View of a GS80 System

Front and Rear View of a GS160/320 System

•

Control Panel

•

Master PCI Ports and PCI Box ID

•

Quad Building Block

•

QBB in GS80 Systems

QBB in GS160/GS320 Systems

System Drawers and System Boxes
-

System Drawers in a GS80 System

System Box in a GS160 System

Two System Boxes in System Cabinet 1

System Boxes in System Cabinet 2

•

Hard QBB Numbers

•

QBB and PCI Box Connections

•

Console Serial Bus

•

System Power-Up

Hardware Overview

2-1

2.1

System Overview

In the AlphaServer GS80 system, all the components of the system are
housed in one cabinet. For the GS160 system, the components are
housed in two cabinets, and for the GS320, in three cabinets.

2.1.1

Front and Rear View of a GS80 System

The processors and other modules in a GS80 system are in either one or
two system drawers.

Figure 2–1 Front and Rear View of a GS80 System
GS80

GS80

Front

Rear

CB1

CB2 CB3 CB4

CB5 CB6 CB7 CB8 CB9 CB10 CB11

CB1

CB2 CB3 CB4

CB5 CB6 CB7 CB8 CB9 CB10 CB11

PK-0142-99

2-2

AlphaServer GS80/160/320 Firmware Reference Manual

➊

One AC input box is required for each drawer in the GS80 system. An AC
input box accepts single-phase 30-amp AC power and routes it to the ACto-DC converters.

➋

Power supplies; six are shown. Two are required for each system drawer; a
third provides n+1 redundancy. That is, if one power supply in a power
subrack fails, the system will still function at full power and the failing
power supply can be “hot swapped” for a replacement without powering
down the whole system.

➌

Two system drawers are shown. Each drawer can be pulled out for
maintenance.

➍

The rear view of two system drawers is shown. The cooling fan of a system
drawer can be accessed from the rear of the cabinet. Two I/O risers
protrude from the system drawers (shown as the light rectangles in the
figure). Each I/O riser provides two I/O cables. Two cables connect to one
PCI box.

➎

The front of the cabinet shows two PCI boxes. The cooling fans for the PCI
boxes can be accessed from the front of the cabinet.

➏

The rear view of two PCI boxes is shown. The PCI boxes can be pulled
forward to remove and replace modules.

Hardware Overview

2-3

2.1.2

Front and Rear View of a GS160/320 System

System components are housed in a power cabinet and either one
(GS160) or two (GS320) system cabinets, depending on the size of the
system.

Figure 2–2 System Front and Rear Views (GS160/320)
GS160/320

GS160/320

Front

Rear

System
cabinet 2

System
cabinet 1

Power
cabinet

System
cabinet 1

1
1

3
1

System
cabinet 2

6
PK-0143B-00

Figure 2–2 shows front and rear views of a GS320 system with the doors open.
(At the front of the machine, the power cabinet is on the right. System cabinet 1
is in the middle, and system cabinet 2 is on the left. A GS160 system consists of
the power cabinet and system cabinet 1; there is no system cabinet 2 on a
GS160 system.

➊

Four system boxes are shown. The modules in each system box are
covered by EMI protective shields, exposing only the I/O risers and the
signal input connectors at the front, and I/O risers and power input at the
rear. Colors strips at the side of each system box show the sequence for
adding system boxes: blue, green, orange, brown.

2-4

AlphaServer GS80/160/320 Firmware Reference Manual

➋

A blower in each system cabinet draws air down through the system boxes
and out the front and back of the cabinet. The speed varies as the ambient
temperature changes, keeping the modules at the proper temperature.

➌

I/O connectors. Four connectors are shown for each system box. Each
connector handles one cable and two cables connect to one PCI box.

➍

Signal input connector. Signals conveying data between modules,
components of the console serial bus, and the operator control panel (OCP)
are transmitted over the signal lines. These lines go to the system boxes at
the front of the machine.

➎

The front of the power cabinet reveals the back side of a master PCI box
and one additional PCI box. The rear of the power cabinet shows the front
side of a master PCI box and one additional PCI box.

➏

Two AC input boxes are required for GS160 and GS320 systems. Each box
accepts three-phase 30-amp AC power and routes it to the power supplies.

➐

Power supplies. Each subrack (row of individual power supplies) provides
power to one system box. The rows are color-coded to match the cover of
the system box to which they provide power. Each power subrack accepts
AC input and converts it to 48-volt DC output.
One power supply is routed to one QBB backplane, and there are two per
system box. The extra power supply provides n+1 redundancy.

➑

Power input connectors. Cables providing 48V to the QBB backplanes
enter each system box here.

➒

The hierarchical switch provides logic that controls the transfer of
instructions and data between memory, CPU, and I/O modules in the
QBBs, and between nodes on the console serial bus (see Section 2.8). A
hierarchical switch is needed for 4-QBB GS160 systems and for all GS320
systems. A component called a distribution board provides a similar
purpose in 2-QBB GS160 systems.

Hardware Overview

2-5

2.2

Control Panel

The operator control panel (OCP) is located on the front door of a GS80
system or the front door of the power cabinet in a GS160/320 system.
The OCP contains a keyswitch that allows a user to fully power up or
power down the system, or secure the system from remote access.
Three buttons allow the user to halt or reset the system, or halt the
system with error registers latched (fault).

Figure 2–3 Control Panel
GS320
GS160

GS80

OCP display screen
OFF

Secure
LED
(green)
Halt
Power LED
LED
(yellow)
(green)

Halt

AlphaServer GS-320
Power ON
Keyswitch - ON

Keyswitch

Fault

Reset
PK-0133-00

2-6

AlphaServer GS80/160/320 Firmware Reference Manual

Figure 2–3 shows the operator control panel (OCP) that is located on the front
door of the GS80 cabinet and the front door of the power cabinet in GS160 and
GS320 systems.
Keyswitch
The three-position keyswitch allows the local user to control power and remote
management features. When in the 1 or On position, the system is enabled to
be powered up. A remote system user can power on or power off the system.
When in the 0 or Off position, the system is powered off and cannot be remotely
powered on by a remote system user.
When in the Secure or lock position, the system is powered on but the Halt,
Fault, and Reset buttons and the local and remote management ports are
disabled.
Pushbuttons
Three pushbutton switches are below the display.
The Halt button causes the operating system to perform a halt, and prevents
the console from booting the operating system. This halt stays in effect until
the SRM continue command is executed.
The Fault button is a momentary switch that causes a system reset without
clearing captured error information in the control and status registers (CSRs).
The Reset button is a momentary switch that causes a system reset that clears
error information captured in the CSRs.
LEDs
The Secure LED indicates that the keyswitch has been turned to the Secure
(lock) position. The Halt, Fault, and Reset buttons, as well as the local and
remote management ports, are disabled.
The Power LED indicates that the system is powered on.
The Halt LED will never be the only LED lit. It may be lit in conjunction with
Power, indicating that the system is powered on, remote console operations are
enabled, and the Halt button is pressed or a halt in command has been issued
at the local or remote console. It may be lit along with both other LEDs,
indicating a powered on system, the Halt button has been pressed or a halt in
command has been issued at the local or remote console, followed by turning the
keyswitch to the Secure (lock) position.

Hardware Overview

2-7

2.3

Master PCI Ports and PCI Box ID

A master PCI box provides ports for a local system console device as
well as a modem port for remote connections from the standard I/O
module. The reverse side of a master PCI box allows access to the
DVD/CD-ROM device as well as various ports, including the connection
from the SCM to the operator control panel.

Figure 2–4 Console and Modem Ports on Standard I/O Module
GS80

GS160/320

Rear

Local console
device port
USB0

USB1

Modem port

Node ID
Switch 0-15

CSB
Connector
PK-0147-00

2-8

AlphaServer GS80/160/320 Firmware Reference Manual

Console and modem ports are on each standard I/O module in a master PCI box
for either the system or an individual partition. The console port is at the top of
the module, and the modem port is at the bottom of the module, as shown in
Figure 2–4.
Figure 2–4 also shows the CSB connector and the node ID switch that is on the
right side of each PCI box. The node ID switch is set when a PCI box is
installed to form the PCI box ID; each setting is unique to the system and can
range from 0 –15. This ID appears in show displays that provide information
on the I/O subsystem. For example, the ID appears as the number in the show
system display for PCI nodes. The PCI ID also appears in the SRM show
config display.
Figure 2–5 shows the DVD/CD-ROM device and the ports provided by a master
PCI.

Figure 2–5 Master PCI Ports
GS80

GS160/320

Operator control panel

Keyboard

Front

COM2

Front

Mouse

Parallel port

DVD/CD-ROM

PK-0148-00

Hardware Overview

2-9

2.4

Quad Building Block

The basic processing component of AlphaServer GS80/160/320 systems
is the quad building block (QBB). The backplane for a QBB differs
slightly in GS80 and GS160/320 systems.

2.4.1

QBB in GS80 Systems

A GS80 system can have one or two QBBs.
drawer.

Each QBB resides in a

Figure 2–6 GS80 QBB Backplane
Main and
Auxiliary CPU0
(Flip Backplane 90 )
Power
Mem1
CPU2
Mem3
Power
Directory
Input

(Twist Backplane 180 )

I/O
Risers
Global
CPU3 Port
Mem2 Connectors
CPU1
= ASICs forming Quad Switch
Note:
Mem0

Clock
Splitter
PSM

PK-0129A-99

Figure 2–6 shows the backplane of a GS80 QBB; the arrows show how the
backplane is oriented to form the bottom of a system drawer within which the
QBB is placed. The backplane has connectors for four processors and four
memories, from which the name quad building block derives. The backplane
also has connectors for power input, a main and an auxiliary power module, two
I/O risers, a clock splitter module, and logic for a global port, used to connect
two backplanes.
The gray shaded blocks are ASICs (small processors). The logic in these
components form what is called the quad switch, which regulates data traffic
between modules in a QBB.

2-10

AlphaServer GS80/160/320 Firmware Reference Manual

Figure 2–7 illustrates how modules are mounted in a system drawer. The first
section (➊) shows two CPUs and two memories. In section ➋, these modules
are replicated and rotated 180°. Section ➌ shows the replicated modules in
place. The modules are color-coded (small shaded blocks), but for GS80
systems, you identify the placement of modules by a label on the inside of the
cover of each system drawer. Section ➍ shows the addition of the remaining
modules. Section ➎ shows the QBB rotated 90º, as it would be in a system
drawer in a GS80 system. Note the cooling fan and I/O extenders as seen from
the rear of the system. Section ➏ shows the QBB rotated 180º, as it would be
seen from the front of the system.

Figure 2–7 Elements of a GS80 QBB (System Drawer)

CPU0
Mem1
CPU2
Mem3
Dirctry

PSM

Front View

R
PW
AUX

Clock Splitter Global
I/O Connectors
Port
Connectors
I/O Connectors

M em 0
PSMSpltr
Clk
PWR
in
a
M

Mem1 CPU1

CPU2 Mem2

PU3
Mem3 C

Global
Port
Connectors

Dirctr
y

m3
3 Me
CPU
try
Dirc

PU2
Mem2 C

Mem1
CPU1

Cooling Fan
I/O Connectors
Rear View

Mem0
CPU1
Mem2
CPU3

5
Mem0 CPU0

Main PWR

Clk Spltr

PSM

Aux PWR

CPU0
Mem1
CPU2
Mem3

CPU
Mem
CPU
Mem

CPU0
Mem1
CPU2
Mem3

CPU
Mem
CPU
Mem

AUX P
W

4
Main PWR

CPU0

PK-0130-98

Hardware Overview

2-11

2.4.2

QBB in GS160/320 Systems

GS160/320 system cabinets contain system boxes, each containing two
QBBs. This section shows the backplane as seen from the rear of the
machine in the lowest system box in system cabinet 1.

Figure 2–8 QBB Backplane for GS160/320 Systems
GS160/320

Rear

QBB Backplane Side 1
Main and
Auxiliary
Power
Modules

QBB Backplane Side 2
(Rotate Side 180 )

CPU0
PSM

Mem1
CPU2
Mem3

Clock
Splitter

Global
Port 1

Global
Port 0
Power
Input
I/O
Ports
Mem0

CPU3 Directory
Mem2
CPU1
Note:

= ASICs forming Quad Switch
PK-0105A-99

2-12

AlphaServer GS80/160/320 Firmware Reference Manual

A QBB backplane in a GS160/320 system box is shown in Figure 2–8 as seen in
system cabinet 1 at the rear of the system. The backplane has connectors for
four processors and four memories, from which the name quad building block
derives. The backplane also contains connectors for power input, main and
auxiliary power modules, two I/O risers, and a clock splitter module. Note
global port 0 on side 1 and global port 1 on side 2 of the backplane.
The gray shaded blocks are ASICs (small processors). The logic in these
components form what is called the quad switch, which regulates data traffic
between modules in a QBB.
Figure 2–9 shows stages of adding modules to construct a QBB. At ➊, we begin
with two CPUs and two memories. At ➋, these modules are replicated and
rotated 180° to produce the mountings shown in ➌. Modules are color-coded
(small shaded blocks). Each type of module has a different color, such as blue
for CPUs. A metal bar bisecting the front of the QBB’s support structure is
coded so that module colors match colors on the bar (see Figure 2–12). Section
➍ shows the addition of the remaining modules. Numbers on the bar and
guides on the backplane ensure that modules are inserted in the correct position
and with the right orientation.

Figure 2–9 Elements of a QBB for GS160/320 Systems

PSM

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR

Main PWR

CPU0
Mem1
CPU2
Mem3

Clock
Splitter

CPU0
Mem1
CPU2
Mem3

Mem0
CPU1
Mem2
CPU3

CPU
Mem
CPU
Mem

Mem
CPU
Mem
CPU

CPU0
Mem1
CPU2
Mem3

I/O Connectors
Power
Input
PK-0108-98

Hardware Overview

2-13

2.5

System Drawers and System Boxes

GS80 systems contain one or two system drawers. GS160 and GS320
systems contain one to four system boxes.

2.5.1

System Drawers in a GS80 System

A GS80 system may contain one or two system drawers. Each system
drawer holds a QBB.

Figure 2–10 System Drawers in a GS80 System

QBB0

QBB1

PK-0135-00

2-14

AlphaServer GS80/160/320 Firmware Reference Manual

QBBs are numbered according to the location they occupy in the system cabinet.
As shown in Figure 2–10, QBB0 is the upper and QBB1 is the lower (in a onedrawer GS80 system, there is only QBB0). The SCM and SRM console
firmware show commands display self-test results, system configuration, and
other information that includes these hard QBB numbers, along with soft QBB
numbers used by the firmware and software.
Both numbers are displayed because, for reasons discussed in Section 2.9, the
firmware and software use soft QBB numbers for addressing. While you might
need only the hard QBB number to find a faulty module revealed by a self-test
display or a show command, you may need the soft QBB number when doing
lower-level debugging.
For example, you will need the soft QBB number to interpret any error register
contents displayed with an examine command. And, you need to be able to
relate the soft QBB number to a particular physical location using the hard
QBB number. Thus, both numbers are displayed in power-up self-test displays
and show command displays.

Hardware Overview

2-15

2.5.2

System Box in a GS160 System

A system box consists of two quad building blocks, connected by global
port modules and a distribution board. This section shows how the
system box for a 2-QBB GS160 system is constructed.

Figure 2–11 Elements of a System Box (GS160 Rear Orientation)
GS160/320

Rear

Replicate QBB

Add global port modules
and distribution board

Clk Splttr
Glbl Port 1
Glbl Port
0

PSM

CPU0
Mem1
CPU2
Mem3

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR

Main PWR

Clk Splttr

PSM

CPU0
Mem1
CPU2
Mem3

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR

Main PWR

Clk Splttr

PSM

CPU0
Mem1
CPU2
Mem3

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR

Main PWR

PSM

CPU0
Mem1
CPU2
Mem3
Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR

Main PWR

Rotate QBB and place
backplanes together

PK-0109-99

2-16

AlphaServer GS80/160/320 Firmware Reference Manual

The smallest GS160 system contains one system box. A system box consists of
two QBBs. Figure 2–11 illustrates the construction of a system box. A QBB is
replicated (➊), and rotated 180º (➋). The backplanes are placed together, so
that both global port connections are on the same side (➌ ).
The global port modules (➍) connect the QBBs to a distribution board, allowing
data to flow between modules from both QBBs of the system box. The reverse
side of a system box (see Figure 2–12) shows signal cabling rather than power
cabling.
Figure 2–12 also shows the system box in detail. The bottom shows the center
bar color coding for the reverse side of a system box. Note that there are digits
as well as colors to identify specific CPUs and memories.

Figure 2–12 Reverse Side of System Box (Front of System Cabinet 1)

AUX PWR

PSM

Front

Main PWR

Mem3
CPU2
Mem1
CPU0

Dirctry
CPU3
Mem2
CPU1
Mem0

Signal Cable

Clock Splitter

Center bar
color coding

Directory
(white)

CPU1
(blue)
Mem2
Mem0
(gray)
(gray)

Mem3
(gray)

1 1

2 2

3 3

Clock
Splitter
(green)

Mem1
(gray)

CPU2
(blue)

Aux
Main
Power Power
(yellow) (red)

0 0

CPU3
(blue)

PSM
(orange)
CPU0
(blue)

PK-0124-99

Hardware Overview

2-17

2-18

AlphaServer GS80/160/320 Firmware Reference Manual
Glbl Port 1

Clk Splttr
Glbl Port 0 Glbl Port 1

Glbl Port 0

PSM

CPU0
Mem1
CPU2
Mem3

PSM

CPU0 Mem0
Mem1 CPU1
CPU2 Mem2
Mem3 CPU3
Dirctry
Clk Splttr

Add System Box

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR
Main PWR

CPU0 Mem0
Mem1 CPU1
CPU2 Mem2
Mem3 CPU3
Dirctry
Clk Splttr
Clk Splttr
Glbl Port 0 Glbl Port 1

PSM

CPU0
Mem1
CPU2
Mem3

PSM

Glbl Port 1

AUX PWR
Main PWR

Clk Splttr
Glbl Port 1

Remove distribution
board

Glbl Port 0

PSM

CPU0
Mem1
CPU2
Mem3

Mem0
CPU1
Mem2
CPU3
Dirctry

Glbl Port 0

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR
Main PWR

2.5.3
Two System Boxes in System Cabinet 1

System cabinet 1 of a GS160/320 system can contain two system boxes,
the second stacked on top of the first. The system boxes are connected
through the four global port modules by a hierarchical switch.

Figure 2–13 System Boxes in System Cabinet 1

GS160/320

Rear

Add Hierarchical Switch

PK-0114-99

System cabinet 1 of a GS160/320 system can contain two system boxes. Figure
2–13 shows how two system boxes are placed and connected by the hierarchical
switch. The distribution board is removed from the system box (➊), and the
second system box is replicated and placed over the first system box (➋ ).
All four of the global port modules on the two system boxes are connected by the
hierarchical switch (➌). The positioning of the modules on the reverse (front)
side of system cabinet 1 are as shown in Figure 2–12 on page 2-17.

Hardware Overview

2-19

PSM

Clk Spltr
Glbl Port 0 Glbl Port 1

AUX PWR

Main PWR
AUX PWR
PSM

CPU0 Mem0
Mem1 CPU1
CPU2 Mem2
Mem3 CPU3
Clk Spltr Dirctry

CPU0
Mem1
CPU2
Mem3

Main PWR
AUX PWR

Mem1
CPU0

CPU3 Mem3
Mem2 CPU2
CPU1 Mem1
Mem0 CPU0
PSM

CPU2

AlphaServer GS80/160/320 Firmware Reference Manual
Mem3

CPU3
Mem2
CPU1
Mem0

Glbl Port 1 Glbl Port 0 Glbl Port 1 Glbl Port 0
Clk Spltr
Dirctry Clk Spltr Dirctry

Clk Spltr
Glbl Port 0 Glbl Port 1 Glbl Port 0 Glbl Port 1

Mem0
CPU1
Mem2
CPU3
Dirctry

Main PWR

PSM

CPU0 Mem0
Mem1 CPU1
CPU2 Mem2
Mem3 CPU3
AUX PWR

Replicate
and rotate
system
box(es) 180

Main PWR

AUX PWR

Rear

Main PWR

Rear

CPU0
Mem1
CPU2
Mem3

Glbl Port 0 Glbl Port 1

CPU0
Mem1
CPU2
Mem3

GS320

Clk Spltr

Dirctry Clk Spltr
Glbl Port 0 Glbl Port 1

CPU0 Mem0
Mem1 CPU1
CPU2 Mem2
Mem3 CPU3
Clk Spltr Dirctry

AUX PWR
Main PWR

GS320

Mem0
CPU1
Mem2
CPU3
Dirctry

2-20
Glbl Port 0 Glbl Port 1

Mem0
CPU1
Mem2
CPU3
Dirctry

AUX PWR
Main PWR

2.5.4
System Boxes in System Cabinet 2

A GS320 system contains three or four system boxes. The system boxes
reside in system cabinets 1 and 2 and are constructed as shown in
Figure 2–14. The system boxes are connected through the global port
modules by the hierarchical switch.

Figure 2–14 Elements of System Cabinets 1 and 2

Connect new global port
modules to hierarchical switch

PK-0117-99

Figure 2–14 shows how three or four system boxes are connected in a GS320
system. The system boxes are connected by the hierarchical switch. In an 8QBB system, the two system boxes in system cabinet 1 (➊) are replicated and
rotated 180 sideways (➋ ). In a 6-QBB system, one system box is replicated,
rotated 180 sideways, and occupies the lower position, as shown in the first
icon at the top of the figure.
The four global ports on the replicated unit are connected to the hierarchical
switch to form an 8-QBB system (➌). Note how the module placement appears
in the replicated unit. The positioning of the modules on the reverse (front) side
of the system are as shown in Figure 2–15.

Figure 2–15 Front of System Box in System Cabinet 2

Clock Splitter
Mem3
CPU2
Mem1
CPU0

PSM

Main PWR

AUX PWR

Dirctry
CPU3
Mem2
CPU1
Mem0

Signal Cable

Center bar
color coding

Aux
Main
Power Power PSM
(red)
(yellow) (orange)

CPU2
(blue)
Mem1
(gray)

Clock
Splitter
(green)

Mem3
(gray)

Mem2
(gray)
CPU1
(blue)

2 2

0 0

Mem0
(gray)

3 3

CPU0
(blue)

1 1

Front

CPU3
(blue)

Directory
(white)
PK-0149-99

Hardware Overview

2-21

2.6

Hard QBB Numbers

Hard QBB numbers define the location of a particular QBB in the
system.

Figure 2–16 Hard QBB Numbers
GS80

GS160/320

Front

Rear

QBB7
QBB5
(behind QBB4)

QBB3
QBB0

QBB2

QBB6

QBB0

QBB4

QBB1
QBB1

Hierarchical
Switch

2-22

AlphaServer GS80/160/320 Firmware Reference Manual

PK-0103-00

QBBs are numbered according to the location they occupy in the system, as
shown in Figure 2–16. These are “hard” QBB numbers. The SCM and SRM
console firmware show commands display self-test results, system
configuration, and other information that includes these hard QBB numbers,
which never change, along with soft QBB numbers, which can change with
configuration changes.
Both numbers are displayed because, for reasons discussed in Section 2.9, the
firmware and software use soft QBB numbers for addressing. While you might
need only the hard QBB number to find a faulty module revealed by a self-test
display or a show command, you may need the soft QBB number when doing
lower-level debugging.
For example, you will need the soft QBB number to interpret any error register
contents displayed with an examine command. And, you need to be able to
relate the soft QBB number to a particular physical location using the hard
QBB number. Thus, both numbers are displayed by the show config
command.

Hardware Overview

2-23

2.7

QBB and PCI Box Connections

This section discusses I/O paths between QBBs and PCI boxes.

Figure 2–17 QBB Local I/O Port Numbers
GS80

GS160/320

2
Front

Rear

3
Local I/O port 1
numbers for
QBBs 0, 2, 5,
and 7 (and
0
as seen from
top for GS80)

Local I/O port
numbers for
QBBs 1, 3, 4,
1 and 6

GS160/GS320

Front

PK-0155-00

Figure 2–17 shows the port numbers for the four connectors on the two I/O riser
modules in a QBB. Labels on the cabinets identify local I/O ports.
Figure 2–18 shows how the four local I/O port connectors in QBB0 could be
connected to remote I/O riser ports in two PCI boxes. Although the figure shows
even local ports being connected to even remote risers, and odd to odd, there are
no electrical or physical restrictions on local port/remote riser cabling.
Guidelines are given in the AlphaServer GS80/160/320 Installation Guides.
Equation 2-1 gives the general algorithm for calculating the logical hose
numbers shown in the SRM show config command.

Equation 2-1 Calculating Logical Hose Numbers
(hard QBB number ✕ 8) + (local port number ✕ 2) + remote riser number

2-24

AlphaServer GS80/160/320 Firmware Reference Manual

Figure 2–18 Sample Cabling to PCI Boxes

1-7 1-6 1-5 1-4 R1 1-3 1-2 1-1 0-7
Bus 0
(Logical hose 2)

Bus 1
(Logical hose 3)

0-6 0-5 0-4 R0 0-3 0-2 0-0/1

Bus 1
(Logical hose 1)

1-7 1-6 1-5 1-4 R1 1-3 1-2 1-1 0-7

IOP
logic
in
backplane

0-6 0-5 0-4 R0 0-3 0-2 0-0/1

Bus 0
Bus 1
(Logical hose 6) (Logical hose 5)

Bus 1
(Logical hose 7)

Bus 0
(Logical hose 0)

Bus 0
(Logical hose 4)

QBB0 backplane

From same local I/O riser card, ports 2 and 3

Two local
I/O riser
modules

3
1
0

From same local I/O riser card, ports 0 and 1

Four connectors
maximum per QBB

PK-0156-00

Hardware Overview

2-25

2.8

Console Serial Bus

System firmware resides on nodes connected to the console serial bus
(CSB). This firmware controls power-up, monitors conditions within
the system, alerts users of potential problems, and provides the
capability for partitions and for remote access.

Figure 2–19 Logic Diagram of the Console Serial Bus
PCI (0-15)

System Control
Manager (0 - 7 (with
partitions))

Hierarchical
Switch (0)

Power System
Manager (0 - 7)

Console Serial Bus (CSB)
PK-0102-98

2-26

AlphaServer GS80/160/320 Firmware Reference Manual

When a GS80/160/320 system is plugged in and the main breaker switch is on,
the console serial bus (CSB) and its nodes receive power and are functional.
The system as a whole is not powered up, however. Figure 2–19 shows the total
possible nodes on the CSB for an eight-QBB GS320 system with 8 partitions.
System Control Manager (SCM)
In a non-partitioned system, the central point of control on the CSB is the
master system control manager (SCM). (There may also be a slave SCM that
serves as a standby, defined by the SCM scm_csb_master_eligible
environment variable.)
In a partitioned system, partitions must be maintained independently. Each
partition requires an SCM. Based on information provided when partitions are
set up, one SCM is selected as the master and the rest are slaves. Each SCM,
master or slave, controls parameters relating to the partition where they reside.
SCM hardware resides on the standard I/O module (SIO), and includes an
AM186ES microprocessor, 256 KB of flash ROM, 8K EEPROM, 128 KB of RAM,
and two dual universal asynchronous receiver/transmitters (UARTs). The
master SCM’s microprocessor handles all communication to and from other
nodes on the console serial bus and the control panel. Each SCM, master or
slave, processes I/O to or from local or remote terminals.
Power System Manager(s) (PSMs)
A power system manager (PSM) is a module in a QBB. PSM hardware includes
a microprocessor, flash EEPROM, RAM, three internal IðC buses, and three
analog/digital hardware monitoring devices, which monitor voltages, temperatures, and fan speeds. A PSM also supports a serial interface to each CPU in a
QBB; it uses this interface to direct the testing of, and collect information from,
the CPUs during power-up.
PCI Backplane Manager(s) (PBMs)
A PCI backplane manager (PBM) resides on the backplane of each PCI
subsystem. PBM hardware consists of a microprocessor and associated
peripherals. The PBM monitors environmental sensors (voltage, temperature,
fan) and sends alerts when appropriate. The PBM also maintains an inventory,
including the backplane, standard I/O module (if any), remote I/O riser modules,
PCI module presence (not specific PCI options), and power supplies.
Hierarchical Switch Power Manager (HPM)
AlphaServer GS160 and GS320 systems contain a hierarchical switch whose
logic regulates data and instruction flow between QBBs. The HPM monitors
environmental sensors (voltage, temperature) for the hierarchical switch.

Hardware Overview

2-27

2.9

System Power-Up

At power-up, component self-tests complete, a primary processor is
selected, and control passes to the SRM console.

Figure 2–20 Location of Nodes on the Console Serial Bus
GS160/GS320

Front
PSM2

Each PCI backplane

PSM7

PSM6

PSM3

PBM

SCM on
SIO module
in primary
PCI subsystem
Hierarchical
Switch
PSM5
PSM0
PSM4

PSM1
PK-0106-00

2-28

AlphaServer GS80/160/320 Firmware Reference Manual

Figure 2–20 shows the physical location of nodes on the console serial bus.
Each of these nodes plays a part in system power-up; individual CPU modules
in QBBs called the local CPUs also play a part in power-up and are eventually
replaced by one primary CPU.
The SCM assumes control when someone turns the keyswitch to the Secure
position or when the keyswitch is in the On or 1 position or a console user issues
a power on command. The SCM checks each PSM.
Each PSM powers up its backplane and initiates module self-tests. Each PSM
then powers up each I/O riser, selects a local CPU (for that QBB) and tells that
CPU to probe for standard I/O modules through the cables for that QBB’s I/O
risers. The local CPU performs initialization of various registers, and if a
standard I/O module is found, returns that information to the PSM.
The PSM waits for all self-tests to complete and reports the good CPUs,
memory, and all standard I/O modules found through that QBB’s I/O risers.
The SCM updates the system map to include these results and selects the
primary CPU and “soft” QBB0. The firmware and operating system software
use physical memory addresses whose high-order three bits include the soft
QBB number. The Tru64 UNIX operating system currently requires memory to
start at physical address 0. Since it is possible that hard QBB0 might not
contain a valid memory module, soft QBB0 is assigned to ensure that what the
firmware and software regards as QBB0 contains at least one valid memory
module. Other soft QBB numbers are selected and this “soft system map” is
passed to the PSM.
At this point, the primary processor assigns soft QBB IDs to all remote QBBs.
The primary processor then configures memory, loads the console firmware
from flash EEPROM on a standard I/O module, and transfers control to the
SRM console.

Hardware Overview

2-29

Chapter 3
Remote Console Operations

The system control manager (SCM) firmware provides a command-line
interface that can be used at the local console terminal or at a remote terminal.
Before a remote console can be used, however, you must initialize the modem,
define the dial-out number for a remote pager, and perform other tasks.
This chapter describes tasks performed at the local console terminal to set up
remote terminal operations, as well as operations that can be performed at
either the local or remote terminal to display status or to supply or remove
power from the system or a part of the system.
Sections in this chapter include:

•

Overview of Remote Setup and Operation

•

Remote Operations Command Summary

•

Displaying Help on SCM Console Commands

•

Setting Up for a Remote Console

•

Dialing In and Invoking SCM

•

Transmission Modes

•

Displaying System Status

•

Controlling Power to the System

•

Leaving the SCM Command-Line Interpreter

•

Terminating the Remote Session

NOTE:

Chapter 4 tells how SCM commands define hard partitions. Chapter 6
describes the SCM commands in alphabetical order.

Remote Console Operations

3-1

3.1

Overview of Remote Setup and Operation

This section lists system management tasks to set up and use a remote
console, the related SCM commands, and the place in this manual
where the commands are described.

Figure 3–1 Overview of Remote Setup and Operation

Set variables
for remote console
access (dial-out
number, baud rate...)

Power
On/Off

SCM Console Functions for
remote console operation

Debug
(show status, deposit,
examine, fault, reset)

Set/Clear/Test
Alerts

Initiate or terminate
remote
console session

PK-0112-98

3-2

AlphaServer GS80/160/320 Firmware Reference Manual

One concept of SCM firmware design is that two different people will maintain
AlphaServer GS80/160/320 systems. System monitoring is done by a system
manager, who may be at a remote location in the next room, building, state, or
even country. The system manager then may dispatch a local service technician
to do on-site activities.
Remote Use of the SCM Monitor
The SCM firmware allows a remote user access to the system for general
system monitoring and maintenance. The SCM firmware notifies the system
manager of alert conditions by dialing out through a modem, usually to a pager
held by the remote diagnostician on call.
To enter the SCM console remotely, the remote user dials in through a modem,
enters a password, and then types a special escape sequence that invokes SCM
command mode. (The system remains in whatever state it is in, including
having the operating system running.) You must set up the remote modem
before you can dial in remotely. (See Section 3.4.)
Local Use of the SCM Monitor
Although SCM commands can also be used from the local console terminal,
there is no local notification when an alert condition occurs. A local user must
initially define the dial-out number and set other parameters.
Also, the SCM provides the power off and power on commands that would be
used by a service technician to power off or on the entire system, or a hard
partition.
To enter the SCM locally, the user types the escape sequence on the local serial
console terminal. (The default escape sequence is <Esc><Esc>scm.) The
operating system state does not change upon entering SCM console mode.
Use of the SCM Monitor from the SRM Console
SCM commands can also be executed from a local or remote terminal from the
SRM console by typing scm in front of the SCM command. For example:
P00>>> scm show csb

Remote Console Operations

3-3

3.2

Remote Operations Command Summary

Table 3–1 lists the SCM commands used for setting up and using
remote console terminals, and the sections where examples of the task
can be found.

Table 3–1 SCM Commands Related to Remote Console
Management
Task

Commands

Section

Get help on SCM commands

help or ?

Section 3.3

Set up for remote console management

set init
set dial
set alert
set password
enable remote
enable alert
test alert

Section 3.4

Initialize the modem to prepare it to
send alerts and receive incoming calls

init
set baud

Section 3.4

Dial in and examine the state of the
system

clear alert
show

Section 3.5
Section 3.6

Low-order debugging

examine
deposit

Chapter 6

Halt the system leaving error registers
intact

fault

Chapter 6

Control power to the system

power

Section 3.8

Reset system or CSB component

reset

Chapter 6

Terminate the remote session

hangup

Section 3.10

Leave the SCM command-line
interpreter

quit

Section 3.9

3-4

AlphaServer GS80/160/320 Firmware Reference Manual

3.3

Displaying Help on SCM Console Commands

The help command displays information on the SCM commands. You
can also type a question mark (?) to see this display.

Example 3–1 Help or ?
SCM_E0> help
SCM CLI Version 1.0

2000/27/07

build <fru> <pn> <sn> <mod> <ali> Build FRU Data(pn=2-5-2.4 sn=xxyzzabcde)
build EEPROM
Restore EEPROM RMC default values
clear {alert, port}
Clear alert state, clear COM1 port comm
deposit [-ipr,-spr(-iic,-offset),&mn, &p<csb_adr>,-next<n>,-q,-l,-w,-b] [data]
Write data to a memory location or CSR/IPR
disable {alert, remote, test<n>} Disable remote dial-in, alert dial-out,test-n
el
Type out event log
enable {alert, remote, test <n>} Enable remote dial-in, alert dial-out, test-n
erase
Erase screen
examine [-ipr, -spr, (-iic,-offset),&mn, &p<csb_adr>, -next <n>, -q, -l, -w, -b]
Read a memory location or CSR/IPR
fault [-all, -partition <n>]
Create a system wide FAULT condition
halt {in, out} <-partition <n>,-all>Halt the system(virtual OCP halt button)
hangup
Terminate remote session
help or ?
Display list of SCM commands
init
Initialize the modem
master <cli cmd>
Slave SCM Command to master SCM
power {on, off} [-all, -partition <n>]
Power command
quit
Switch from SCM-CLI mode COM1 port
reset [-all –partition <n>]
System level reset
set flow {com1,local,modem} {hard,soft,both,none}
Set a port's flow control characteristic
set baud {com1,local,modem} <value> Set a port's baud rate
set com1_mode {through,snoop,software_bypass,firm_bypass,local}
Set COM1 operating mode
show{csb,system,status,fru,nvr}
Show various system information
test {alert, &pc<n> test_num}
Trigger an alert or run a CPU test
update {-csb <node_address,…>
Update micro FLASH on CSB node(s)
SCM_E0>

The help command displays information about the commands available from
the SCM firmware. You can also type a question mark (?) to display this
information.

Remote Console Operations

3-5

3.4

Setting Up for a Remote Console

A series of SCM commands must be issued from the local console
terminal to prepare the system to automatically “call out” over a
modem (to a pager, for example) when an alert condition occurs and to
enable the remote user to dial in.

Example 3–2 Sample Setup for a Remote Console
P00>>> <Esc><Esc>scm ➊
SCM_E0> enable remote ➋
SCM_E0> set password newpassword ➌
SCM_E0> set init ate0v0&c1s0=2
➍
SCM_E0> init
➎
Querying the modem port…modem detected
Initializing modem…passed
➏
SCM_E0> set dial atdt9,15551212
SCM_E0> set alert ,,,,5085551234#;
➐

SCM_E0> enable alert ➑
SCM_E0> test alert ➒

To enable remote connections, a user at the local console must use the SCM
command language to set initial parameters. Example 3–2 shows a sample
sequence of SCM commands. A detailed description of each command is given
in the SCM command reference chapter, Chapter 6.

➊

From the SRM console, type the escape sequence that returns you to the
SCM console prompt. The default sequence is <Esc><Esc>scm.

➋

The enable remote command directs the SCM to accept incoming calls
through the local modem. Note: the keyswitch on the operator control panel
must not be in the Secure position, which prevents remote dial-in.

➌

The set password command requests that a remote user supply a password
when dialing in. The set password command does not affect local access to
the system. The default remote access password is wffirmware.

➍

The set init command gives the initialization string for the local modem.
Currently supported modems and their initialization strings are:
Hayes Accura 336/56k
Compaq Microcom 510

3-6

ate0v0&c1&k3s0=2
ate0v0&c1s0=2

AlphaServer GS80/160/320 Firmware Reference Manual

3Com USR Courier V.Everything

ate0v0&c1so=2

3Com USR 56K* (5676) (Japanese)
AT&T Dataport 14.4
MultiTech MT5600ZDS
Aiwa PV-BW5610 (Japanese)

ate0v0&c1so=2
ate0v0&c1so=2
ate0v0&c1so=2
ate0v0&c1so=2

Omrom ME5614D (Japanese)

ate0v0&c1so=2

➎

The init command initializes the modem. At this point, the modem is
configured for remote dial-in and can be accessed through the modem.

➏

The set dial command specifies the dial-out string sent to the modem when
an alert condition occurs. The dial string is case sensitive. The SCM
automatically converts all alphabetic characters to uppercase. In the
example, the following characters are used:
AT = Attention.
D = Dial
T = Tone (for touch-tone)
9 = Number for an outside line
, = Pause for 2 seconds
15551212 = Number to be dialed (usually a paging service)

➐

The set alert command defines the time to wait for the remote pager to
respond, and a message passed to the pager (usually a telephone number for
the remote user to dial in). In the example, the following values are used:
,,,, = Each comma (,) provides a 2-second delay. In this example, a delay of
8 seconds is set to allow the paging service to answer.
5085551234 The message displayed on the remote pager.
# = Terminating character
; = Returns modem to command mode

➑

The enable alert command directs the SCM to monitor alert conditions and,
when one occurs, to initiate the dial-out sequence defined by the set init and
set dial commands issued previously.

➒

The test alert command directs the SCM to generate an alert condition and
test the dial-out procedure. (The show status command reports on alert
conditions detected by the SCM.)

Remote Console Operations

3-7

3.5

Dialing In and Invoking SCM

To access a system from a remote console terminal, dial the modem,
enter the modem password at the # prompt, and type the escape
sequence. Use the hangup command to terminate the session.

Example 3–3 Sample Remote Dial-In Dialog
AT ➊
OK
ATDT15085551212
➋
# password
P00>>> <Esc><Esc>scm
SCM_E0> show status

➌
➍

System Management Settings
RMC escape sequence
Local Baud/flow control
COM1 Baud/flow control
Modem Baud/flow control
COM1 mode
OCP power switch
OCP halt
OCP secure
Remote Access
Remote User
Remote status
Alerts
Modem password
Modem init string
Modem dial string
Modem alert string
Alert pending
Most recent alert
SCM_E0> clear alert ➏
Pending alert cleared
SCM_E0> hangup ➐

3-8

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

[ESC][ESC]scm
57600 / soft
57600 / hard
57600 / hard
Pass-through
On
Deasserted
Non-Secure
Enabled
Connected
Using SCM CLI
Enabled
newpassword
ate0v0&c1s0=2
atdt9,15551212
,,,,5085551234#
➎
YES
User initiated…from CSB node e0

AlphaServer GS80/160/320 Firmware Reference Manual

Example 3–3 shows a brief session from a remote console.

➊
➋

AT = Attention. Standard modem response when ready.

➌

After the password has been given, the SCM banner displays. The user is
connected to the modem port, and is at whatever level the system or
partition was operating at dial-in (the SCM console, the SRM console, or
the operating system level.) You can type <Esc><Esc>scm to return to
the SCM console.

➍

The show status command is a reasonable first command in the event you
are dialing in to a system after receiving an alert on a pager. It shows
current settings for remote access and the most recent alert.

➎

The most recent alert is shown to be user-initiated by a test alert
command from CSB node e0.

➏

The remote user clears the alert, so that other alerts can be logged (such as
overtemperature). The remote user would then log a call to the service
technician to check on the condition causing the alert.

➐

The hangup command terminates the remote connection.

The remote user types the dial-in password set with the SCM command
set password. The password is not displayed.

Remote Console Operations

3-9

3.6

Transmission Modes

By default, all data transmissions between the local and remote
console devices and the system pass through the SCM. You can select
other modes of transmission.

3.6.1

Through Mode and Local Mode

In through mode, data passes between the local and remote console
devices and the system through the SCM. In local mode, the remote
console can only communicate with the SCM, not the system.

Figure 3–2 Through and Local Modes
Through Mode -All data passes through SCM

Local Mode -Local data passes through SCM
Remote can reach only SCM
Remote User

Remote User

Modem

SCM
data
data

Operating System
or
SRM Console

SCM
data
data

Operating System
or
SRM Console

Standard I/O module
Modem

Modem

PK-0125B-00

3-10

AlphaServer GS80/160/320 Firmware Reference Manual

Through Mode
Through mode is the default operating mode. The SCM routes every character
of data between the system (the operating system or the SRM console) 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 escape sequence, it enters the SCM CLI. This
mode is illustrated by the left half of Figure 3–2.
If you wish to change from another transfer mode to local mode, you can use the
SCM set com1_mode through command.

Example 3–4 Set com1_mode through Command
SCM_E0> set com1_mode through

Local Mode
In local mode, only the local port can communicate with the system; the modem
is prevented from sending characters to the system, but a remote user can still
enter the SCM from the modem. This mode is illustrated by the right half of
Figure 3–2.

Example 3–5 Set com1_mode local Command
SCM_E0> set com1_mode local

Remote Console Operations

3-11

3.6.2

Bypass Modes

The bypass modes determine how much part the SCM plays in data
transfers between the system and the local or remote console device.

Figure 3–3 Bypass Modes
Snoop Mode -Data bypasses the SCM,
which listens passively for
SCM escape sequence.
If detected, enter SCM CLI.
Remote User

Soft Bypass Mode -Remote data bypasses the SCM,
which listens passively for
loss of carrier. If detected,
enter Snoop mode.
Remote User
Modem

Modem

SCM escape?

Loss of carrier?

Operating System
or
SRM Console

SCM

Modem

Firm Bypass Mode -Disables SCM. Can switch to
other modes from SRM or from
local console device.

Hard Bypass Mode -Jumper on standard I/O
disables SCM.

Remote User

Modem

Operating System
or
SRM Console

Operating System
or
SRM Console
SCM

SCM

Modem

Operating System
or
SRM Console

Modem
PK-0125C-00

Figure 3–3 shows the data flow in the various bypass modes. Note that the
local terminal is still connected to the SCM and can still enter the SRM to
switch the com1_mode to alter the bypass mode, if necessary. In any of the
bypass modes, when the system loses power, the default is snoop mode.

3-12

AlphaServer GS80/160/320 Firmware Reference Manual

Snoop Mode
In snoop mode, all data bypasses the SCM as it passes between the system and
the remote console device. 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. This mode is selected by the command set com1_mode
snoop.
The escape sequence is also passed to the system. 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. It also responsible for monitoring modem connectivity.
Snoop mode is useful when you want to monitor the system but also ensure
optimum transfer speed between the system and the remote console device.
Soft Bypass Mode
In soft bypass mode, the SCM is again bypassed, but it listens passively for loss
of carrier. 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. This mode is
selected by the command set com1_mode software_bypass.
Soft bypass mode is useful if system management applications need to perform
a remote binary download, because it ensures that the SCM does not accidentally interpret some binary data as the escape sequence. 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, or you can hang up the
current modem session and reconnect it.
Firm Bypass Mode
In firm bypass mode, the SCM is disabled. The SCM does not configure or
monitor the modem, and the SCM dial-in and call-out features are disabled.
You select this mode with the command set com1_mode firmware_bypass.
This mode is useful if you want the system, not the SCM, to control the modem
port and you want to disable SCM remote management features. You can switch
to other modes by resetting the SRM com1_mode environment variable.
Hard Bypass Mode
In this mode, the SCM is disabled by a jumper on the standard I/O module.

Remote Console Operations

3-13

3.7

Displaying System Status

The show command displays the status of the requested components of
the system. Examples of the three “systemwide” show commands are
given in this section. See Chapters 6 and 7 for SCM and SRM
commands that display system and/or partition status.

3.7.1

Show CSB

The show csb command displays a list of all known nodes on the
console serial bus.

Example 3–6 Show CSB Command
SCM_E0> show csb

➊

➋

CSB Type

➌

Firmware Revision

➍

FSL Revision

Power State

10
11
12
13
15
16
30
30
c0
c1
c2
c3
c0
c1
c2
c3
31
31
c4
c5
c6
c7
c4
c5
c6
c7

PBM
PBM
PBM
PBM
PBM
PBM
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
IOR2
IOR3
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
IOR2
IOR3

X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)

X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)

X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

3-14

➎

➏

ON
ON
ON
ON
ON
ON
ON
ON

AlphaServer GS80/160/320 Firmware Reference Manual

➐

32
32
c8
c9
ca
cb
c8
c9
33
33
cc
cd
ce
cf
cc
cd
40
e0
e1
e2
e6

PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
HPM
SCM MASTER
SCM SLAVE
SCM SLAVE
SCM SLAVE

➊

The user enters the show csb command.

➋

The possible addresses on the console serial bus run from 10-1F (PBM), 3037 (PSM), 40 (HPM), and E0-EF (SCM). This column identifies the
address (hexadecimal) of each node on the CSB. You can use this address
to identify PCI subsystems (for example, in a power off command) to
replace a module in such a subsystem without powering off the entire
system.

➌

This column identifies the type of module at each address.

➍

This column identifies the firmware revision level of the firmware code
residing at this address.

➎

This column identifies the firmware revision level of the fail-safe loader
residing at this address.

➏

This column gives the power state of the CSB node. In the example, all
nodes are On. The column would show Off for nodes whose power had
been removed for a hot or warm swap operation.

➐

X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)

X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)

X05.7
X05.7
X05.7
X05.7
X05.7

(11.03/01:11)
(11.03/01:13)
(11.03/01:13)
(11.03/01:13)
(11.03/01:13)

X5.7 (06.09)

SrvSw: NORMAL

X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)

ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON

Ineligible
Ineligible
Ineligible

This column lists the service status of the node; NORMAL means that
power is being supplied to the node. SERVICE means power is not being
supplied to the node; it is ready for removal and replacement operations by
field service. This column also lists whether an SCM node is eligible to
serve as SCM master in a partitioned system. See Chapter 4 for more
information on partitions and master and slave SCMs.

Remote Console Operations

3-15

3.7.2

Show System Command

The show system command displays an overall system summary.

Example 3–7 Show System Command
SCM_E0> show system
System Primary QBB0 : 1
System Primary CPU : 1 on QBB1

➋

➌

➍

➎

➊
➏

➐ ➑

➒

➓

➀

Par hrd/csb CPU Mem
QBB#
3210 3210

IOR3 IOR2 IOR1 IOR0
(pci_box.rio)

GP QBB
Mod BP

Dir PS Temp
Mod 321 (ºC)

(3) 0/30
(0) 1/31
(2) 2/32
(1) 3/33

Px.x P2.0 Pf.1 Pf.0
P4.0 Px.x Px.x Px.x
Px.x P0.0 Px.x P3.0
--.- --.- Px.x P5.0

P
P
P
P

--PP ---P
--PP --PP
--PP ---P
--PP ---P

HSwitch

Type

HPM40

4-port

➃

PCI Rise1-1
Cab 7 6 5 4
10
12
13
14
15
1f

- - - - - - - - - - - - - - - - - - -

Cables 7 6 5 4 3 2 1 0

➄

➁

- - - - P P P P

P
P
P
P

PPP
PPP
PPPP-

28.0
30.0
26.5
28.1

Temp(ºC)

➂

26.0

➅

➆

➇

Rise1-0
3 2 1

Rise0-1
7 6 5 4

Rise0-0
3 2 1

RIO
1 0

PS
21

Temp
(ºC)

- - - - - - - - - - - - -

- L - L
- - - - - L - - L L - - - - - H

- - S
- L S
- - S
L - S
- - S
L - S

- P
- P
- P
- P
- P
P P

-P
PPPP
PP
PP

32.5
32.5
32.5
32.5
32.5
32.5

Example 3–7 shows a show system command for a 4-QBB system.

➊ The display shows the system primary QBB and CPU.
➋ The hard partition number (if no hard partitions, a dash is displayed).
➌ The hard QBB number (defined by the location of the QBB; see Section 2.4)
and the CSB address for the power system manager (PSM) for the QBB.

➍ CPU self-test results, identified by the slot number in the QBB. Note that
not all QBBs are fully populated with four CPU modules.

➎ Memory self-test results, identified by the slot number in the QBB. Note
that each QBB has two CPUs and one or two memory modules.

3-16

AlphaServer GS80/160/320 Firmware Reference Manual

➏ Status of I/O risers in the QBB.

➐
➑
➒
➓
➀
➁

➂
➃
➄

P passed and powered on
p passed and powered off
m.n m= PCI box (0-f), n = remote I/O riser (0,1)
x.x nothing is connected
Global port self-test results for the QBB.
QBB backplane self-test results.
Directory module self-test results for the QBB.
Status of the power supplies to the QBB. Note that QBBs 0 and 1 have
redundant power supplies, while QBBs 2 and 3 do not.
Temperature of the QBB.
This section of the report gives the status of the hierarchical switch.
Possible values are
P passed
V valid; present, but may not be turned on
* present
not present
Temperature surrounding the H-switch.
The number of the PCI cabinet for which information is displayed. These
numbers are defined by the node ID switch setting.
The status of the slots in the PCI card cages connected to the I/O risers.
S standard I/O module
* present
- not present
L Low power dissipation
M Medium power dissipation
H High power dissipation

➅ Status of remote I/O riser P = present, - = not present.
➆ Status of power supplies to the PCI box.
P passed and powered on
p passed and powered off
F failed and powered on
f failed and powered off
* present but no status yet
- not present

➇ Temperature of the PCI box.

Remote Console Operations

3-17

3.7.3

Show FRU Command

The show FRU command lists the field-replaceable units (FRUs) in the
system.

Example 3–8 Show FRU Command
SLV_E2>

➊

show fru

FRUname
PBP0
PBP0.SIO
PBP0.RIO0
PBP1
PBP1.SIO
PBP1.RIO0
PBP2
PBP2.SIO
QBB5
QBB5.PSM
QBB5.PWR
QBB5.AUX
QBB5.CPU0
QBB5.CPU1
QBB5.MEM1
QBB5.MEM1.DIM0
QBB5.MEM1.DIM1
QBB5.MEM1.DIM2
QBB5.MEM1.DIM3
QBB5.MEM1.DIM4
QBB5.MEM1.DIM5
QBB5.MEM1.DIM6
QBB5.MEM1.DIM7
QBB5.IO01
QBB5.IO23
QBB5.GP
SLV_E2>

3-18

➋

E Part#
02 00-00000-00.A00
00 54-B4190-BA.A01
00 B4171-AA.D02
42 54-25027-01.A02
00 B4190-BA.B01
00 B4171-AA.D02
02 00-00000-00.A00
00 54-B4190-BA.A01
00 54-25043-02.D01
00 54-25074-01.E02
00 54-25017-01.D01
00 54-25123-01.D03
00 B4115-AA.B02
00 54-B4115-AA.B02
00 54-B4150-AA.C01
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00 54-24941-BA. C02
00
-B4170-AA.D01
00
-B4170-AA.D01
00 54-30330-02.A01

➌

➍

➎

Serial#
Model/Other Alias/Misc
NI00000000 FRU
REG
NI91960002 OB5QBB1
NI93473157
NI23234454 OB5QBB1
NI93160206
NI93473157
NI00000000 FRU
REG
NI91960002 OB5QBB1
NI92460907 OB5QBB1
NI91860246 OB5QBB1
NI90665951 OB5QBB1
NI93060053 .......... ................
NI91360068 EV6
OB2QB3
NI91360077 OB5QBB1
NI90863268 OB5QBB1
AY305#J0
AY305&J0
AY305=K0
AY305<K0
AY305XI0
AY305DJ0
AY305CJ0
AY305BJ0
NI93871029 .......... ................
NI93870976 .......... ................
NI91360395 OB5-F
FAKEGP

AlphaServer GS80/160/320 Firmware Reference Manual

Example 3–8 shows a show fru command issued from a local or remote console
terminal connected to a particular hard partition. (See Chapter 4 for a
discussion of partitions.)

➊

The name of the FRU:
PBP
SIO
RIO
QBB
PSM
PWR
AUX
CPU
MEM
DIM
IO
GP

➋
➌
➍
➎

PCI backplane
Standard I/O module
Remote I/O riser (located in PCI box)
Quad building block
Power system manager module
Main power module
Auxiliary power module
CPU module
Memory module
DIMM memory array
Local I/O riser (located in QBB)
Global port module

Part number by which the FRU can be ordered.
The serial number of the FRU.
Optional manufacturing specifications; usually blank.
Optional manufacturing specifications; usually blank.

Remote Console Operations

3-19

3.8

Controlling Power to the System

Once you have determined the cause of a system problem, you may
want to power off the system or a particular component of the system.
This can be done remotely, but unless the situation is catastrophic, it is
probably best to let the local service technician handle power on and
power off.

Example 3–9 Power Off Command
SCM_E0> show system
System Primary QBB0 : 1
System Primary CPU : 1 on QBB1
Par hrd/csb CPU Mem
QBB#
3210 3210

IOR3 IOR2 IOR1 IOR0
(pci_box.rio)

GP QBB
Mod BP

Dir PS Temp
Mod 321 (ºC)

(3) 0/30
(0) 1/31
(2) 2/32
(1) 3/33

Px.x P2.0 Pf.1 Pf.0
P4.0 Px.x Px.x Px.x
Px.x P0.0 Px.x P3.0
--.- --.- Px.x P5.0

P
P
P
P

HSwitch
HPM40

--PP ---P
--PP --PP
--PP ---P
--PP ---P
Type
4-port

Cables 7 6 5 4 3 2 1 0
- - - - P P P P

➊

F
P
P
P

Rise1-0
3 2 1

Rise0-1
7 6 5 4

Rise0-0
3 2 1

RIO
1 0

PS
21

Temp
(ºC)

10
12
13
14
15
1f

- - - - - - - - - - - - -

- L - L
- - - - - L - - L L - - - - - H

- - S
- L S
- - S
L - S
- - S
L - S

- *
- *
- *
- *
- *
* *

-P
PPPP
PP
PP

32.5
32.5
32.5
32.5
32.5
32.5

SCM_E0> power off –par 0,3

28.0
30.0
26.5
28.1

Temp(ºC)
26.0

PCI Rise1-1
Cab 7 6 5 4
- - - - - - - - - - - - - - - - - - -

PPP
PPP
PPPP-

➋

➊ The show system command reveals a QBB backplane as failing.
➋ The user removes power from hard partitions 0 and 3 (hard QBBs 0 and 1)
in preparation for replacing a system box, leaving the remaining partitions
up and running.

3-20

AlphaServer GS80/160/320 Firmware Reference Manual

3.9

Leaving the SCM Command-Line Interpreter

It is often useful in debugging to leave the SCM command-line
interpreter and return to the SRM interpreter. The quit command
exits the SCM and returns control to the COM1 port, through which the
SRM firmware communicates.

Example 3–10 Using Quit to Return to SRM
SCM_E0> quit
➊
Returning to COM1 port.
P00>>> boot ➋
[system boots and displays prompt]

➊ The quit command does not terminate the modem connection; rather, it
transfers I/O operations from the SCM to the COM1 port, where the user
can issue SRM commands.

➋ The remote user boots the operating system to return the system to work.

Remote Console Operations

3-21

3.10 Terminating the Remote Session
The hangup command terminates the remote session, disconnecting
the remote modem and returning I/O to the COM1 port.

Example 3–11 Using the Hangup Command
SCM_E0>
SCM_E0>

hangup

➋

➊

The hangup command terminates the remote connection.

➋

In this case, the hangup command was issued by a user at the local
console, so the SCM prompt appears. The hangup command can be
issued either by the remote user or at the local console device.

3-22

AlphaServer GS80/160/320 Firmware Reference Manual

Chapter 4
Partitions

Partitions are defined as individual subsets of a system’s computing resources,
each of which is capable of running a copy, or instance, of an operating system.
This chapter describes hard and soft partitions and the firmware used to define
them. Sections include:

•

Maintaining Partitions Locally

•

Hard and Soft Partitions

Hard Partitions

Soft Partitions

•

Hardware Requirements

•

Defining Hard Partitions

•

SCM Commands That Define Hard Partitions

Detailed Directions for hp_qbb_mask

Defining Soft Partitions
-

SRM Commands That Define Soft Partitions

Detailed Directions for lp_io_mask

Detailed Directions for lp_cpu_mask

Detailed Directions for lp_mem_size

Detailed Directions for lp_shared_mem_size

•

Lpinit Command

•

Soft Partitions Within Hard Partitions

•

Master and Slave SCMs

•

SCM Functionality from Master and Slave SCMs

Partitions

4-1

4.1

Maintaining Partitions Locally

Partitions are monitored at the local site using the system management
console (SMC).

Figure 4–1 Maintaining Multiple OS Instances at the SMC

AlphaServer GS320

Partition 3
Partition 2
Partition 1

PK-0100C-99

4-2

AlphaServer GS80/160/320 Firmware Reference Manual

Figure 4–1 shows a GS320 system with three partitions, each maintained at the
system management console by a separate invocation of a terminal emulator.
The system management console may also be used from remote locations, or the
system administrator can dial in from a remote serial terminal or from a system
using terminal emulator software. See the AlphaServer GS80/160/320 System
Management Console Installation and User’s Guide for information about this
console device.

Partitions

4-3

4.2

Hard and Soft Partitions

The firmware supports two types of partitioning: hard and soft.

4.2.1

Hard Partitions

Hard partitions are defined by naming the QBBs in each partition.

Figure 4–2 Hard Partitions
QBB7

GS160/320

QBB3

QBB2

QBB6

QBB0

QBB4

QBB5
(behind QBB4)

Rear

QBB1

7
6

2
5

1
0
Partition 0
(QBBs 0, 1, 2, and 3)

4
Partition 1
(QBBs 4 and 5)

Partition 2
(QBBs 6 and 7)
PK-0151-00

4-4

AlphaServer GS80/160/320 Firmware Reference Manual

As shown in Figure 4–2, hard partitions are defined along QBB boundaries.
The figure shows a GS320 system with eight QBBs divided into three hard
partitions.
There is no sharing of CPU, memory, or I/O resource between hard
partitions. The boundaries of these partitions are considered “hard.”
An instance of an operating system may run in each hard partition; these
instances run completely independently of each other.
Tru64 UNIX instances do support individual applications using a specified
percentage of a given resource, such as processor sets. This type of resource
partitioning is described in detail in the Tru64 UNIX System Management
manual.
OpenVMS implements resource sharing differently, building on SRM firmwarebased entities called soft partitions, discussed next.

Partitions

4-5

4.2.2

Soft Partitions

Soft partitions are defined by naming the specific CPUs, memory
allocation, and I/O modules comprising each partition. CPUs can be
moved from one instance to another as computation load changes.
Also, soft partitions allow instances to share memory. Only OpenVMS
Galaxy is an implementation of soft partitions.

Figure 4–3 Soft Partitions
CPU CPU CPU CPU
I/O

CPU CPU CPU CPU

Private Memory

CPU CPU CPU CPU

CPU CPU CPU CPU
Private Memory

CPU CPU CPU CPU
I/O

I/O

Shared Memory

I/O

Private Memory

I/O

CPU CPU CPU CPU

Private Memory

CPU CPU CPU CPU

Private Memory

I/O

I/O
PK-012HP-00

4-6

AlphaServer GS80/160/320 Firmware Reference Manual

Soft partitions allow a portion of memory to be defined as shared
memory; they also allow CPUs to be reassigned by agreement of the
operating system instances running in the partitions. The boundaries
defined by the firmware are thus considered “soft.”
Figure 4–3 shows a GS320 system with eight soft partitions set up on QBB
boundaries. Each partition has private memory. In addition, you can allocate
shared memory that all instances can use, as shown in the center of the
diagram.
In addition to shared memory, soft partitions differ from hard partitions in that,
with soft partitions, operating system instances may agree to share CPU
resources. CPUs can be reassigned to different instances as load varies.
Soft partitions are defined using the SRM firmware. The division of resources
defined can be thought of as a starting point. Once an operating system
instance is running in each soft partition, resources can be reassigned as needed
at the operating system level. See the OpenVMS Alpha Galaxy and
Partitioning Guide for more information on this type of resource sharing.

Partitions

4-7

4.3

Hardware Requirements

A partition requires at least one CPU, one memory, an I/O module, and
a master PCI box with a standard I/O module.

Figure 4–4 Hardware Requirements for Each Partition

1 CPU
Module

64 MB Memory

1 IOP
(I/O Riser 0)

1 PCI master box with a standard I/O module
PK-003HP-99

4-8

AlphaServer GS80/160/320 Firmware Reference Manual

A hard or soft partition requires at least one CPU (resident in the QBB with
I/O) and 64 Mbytes of memory. I/O requirements are at least one local I/O riser
(IOR0) be present per partition connected to a master PCI box. A master PCI
box is one with a DVD/CD-ROM drive and keyboard and mouse ports, etc., and
contains a standard I/O module with local and modem ports for connection to a
console device. (Two I/O risers are supported by one QBB; if both are present in
a QBB, they cannot be split between partitions.)
With hard partitions, at least one QBB is required per partition. Soft partitions
allow more flexible assignment of resources; however, the two I/O riser modules
in a QBB cannot be split between partitions.
The maximum number of partitions varies according to the configuration. With
hard partitions, a two-drawer GS80 supports two hard partitions. A partition
may include more than one QBB. For example, an 8-QBB GS320 system could
have two partitions, one with five QBBs and one with three QBBs.
With soft partitions, a 2-QBB system is still limited to only two soft partitions
while an 8-QBB GS320 system supports up to eight soft partitions. The number
of soft partitions is limited by the constraint that the two I/O riser modules in a
QBB cannot be split between partitions.
Each partition must include a master PCI box with a standard I/O module. The
standard I/O module contains both SRM firmware and SCM firmware. Hard
partitions are defined using the SCM firmware. Soft partitions are defined
using the SRM firmware.

Partitions

4-9

4.4

Defining Hard Partitions

4.4.1

SCM Commands That Define Hard Partitions

Use the SCM set command for the hp_count and hp_qbb_maskn
environment variables, and the power on command for initialization.

Figure 4–5 SCM Commands for Hard Partitions
P0
SCM environment variables
define:

1. Number of partitions:
hp_count (0, 2, 3, ... 8)
SCM_E0> set hp_count 3

Partition 0

2. QBBs in each partition:
hp_qbb_mask* (bit mask)
QBB0

SCM_E0> set hp_qbb_mask0 = 3
SCM_E0> set hp_qbb_mask1 = C
SCM_E0> set hp_qbb_mask2 = F0

QBB1

QBB2

QBB3

QBB4

QBB5

QBB6

QBB7

QBB2

QBB3

QBB4

QBB5

QBB6

QBB7

QBB2

QBB3

QBB4

QBB5

QBB6

QBB7

Partition 1

QBB0

QBB1

Partition 2

Power on commands
initialize partitions defined:
SCM_E0> power on -all

QBB0

QBB1

P0
P1

PK-001HP-99

4-10 AlphaServer GS80/160/320 Firmware Reference Manual

At the SCM prompt, you set a value for the hp_count environment variable to
define the number of hard partitions on your system, and values for
hp_qbb_maskn environment variables to define the QBBs in each partition.
Figure 4–5 and Table 4–1 give an overview of the environment variables and
what they do. Environment variable settings for the hp_qbb_maskn are
discussed in the next section.

Table 4–1 SCM Environment Variables for Hard Partitions
Environment
Variable

Definition

hp_count n

The number of hard partitions you wish to create on the
system. Possible values are 0 (partitions disabled), 1 (for one
partitions), 2 (for two partitions), 3 (for three partitions), and so
forth, to a maximum of 8.

hp_qbb_mask* x

For the *, you supply the number of the partition, which may
be 0, 1, 2, up to 7. Partition numbers must be in sequence; for
example, you could not have partitions 0, 3, and 8 only.)The
value x gives a binary mask indicating which QBBs you want
included in the partition. See Section 4.4.2 for detailed
examples.

A power on –par n command supplies power to each partition, which goes
through its own power-up process, displayed at the partition’s console window.
You can also do a power on –all command to initialize all partitions as shown
in Figure 4–5.
If you are defining partitions on a system that is already powered on, issue a
reset –all command to initialize the system with the new partition definitions.
Once a partition is powered on or reset, you will notice that show displays
reflect CPUs, CSB nodes, adapters, and devices that are numbered beginning
with 0 for each hard partition. The only exception is the hard QBB number,
which remains as though the system were not partitioned. Any commands that
use the CPU number, CSB node address, adapter number, or device number
must reflect the soft numbering given in the show commands for the individual
partition.

Partitions

4-11

4.4.2

Detailed Directions for hp_qbb_mask

The hp_qbb_mask environment variable is set to a value that creates a
binary mask in which a bit set to 1 indicates that an individual QBB
belongs to a partition.

Figure 4–6 Sample QBB Bit Masks
Partition 0
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
0 0 0 0 0 0 1 1

= hex value 3

Partition 1
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
0 0 0 0 1 1 0 0

= hex value C

Partition 2
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
1 1 1 1 0 0 0 0

= hex value F0
PK-002HP-99

4-12 AlphaServer GS80/160/320 Firmware Reference Manual

QBB modules can be assigned to partitions in any order, although there are
considerations for maximum efficiency and reliability, as described in the
manual Getting Started with Partitions. Bit values for one nibble of data are as
follows:
Hex

Binary

Hex

Binary

0000

1000

0001

1001

0010

1010

0011

1011

0100

1100

0101

1101

0110

1110

0111

1111

Example 4–1 shows the SCM commands used to create hard partitions for the
configuration shown in Figure 4–5.

Example 4–1 Sample Hard Partition Setup
SCM_E0> set hp_count 3
SCM_E0> set hp_qbb_mask0 3
SCM_E0> set hp_qbb_mask2 C
SCM_E0> set hp_qbb_mask1 F0
SCM_E0> power on -all
Powering on Hard_partition_0 consisting of
QBB0
QBB1
Powering on PCI Box 0
Powering on PCI Box 1
.
.
.

Partitions

4-13

4.5

Defining Soft Partitions

4.5.1

SRM Commands That Define Soft Partitions

Soft partitions are defined by setting environment variables that define
the number of partitions, as well as the CPUs, I/O risers, and memory
sizes of each partition, the size of shared memory, and the partition to
receive error interrupts. Soft partitions are initialized with the lpinit
command.

Figure 4–7 Soft Partitions
SRM environment variables
define:

1. Number of partitions:
lp_count (0, 1, 2, 3, ... 8)
P00>>>> set lp_count 3
2. Resources in each partition:
P00>>> set lp_io_mask0 1
P00>>> set lp_cpu_mask0 F
P00>>> set lp_mem_size0 6GB

Partition 0

P00>>> set lp_io_mask1 6
P00>>> set lp_cpu_mask1 FF0
P00>>> set lp_mem_size1 12GB

Partition 1

QBB0

QBB1

QBB2

QBB3

(CPUs 0 - 3)

QBB0

QBB1

QBB2

QBB3

(CPUs 4 - 11)
P00>>> set lp_io_mask2 8
P00>>> set lp_cpu_mask2 F000
P00>>> set_mem_size2 10GB

Partition 2
QBB0

P00>>> set lp_shared_mem_size 4GB
P00>>> set lp_error_target 0

Lpinit command
initialize partitions defined:

QBB1

QBB2

QBB3

(CPUs 12-15)

P00>>> lpinit
PK-001LP-99

4-14 AlphaServer GS80/160/320 Firmware Reference Manual

You set values for environment variables to define the number of partitions, the
CPU, memory, and I/O resources belonging to each partition, the amount of
shared memory, and the partition to receive error interrupts. Figure 4–7 and
Table 4–2 give an overview of the environment variables and what they do.
Succeeding sections describe the more complex environment variables and the
lpinit command, which initializes soft partitions.

Table 4–2 SRM Environment Variables for Soft Partitions
Environment Variable

Definition

lp_count n

The number of soft partitions to create. Possible
values:
0

Default. All IOPs, CPUs, and memory are
assigned to one soft partition. No shared
memory is defined.

One soft partition is created (partition 0).

2-8

From two to eight soft partitions can be
defined.

lp_io_mask* x

For the *, supply the partition number (0 – 7). The
value x gives a binary mask indicating the soft QBB
numbers (as displayed by show config) for QBBs
(containing I/O risers) to be included in the
partition. See Section 4.5.2 for details.

lp_cpu_mask* x

For the *, supply the partition number. The value x
gives a binary mask indicating which CPUs (using
soft CPU numbers as displayed by show config)
are part of the partition. See Section 4.5.3 for
details.

lp_mem_size* n

For the *, you supply the number of the partition.
The value n can be a size or list of sizes. See
Section 4.5.4 for details.

lp_shared_mem_size n

Size of memory shared by all partitions. See
Section 4.5.5 for details.

lp_error_target

The number of the soft partition that is to receive
error interrupts. The primary CPU of this soft
partition will receive the interrupts. If lp_count is
0, lp_error_target is ignored.

Partitions

4-15

4.5.2

Detailed Directions for lp_io_mask

The lp_io_mask environment variable is set to a value that creates a
binary mask in which a bit set to 1 indicates that an individual IOP
(same as soft QBB number) belongs to a soft partition.

Figure 4–8 Sample lp_io_mask Bit Masks
Partition 0
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
0 0 0 0 0 0 1 1

= hex value 3

Partition 1
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
0 0 0 0 1 1 0 0

= hex value C

Partition 2
Soft
QBB No.
Bits set

7 6 5 4 3 2 1 0
1 1 1 1 0 0 0 0

= hex value F0
PK-002HP-99

4-16 AlphaServer GS80/160/320 Firmware Reference Manual

I/O ports (IOPs), defined by the soft QBB number for the QBB in which they
reside, can be assigned to soft partitions in any order. Soft QBB numbers are
displayed by a show config command. Each soft partition must contain at
least one IOP with an I/O riser connected to a master PCI box with a standard
I/O module.
Bit values for one nibble of data are as follows:
Hex

Binary

Hex

Binary

0000

1000

0001

1001

0010

1010

0011

1011

0100

1100

0101

1101

0110

1110

0111

1111

Example 4–2 Sample lp_io_mask Setup
P00>>> set lp_io_mask0 3
P00>>> set lp_io_mask1 2C
P00>>> set lp_io_mask2 F0
In Example 4–2, the first command defines the IOPs in soft QBBs 0 and 1 as
part of soft partition 0. The second command defines the IOPs in soft QBBs 2
and 3 as part of soft partition 1. The third command defines the IOPs in soft
QBBs 4, 5, 6, and 7 as part of soft partition 2.

Partitions

4-17

4.5.3

Detailed Directions for lp_cpu_mask

The lp_cpu_mask environment variable is set to a value that creates a
binary mask in which a bit set to 1 indicates that an individual CPU
belongs to a soft partition.

Figure 4–9 Sample lp_cpu_mask Bit Masks for 32-Processor System
with No Hard Partitions

10
f

e
d

b
a

9
8

7
6
5
4
3
2

16
15

14
13

11
10

9
8

7
6
5
4
3
2

18 12
17 11

21 15
20 14
19 13

24 18
23 17
22 16

1d
1c
1b
1a
19

hex
dec

29
28
27
26
25

Soft
CPU No.

31 1f
30 1e

Partition 0

= FFF (hex)

0 0 0 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1

Bits set

1
1

= FF000 (hex)

7
6
5
4
3
2
7
6
5
4
3
2

9
8
9
8

b
a
11
10

e
d
14
13

10
f
16
15

18 12
17 11

21 15
20 14
19 13

24 18
23 17
22 16

1d
1c
1b
1a
19

hex
dec

29
28
27
26
25

Soft
CPU No.

31 1f
30 1e

Partition 1

0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 00 0 0 0

Bits set

1
1

7
6
5
4
3
2
7
6
5
4
3
2

9
8
9
8

b
a
11
10

e
d
14
13

10
f
16
15

18 12
17 11

21 15
20 14
19 13

24 18
23 17
22 16

1d
1c
1b
1a
19
29
28
27
26
25

hex
dec

31 1f
30 1e

Partition 2

Soft
CPU No.

= FFF00000 (hex)

1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
PK-003LP-00

4-18 AlphaServer GS80/160/320 Firmware Reference Manual

Figure 4–9 shows some examples of bit masks for the lp_cpu_mask
environment variable on a fully populated GS320 system (up to 32 processors)
with no hard partitions. Both hexadecimal and decimal are given for bit place
values.
Note that if you are defining a soft partition within a hard partition, the SCM
firmware, when the hard partition is powered on, supplies new “soft” CPU
numbers from 0 at the lowest-numbered hard QBB within the partition and
proceeding upward. An SRM show config display for the partition will show
the soft CPU numbers. An example of how to construct CPU numbers given the
soft QBB numbers in the partition is given in Section 4.6.
You can use the table on page 4-17 to construct values for as many hexadecimal
digits as you need to form a bit mask.
Example 4–3 shows the SRM commands used to create lp_cpu_mask
environment variables for the configuration shown in Figure 4–9.

Example 4–3 Sample lp_cpu_mask Setup
P00>>> set lp_cpu_mask0 FFF
P00>>> set lp_cpu_mask1 FF000
P00>>> set lp_cpu_mask2 FFF00000

Partitions

4-19

4.5.4

Detailed Directions for lp_mem_size

The lp_mem_size environment variable is set to a value, or a list of
values, that define the amount of memory allocated to a soft partition.

Example 4–4 Example for Constructing lp_mem_size
P00>>> show config ➊
Compaq AlphaServer GS320 6/731
QBB 0
Hard QBB 0
Quad Switch
.
.
.
QBB
Size
Interleave
0
16 GB
32-Way ➌
1
16 GB
32-Way
2
16 GB
32-Way
3
16 GB
32-Way

QSA rev 2, QSD revs 0/0/0/0

System Memory 64 GB

➋

As shown in Example 4–4, the SRM command show config (see ➊ ) displays
the system memory size (see ➋ ). From this number, you assign the amount of
memory in each soft partition. The total amount of memory for all partitions
and that allocated for shared memory (see next section) cannot exceed this total.
Note that if less than the total amount of memory is allocated for partitions and
shared memory, the unallocated memory is unusable by any partition.
The format of the command is:
set lp_mem_size* [size | list-of-sizes]
where:
*

Partition number (0 – 7).

size

Can be specified in hexadecimal bytes, decimal megabytes (MB) or
decimal gigabytes (GB). The size must be on a 64 MB boundary. The
size must also be at least as much memory required by the operating
system that will be booted in soft partition n. For example, OpenVMS
requires 64 MB.

4-20 AlphaServer GS80/160/320 Firmware Reference Manual

Can be bound to a QBB by using the form
n = size
where n is the QBB number and size is as described previously.

list-ofsizes

Only one unbound (not attached to a QBB) size may be given for any
partition. Note that if lp_shared_mem_size allocates memory that
is bound to specific QBBs, so must the lp_mem_
size allocations be bound to specific QBBs.
A comma-separated list of sizes from particular QBBs (see ➌ in
Example 4–4) for soft partition n. One element in the list of sizes
must be at least the minimum amount of memory required by the
operating system that will be booted in soft partition n. Each size can
be specified in hexadecimal bytes, decimal megabytes (MB), or
decimal gigabytes (GB). Each size must be on a 64 MB boundary..
No more than one size can be bound to an individual QBB. No more
than one unbound size can be given. Note that if lp_shared_mem_
size allocates memory that is bound to specific QBBs, so must the
lp_mem_size allocations be bound to specific QBBs.

Example 4–5 Examples of lp_mem_size
P00>>> set lp_mem_size0 100000000
➊
P00>>> set lp_mem_size1 1024 MB
➋
P00>>> set lp_mem_size2 0 = 8 MB, 2 = 2 GB

➊
➋
➌

➌

Soft partition 0 is assigned 100000000 hex bytes from any QBBs in the
system (or hard partition).
Soft partition 1 is assigned 1024 (decimal) Mbytes from any QBBs in the
system (or hard partition).
Soft partition 2 is assigned 8 Mbytes from QBB0 and 2 Gbytes from QBB2
in the system (or hard partition).

Example 4–6 Illegal Use of lp_mem_size
P00>>> set lp_mem_size_0 0=64 MB, 0=128MB
P00>>> set lp_mem_size1 1=100 MB ➋

➊
➋

➊

Two allocations are bound to QBB0.
Allocation is not on 64 MB boundary.

Partitions

4-21

4.5.5

Detailed Directions for lp_shared_mem_size

The lp_shared_mem_size environment variable defines the amount of
memory to be shared by the defined soft partitions.

Example 4–7 Example of Constructing lp_shared_mem_size
P00>>> show config ➊
Compaq AlphaServer GS320 6/731
QBB 0
Hard QBB 0
Quad Switch
QSA rev 2, QSD revs 0/0/0/0
Duplicate Tag
Up To 4 MB Caches
DTag revs 1/1/1/1
CPU 0
CPU 0
4 MB Cache
EV67 pass 2.2.3
CPU 1
CPU 1
4 MB Cache
EV67 pass 2.2.3
CPU 2
CPU 2
4 MB Cache
EV67 pass 2.2.3
CPU 3
CPU 3
4 MB Cache
EV67 pass 2.2.3
.
.
.
Hierarchical Switch
HSA revs 1/1, HSD revs 1/1/1/1
.
.
.
QBB
Size
Interleave
System Memory 64 GB ➋
0
16 GB
32-Way ➌
1
16 GB
32-Way
2
16 GB
32-Way
3
16 GB
32-Way

4-22 AlphaServer GS80/160/320 Firmware Reference Manual

As shown in Example 4–7, the SRM command show config ( ➊ ) displays the
system memory size (see ➋ ). From this number, you assign the amount of
memory to be shared. The total amount of memory for all partitions (see
previous section) and that allocated for shared memory cannot exceed this total.
Note that if less than the total amount of memory is allocated for partitions and
shared memory, the unallocated memory is unusable by any partition.
The format of the command is:
set lp_shared_mem_size [size | list-of-sizes]
where:
size

Can be specified in hexadecimal bytes, decimal megabytes (MB), or
decimal gigabytes (GB). The size must be on a 64-MB boundary.
Can be bound to a QBB by using the form
n= size
where n is the QBB number and size is as described previously.

list-of
-sizes

A comma-separated list of sizes from particular QBBs (see ➌ in
Example 4–7) for shared memory. Each size can be specified in
hexadecimal bytes, decimal megabytes (MB), or decimal gigabytes
(GB). Each size must be on a 64-MB boundary. No more than one size
can be bound to an individual QBB. No more than one unbound size
may be given. Also, if lp_shared_mem_size is allocated from specific
QBBs, so must the lp_mem_size allocations.

Example 4–8 Examples of lp_shared_mem_size
P00>>> set lp_shared_mem_size 100000000
➊
P00>>> set lp_shared_mem_size 1024 MB
➋
P00>>> set lp_shared_mem_size 0 = 64 MB, 2 = 2 GB

➊
➋
➌

➌

100000000 hex bytes from any QBBs in the system is allocated for
memory to be shared by all soft partitions.
1024 (decimal) Mbytes from any QBBs in the system is allocated for
memory to be shared by all soft partitions.
64 Mbytes from QBB0 and 2 Gbytes from QBB2 is allocated for memory to
be shared by all soft partitions.

Partitions

4-23

4.5.6

Lpinit Command

An lpinit command initializes the soft partitions defined, either for the
system (no hard partitions) or within a hard partition, at the system (or
partition) console device.

Example 4–9 Show Config Command for a Hard Partition
P00>>> show config
Compaq Computer Corporation
Compaq AlphaServer GS320 6/731
SRM Console V5.8-1, built on May 26, 2000 at 12:15:01
PALcode
OpenVMS PALcode V1.81-1, Tru64 UNIX PALcode V1.75-1
Micro Firmware X5.7
QBB 0
Quad Switch
Duplicate Tag

Hard QBB 1

CPU 0
CPU 1
CPU 2
CPU 3
Memory 0
Memory 1
Memory 2
Memory 3
.
.
.

CPU 0
CPU 1
CPU 2
CPU 3

➋

➌

QBB 1
Hard QBB 2
Quad Switch
Duplicate Tag

➋

CPU 0
CPU 1
CPU 2
CPU 3
Memory 0
Memory 1
Memory 2
Memory 3
.
.
.
QBB
Size
0
4 GB
1
4 GB

➌

CPU 4
CPU 5
CPU 6
CPU 7

Interleave
8-Way
8-Way

➊
Up To 4 MB Caches
4 MB Cache
4 MB Cache
4 MB Cache
4 MB Cache

EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1

➊
Up To 4 MB Caches
4 MB Cache
4 MB Cache
4 MB Cache
4 MB Cache

QSA rev 2, QSD revs 0/0/0/0
DTag revs 1/1/1/1

QSA rev 2, QSD revs 0/0/0/0
DTag revs 1/1/1/1
EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
EV67 pass 2.4, 731 MHz
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1
MPA rev 2, MPD revs 1/1

System Memory 8 GB

4-24 AlphaServer GS80/160/320 Firmware Reference Manual

Soft partitions within hard partitions are discussed in the next section. For
convenience, simply assume for now that the show config command in
Example 4–9 was issued from the console device for the second hard partition of
a 3-hard-partition system.
Note the QBB numbering. A “soft QBB number” is given on the left, and the
hard QBB number is given on the right (see ➊).
Note the processor numbering: two columns are given. The first column gives
the processor numbers shown on the QBB (see ➋). The second column gives
what are called the “soft CPU numbers,” running from 0 through 7 in this
example, so that there is a unique CPU number for each CPU in the partition
(see ➌).
Example 4–10 shows how two soft partitions might be set up within this hard
partition. Note that soft CPU numbers 0, 1, 2, and 3 are allocated to soft
partition 0, and soft CPU numbers 4, 5, 6, and 7 are allocated to soft partition 1
(see ➊). Likewise, soft QBB numbers are used in setting the lp_io_mask
environment variables.
Shared memory is allocated from both of the two QBBs.
The lpinit command initializes the soft partitions defined, and the soft
partitions are started up with displays at their respective console devices.

Example 4–10 Setting Up Soft Partitions
P00>>> set lp_count 2
➊
P00>>> set lp_cpu_mask0 f
P00>>> set lp_cpu_mask1 f0
P00>>> set lp_error_target 0
➋
P00>>> set lp_io_mask0 1
P00>>> set lp_io_mask1 2
P00>>> set lp_mem_size0 0 = 3GB
P00>>> set lp_mem_size1 1 = 3GB
P00>>> set lp_shared_mem_size 0 = 1GB, 1 = 1GB
P00>>> lpinit

Partitions

4-25

4.6

Soft Partitions Within Hard Partitions

It is possible to define soft partitions within hard partitions in a
system.

Table 4–3 Example of Soft Partitions Within Hard Partitions
Hard Part.
0

Hard Partition 2

Hard Part.
1

Soft Part. 0

Soft Part. 1

Soft Part. 2

Hard QBB
Number

0, 1

2, 3

5, 6

6, 7

Soft QBB
Number

0, 1

1, 2

2, 3

Systemwide
CPU
Number

0–7

8–15

16–19

20, 21, 24,
25

22, 23, 26–
31

Soft CPU
Number

0–7

0–3

4, 5, 8, 9

6, 7, 10–15

Number of
PCI Boxes

4; 2 with
SIO

4; 1 with
SIO

2; 1 with
SIO (from
soft QBB0)

2 with SIO
(from sofy
QBB1)

4; 2 with
SIO (from
soft QBB2
and 3)

Memory

From
QBB0 and
1

From
QBB2
and 3

1 GB

2 GB

Shared memory: 5 GB

4-26 AlphaServer GS80/160/320 Firmware Reference Manual

Table 4–3 shows how a system might be divided into hard partitions and soft
partitions. The table shows three hard partitions. The third hard partition is
then divided into three soft partitions. An example of the commands that would
define such partitioning is given below.

Example 4–11 Soft Partitions Within Hard Partitions
SCM_E0> set hp_count 3
SCM_E0> set hp_qbb_mask0 3
SCM_E0> set hp_qbb_mask1 c
SCM_E0> set hp_qbb_mask2 f0
SCM_E0> power on –par 0
SCM_E0> power on –par 1
SCM_E0> power on –par 2
SCM_E0> quit
.
.
.
[go to the console device or terminal emulator screen
that controls hard partition 2]
P00>>> set lp_count 3
P00>>> set lp_cpu_mask0 f
P00>>> set lp_cpu_mask1 330
P00>>> set lp_cpu_mask2 fcc0
P00>>> set lp_error_target 0
P00>>> set lp_io_mask0 1
P00>>> set lp_io_mask1 4
P00>>> set lp_io_mask2 c
P00>>> set lp_mem_size0 1GB
P00>>> set lp_mem_size1 2GB
P00>>> set lp_mem_size2 2GB
P00>>> set lp_shared_mem_size 0 = 5GB, 1 = 5GB,2 = 5GB
P00>>> lpinit

Partitions

4-27

4.7

Master and Slave SCMs

The multiple standard I/O modules needed for hard or soft partitions
introduce the need for “master” and “secondary” SCMs. The master
SCM, controls the console serial bus (CSB). Other SCMs are secondary.

Figure 4–10 Multiple SCMs in a Partitioned System
Hard Partition 1

Hard Partition 0

Hard Partition 2
Soft
partition 1
Soft
partition 0

Terminal server
Soft
partition 2

PK-007HP-00

4-28 AlphaServer GS80/160/320 Firmware Reference Manual

A user needs access to an individual partition for maintenance and debugging.
This access is provided through the requirement that each partition, hard or
soft, must be attached to a master PCI box with a standard I/O module.
The standard I/O module contains both SCM and SRM firmware. Only one
SCM can control the console serial bus (CSB) at any given time. This SCM is
called the master SCM. All other SCMs are called secondary, or slave, SCMs.
A master SCM must be:

•

Attached to the operator control panel (OCP).

•

Have its scm_csb_master_eligible environment variable set to 1. (By
default, each SCM’s scm_csb_master_eligible environment variable is set
to 1. You can override a particular SCM’s eligibility by setting this
environment variable to 0 set from the console connected to that SCM.)

Figure 4–10 illustrates a system divided into three hard partitions. One hard
partition is divided into three soft partitions. Each of these partitions has a
master PCI box with a standard I/O module containing SCM and SRM
firmware. Note that hard partition 2 is connected to three master PCI boxes.
The SRM that controls the definition of soft partitions within hard partition 2 is
the SRM residing on the standard I/O module in the master PCI box with the
lowest-numbered hose connection within the hard partition.
At VAUX power-up on a system with multiple SCMs, the master SCM is
selected as the one with the lowest-numbered CSB address (determined by the
node ID switch setting on the PCI box) that is also connected to the OCP and
has the scm_csb_master_eligible environment variable set to 1. The standby
SCM is selected as the one with the next-lowest CSB adress that is also
connected to the OCP and has the scm_csb_master_eligible environment
variable set to 1.

Partitions

4-29

4.8

SCM Functionality from Master and Slave SCMs

Systemwide functionality is provided by the master SCM; partitiondependent functionality is provided at the local (master or slave) level.

Figure 4–11 Systemwide Functionality
Function only if issued from Master SCM node
reset -all
power on -all

ted back to issu
lay rou
ing
nod
Disp
e

Can be issued from Master or Slave; if Slave,
routed to Master: show csb
show system
show fru
set hp_*
PK-004HP-00

4-30 AlphaServer GS80/160/320 Firmware Reference Manual

Figure 4–11 shows which SCM commands affect the whole system (systemwide
functionality). Commands that affect all nodes on the console serial bus can be
executed only from the master SCM. For example, commands that display
information for all CSB nodes are routed through the master SCM for execution.
Figure 4–12 shows those SCM commands providing partition-specific
functionality. As shown, you can set up and use remote access for each hard or
soft partition (as long as they have a PCI box with a standard I/O module
attached). The halt, reset, and power commands affect only the hard partition
in which they are executed; however, they do have –partition options that can
affect other partitions if executed from the master SCM.

Figure 4–12 Partition-Dependent Functionality

Affects only the SCM's local environment (hard partition)
Take action from local SCM (Master or Slave):
show status
el
build EEPROM
help
show nvr
erase
clear alert
init
test alert
examine
deposit
quit
hangup
disable
set *
(*Set hp_* routed
to master SCM)
Routed to Master SCM; affects only the hard
partition from which it is issued (hp_count=0):
/
halt [in, out]
power [off, on]
reset
PK-005HP-00
fault

Partitions

4-31

Chapter 5
Booting an Operating System

This chapter briefly describes how to boot the OpenVMS and Tru64 UNIX
operating systems on AlphaServer GS80/160/320 systems. More complete
information on booting and installing an operating system is given in the
AlphaServer GS80/160/320 User’s Guide.
Sections include:

•

Preparation

•

Selecting a Boot Device

•

Booting an Operating System

5-1

5.1

Preparation

There are some steps you must take preparatory to booting and other
steps that can make booting thereafter easier.

5.1.1

Set os_type Environment Variable

For factory-installed software (FIS), a default operating system is
defined. If you do not have factory-installed software, or you wish to
change the default operating system, you use the set os_type
command.

Example 5–1 Setting os_type for OpenVMS
P00>>> set os_type vms

Example 5–2 Setting os_type for Tru64 UNIX
P00>>> set os_type unix

NOTE: If your system is partitioned, you must set these and any other relevant
environment variables for each partition.

5-2

AlphaServer GS80/160/320 Firmware Reference Manual

5.1.2

Set Console Environment Variable

For OpenVMS systems, the console environment variable should be set
to serial (the default).
For Tru64 UNIX systems, the console
environment variable may be either serial or graphics (if a graphics
device is attached).

Example 5–3 Set Console to Serial
P00>>> set console serial

Example 5–4 Set Console to Graphics
P00>>> set console graphics
All operating systems require a serial console terminal. Some operating
systems support a graphics monitor as well. The set console graphics
command is needed for systems having a graphics monitor as part of their
console interface. The default setting for the console environment variable is
serial.
By specifying set console graphics, the SRM console will build the proper
parameters in a data structure called the HWRPB, or hardware restart
parameter block, so that an operating system will build with graphics enabled.

Booting an Operating System

5-3

5.1.3

Set auto_action Environment Variable

You can direct the SRM console to automatically boot the operating
system upon system power-up, restart, or init. The default is to halt
the system after system self-test and leave the console device in SRM
console mode.

Example 5–5 Setting the auto_action Environment Variable
P00>>> show auto_action
auto_action
halt
P00>>> set auto_action boot

5-4

AlphaServer GS80/160/320 Firmware Reference Manual

The auto_action environment variable is set to halt by default. In this case,
at system restart (power-up, reset, or SRM init command), the SRM console
software will display the system self-test and display the SRM console prompt
to accept commands.
If you set the auto_action environment variable to boot, at system restart,
the SRM console software will display the system self-test and then
automatically boot the operating system according to the default boot
parameters you defined.

Booting an Operating System

5-5

5.2

Selecting a Boot Device

An operating system can be booted from a number of devices: the
DVD/CD-ROM drive, a local system disk, a disk connected to the
system through a CIPCA adapter, or by Ethernet from a remote disk
on another system. Certain operating systems use a subset of these
devices. Note that factory-installed software has a default boot device
selected.

Table 5–1 Boot Devices
Device

Location

DVD/CD-ROM

In-cabinet compact disk drive, used for booting the Loadable
Firmware Update (LFU) Utility. See Appendix B.

Local device

Disk connected to the system through an adapter on an I/O
bus.

CI disk

Disk located on the system’s HSC controller connected to
the system by a CIPCA adapter on the PCI bus.

Remote disk

Disk connected to another system on the Ethernet, through
the Ethernet port interface or the adapter.

5-6

AlphaServer GS80/160/320 Firmware Reference Manual

Table 5–1 lists the types of devices available for your operating system for
booting. For systems with factory-installed software (FIS), a default boot
device has already been selected for you. If you want to change this default,
follow the instructions here.
NOTE: The default boot device selected applies to the operating system. If you
wish to boot the Loadable Firmware Update (LFU) utility, you must
specify the boot device where LFU is located on your system, since LFU
is not on the FIS boot device.
You can set or change the default boot device with the set bootdef_dev
command, as described in Sections 5.2.1 and 5.2.2. You can also specify a
particular device with the SRM boot command.

Booting an Operating System

5-7

5.2.1

Show Device Command

If you do not wish to use the default boot device selected for factoryinstalled OpenVMS or Tru64 UNIX systems, the show device SRM
console command displays your system I/O configuration, allowing
you to identify and select an appropriate boot device.

Example 5–6
P00>>> sho dev
dka0.0.0.1.0
dkb0.0.0.7.1
dkb100.1.0.7.1
dkb200.2.0.7.1
dkb300.3.0.7.1
dkc0.0.0.1.2
.
.
.
dkn0.0.0.1.8
dqa0.0.0.15.0
dqc0.0.0.15.6
dqe0.0.0.15.8
ewa0.0.0.3.8
fwa0.0.0.4.1
fwb0.0.0.5.7
fwc0.0.0.1.10
pga0.0.0.7.7
pka0.7.0.1.0
pkb0.7.0.7.1
pkc0.7.0.1.2
pkd0.7.0.2.2
pke0.7.0.3.2
pkf0.7.0.4.3
pkg0.7.0.5.3
pkh0.7.0.6.3
pki0.7.0.7.3
pkj0.7.0.2.4
pkk0.7.0.6.5
pkl0.7.0.1.6
pkm0.7.0.2.6
pkn0.7.0.1.8
pko0.7.0.2.8
pkp0.7.0.1.16
P00>>>

Show Device Command

DKA0
DKB0
DKB100
DKB200
DKB300
DKC0

DKN0
DQA0
DQC0
DQE0
EWA0
FWA0
FWB0
FWC0
PGA0
PKA0
PKB0
PKC0
PKD0
PKE0
PKF0
PKG0
PKH0
PKI0
PKJ0
PKK0
PKL0
PKM0
PKN0
PKO0
PKP0

RZ1DF-BF
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0

1614
3B05
3B05
3B05
3B05
3B05

RZ1DF-BF
TOSHIBA CD-ROM XM-6302B
TOSHIBA CD-ROM XM-6302B
TOSHIBA CD-ROM XM-6302B
08-00-2B-C3-BD-00
00-00-F8-CD-1F-39
00-00-F8-CD-22-E0
00-00-F8-CD-22-FB
WWN 1000-0000-c920-da1e
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7

1614
1017
1017
1017

➊

5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57
5.57

➊ The example shows a CD-ROM disk drive, where you can load firmware
update CD-ROM disks. You can use the boot command to boot LFU from

5-8

AlphaServer GS80/160/320 Firmware Reference Manual

the disk. In this example, the command would be:
P00>>> boot dqa0
If you are not planning to use the default boot device selected for your factoryinstalled software, or if your operating system is not factory installed, select an
appropriate boot device for your system. Use the show device command to
display all the devices on your system. The format for device names is:
ddau.n.c.s.h
where the fields are as defined in Table 5–2.
Table 5–2 SRM Console Device Naming Conventions
Field

Meaning

Description

Device driver

Two-letter designator for a port or class device
driver. Usually one of:
dk SCSI drive or CD
dq IDE CD-ROM
dr RAID set device

ei Ethernet port
fw FDDI device
mk SCSI tape
pk SCSI port

Adapter ID

Specifies the one-letter designator for adapter ID.
One of a, b, c,…

Unit number

Specifies the device unit number. For MSCP
devices, this is a unique increasing number. For
SCSI devices, this is 100 times the bus node no.

Node number

Specifies the bus node ID.

Channel
number

Specifies the channel or PCI function number. Only
meaningful for multi-channel or multi-function
devices.

Slot number

Specifies the device’s logical slot number. The
output of a show config command indicates
the logical slot numbers for devices in a system.

Hose number

Specifies the device’s hose number.

Ideally, your system manager labeled the I/O devices on your system, so that
you can identify a particular unit by its name. If not, you will have to follow

Booting an Operating System

5-9

cables back to the device adapter and then back to the hose to identify a
particular unit.
In either case, select a device on your system that is of the type appropriate for
the media your operating system software is on. It is useful to reserve one
device on your system for this use, for consistency. This is done by setting the
bootdef_dev environment variable, as described next.

5-10

AlphaServer GS80/160/320 Firmware Reference Manual

5.2.2

Boot Environment Variables

You can change the factory-installed default boot device, or, if your
operating system is not factory-installed, define a default boot device,
to be used automatically if no device is specified in the boot command
itself.

Example 5–7 Viewing and Setting Boot Environment Variables
P00>>> show boot*
➊
boot_dev
boot_file
boot_osflags
0
boot_reset
OFF
bootdef_dev
booted_dev
booted_file
booted_osflags
➋
P00>>> set bootdef_dev dkb100
P00>>> show boot*
boot_dev
boot_file
boot_osflags
0
boot_reset
OFF
bootdef_dev
dkb100.1.0.6.1
booted_dev
booted_file
booted_osflags
Some boot environment variables can be set by the user using the set SRM
console command. Others are set by values you may specify in a boot
command. See the AlphaServer GS80/160/320 User’s Guide for a discussion of
boot environment variables.

➊

The show boot* command displays the current settings of the boot
environment variables.

➋

In Example 5–7, the user sets the default boot device environment
variable bootdef_dev to device dkb100.

Booting an Operating System

5-11

5.3

Booting an Operating System

Use the show boot* command to ensure that the device from which to
boot the operating system, and other boot parameters, are correct.
Issue the boot command.

Example 5–8 Tru64 UNIX Boot
P00>>> show boot*
➊
boot_dev
dka0.0.0.1.0
boot_file
boot_osflags
a
boot_reset
OFF
dka0.0.0.1.0
bootdef_dev
booted_dev
booted_file
booted_osflags
➋
P00>>> boot
(boot dka0.0.0.1.0 -flags a)
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.

5-12

AlphaServer GS80/160/320 Firmware Reference Manual

Example 5–8 Tru64 UNIX Boot (Continued)
using 94344 buffers containing 737.06 megabytes of memory
Master cpu at slot 0.
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 5–8 shows an example of booting a Tru64 UNIX system.

➊

The show boot command shows the values of all the environment
variables beginning with the characters “boot.”

➋

The user issues the boot command.

➌

The operating system boots and displays its login prompt.

Booting an Operating System

5-13

Chapter 6
SCM Command Reference

The format of the commands recognized by the SCM command parser is
described in full in this chapter. The sections are:

•
•
•

Language Overview

•
•
•

Halt Command

•

Clear Command

•

Init Command
Power Command

Deposit Command

•
•

•
•
•

Disable Command

•

Reset Command

El Command

•
•

Enable Command

•
•

Set Commands

•
•

•

Examine Command

Test Alert Command
Test &pcn Command

•

Fault Command

SCM Command Summary
SCM Command Description
Conventions

Erase Command

Hangup Command
Help Command

Quit Command

Show Commands

When the operator enters SCM mode for the system or partition, the operating
system state is unchanged. The operator communicates with the firmware
through the console terminal, which displays one of the following prompts:
SCM_nn> or

SLV_nn>
Where SCM is given for a console device attached to the master CSB. SLV
indicates a console device attached to a slave CSB node, and nn may range
from E0 to EF (the number shown by a show csb display for the CSB node).

SCM Command Reference

6-1

6.1

Language Overview

This section lists system management tasks, the related SCM
commands, and the place in this manual where a description of the
commands can be found.

Figure 6–1 Overview of SCM Command Language Functionality
Initiate or terminate
remote
console session

Set variables
for remote console
access (dial-out
number, baud rate...)

Power
On/Off

Set/Clear/Test
Alerts

SCM Console Functions
Define hard partitions

Debug
(show status, deposit,
examine, fault, reset)
PK-0112a-00

6-2

AlphaServer GS80/160/320 Firmware Reference Manual

Remote Access
As described in Section 3.1, the SCM allows remote maintenance of AlphaServer
GS80/160/320 systems.
System monitoring and troubleshooting can be done by a system manager at a
remote location; either in the next room, building, state, or even country. Once
a specific problem has been identified, the system manager can dispatch a local
service technician to handle the problem.
A subset of SCM commands must be issued from the local console to define
parameters needed for remote access. Another subset of commands can be used
from either the local or remote console to display system status and
troubleshoot the system as a whole.
Hard Partitions
As described in Chapter 4, you can use SCM commands to divide the system
into hard partitions. This capability allows separate copies, or instances, of an
operating system to run in each partition.
Entering and Leaving the SCM Console
To enter the SCM command-line interpreter, the user types the escape sequence
on the local or remote serial console terminal. (The default escape sequence is
<Esc><Esc>scm.) The operating system state does not change when the user
enters SCM command mode.
The quit command terminates SCM console usage and returns the system to
the state it was in when the escape sequence was entered.

SCM Command Reference

6-3

6.2

SCM Command Summary

Table 6–1 lists the commands used for various tasks, and the sections or
chapters where examples of the task can be found. (Detailed information on SCM command format is given in Section 6.3.)

Table 6–1 Management Tasks and Related SCM Commands
Task

Commands

Section

Get help on SCM commands

help or ?

Section 3.3

Erase the current screen

erase

Section 6.9

Set up for remote console management
features

set init
set dial
set alert
set password
enable remote
enable alert
test alert
set com1_mode

Section 3.4

Initialize the modem to prepare it to
send alerts and receive incoming calls;
clear alerts.

init
set baud
clear alert

Section 3.4
Section 6.19.2
Section 6.4

Examine the state of the system

show
el

Section 3.7
Section 6.7

Low-order debugging

deposit
examine

Section 6.5
and 6.10

Define hard partitions

set hp_count
set hp_qbb_mask*

Section 4.4

Control power to the system, initialize
hard partitions

power

Sections 3.8,
4.4

Reset system or QBB

reset

Section 6.18

Terminate the remote session

hangup

Section 3.10

Leave the SCM command interpreter

quit

Section 3.9

6-4

AlphaServer GS80/160/320 Firmware Reference Manual

Section 3.6

6.3

SCM Command Description Conventions

The following conventions are used in the descriptions of the SCM
command-line interface.

Table 6–2 SCM Command Description Conventions
Convention

Meaning

fixed-font

SCM command examples are shown in a fixed-width font.

bold

Command and option keywords are presented in bold type.

item

Italics indicate a placeholder for an item that the user supplies.

[item]

Square brackets are used to enclose optional parameters,
qualifiers, and values. For example, help [topic].

{a, b, c}

Braces containing items separated by commas imply mutually
exclusive values. For example {a, b, c} indicates that you can
choose one of a, b, or c.

{a | b | c}

Braces containing items separated by the vertical bar indicate
that you can choose any combination of a, b, and c.

SCM Command Reference

6-5

6.4

Clear Command

The clear command clears the current alert condition.

Syntax
clear {alert, port}
Arguments
alert

Clears the current alert condition and causes the SCM to stop
paging the remote operator. If the alert is not cleared, the SCM
will continue to page the remote operator every 30 minutes. The
first alert to occur is logged as the alert type. Subsequent alerts
will not be seen by the SCM until the current alert condition is
cleared. Only one alert can be pending at any given time.

port

Clears communication of terminal emulator when the port is
“wedged” in COM1 mode. Escape back to the SCM and clear the
port to COM1.

Example
SCM_E0> clear alert

6.5

Deposit Command

The deposit command stores data in the contents of memory or in IPRs
and GPRs in specific processors, including those processors on the CSB.

Syntax
deposit [ - {b, w, l, q, o}] [-{gpr n, ipr n, p}] [-n count ] [&{p, m}n]
[*, address ] [data]
Options
-b

The data deposited is a byte (8 bits).

-w

The data deposited is a word (16 bits).

6-6

AlphaServer GS80/160/320 Firmware Reference Manual

-l

The data deposited is a longword (32 bits).

-q

The data deposited is a quadword (64 bits). This is the default.

-o

The data deposited is an octaword (128 bits).

-gpr n

The data is deposited in general-processor register (GPR) n (hex).

-ipr n

The data is deposited in internal-processor register (IPR) n (hex).

-p

The data is deposited in a physical memory address (default).

-n count

The address will be incremented count (hex) times. The address
increment is determined by the address size option (-b, -w, -l, -q, -o).

&pn

Specifies the CPU on which the deposit is to be made. The argument
n is the soft CPU number displayed in the show csb command.

&mn

Specifies the number of the CSB node (AM186 processor) on which
the deposit is to be performed. The argument n is the CSB address
shown in the show csb command.

Arguments
*
The set of arguments (address, data) used in the latest deposit or
examine command are to be used here.
address

A physical address in system memory.

data

The data (hex) to be written to the specified address or register.

Example
➊
SCM_EF> ex &mef 80000
CSB_EF/00080000: 00
➋
SCM_EF> dep &mef 80000 1b
SCM_EF> ex &mef 80000
➌
CSB_EF/00080000: 1B

➊
➋
➌

Examines location 80000 in CSB node EF. The current value is 00.
Deposits the hexadecimal value 1b into location 80000 of CSB node EF.
Examines location 80000 in CSB node EF. It has been changed to 1B.

SCM Command Reference

6-7

6.6

Disable Command

The disable command disables system alerts and remote console
operations.

Syntax
disable {alert, remote}
Arguments
alert

Stops the SCM from monitoring alert conditions. Using this
command is strongly discouraged. Alert monitoring is essential
to ensuring that environmental conditions do not damage the
hardware.

remote

Disables the capability for a remote user to dial in to the system and
execute commands.

Examples
SCM_E0> disable alert
SCM_E0> disable remote

6-8

AlphaServer GS80/160/320 Firmware Reference Manual

6.7

El Command

The el command displays the current event log on the console screen.
The event log contains the most immediate (up to 4 Kbytes) input and
output that has passed through the SCM. The el command is useful for
reviewing recent command history.

Syntax
el
Example
SCM_E0> el
fff

➊

PSM33 SysEvent: QBB_POWER_OFF
SysEvent Reg0: 1cbc
SysEvent Reg1: cfff

➋

SCM_E0>
SCM_E0> p on
➌
Powering on PCI Box 0
Powering on PCI Box 1
.
.
.
Qbb0 unloading console across hose2 from PCI Box-0
Console COM1 from master PCI Box-0
Retrieve FRU information for Shared RAM
SCM_E0> .
QBB3 now Testing Step-e.
QBB0 now Testing Step-e
QBB1 now Testing Step-e
QBB2 now Testing Step-e...
Power On Complete
SCM_E0> el
➍

➊

The user types the el command.

➋

The end of a display produced by a power off command is the most
recent event in the event log history.

➌

A power on command was issued; the display contains the entire output
of the power-up, abbreviated here.

➍

The most recent command, the el command itself, is displayed.

SCM Command Reference

6-9

6.8

Enable Command

The enable command enables system alerts or remote access.
Syntax
enable {alert, remote}
Arguments
Enables the SCM’s monitoring of all alert conditions:

alert

•
•
•
•
•
•
•
•
•
•

Blower failure from a PSM
Vital power failure from a PSM
Overtemperature failure from a PSM
Overtemperature failure from an HPM
Vital power failure from an HPM
System clock failure from an HPM
Fan failure from a PBM
Overtemperature failure from a PBM
Power supply failure from a PBM
User-initiated alert

When an alert occurs, the dial-out sequence is sent. The alert is
repeated every 30 minutes until a clear alert or disable alert, or
until the OCP keyswitch is turned to Secure.
remote

Enables remote dial-in. (See Section 3.4 for a discussion of values
that must be set for the init of the modem to succeed.)

Examples
SCM_E0> enable alert ➊
SCM_E0> enable remote ➋

➊
➋

6-10

Turns on alert condition monitoring in the SCM.
Initializes the modem (allows remote access).

AlphaServer GS80/160/320 Firmware Reference Manual

6.9

Erase Command

The erase command erases the current display screen on the console
terminal.

Syntax
erase
Example
SCM_E0> erase

SCM Command Reference

6-11

6.10 Examine Command
The examine command displays the contents of memory or IPRs and
GPRs in specific processors, including those processors on the CSB.

Syntax
examine [ - {b, w, l, q}] [-{gpr n, ipr n, p}] [-n count ] [&{p, m}n] [*, address ]
Options
-b

The data to be displayed is a byte (8 bits).

-w

The data to be displayed is a word (16 bits).

-l

The data to be displayed is a longword (32 bits).

-q

The data to be displayed is a quadword (64 bits). This is the default.

-gpr n

The data to be displayed is in general-processor register (GPR) n (hex).

-ipr n

The data to be displayed is in internal-processor register (IPR) n (hex).

-n count

The address will be incremented count (hex) times. The address
increment is determined by the address size option (-b, -w, -l, -q, -o).

&pn

Specifies the CPU module on which the examine is to be performed.
The argument n is the CPU number shown under the heading CSB in
the show csb command.

&mn

Specifies the number of the CSB node (AM186 processor) on which the
examine is to be performed. The argument n is the CSB address
shown in the first column in the show csb command.

6-12

AlphaServer GS80/160/320 Firmware Reference Manual

Arguments
*

Indicates that the set of arguments (address, data) used in the last
deposit or examine command are to be used here.

address

A physical address in system memory.

Example

➊
SCM_EF> ex &mef 80000
CSB_EF/00080000: 00
➋
SCM_EF> dep &mef 80000 1b
SCM_EF> ex &mef 80000
➌
CSB_EF/00080000: 1B
➊
➋
➌

SCM Command Reference

6-13

6.11 Fault Command
The fault command emulates the control panel Fault button. It is
similar to the reset operation, except that the contents of error
registers in the system are “latched.” That is, they retain their values.

Syntax
fault [-all, -par[tition] n]
Options
-all

Asserts the fault condition for all hard partitions (the
default).

-par[tition] n

Asserts the fault condition for hard partition n.

Example
SCM_E0> fault
Returning to system COM1 port
P00>>>

6-14

AlphaServer GS80/160/320 Firmware Reference Manual

6.12 Halt Command
The halt command emulates the control panel Halt button.

Syntax
halt { in, out} [ -par[tition n], -all ]
Arguments
in

Asserts system halt. Causes the operating system to perform a halt, and
prevents the console from booting the operating system. This halt stays
in effect until an SRM continue command is given.

out

Deasserts system halt.

Options (only effective from Master SCM)
-par[tition] n

Asserts or deasserts halt on the hard partition identified by n.

-all

Asserts or deasserts halt on all hard partitions (the default).

Example
SCM_E0> halt in
Returning to system COM1 port
P00>>>

6.13 Hangup Command
The hangup command terminates a remote access session,
disconnecting the modem. The command can be issued from a remote
terminal or from the local console.

Syntax
hangup
Example
SCM_E0> hangup

SCM Command Reference

6-15

6.14 Help Command
The help (or ?) command displays information about SCM command
format and function.

Syntax
help
Example
SCM_E0> help

SCM CLI Version 1.0

2000/27/07

6-16

AlphaServer GS80/160/320 Firmware Reference Manual

6.15 Init Command
The init command initializes the modem; used in conjunction with
other commands to enable remote access (see Chapter 3).

Syntax
init
Example
SCM_E0> init
Querying the modem port. . . non-modem detected
Modem port initialized

➊

SCM_E0> init
Querying the modem port. . . no device detected

➋

SCM_E0> init
Querying the modem port. . . modem detected
Modem port initialized

➊
➋
➌

➌

In this case, a terminal is connected to the modem port.
Here, nothing is connected to the modem port.
In the final example, a modem is connected to the modem port.

SCM Command Reference

6-17

6.16 Power Command
The power on command directs the SCM to supply power to the system
or the specified components. Likewise, the power off command directs
the SCM to remove power from the system or specified components.

Syntax
power [on, off] [none, -all, -par[tition] n]
Arguments
on

Supplies power to the entire system or the specified component(s).

off

Removes power from the entire system or the specified component(s).

Options
On partitioned systems: Powers on or off only the QBBs that
comprise the hard partition from which the command is issued.

none

On nonpartitioned systems: Powers on or off the entire
system.
On partitioned systems: Can be issued from the master SCM
to power on or off all hard partitions, including PCI boxes.

-all

On nonpartitioned systems: Functions the same as supplying
no arguments (powers on or off the entire system).
-par n

Can be issued from the master SCM; supplies power to and
removes power from the hard partition specified by n. See
Chapter 4.

Description
Power is supplied to the nodes on the console serial bus (CSB) whenever the
system is plugged in and the main breaker switch is on. The power on
command causes the SCM to supply power to the rest of the system or to the
specified partition. The power on display is lengthy, detailing the process of
powering on the system in each of its five phases, and can fill many screens.
(The el command is useful for examining the steps of a power-up after the fact.)
As a synopsis, the power on display terminates with the same display
produced by the show system command.

6-18

AlphaServer GS80/160/320 Firmware Reference Manual

The power off command removes power from the entire system or from a
particular partition in an orderly fashion.
WARNING: The keyswitch on the control panel must be set to Secure before any
removal or replacement operation. Otherwise, a remote operator
could dial in and inadvertently issue a power on command while
the local service technician is working with a component. Injury to
the service technician and/or damage to the component could
occur.
Example
SCM_E0> p on
Powering on PCI Box 0
Powering on PCI Box 1
Powering on PCI Box 2
Powering on PCI Box 3
Powering on PCI Box 5
Powering on PCI Box 6
Powering ON on QBB-0
Power ON Phase INIT
Powering ON on QBB-1
Powering ON on QBB-2
Powering ON on QBB-3
SCM powered via PBM
SCM_E0>
QBB0 now Testing Step-0
QBB1 now Testing Step-0
.
.
.

SCM Command Reference

6-19

6.17 Quit Command
The quit command changes the user’s input focus from the SCM
command language interface to the system COM1 port.

Syntax
quit
Example
SCM_E0> quit
Returning to system COM1 port

6-20

AlphaServer GS80/160/320 Firmware Reference Manual

6.18 Reset Command
The reset command resets the entire system or a specified component.

Syntax
reset [none, {-partition [n], -qbb [n], -cpu [n] , –pci [n], –hswitch}]
Arguments
none

Resets the entire system.

-partition

Resets the partition specified by n.

-qbb

Resets the QBB specified by the soft QBB number n.

-cpu

Resets the CPU specified by the soft CPU number n.

-pci

Resets the PCI box specified by the PCI ID number n.

-hswitch

Resets the hierarchical switch.

SCM Command Reference

6-21

6.19 Set Commands
The set commands are used to set system parameters necessary for
remote connections to the SCM command-language interpreter.

6.19.1 Set Alert Command
The set alert command specifies a string that defines the time to wait
for the remote pager to respond to a dial-out, and a message to be sent
to the remote pager. Two terminating characters (#;) are necessary.

Syntax
set alert string

Defines the wait time for the remote pager to respond, as
well as a message to be displayed on the pager, usually
the telephone number the remote user uses to reach the
local system.

Table 6–3 Alert String Elements
String Elements

Description

,,,,,,

A series of commas, each specifying a 2-second wait for the
remote pager to respond. The six commas shown would call
for a wait of 12 seconds.

message

A message to be displayed at the remote pager; usually the
number for the remote user to dial in to initiate remote
access to the system. Must be terminated with the
characters “#;”.

Example
SCM_E0> set alert ,,,,,,9785551212#;

6-22

AlphaServer GS80/160/320 Firmware Reference Manual

6.19.2 Set Baud Comand
The set baud command changes the baud rate between the system and
the modem or between the system and the local terminal port.

Syntax
set baud [modem, local, com1] [2400, 3600, 4800, 7200, 9600, 19200, 38400,
57600]
or
set [modem_baud, local_baud, com1_baud] [2400, 3600, 4800, 7200, 9600,
19200, 38400, 57600]
Arguments
modem or
modem_baud

Changes the baud rate of the SCM-to-modem UART.

local or local_baud

Changes the baud rate of the SCM-to-local-consoledevice UART.

com1 or
com1_baud

Changes the baud rate to the SCM-to-system UART.

Options
2400
3600
4800
7200
9600
19200
38400
57600

The actual baud rate for the specified channel. The default for
the modem port is 57600. The default for the local port is 9600.

Example
SCM_E0> set baud modem 38400

SCM Command Reference

6-23

6.19.3 Set Com1_Mode Command
The set com1_mode command defines routes for information flow
between the system and the local or remote console device.

Syntax
set com1_mode mode
Arguments
mode

6-24

Defines the path of data flow between the local or modem port and
the system. The values of mode are:
through

All characters routed through SCM. Default.

local

Only local port can communicate, but you can
enter the SCM from the modem.

snoop

Data between remote and system bypasses the
SCM, except SCM listens passively for SCM
escape sequence, and if detected, enters SCM
command-language interface. Useful for
optimizing data transfer by bypassing the
SCM except where specifically requested.

software_ bypass

Data flow between remote and system
bypasses the SCM, except SCM listens for loss
of carrier, then switches to snoop mode.
Useful for binary download, as binary data
may contain escape characters that the SCM
would respond to.

firmware_bypass

Data flow between remote and system
completely bypasses the SCM. Useful if you
want the system, not the SCM to control the
modem port and you want to disable SCM
remote management features. You can switch
to other modes by resetting the com1_mode
environment variable from the SRM console.

AlphaServer GS80/160/320 Firmware Reference Manual

6.19.4 Set Dial Command
The set dial command defines the number to be dialed out to when an
alert occurs; usually the number of a pager.

Syntax
set dial string

Defines the string sent to the system modem. See Table 6–4.

Table 6–4 Dial String Elements
String Elements

Description

ATDT

Enter characters either in all upper case or all lower case:
AT = Attention
D = Dial
T = Tone (for touch-tone)

outside-line,

In the example below, “9” gets an outside line. Enter the
number for an outside line if your system requires it. The
comma causes a pause of 2 seconds to wait for the outside
line.

pager-number

The telephone number of the pager to be activated.

Example
SCM_E0> set dial ATDT9,16035551212
See Section 3.4 for an overview of how this command is used in conjunction with
others to prepare for remote access.

SCM Command Reference

6-25

6.19.5 Set Escape Command
The set escape command allows you to change the escape sequence
used for entering SCM mode. The escape sequence can be any
printable character string, up to six characters.

Syntax
set escape string
Argument
string

6-26

A string of up to six printable characters to be used as the escape
sequence to enter into SCM mode. The default escape sequence is
<Esc><Esc>scm. Note: the escape key on a PC keyboard is
equivalent to <Ctrl>] (control key and right bracket).

AlphaServer GS80/160/320 Firmware Reference Manual

6.19.6 Set <environment_variable> Command
The SCM has three environment variables.

Syntax
set {hp_count n, hp_qbb_maskn mask, scm_csb_master_eligible {n, list}}
Arguments
hp_count n

Defines the number of hard partitions that the
system is to be divided into by the decimal
number n, which may range from 0 – 8.

hp_qbb_maskn mask

Defines the QBBs to be included in hard
partition n (0 – 7) by the hexadecimal value
mask. A bit set in the mask indicates that the
QBB is to be included in partition n.

scm_csb_master_eligible n

Set from within a hard partition to define
whether the SCM for that partition is eligible (n
= 1) or ineligible (n = 0 or not set) to become a
master SCM.

Example
SCM_E0> set hp_count 3 ➊
SCM_E0> set hp_qbb_mask0 1
SCM_E0> set hp_qbb_mask1 2
SCM_E0> set hp_qbb_mask2 c
SCM_E0> set scm_csb_master_eligible 1
SCM_E0> power on –par 0

➊

➋

Defines three hard partitions for the system. Hard partition 0 consists
of QBB0. Hard partition 1 consists of QBB1. Hard partition 2 consists
of QQB2 and QBB3. (See Chapter 4 for a detailed description of setting
bit masks for the hp_qbb_mask environment variable.)
The SCM node E0 is declared eligible to be selected as the master CSB
node for the system.

SCM Command Reference

6-27

6.19.7 Set Flow Command
The set flow command allows you to change the protocol used to handle
flow control on one of the local, remote, or system COM1 ports.

Syntax
set [local, modem, com1] protocol_type
Options
local

Defines the protocol for the local port

remote

Defines the protocol for the remote port

com1

Defines the protocol for the COM1 port

Arguments
protocol_type

6-28

hard

Flow control protocol is handled by special cables
that implement flow control signals. Typically used
when a user wishes to transfer data that may
contain software flow control characters that are not
to be interpreted as such.

soft

Flow control protocol implemented by software conventions defining certain characters that regulate
flow, such as characters that define the start and
end of a particular transmission. Binary transfers
are not possible since data may inadvertently contain one of the special characters.

both

Both hard and soft flow control may be used.

none

No flow control is used.

AlphaServer GS80/160/320 Firmware Reference Manual

6.19.8 Set Init Command
The set init command assigns the modem initialization string
appropriate for the dial-out modem at the system site. The format of an
initialization string is unique to each modem.

Syntax
set init string

Defines the parameter to be set as the initialization string for
the local modem. See the user guide for your modem to
determine how you want to set parameters controlling the
modem’s operation, and construct the string value
accordingly. Table 6–5 lists some typical modem
initialization strings.

Table 6–5 Modem Initialization Strings
Modem

Initialization String

Hayes Accura 336/56k

ate0v0&c1&k3s0=2

Compaq Microcom 510

ate0v0&c1s0=2

3Com USR Courier V.Everything

ate0v0&c1s0=2

3Com USR 56K* (5676) (Japanese)

ate0v0&c1s0=2

AT&T Dataport 14.4

ate0v0&c1s0=2

MultiTech MT5600ZDS

ate0v0&c1s0=2

Aiwa PV-BW5610 (Japanese)

ate0v0&c1s0=2

Omrom ME5614D (Japanese)

ate0v0&c1s0=2

Example
SCM_E0> set init ate0v0&c1s0=2
See Section 3.4 for an overview of how this command is used in conjunction with
others to prepare for remote access.

SCM Command Reference

6-29

6.19.9 Set Ocp_text Command
The set ocp_text command allows you to define a line of text to be
displayed on the operator control panel after power-up. Typically used
to identify a particular node in multi-system configurations.

Syntax
set ocp_text “string”
Argument
string

Characters to be displayed on the OCP after power-up.

Example
SCM_E0> set ocp_text “Node A1”

6-30

AlphaServer GS80/160/320 Firmware Reference Manual

6.19.10 Set Password Command
The set password command defines a password to be used by the
remote user when dialing in to the system. The password must be set
before the remote enable command is issued.

Syntax
set password password

The password argument consists of up to 14
characters. No escape characters can be used.

Example
SCM_E0> set password flamenco
See Section 3.4 for an overview of how this command is used in conjunction with
others to prepare for remote access.

SCM Command Reference

6-31

6.20 Show Commands
The show commands display the status of the requested components of
the system.

6.20.1 Show CSB Command
The show csb command displays a list of all known nodes on the
console serial bus. The CSB address is used to identify a particular
node when using other SCM commands.

Syntax
show [csb]

Argument
csb

Displays information about the nodes on the console serial bus.

Options
None
Example
SCM_E0> show csb ➊

➋

➌

➍

➎

➏

CSB Type

Firmware Revision

FSL Revision

Power State

10
11
12
13
15
16
30
30
c0
c1
c2
c3
c0
c1
c2
c3
31
31

X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)
(06.12/02:16)

X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)
X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

X05.7
X05.7

(06.12/02:16)
(06.12/02:16)

X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

PBM
PBM
PBM
PBM
PBM
PBM
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
IOR2
IOR3
PSM
XSROM

6-32

AlphaServer GS80/160/320 Firmware Reference Manual

c4
c5
c6
c7
c4
c5
c6
c7
32
32
c8
c9
ca
cb
c8
c9
33
33
cc
cd
ce
cf
cc
cd
40
e0
e1
e2
e6

CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
IOR2
IOR3
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
PSM
XSROM
CPU0/SROM
CPU1/SROM
CPU2/SROM
CPU3/SROM
IOR0
IOR1
HPM
SCM MASTER
SCM SLAVE
SCM SLAVE
SCM SLAVE

V6.0-7
V6.0-7
V6.0-7
V6.0-7

➊

The user enters the show csb command.

➋

This column identifies the address (hexadecimal) of each node currently
on the console serial bus (CSB). You can use this address to identify
nodes for SCM examine, deposit, update, and test commands.

➌

This column identifies the type of node on the console serial bus being
described. This example shows seven PCI backplane managers (PBMs,
four power system managers (PSMs), indicating four QBBs are present.
Under each PSM are listed its XSROM and any CPUs (with attendant
SROM and resident firmware). The HPM is the hierarchical switch
power manager, and the SCM MASTER is the controlling firmware
resident on the standard I/O module selected as the master.

➍

This column lists the firmware revision number and date the firmware
was compiled.

➎
➏

The FSL revision states the revision level of the fail-safe loader.

X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)

X05.7
X05.7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

(06.12/02:16)
(06.12/02:16)

X05.7
X05.7
X05.7
X05.7
X05.7

(11.03/01:11)
(11.03/01:13)
(11.03/01:13)
(11.03/01:13)
(11.03/01:13)

X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

X5.7 (06.09)

ON
ON
ON
ON
ON
ON
ON

SrvSw: NORMAL

T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)
T4.2 (09.08)

ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON

Ineligible
Ineligible
Ineligible

This column lists the power state of each node. In this case, each node is
receiving power. The SrvSw indicator for each PSM indicates either
NORMAL (power on) or SERVICE (power off; the component can be
serviced).

SCM Command Reference

6-33

6.20.2 Show FRU Command
The show fru command displays information on field-replaceable units
(FRUs) in the system.

Syntax
show fru
Example
SCM_E2> show fru
➊
➋

➌

➍

➎

FRUname
PBP0
PBP0.SIO
PBP0.RIO0
PBP0.RIO1
PBP1
PBP1.RIO0
PBP1.RIO1
.
.
.
QBB0
QBB0.PSM
QBB0.PWR
QBB0.AUX
QBB0.CPU0
QBB0.CPU1
QBB0.CPU2
QBB0.CPU3
QBB0.MEM0
QBB0.MEM0.DIM0
QBB0.MEM0.DIM1
QBB0.MEM0.DIM2
QBB0.MEM0.DIM3
QBB0.MEM0.DIM4
QBB0.MEM0.DIM5
QBB0.MEM0.DIM6
QBB0.MEM0.DIM7

E Part#
02 54-25027-01.E01
00 B4190-BA.A01
00
B4171-AA.E01
00 -B4171-AA.D02
02 54-25027-01.E02
00 -B4171-AA.E01
00
-B4171-AA.E01

00 54-25043-02.D02
NI93870848 ..........
00 54-25074-01.E03
NI92160238
00 54-25017-01.E02
NI92660457 ..........
00 54-25123-01.D01
NI90260771
00 7X-B4125-AA.B02
NI93260349 ..........
00 7X-B4125-AA.B02
NI93260309 ..........
00 7X-B4125-AA.B02
NI93260307 ..........
00 73-B4125-AA.B02
NI93470069 ..........
00
-B4150-AA.D02
NI93471470 ..........
00 54-24941-FA.C03
AY92903143 ..........
00 54-24941-FA.C03
AY92903017 ..........
00 54-24941-FA.C03
AY92902981 ..........
00 .................. ??000
..........
00 54-24941-FA.C03
AY92626235 ..........
00 54-24941-FA.C03
AY92626256 ..........
00 54-24941-FA.C03
AY92626234 ..........
00 54-24941-FA.C03
AY92902979 ..........

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

QBB7.DIR
QBB7.DIR0.DIM0
QBB7.DIR0.DIM1
QBB7.DIR0.DIM2
QBB7.DIR0.DIM3
QBB7.DIR0.DIM4
QBB7.DIR0.DIM5
QBB7.DIR0.DIM6
QBB7.DIR0.DIM7
QBB7.IO01
QBB7.IO23
QBB7.GP
HSW8

00
-B4140-AA.D01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00 54-25023-BA.A01
00
-B4170-AA.E01
00
-B4170-AA.E01
00
-B4181-BB.A01
00 B4188-AB.A01

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

6-34

Serial#
Model/Other Alias/Misc
NI92660355
NI91260219
NI93671623 .......... ................
NI93871224 RRISER
WF124A
NI93772160 PCI_BPLANE
WF124
NI94270223 RRISER
WF124A
NI94270218 .......... ................

NI93971621 ..........
AY92604007 ..........
AY92604006 ..........
AY92604484 ..........
AY92617927 ..........
AY92604007 ..........
AY92604006 ..........
AY92604484 ..........
AY92617927 ..........
NI94372518 ..........
NI94372517 ..........
NI94870364 ..........
SW00400007

AlphaServer GS80/160/320 Firmware Reference Manual

HSW8.HPM0
HSW8.PWR1
HSW8.PWR2

➊

00 54-25115-01.D01
00 54-30194-01.C03
00 54-30194-01.C03

Error field. FRUs without errors show 00 (hex). Other values are:
01
02
04
08
10
20
40
80

➌
➍
➎

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

The name of the FRU; acronyms include:
PBP
SIO
RIO
QBB
PSM
PWR
AUX
CPU
MEM
DIM
IO
GP

➋

NI93870661
NI94271569 ..........
NI94271380 ..........

Hardware failure
TDD error has been logged
SDD error has been logged
Reserved
Checksum failure on bytes 0-62
Checksum failure on bytes 64-126
Checksum failure on bytes 128-524
FRU’s system serial number does not match system’s

The part number by which the FRU can be ordered.
The serial number of the FRU.
Optional manufacturing specifications; usually blank.

SCM Command Reference

6-35

6.20.3 Show nvram Command
The show nvram command displays the current settings of
environment variables and parameters set in the NVRAM for the SCM.

Syntax
show nvr[am]
Example
SCM_E0> show nvram
COM1_PRINT_EN
HP_COUNT
HP_QBB_MASK0
HP_QBB_MASK1
HP_QBB_MASK2
HP_QBB_MASK3
HP_QBB_MASK4
HP_QBB_MASK5
HP_QBB_MASK6
HP_QBB_MASK7
SROM_MASK
XSROM_MASK
PRIMARY_CPU
PRIMARY_QBB0
AUTO_QUIT_SCM
FAULT_TO_SYS
DIMM_READ_DIS
SCM_CSB_MASTER_ELIGIBLE
PERF_MON
SCM_FORCE_FSL
OCP_TEXT
AUTO_FAULT_RESTART
SCM_E0>

6-36

➊

1
4
➋
11
22
44
88
0
0
0
0
ff f
ff ff ff ff ff ff ff ff ff 1 0 0
ff
ff
1
0
0
1
➌
20
0
Uninitialized
1

AlphaServer GS80/160/320 Firmware Reference Manual

➊ The user types the show nvram command.
➋ The system has four hard partitions.
➌ This SCM is eligible to become the SCM master.

SCM Command Reference

6-37

6.20.4 Show Status Command
The show status command displays SCM status and information.

Syntax
show status
Example
SCM_E0> show status
System Management Settings
SCM escape sequence

Local Baud/flow control
COM1 Baud/flow control
Modem Baud/flow control
COM1 mode
OCP power switch
OCP halt
OCP secure
Remote access
Remote user
Alerts
Modem password
Modem init string
Modem dial string
Modem alert string
Alert pending
Most recent alert
SCM_E0>

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

6-38

[ESC][ESC]scm

➊

57600 / soft
➋
57600 / hard
57600 / hard
Pass-through
➌
Off
Deasserted
Non-Secure
➍
Disabled
Not Connected
➎
Disabled
wffirmware
➏
ate0v0&c1s0=2
➐
atdt915085551212
,,,,,,,5085551212#;
➑
No

➒

AlphaServer GS80/160/320 Firmware Reference Manual

➊ The escape sequence that returns control to the SCM; in this case, the
default.

➋ Settings of SRM environment variables controlling flow control, baud rate,
and mode used for transmissions between the system and the local and
remote console device.

➌ The current settings of the operator control panel (OCP) power, halt, and
secure options.

➍ The state of remote access to the system; in this case, remote access is
disabled, and no remote connection exists.

➎
➏
➐
➑
➒

Alerts have been disabled since no remote users currently allowed.
The remote password is the default (wffirmware).
Settings defining modem initialization, dial, and alert strings.
No alerts are pending.
There have been no alerts since the system was powered on.

SCM Command Reference

6-39

6.20.5 Show System Command
The show system command displays an overall system summary,
including the most recent system self-test results and the current
temperature readings.

Syntax
show system
Example
SCM_E0> show system
System Primary QBB0 : 1
System Primary CPU : 1 on QBB1

➋

➌

➍

➎

➊
➏

➐ ➑

➒

➓

➀

Par hrd/csb CPU Mem
QBB#
3210 3210

IOR3 IOR2 IOR1 IOR0
(pci_box.rio)

GP QBB
Mod BP

Dir PS Temp
Mod 321 (ºC)

(3) 0/30
(0) 1/31
(2) 2/32
(1) 3/33

Px.x P2.0 Pf.1 Pf.0
P4.0 Px.x Px.x Px.x
Px.x P0.0 Px.x P3.0
--.- --.- Px.x P5.0

P
P
P
P

--PP ---P
--PP --PP
--PP ---P
--PP ---P

HSwitch

Type

HPM40

4-port

➃

PCI Rise1-1
Cab 7 6 5 4
10
12
13
14
15
1f

- - - - - - - - - - - - - - - - - - -

Cables 7 6 5 4 3 2 1 0

➄

➁

- - - - P P P P

P
P
P
P

PPP
PPP
PPPP-

28.0
30.0
26.5
28.1

Temp(ºC)

➂

26.0

➅

➆

➇

Rise1-0
3 2 1

Rise0-1
7 6 5 4

Rise0-0
3 2 1

RIO
1 0

PS
21

Temp
(ºC)

- - - - - - - - - - - - -

- L - L
- - - - - L - - L L - - - - - H

- - S
- L S
- - S
L - S
- - S
L - S

- P
- P
- P
- P
- P
P P

-P
PPPP
PP
PP

32.5
32.5
32.5
32.5
32.5
32.5

➍ CPU self-test results, identified by the slot number in the QBB. Note that
each QBB has two CPUs and one or two memory modules.

6-40

AlphaServer GS80/160/320 Firmware Reference Manual

➎ Memory self-test results, identified by the slot number in the QBB. Note
that not all QBBs are fully populated with four memory modules.

➏ Status of I/O risers in the QBB.

➐
➑
➒
➓
➀
➁

➂
➃
➄

P passed and powered on
p passed and powered off
m.n m = PCI box ID (0-f); n = remote I/O riser (0, 1)
x.x nothing is connected
Global port self-test results for the QBB.
QBB backplane self-test results.
Directory module self-test results for the QBB.
Status of the power supplies to the QBB. Note that QBBs 0 and 1 have
redundant power supplies, while QBBs 2 and 3 do not.
Temperature of the QBB backplane.
This section of the report gives the status of the hierarchical switch.
Possible values are
P Passed
V Valid; present, but may not be turned on
* present
not present
Temperature surrounding the H-switch.
The CSB address of the PBM for each PCI box. This is equal to the PCI box
ID (0 – f) with 10 (hex) added.
The status of the slots in the PCI boxes connected to the I/O risers.
S Standard I/O
* present
- not present
L Low power dissipation
M Medium power dissipation
H High power dissipation

➅ Status of remote I/O riser
P = present
- = not present.
➆ Status of power supplies to the PCI cabinets.
P passed and powered on
p passed and powered off
F failed and powered on
f failed and powered off
- not present
* present but no status yet
➇ Temperature of the PCI box.

SCM Command Reference

6-41

6.21 Test Alert Command
The test alert command tests the modem setup and connection to the
remote pager or computer. The modem must be initialized, alerts must
be enabled, and the OCP keyswitch must not be in the Secure position
before this command can be issued.

Syntax
test alert
Example
SCM_E0> test alert

6.22 Test &pcn Command
The test &pcn command allows you to run tests on CPUs.

Syntax
test -&pcn test_number
Argument
-&pcn

Defines the processor to be tested, where n is the soft CPU number of
the processor as shown in a show csb command. The test_number
parameter gives the number of the test to be run. See the AlphaServer
GS80/160/320 Service Manual for a discussion of the tests that can be
run for processors.

Example
SCM_E0> test -&pc8 1

6-42

AlphaServer GS80/160/320 Firmware Reference Manual

Chapter 7
SRM Command Reference

This chapter describes the SRM console program’s command language.
Sections in this chapter include:

•
•
•

SRM Command Overview

•

SRM Console Shell Syntax

•

SRM Console Commands (in alphabetical order)

SRM Command Description Conventions
SRM Command Language Environment Variables

boot

deposit

grep

lpinit

nettest

scm

cat

edit

halt

nvram

set

clear

examine

help

man

power

show

continue

exer

info

memexer

show_status

crash

galaxy

init

memexer_mp

reset

sys_exer

csr

gct

kill

migrate

test

kill_
diags

run bios

wwidmgr

When the system or (partition) is in SRM console mode, the operating system is
halted and the SRM console firmware is executing. The operator communicates
with the firmware through the console terminal, which displays the following
prompt:
Pnn>>>
where nn may range from 00 to 1F (for 32-processor systems). The value
depends on which processor module is the primary processor, as determined
during power-up.

SRM Command Reference

7-1

7.1

SRM Command Overview

The SRM console firmware supports capabilities for the operating
systems offered with AlphaServer GS80/160/320 series systems.

Table 7–1 Summary of SRM Console Commands
Command

Function

boot

Boots the operating systems.

cat

Displays the named file.

clear

Clears the SRM password or an environment variable.

continue

Resumes processing after a Ctrl/P is issued (OpenVMS
systems).

crash

Forces a crash dump of the operating system.

csr

Displays contents of control and status registers.

deposit

Writes data to the specified address.

edit

Invokes the console line editor, which can be used to edit a
RAM file or the user power-up script, “nvram,” which is
always invoked during the power-up sequence.

examine

Displays the contents of a memory location or device
register.

exer

Exercises one or more devices by performing specified read,
write, and compare operations.

galaxy

Initializes soft partitions (same as lpinit).

gct

Rebuilds the Galaxy configuration tree in SRM main
memory.

grep

Globally searches for regular expressions and prints
matches.

halt

Halts the specified processor or device.

help (or man)

Displays information about all or a specific SRM command.

7-2

AlphaServer GS80/160/320 Firmware Reference Manual

Table 7–1 Summary of SRM Console Commands (Continued)
Command

Description

info

Displays registers and data structures.

init

Stores any changes made to environment variables and
reinitializes the hardware.

kill

Stops a process that is running on the system.

kill_diags

Stops all console-based diagnostic processes running on the
system.

lpinit

Initializes soft partitions (same as galaxy).

Displays names of files on the system.

memexer

Runs a requested number of memory tests in the
background.

memexer_mp

Exercises ability of CPUs to share data and remain coherent
by running memory tests on all CPUs.

migrate

Moves one or all CPUs to a given soft partition.

Displays a file one screen at a time.

nettest

Runs loopback tests for PCI-based Ethernet ports. Also
used to test a port on a “live” network.

nvram

Runs the nvram script.

power

Turns power on or removes power from the specified CPU,
I/O riser, or PCI box.

Displays process status and statistics.

Removes files from the file system.

scm

Executes an SCM command from the SRM console prompt.

set envar

Sets the value of an environment variable.

show envar

Displays the state of all or a specified environment variable.

show config

Displays the configuration at the last system initialization.

show device

Displays the controllers and bootable devices in the system.

show fru

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

SRM Command Reference

7-3

Table 7–1 Summary of SRM Console Commands (Continued)
Command

Description

show memory

Displays memory module information.

show pal

Displays version of Tru64 UNIX and OpenVMS PALcode.

show_status

Displays the progress of diagnostic tests. Reports one line of
information for each executing diagnostic.

show version

Displays the version of the SRM console program.

sys_exer

Exercises the entire system.

test

Tests the entire system.

wwidmgr

Manages the WWID registration (Fibre Channel).

7-4

AlphaServer GS80/160/320 Firmware Reference Manual

Table 7–2 Notation Formats for SRM Console Commands
Command
Parameter

Attribute or Action

Length

Up to 255 characters, not including the terminating carriage
return or any characters deleted as the command is entered.
To enter a command longer than 80 characters, use the
backslash character for line continuation (see Table 7–3).

Case

Upper- or lowercase characters can be used for input.
Characters are displayed in the case in which they are
entered.

Abbreviation

Only by dropping characters from the end of words. You
must enter the minimum number of characters to identify the
keyword unambiguously. Abbreviation of environment
variables is allowed with the show command.

Options

You can use command options, to modify the environment,
after the command keyword or after any symbol or number in
the command. See individual command descriptions for
examples.

Numbers

Most numbers are decimal. Addresses and numbers used
with the deposit command are hexadecimal.

No
characters

A command line with no characters is a null command. The
console program takes no action and does not issue an error
message; it returns the console prompt. The SRM console
supports command-line recall (using the up and down arrow
keys) and editing, including use of the right and left arrow
keys.

Spaces or
tabs

Multiple adjacent spaces and tabs are compressed and
treated as a single space. Leading and trailing spaces are
ignored.

SRM Command Reference

7-5

Table 7–3 Special Characters for the SRM Console
Character

Function

Return or Enter

Terminates a command line. No action is taken on a
command until it is terminated.
Continues a command on the next line. Must be the
last character on the line to be continued.
Deletes the previous character.
Toggles between insertion/overstrike mode. The
default is overstrike.
Recalls previous command(s). The last 16 commands
are stored in the recall buffer.
Terminates the running process. Clears Ctrl/S;
resumes output suspended by Ctrl/O. When entered as
part of a command line, deletes the current line. Ctrl/C
has no effect as part of a binary data stream.
Moves the cursor left one position.
Moves the cursor to end of line.
Moves the cursor right one position.
Moves the cursor to beginning of the line.
Deletes the previous word.
Deletes one character.
Stops output to console terminal for current command.
Toggles between enable/disable. The output can be
reenabled by other means as well: when the console
prompts for a command, issues an error message, or
enters program mode, or when Ctrl/P is entered.
Ignored in SRM mode. In program mode, on the
OpenVMS operating system, causes the boot processor
to halt and begin running the SRM console program.

Backslash (\)
Delete
Ctrl/A
Ctrl/B or up-arrow
Ctrl/C

Ctrl/D or left-arrow
Ctrl/E
Ctrl/F or right-arrow
Ctrl/H
Ctrl/J
Backspace
Ctrl/O

Ctrl/P

7-6

AlphaServer GS80/160/320 Firmware Reference Manual

Table 7–3 Special Characters for the SRM Console (Continued)
Character

Function

Ctrl/Q

Resumes output to the console terminal that was
suspended by Ctrl/S.

Ctrl/R

Redisplays the current line. Deleted characters are
omitted. This command is useful for hardcopy
terminals.

Ctrl/S

Suspends output to the console terminal until
Ctrl/Q is entered. Cleared by Ctrl/C.

Ctrl/U

Deletes the current line.

Wildcarding for certain commands such as show.

“ ”

Double quotes let you denote a string for
assignment as an environment variable name.

Specifies that all text between it and the end of the
line is a comment. Control characters are not
considered part of a comment.

SRM Command Reference

7-7

7.2

SRM Command Description Conventions

The following conventions are used in the descriptions of the SRM
console command language.

Table 7–4 SRM Command Description Conventions
Convention

Meaning

fixed-font

SCM command examples are shown in a small fixed-width font.

bold

Command and option keywords are presented in bold type.

item

Italics indicate a placeholder for an item that the user supplies.

[item]

Square brackets are used to enclose optional parameters,
qualifiers, and values. For example, help [topic].

{a, b, c}

Braces containing items separated by commas imply mutually
exclusive values. For example {a, b, c} indicates that you can
choose one of a, b, or c.

{a | b | c}

Braces containing items separated by the vertical bar indicate
that you can choose any combination of a, b, and c.

7-8

AlphaServer GS80/160/320 Firmware Reference Manual

7.3

SRM Command Language Environment Variables

Environment variables allow the user to modify the way the console
commands operate.
An environment variable is a name and value association maintained by the
console program. The value associated with an environment variable is an
ASCII string (up to 127 characters in length) or an integer. Some environment
variables can be set to tailor the recovery behavior of the system on power-up
and after system failures.
Volatile environment variables are initialized to their default by a system reset.
Nonvolatile environment variables stay set across system failures.
Environment variables can be created, modified, displayed, and deleted using
the SRM commands create, set, show, and clear. A default value is
associated with any variable that is stored in the EEPROM area.
Table 7–5 (in the description of the set command, Section 7.5.33) lists the
console environment variables, their attributes, and their functions.

SRM Command Reference

7-9

7.4

SRM Console Shell Syntax

The SRM console command language is modeled after the Bourne shell
which runs under the UNIX operating system. Some useful features of
this implementation are described here.

7.4.1

I/O Pipes

A pipeline is a sequence of one or more commands separated by the pipe
operator “|”. The output of each command with the exception of the last
command is used as input to the next command. For example, to locate SCSI
devices in a system, pipe the output of the show device command into the
grep command:
P00>>> show device | grep dk
dka0.0.0.1.0
dkb0.0.0.7.1
dkb100.1.0.7.1
dkb200.2.0.7.1
dkb300.3.0.7.1

7.4.2

DKA0
DKB0
DKB100
DKB200
DKB300

RZ1DF-BF
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0

1614
3B05
3B05
3B05
3B05

Redirecting Output

With the lengthy output provided by some of the commands, it may be useful to
direct output to a file that can be examined with the cat or more command.
You can direct the output of a command into a file using the output operator
“>”. For example:
P00>>> show config > cfgtemp
P00>>> more cfgtemp
[first screen of show config output]
P00>>>

7-10

AlphaServer GS80/160/320 Firmware Reference Manual

7.4.3

Background Operator

The background operator “&” is used at the end of the command line to execute
command sequences in the background as a separate process. This is especially
useful when starting concurrent tests or exercisers on the system. For example:
P00>>> memtest –sa 2000000 –ea 3000000 –p 0 &
P00>>> show_status
ID
Program
Device
Pass
Hard/Soft Bytes Written
------------------------- --------- ------------00000001
idle
system
0
0
0
0
00000184
memtest
memory
832438
0
0
6819323904

Bytes Read
---------0
6819323904

SRM Command Reference

7-11

7.5

SRM Console Commands

SRM commands allow you to examine and modify system state.
Additionally, you can test specific components of the system.

7.5.1

Boot Command

The boot command boots the Tru64 UNIX and OpenVMS operating
systems and the Loadable Firmware Update (LFU) utility.

Syntax
b[oot] [-file filename] [-flags [value]] [-halt] [-protocols enet_protocol] [boot_dev]
Options
-file filename

Specifies the name of the file to load into the system. Use the
set boot_file command to set a default bootfile. See Section
7.5.33.
NOTE: For booting from Ethernet, the filename is limited by
the MOP V3 load protocol to 15 characters. The MOP
protocol is used with OpenVMS systems.

-flags [value]

Provides additional operating system-specific boot information.
In Tru64 UNIX, specifies boot flags. In OpenVMS, specifies the
system root number and boot flags. Preset default boot flag
values are 0,0. Use the set boot_osflags command to change
the default boot flag values. See Section 7.5.33.

-halt

Forces the bootstrap operation to halt and invoke the SRM
console program. The console is invoked after the bootstrap
image is loaded and page tables and other data structures are
set up. Console device drivers are not shut down. Transfer
control to the bootstrap image by entering the continue
command.

7-12

AlphaServer GS80/160/320 Firmware Reference Manual

protocols
enet_protocol

Specifies the Ethernet protocol to be used for the network boot.
Either mop (for OpenVMS) or bootp (for Tru64 UNIX) may be
specified. Use the set_ew*0_protocols command to set a
default network boot protocol. See Section 7.5.33.

Arguments
boot_dev

A device path or list of devices from which the SRM console
program attempts to boot. Use the set bootdef_dev command
to set a default boot device. See Section 7.5.33.

Entering values for boot flags, the boot device name, or Ethernet protocol with
the boot command overrides the current default value for the current boot
request, but does not change the corresponding environment variable. For
example, if you have defined a value for boot_osflags and you specify the
–flags option on the boot command line, the –flags argument takes precedence
for that boot session.

SRM Command Reference

7-13

Example (Boot Command)

P00>>> b dkb4 -fl A –file vmunix
➊
(boot dkb400.4.0.1.2 -file vmunix -flags A)
block 0 of dkb400.4.0.1.2 is a valid boot block
reading 13 blocks from dkb400.4.0.1.2
bootstrap code read in
base = 344000, image_start = 0, image_bytes = 1a00
initializing HWRPB at 2000
➋
initializing page table at 3fffb2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
➌
.
.
.
Digital UNIX Version V4.0 (wfsys6.eng.pko.dec.com) console
login: root
➍
Password:
Last login: Wed Sep 8 23:49:02 on console
.
.
.
➎
sys6>

7-14

AlphaServer GS80/160/320 Firmware Reference Manual

The example shows an operator booting the Tru64 UNIX operating system,
using the SRM console command boot (abbreviated as b in the example). The
SRM console operates in a processor on the system called the primary processor,
selected during power-up, as described in Chapter 2.

➊

➋

➌

The SRM jumps to bootstrap code that has been loaded into memory from
the boot device to boot the operating system from the disk named in the
boot command.

➍

The Tru64 UNIX operating system is given control and displays the
prompt for login name and password.

➎

The operator is at the operating system prompt and can initiate operations
to be performed by the operating system.

SRM Command Reference

7-15

7.5.2

Cat Command

This command concatenates files that you specify to the standard
output. If you do not specify files on the command line, cat copies
standard input to standard output.

Syntax
cat [-length n] [-block n] [-start offset] [-quiet] file…
Options
-length n

Specifies the number of bytes in hex of each input file to copy.

-block n

Size of the internal buffer cat uses to copy files, in hex. By
default, this is DEF_ALLOC (2048) bytes. For performance in
copying disks, a number such as 10000 can be used.

-start n

Specifies the offset to seek to in hex. If the file(s) are not
seekable, then this qualifier has no effect.

-quiet

Uses silent mode on fopens.

Argument
file…

The name of the input file or files to be copied.

Example
P00>>> cat el

➊

starting console on CPU 0
➋
initialized idle PCB
initializing semaphores
initializing heap
initial heap 2c0c0
memory low limit = 1f6000
heap = 2c0c0, 1ffc0
initializing driver structures
initializing idle process PID
initializing file system
initializing timer data structures
lowering IPL
CPU 0 speed is 731 MHz
create dead_eater

7-16

AlphaServer GS80/160/320 Firmware Reference Manual

create poll
create timer
create powerup
access NVRAM
QBB 0 memory, 8 GB
QBB 1 memory, 8 GB
total memory, 16 GB
probe I/O subsystem
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1
.
.
.
Change to Internal loopback.
Change to Normal Operating Mode.
Change to Internal loopback.
Change to Normal Operating Mode.
fwb0.0.0.3.8 StateExpt = 4 StateRcv = 5
fwb0.0.0.3.8 StateExpt = 4 StateRcv = 5
fwb0.0.0.3.8 StateExpt = 4 StateRcv = 5
fwb0.0.0.3.8 StateExpt = 4 StateRcv = 5
P00>>>

➊

The user types the command cat el to display the event log on the console
device.

➋

The event log for the current period of execution is displayed.

SRM Command Reference

7-17

7.5.3

Clear Command

This command clears the SRM password or an environment variable.

Syntax
clear {password, environment_variable}
Arguments
password

The clear password command is used in conjunction with
the set secure, set password, and login commands. The
clear password command clears the password; there must
be a valid password and the console must be logged in for the
command to function.

environment_
variable

Clears the named environment variable, if it is volatile
(including environment variables created by the user with the
set command). Will not clear nonvolatile environment
variables.

Example
P00>>> show hp_count

➊

hp_count

P00>>> clear hp_count
P00>>> show hp_count
hp_count

➋
P00>>> clear password
Please enter the password:
Password successfully cleared
P00>>>
➊

The show command shows the value of the hp_count environment
variable to be 2. The clear hp_count command clears it to 0.

➋

The clear password command prompts for the current password. When
it is entered, the password is cleared, and a message to that effect is
displayed.

7-18

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.4

Continue Command

For OpenVMS systems, the continue command resumes processing at
the point where it was interrupted by a Ctrl/P at the console terminal,
by the Halt button on the operator control panel, or by an SCM halt in
command.

Syntax
c[ontinue]
Example
P00>>> continue

➊

continuing CPU

➋

<Enter>
$

➌

➍

➊ The user types the continue command.
➋ The SRM console code prints the “continuing CPU” message.
➌ Control returns to the operating system. No displays are forthcoming, so
the user presses the Enter (or Return) key to see what happens.

➍ In this case, the OpenVMS system was waiting for command line input.
When the user enters Return, it redisplays the $ prompt.

SRM Command Reference

7-19

7.5.5

Crash Command

The crash command causes the operating system to be restarted and
generates a memory dump.

Syntax
cra[sh]
Example
P00>>> crash

➊

CPU 0 restarting
DUMP: 1983738 blocks available for dumping
DUMP: 118178 wanted for a partial compressed dump.
DUMP: Allowing 2060017 of the 2064113 available on 0x800001
device string for dump = SCSI 1 1 0 0 0 0 0.
DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787
DUMP: Header to 0x800001 at 2064113 (0x1f7ef1)
device string for dump = SCSI 1 1 0 0 0 0 0.
DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787
DUMP: Dump to 0x800001: .......: End 0x800001
device string for dump = SCSI 1 1 0 0 0 0 0.
DUMP.prom: dev SCSI 1 1 0 0 0 0 0, block 2178787
DUMP: Header to 0x800001 at 2064113 (0x1f7ef1)
succeeded
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc0000568704
P00>>>

➊ The crash command restarts the operating system and generates a memory
dump.

This command is useful when the operating system is hung. The user can
return to the SRM console, and then issue the crash command to restart
the operating system and generate a memory dump.

7-20

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.6

CSR Command

The csr command displays the contents of the system’s control and
status registers (CSRs). If a hex data value is specified, the command
deposits to the specified register or registers before displaying.

Syntax
csr [ name [ data ] ]
Arguments
name

Name of the CSR register to be displayed, and if data is supplied,
deposited to and then displayed. Wildcarding is permissible (see
example). If no name is specified, all registers are displayed or
deposited to.

data

A hexadecimal value to be deposited in the named register or
registers.

Example
P00>>> csr *scratch

➋

➊

➌

CSR Name
CSR Address
---------------------------------------------QBB0.QSD.CPU0_SCRATCH
fffff940800
QBB0.QSD.CPU1_SCRATCH
fffff940840
QBB0.QSD.CPU2_SCRATCH
fffff940880
.
.
.
QBB0.IOP.IOA_SCRATCH
fffffa01400
QBB0.IOP.IOD_SCRATCH
fffffa01440
QBB0.IOPort0.PCA_SCRATCH
fffffb00140
QBB0.IOPort3.PCA_SCRATCH
fffffbc0140
QBB0.IOPort0.NE_SCRATCH
fffffb10240
QBB0.IOPort3.NE_SCRATCH
fffffbd0240
QBB0.IOPort0.FE_SCRATCH
fffffb18240
QBB0.IOPort3.FE_SCRATCH
fffffbd8240
QBB0.GP.GPA_SCRATCH
fffffc02800
QBB0.GP.GPD_SCRATCH
fffffc21000
P00>>> csr iop*a*scratch cedebeadfeedface
➎
CSR Name
CSR Address
---------------------------------------------QBB0.IOP.IOA_SCRATCH
fffffa01400
QBB0.IOPort0.PCA_SCRATCH
fffffb00140
QBB0.IOPort3.PCA_SCRATCH
fffffbc0140
P00>>>

➍

CSR Data
---------------0000000000000000
0000000000000000
0000000000000000

0000000a0000000a
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
0000000000000000
0000000000000000
CSR Data
---------------cedebeadfeedface
cedebeadfeedface
cedebeadfeedface

SRM Command Reference

7-21

➊

The user issues a csr command to display information about the control
and status registers. In this case, all registers ending with the
characters “scratch” are requested.

➋

The names of the control and status registers.

➌
➍
➎

The addresses of the registers.

7-22

AlphaServer GS80/160/320 Firmware Reference Manual

The contents of the registers.
The user issues a csr command. In this case, all registers beginning with
the letters “iop”, containing an “a”, and terminating with “scratch” are to
be displayed. In addition, the hexadecimal value “cedebeadfeedface” is to
be deposited in each register before it is displayed.

7.5.7

Deposit and Examine Commands

The deposit command stores data in an address that you specify: a
memory location, a register, a device, or a file. The examine command
displays from the same locations.

Syntax
d[eposit] [ - {b, w, l, q, o, h}], [-{physical, virtual, gpr, fpr, ipr}]
[-n count ] [-s step] [device:] address data
e[xamine] [-{b, w, l, q, o, h}] [-{physical, virtual, gpr, fpr, ipr}]
[-n count] [-s step] [device:] address
Options
-b

The data deposited is a byte (8 bits).

-w

The data deposited is a word (16 bits).

-l

The data deposited is a longword (32 bits).

-q

The data deposited is a quadword (64 bits). This is the default.

-o

The data deposited is an octaword (128 bits).

-h

The data deposited is a hexword (256 bits).

-gpr

The address space is general-purpose registers.

-ipr

The address space is internal processor registers.

-fpr

The address space is floating-point registers.

-physical

The address space is physical memory.

-virtual

The address space is virtual memory.

-n count

The address will be incremented count (hex) times.

-s step

The increment size (hex). Normally this defaults to the data size,
but is overriden by the presence of this qualifier. This option must
be specified each time; it does not apply to following deposit or
examine commands.

SRM Command Reference

7-23

Arguments
device:

The optional device name (or address space) selects the device to
access. Possible values are:
pmem:
vmem:

Physical memory
Virtual memory. All access and protection checking occur.
If the access would not be allowed to a program with the
current PS, the SRM console issues an error message. If
memory mapping is not enabled, virtual adressses are
equal to physical addresses.

gpr:

General purpose register set R0 – R31
Data size default = q
fpr:
Floating-point register set, F0-F31
Data size default = q
pt:
PAL temporary register set PT0-PT31
Data size default = q
eerom: 8 KB NVRAM
flash:
2 MB flash EEPROM
ipr:
Internal processor register
pcicfg: PCI configuration space
pciio:
PCI I/O space
pcimem: PCI memory space
psr:
Processor status register
toy:
Time of year clock

address

An address that specifies the offset within a device into which data is
deposited. The address may be any valid hexadecimal offset in the
device’s address space.

data

The data (hex) to be written to the specified address or register.

Symbolic forms can be used for the address. They are:
pc

The program counter. The address space is set to GPR.

The location immediately following the last location referenced in a
deposit or examine command. For physical and virtual memory, the
referenced location is the last location plus the size of the reference (1
for byte, 2 for word, etc.) For other address spaces, the address is the
last referenced address plus 1.

The location immediately preceding the last location referenced in a

7-24

AlphaServer GS80/160/320 Firmware Reference Manual

deposit or examine command. Memory and other address spaces are
handled as above.
*

The last location referenced in a deposit or examine command.

The location address by the last location referenced in a deposit or
examine command.

Example

➊
P00>>> deposit -q -p -n 3 0 a5a5a5a5
P00>>> examine -q -p -n 10 0
➋
pmem:
0 00000000A5A5A5A5
➌
pmem:
8 00000000A5A5A5A5
pmem:
10 00000000A5A5A5A5
pmem:
18 00000000A5A5A5A5
pmem:
20 0000000000000000
pmem:
28 0000000000000000
pmem:
30 0000000000000000
pmem:
38 0000000000000000
pmem:
40 0000000000000000
pmem:
48 0000000000000000
pmem:
50 0000000000000000
pmem:
58 0000000000000000
pmem:
60 0000000000000000
pmem:
68 0000000000000000
pmem:
70 0000000000000000
pmem:
78 0000000000000000
pmem:
80 0000000000000000
P00>>>
➊

The deposit command deposits four quadwords (the original deposit plus
three increments) with the value a5a5a5a5 in physical memory beginning
at location 0.

➋

The examine command requests the display of 11 (hexadecimal)
quadwords of physical memory beginning at location 0 and incrementing
this address 10 (hexadecimal) times.

➌

The value a5a5a5a5 has been stored in the first four memory locations, as
the display shows.

SRM Command Reference

7-25

7.5.8

Edit Command

The system comes with a nonvolatile file named “nvram” that is stored
in EEROM on the standard I/O module. The nvram file is a usercreated power-up script (set of commands) that is always invoked
during the power-up sequence. Use the edit command to create or alter
the nvram script.

Syntax
edit file
Argument
file

The name of the file to be edited. Most commonly used to create and
edit the file named nvram.

Description
You can create an nvram script to include any commands you want the system
to execute at power-up. You create and edit the nvram script using the SRM
edit command. With edit, lines may be added, overwritten, or deleted. To
clear the script, enter the existing line numbers without any text. This deletes
the lines.
Once you issue the edit command, the editor displays informative messages
(see example) and displays an asterisk prompt (*). You can then use the
following commands:
help

Displays the brief help file.

list

Displays the current file prefixed with line numbers.

renumber

Renumbers the lines of the file in increments of 10.

exit

Leaves the editor and closes the file, saving all changes.

quit

Leaves the editor and closes the file without saving changes.

Deletes line number nn.

nn text

Adds or overwrites line number nn with the specified text.

7-26

AlphaServer GS80/160/320 Firmware Reference Manual

Example
P00>>> edit nvram ➊
editing ‘nvram’
➋
0 bytes read in
*10 set mopv3_boot 1 ➌
*exit
➍
17 bytes written out to nvram
P00>>> edit nvram ➎
editing ‘nvram’
20 bytes read in
➏
*list
10 set mopv3_boot 1
➐
*10
*quit
➑
17 bytes written out to nvram
P00>>>

➊
➋
➌

➍
➎
➏
➐
➑

The user issues the command to edit the nvram file.
The editor displays the name of the file being edited and the number of
bytes currently in the file.
The user creates a line numbered “10” with a command that sets the
mopv3_boot environment variable to 1. (By default, MOP boots send four
MOPV4 requests before defaulting to MOPV3. This environment variable
setting forces the SRM console to bypass MOP V4 requests. This speeds up
MOP booting on networks with MOP V3 software.)
The exit command writes the file named nvram to EEROM on the
standard I/O module, including the new line, and returns control to the
SRM console code.
The user again issues a command to edit the file named nvram.
The list command displays the contents of the file.
The user enters the line number 10 without text, deleting the line.
The quit command writes the file to the standard I/O module without the
changes made during the current editing session. The file is unchanged.

CAUTION: An inappropriate command in the nvram script can disable the
system. For example, the init command will cause the system to go
into an endless loop.
To correct this error, press the Halt button during power-up. When
the Pnn>>> prompt is displayed, edit the script to remove the
improper command.

SRM Command Reference

7-27

7.5.9

Exer Command

The exer command exercises one or more devices by performing
specified read, write, and compare operations. Advanced users may
want to use the specific options described here.

CAUTION: Running exer on disks can destroy data on the disks.
Syntax
exer [-sb start_block] [-eb end_block] [-p pass_count]
[-l blocks] [-bs block_size] [-bc blocks_per_io]
[-d1 buf1_string] [-d2 buf2_string]
[-a action_string] [-sec seconds] [-m] [-v] [-delay millisecs] device_name
Options
-sb start_block

Specifies the starting block number (hex) within the
filestream. The default is 0.

-eb end_block

Specifies the ending block number (hex) within the
filestream. The default is 0.

-p pass_count

Specifies the number of passes to run the exerciser. If 0,
then run forever or until Ctrl/C. The default is 1.

-l blocks

Specifies the number of blocks (hex) to exercise. The option l
has precedence over eb. If only reading, then not using
either –l nor –eb defaults to read until end-of-file. If
writing, and neither –l or –eb are specified, then exer will
write for the size of device. The default for blocks is 1.

-bs block_size

Specifies the block size (hex) in bytes. The default is 200
(hex).

-bc blocks_per_io

Specifies the number of blocks (hex) for each I/O operation.
On devices without length (tape), use the specified pack size
or default to 2048. The maximum block size allowed with
variable-length block reads is 2048 bytes. Default = 1.

-d1 buf1_string

String argument for eval to generate buffer 1 data pattern
from. Buffer 1 is initialized only once before any I/O occurs.

7-28

AlphaServer GS80/160/320 Firmware Reference Manual

Default = all bytes set to hex 5As.
-d2 buf2_string

String argument for eval to generate buffer 2 data pattern
from. Buffer 2 is initialized only once before any I/O occurs.
Default = all bytes set to hex 5As.

-a action_string

Specifies an exerciser action string that determines the
sequence of reads, writes, and compares to various buffers.
The default action string is ?r. The action string characters
are:
r
w
R
W
n
N
c
?

Read into buffer 1
Write from buffer 1
Read into buffer 2
Write from buffer 2
Write without lock from buffer 1
Write without lock from buffer 2
Compare buffer1 with buffer 2
Seek to file offset prior to last read or write
Seek to a random block offset within the specified range
of blocks. exer calls the program, random, to “deal”
each one of a set of numbers once. exer chooses a set
that is a power of two and is greater than or equal to
the block range. Each call to random results in a
number that is then mapped to the set of numbers that
are in the block range and exer seeks to that location
in the filestream. Since exer starts with the same
random number seed, the set of random numbers
generated will always be over the same set of block
range numbers.
Sleep for a number of milliseconds specified by the
delay qualifier. If no delay qualifier is present, sleep
for 1 millisecond. Note: Times as reported in verbose
mode will not necessarily be accurate when this action
character is used.

Zero buffer 1

Zero buffer 2

Add constant to buffer 1

Add constant to buffer 2

SRM Command Reference

7-29

-sec seconds

Specifies termination of the exercise after the number of
seconds have elapsed. By default, the exerciser continues
until the specified number of blocks of passes are processed.

-m

Specifies metric mode. At the end of the exercise, a total
throughput line is displayed.

-v

Specifies verbose mode. Data read is also written to the
standard output. This is not applicable on writes or
compares. The default is verbose mode off.

-delay millisecs

Specifies the number of milliseconds to delay when “s”
appears as a character in the action string.

Description
The exer command reports performance statistics:

•

A read operation reads from a specified device into a buffer.

•

A write operation writes from a buffer to a specified device.

•

A compare operation compares the contents of the two buffers.

•

The exer command uses two buffers, buffer 1 and buffer 2, to carry out the
operations. A read or write operation can be performed using either buffer.
A compare operation uses both buffers.

Examples

➊
P00>>> exer dk*.* -p 0 –secs 36000
P00>>> exer –l 2 dkb0
➋
P00>>> exer –sb 1 –eb 3 –bc 4 –a ‘w’ –d1 ‘0x5a’ dka100
P00>>> exer –eb 64 –bc 4 –a ‘?w-Rc’ dkb0
➍
P00>>> exer –a ‘?r-w-Rc’ dka400
➎

➌

➊

Reads all SCSI type disks for the entire length of each disk. Repeat this
until 36000 seconds (10 hours) have elapsed. All disks will be read
concurrently. Each block read will occur at a random block number on each
disk.

➋
➌

Read block number 0 and 1 from device dkb0.

7-30

Write hex 5As to every byte of blocks 1, 2, and 3 of dka100. The packet size
is bc times bs, or 4 times 512, or 2048 for all writes.

AlphaServer GS80/160/320 Firmware Reference Manual

➍

➎

A destructive write test over block numbers 0 through 100 on disk dkb0.
The packet size is 2048 bytes. The action string specifies the following
sequence of operations:
1.

Set the current block address to a random block number on the disk
between 0 and 97. A four-block packet, starting at block numbers 98,
99, or 100 would access blocks beyond the end of the length to be
processed, so 97 is the largest possible starting block address of a
packet.

Write a packet of hex 5As from buffer 1 to the current block address.

Set the current block address to what it was just prior to the previous
write operation.

From the current block address, read a packet into buffer 2.

Compare buffer 1 with buffer 2 and report any discrepancies.

Repeats steps 1 through 5 until enough packets have been written to
satisfy the length requirement of 101 blocks.

A nondestructive write test with packet size of 512 bytes. The action string
specifies the following sequence of operations:
1.

Set the current block address to a random block number on the disk.

From the current block address on the disk, read a packet into buffer 1.

Set the current block address to the device address where it was just
before the previous read operation occurred.

Write a packet of hex 5As from buffer 1 to the current block address.

Set the current block address to what it was just prior to the previous
write operation.

From the current block address on the disk, read a packet into buffer 2.

Compare buffer 1 with buffer 2 and report any discrepancies.

Repeat the above steps until each block on the disk has been written
once and read twice.

SRM Command Reference

7-31

7.5.10 Galaxy Command
The galaxy command initializes soft partitions (same as lpinit).

Syntax
galaxy
Example
P00>>> galaxy
lp_count = 3
lp_mem_size0 = 2000 (8 GB)
CPU 0 chosen as primary CPU for partition 0
lp_mem_size1 = 4000 (16 GB)
CPU 4 chosen as primary CPU for partition 1
lp_mem_size2 = 2000 (8 GB)
CPU 12 chosen as primary CPU for partition 2
lp_shared_mem_size = 2000 (8 GB)
initializing shared memory
partitioning system
OpenVMS PALcode V1.8-1, Tru64 UNIX PALcode V1.75-1
system = QBB 0 1 2 3
+ HS
QBB 0 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA 0
3 + GP (Hard QBB 0)
QBB 1 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA
3 + GP (Hard QBB 1)
QBB 2 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA
+ GP (Hard QBB 2)
QBB 3 = CPU 0
2 3 + Mem 0
3 + Dir + IOP + PCA
1 2 3 + GP (Hard QBB 3)
partition 0
CPU 0 1 2 3
IOP 0
private memory size is 8 GB
shared memory size is 8 GB
micro firmware version is X5.7
shared RAM version is 1.4
hose 0 has a standard I/O module
.
.
.
initializing GCT/FRU at 1f6000
initializing pke pka pkb pkd ewa dra pkc dqa eia eib eic eid eie eif eig
eih eii pkf pkg
AlphaServer Console V5.8-1, built on May 26, 2000 at 12:15:01
P00>>>

7-32

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.11 Gct Command
The Galaxy configuration tree is built automatically when hard
partitions are powered up.
The gct command rebuilds the
configuration tree.

Syntax
gct
Example
P00>>> gct
P00>>>

SRM Command Reference

7-33

7.5.12 Grep Command
The grep command is very similar to the UNIX grep command. It
searches the named files for the expression and prints any lines that
match. Grep works only on ASCII files.

Syntax
grep [ - {c | i | n | v |}], [-f file] [expression] [file..]
Options
-c

Prints only the number of lines matched.

-i

Ignores case in the search. By default, grep is case sensitive.

-n

Prints the line numbers of the matching lines.

-v

Prints all the lines that do not contain the expression.

-f file

Takes the regular expressions from the named file, instead of the
command.

Arguments
expression

7-34

Specifies the target regular expression. If any metacharacters (see
following) are present, the expression should be enclosed with
quotes so the metacharacters will not be confused with characters
to be searched for. The metacharacters are:
^

Matches the beginning of line

Matches the end of line

Matches any single character

[]

Set of characters; [ABC] matches either ‘A’ or ‘B’ or ‘C’. A
dash (other than first or last of the set) denotes a range of
characters. For example [A-Z] matches any uppercase letter.
If the first character of the set is ‘^’, then the sense of the
match is reversed. For example, [^0-9] matches any nondigit. Several characters need to be quoted with backslash
(\) if they occur in a set: ‘\’, ‘]’ ‘-‘, and ‘^’.

AlphaServer GS80/160/320 Firmware Reference Manual

file…

Repeated matching. When placed after a pattern, indicates
that the pattern should match any number of times. For
example, ‘a[a-z][0-9]*’ matches a lowercase letter followed by
zero or more digits.

Repeated matching. When placed after a pattern, indicates
that the pattern should mach one or more times. For
example, ‘[0-9]+’ matches any non-empty sequence of digits.

Optional matching. Indicates that the patern can match zero
or one times. For example, ‘[a-z][0-9]?’ matches lowercase
letter alone or followed by a single digit.

Quote character. Prevents the character that follows from
having special meaning.

Specifies the file(s) to be searched. If none are present, then the
standard input is searched.

Example
P00>>> scm show csb | grep CPU
c0
CPU0/SROM
c1
CPU1/SROM
c2
CPU2/SROM
c3
CPU3/SROM
c4
CPU0/SROM
c5
CPU1/SROM
c6
CPU2/SROM
c7
CPU3/SROM
c8
CPU0/SROM
c9
CPU1/SROM
ca
CPU2/SROM
cb
CPU3/SROM
cc
CPU0/SROM
cd
CPU1/SROM
ce
CPU2/SROM
cf
CPU3/SROM
P00>>>

V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7
V6.0-7

ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON
ON

➊

The user types a command to pipe the SCM command show csb into a
grep to search for the characters CPU.

➋

The grep command displays the lines of the show csb command that
contain the letters CPU.

SRM Command Reference

7-35

7.5.13 Halt
The halt command halts the specified processor or device. Equivalent
to the stop command.

Syntax
halt [-drivers [device_prefix]] [ processor-number]
Options
-drivers [device_prefix]

Specifies the name of the device or device class to
stop. If no device prefix is specified, then all drivers
are stopped.

Argument
processor-number

The soft processor number (from show config or the
SCM’s show csb) of the processor to stop.

Example
P00>>> halt
P00>>>

7-36

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.14 Help or Man Command
The help (or man) command provides basic information on the console
commands.

Syntax
help [command]
Argument
command

The command for which information is to be displayed. If omitted,
help for all commands available is displayed.

Example
P00>>> help edit
NAME
edit
FUNCTION
Invoke the console BASIC-like line editor on a file.
SYNOPSIS
edit <file>
[Subcommands: HELP, LIST, RENUMBER, EXIT or CTL/Z, QUIT]
[<nn> : Delete line number <nn>.]
[<nn> <text> : Add or overwrite line <nn> with <text>.]

7.5.15 Info Command
The info command displays registers and data structures. You can
enter the command by itself or followed by a number (0-6). If you do
not specify a number, a list of selections is displayed and you are
prompted to enter a selection.

Syntax
info [n]
Argument
n

A number from 0 – 6 selecting the information to be displayed:
0

Displays the SRM memory description as described in the Alpha
System Reference Manual.

SRM Command Reference

7-37

Reserved.

Dumps the Galaxy Configuration Tree (GCT) FRU table. Galaxy
is a software architecture that allows multiple instances of
OpenVMS to execute cooperatively on a single computer.

Reserved.

Displays the per CPU impure area in abbreviated form. The
console uses this scratch area to save processor context.

Displays the per CPU impure area in full form. The console uses
this scratch area to save processor context.

Reserved.

Example – Info 0
P00>>> info 0
HWRPB: 2000

MEMDSC:7340

Cluster count: 5

Cluster: 0, Usage: Console
START_PFN: 00000000 PFN_COUNT: 0000026b PFN_TESTED: 00000000
619 pages from 0000000000000000 to 00000000004d5fff
Cluster: 1, Usage: System
START_PFN: 0000026b PFN_COUNT: 000ffd7c PFN_TESTED: 000ffd7c
BITMAP_VA: 0000000000000000 BITMAP_PA: 00000001fffe0000
1047932 good pages from 00000000004d6000 to 00000001fffcdfff
Cluster: 2, Usage: Console
START_PFN: 000fffe7 PFN_COUNT: 00000019 PFN_TESTED: 00000000
25 pages from 00000001fffce000 to 00000001ffffffff
Cluster: 3, Usage: System
START_PFN: 00800000 PFN_COUNT: 000fffe4 PFN_TESTED: 000fffe4
BITMAP_VA: 0000000000000000 BITMAP_PA: 00000011fffc8000
1048548 good pages from 0000001000000000 to 00000011fffc7fff
Cluster: 4, Usage: Console
START_PFN: 008fffe4 PFN_COUNT: 0000001c PFN_TESTED: 00000000
28 pages from 00000011fffc8000 to 00000011ffffffff
P00>>>

7-38

AlphaServer GS80/160/320 Firmware Reference Manual

Example – Info 2
P00>>> info 2
GCT_ROOT_NODE
GCT_NODE:
1fc000
type
1
subtype
0
hd_extension
0
size
30000
rev_major
6
rev_minor
0
id
0000000000000000
node_flags
0
saved_owner
0
affinity
0
parent
0
child
2c0
fw_usage
0
Root->lock
ffffffff
Root->transient_level
2b
Root->current_level
2b
Root->console_req
200000
Root->min_alloc
800000
Root->min_align
800000
Root->base_alloc
4000000
Root->base_align
4000000
Root->max_phys_addr
7fffffffff
Root->mem_size
c0000000
Root->platform_type
50000500000023
Root->platform_name
0000000000000280
Root->primary_instance
0
Root->first_free
b700
Root->high_limit
2fcc0
Root->lookaside
0
Root->available
21780
Root->max_partition
8
Root->partitions
0000000000000180
Root->communities
00000000000001c0
Root->bindings
0000000000000200
Root->max_plat_partition 8
Root->max_desc
8
Root->galaxy_id
1fc128
Root->root_flags
3
dump depth view ? (Y/<N>) n
dump each node ? (Y/<N>) n
dump binary ? (Y/<N>) n
show flags? ( Y/<N>) n

SRM Command Reference

7-39

Example – Info 4
P00>>> info 4
cpu00
cpu03
per_cpu impure area
cns$flag
cns$flag+4
cns$hlt
cns$hlt+4
cns$mchkflag
.
.
.
cns$dc_ctl
cns$dc_ctl+4
cns$dc_stat
cns$dc_stat+4
cns$write_many
cns$write_many+4

00008000 00008c00
00000001 00000001 : 0000
00000000 00000000 : 0004
00000000 00000000 : 0008
00000000 00000000 : 000c
00000158 00000158 : 0210

000000c3 000000c3 : 0330
00000000 00000000 : 0334
00000000 00000000 : 0338
00000000 00000000 : 033c
73fff8c1 73fff8c1 : 0340
00000003 00000003 : 0344

Example – Info 5
P00>>> info 5
cpu00
cpu03
per_cpu impure area
cns$flag
cns$flag+4
cns$hlt
cns$hlt+4
cns$gpr[0]
cns$gpr[0]+4

00008000 00008c00
00000001 00000001 : 0000
00000000 00000000 : 0004
00000000 00000000 : 0008
00000000 00000000 : 000c
00020000 00020000 : 0010
00000000 00000000 : 0014

.
.
.

cns$write_many
cns$write_many+4
P00>>>

7-40

73fff8c1 73fff8c1 : 0340
00000003 00000003 : 0344

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.16 Init Command
The init command resets the SRM console firmware, incorporating any
changes made to environment variables during the foregoing console
session, and reinitializes the hardware.

Syntax
init
Example
P00>>> init
OpenVMS PALcode V1.8-1, Tru64 UNIX PALcode V1.75-1
system = QBB 0 1
+ HS
(Hard Partition 0)
QBB 0 = CPU 0 1 2 3 + Mem 0
2
+ Dir + IOP + PCA 0 1
+ GP (Hard QBB 0)
QBB 1 = CPU 0 1 2 3 + Mem 0 1
+ Dir + IOP + PCA 0 1
+ GP (Hard QBB 1)
micro firmware version is X5.7
shared RAM version is 1.4
hose 0 has a standard I/O module
starting console on CPU 0
initialized idle PCB
initializing semaphores
initializing heap
initial heap 2c0c0
memory low limit = 1f6000
heap = 2c0c0, 1ffc0
initializing driver structures
initializing idle process PID
initializing file system
initializing timer data structures
lowering IPL
CPU 0 speed is 731 MHz
create dead_eater
.
.
.
initializing GCT/FRU at 1f6000
initializing pka pkb pkc pkd pke pkf pkg pkh pki pkj pkk fwa fwb dqa dqb
eia eib pga pga0.0.0.1.10 - Nvram read failed.
Testing the System
Testing the Disks (read only)
Reservation conflict for dkc0.0.0.5.1
.
.
.
Testing the Network
AlphaServer Console V5.801, built on May 26, 2000 at 12:15:01
P00>>>

SRM Command Reference

7-41

7.5.17 Kill Command
The kill command allows you to kill a process that is running on the
system. This is useful for stopping exercisers that may be running.
First, use the show_status or ps command to get the process ID. Then
use the kill command specifying that process ID.

Syntax
kill process_id
Example
P00>>> show_status
➊
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
00000123
memtest memory
2
0
0
520093696
520093696
P00>>> kill 123

➋

P00>>> show_status
➌
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
P00>>>

➊

The user types the show_status command to show the status of any
background processes. Process 123 is shown as a memory exerciser.

➋

The user issues the kill 123 command to terminate the execution of the
memory exerciser.

➌

This show_status command confirms that the memory exerciser is no
longer running.

NOTE: Issue an init command after running tests and/or exercisers before
booting to ensure that registers are properly initialized.

7-42

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.18 Kill_diags Command
The kill_diags command stops all console-based diagnostic processes
running on the system.

Syntax
kill_diags
Example
P00>>> show_status
➊
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
0000011d
memtest memory
2
0
0
520093696
520093696
00000123
memtest memory
2
0
0
520093696
520093696
00000162
memtest memory
2
0
0
520093696
520093696
P00>>> kill_diags

➋

P00>>> show_status
➌
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
P00>>>

➊

The show_status command shows three memory exerciser processes
running on the system.

➋

The kill_diags command terminates all diagnostic processes.

➌

This show_status command shows that the memory exercisers are no
longer running.

NOTE: Issue an init command after running tests and/or exercisers before
booting to ensure that registers are properly initialized.

SRM Command Reference

7-43

7.5.19 Lpinit Command
The lpinit command initializes soft partitions (same as galaxy).

Syntax
lpinit
Example
P00>>> sh lp* ➊
lp_count
3
lp_cpu_mask0
000f
lp_cpu_mask1
0ff0
lp_cpu_mask2
f000
lp_cpu_mask3
0
lp_cpu_mask4
0
lp_cpu_mask5
0
lp_cpu_mask6
0
lp_cpu_mask7
0
lp_error_target
0
lp_io_mask0
1
lp_io_mask1
6
lp_io_mask2
8
lp_io_mask3
0
lp_io_mask4
0
lp_io_mask5
0
lp_io_mask6
0
lp_io_mask7
0
lp_mem_size0
0 = 8 GB
lp_mem_size1
1 = 8 GB, 2 = 8 GB
lp_mem_size2
3 = 8 GB
lp_mem_size3
0
lp_mem_size4
0
lp_mem_size5
0
lp_mem_size6
0
lp_mem_size7
0
lp_shared_mem_size
8 GB
P00>>> lpinit
➋
lp_count = 3
lp_mem_size0 = 2000 (8 GB)
CPU 0 chosen as primary CPU for partition 0
lp_mem_size1 = 4000 (16 GB)
CPU 4 chosen as primary CPU for partition 1
lp_mem_size2 = 2000 (8 GB)
CPU 12 chosen as primary CPU for partition 2
lp_shared_mem_size = 2000 (8 GB)
initializing shared memory
partitioning system
➌
OpenVMS PALcode V1.8-1, Tru64 UNIX PALcode V1.75-1
system = QBB 0 1 2 3
+ HS
QBB 0 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA 0

7-44

3 + GP

AlphaServer GS80/160/320 Firmware Reference Manual

(Hard QBB 0)

QBB 1 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA
3 + GP (Hard QBB 1)
QBB 2 = CPU 0 1 2 3 + Mem 0 1 2 3 + Dir + IOP + PCA
+ GP (Hard QBB 2)
QBB 3 = CPU 0
2 3 + Mem 0
3 + Dir + IOP + PCA
1 2 3 + GP (Hard QBB 3)
partition 0
CPU 0 1 2 3
IOP 0
private memory size is 8 GB
shared memory size is 8 GB
micro firmware version is X5.7
shared RAM version is 1.4
hose 0 has a standard I/O module
.
.
.
initializing GCT/FRU at 1f6000
initializing pke pka pkb pkd ewa dra pkc dqa eia eib eic eid eie eif eig
eih eii pkf pkg
AlphaServer Console V5.8-1, built on May 26, 2000 at 12:15:01
P00>>>

➊

The show lp* command shows the soft partition definition for the system.
At this point, the system has no soft partitions.

➋

The lpinit command initializes the soft partitions for the system.

➌

At this point, the display is only for partition 0. The other partitions are
initializing in their own console windows provided through the SMC
terminal emulator.

SRM Command Reference

7-45

7.5.20 Ls Command
The ls command lists files in the system. Files include script files,
diagnostics, and executable shell commands.

Syntax
ls [-l] [filename…]
Option
Specifies that the list is to be in long format; listing other information
besides the file name.

-l

Argument
filename…

Specifies the file(s) to be listed.

Example
P00>>> ls
alloc
break
.
.
.
srflashload
test
tta0
wc
P00>>> ls *pr
fpr

➊

b
buf

boot
buildfru

bootp
c

bpt
call

start
tftp
tta1
wf

stop
toy
uptime
wwidmgr

sym
true
vmem

sys_exer
tt
vmem_render

➋

gpr

P00>>> ls -l sys_exer
rwx- rd
P00>>>

➌

ipr

3705/3705

1c0cd4

sys_exer

➊ The ls command lists the names of all files in the system.
➋ Wildcarding is allowed with the ls command. Here, all files ending in the
characters “pr” are listed.

➌ This example shows the long form of the listing. The information is in six
fields: (1) access: r=read, w=write, x=execute, b=binary, (2) driver name, (3)
actual size/allocated size in bytes, (4) location in memory (if an rd file), (5)
reference count (how many times this file is currently open, and (6) file name.

7-46

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.21 Memexer Command
The memexer command allows you to test the memory on your system,
using a Gray code memory exerciser. The program randomly allocates
and tests blocks of memory two times the size of the B-cache using all
available memory. The memexer command automatically does testing
in background mode without using the &.

Syntax
memexer [n]
Argument
n

Specifies the number of memory test processes to start. The default is l.

Example
P00>>> memexer 3
➊
memtest -bs 1000000 -rb -p 0 &
memtest -bs 1000000 -rb -p 0 &
memtest -bs 1000000 -rb -p 0 &

➋
P00>>> show_status
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
0000011d
memtest memory
2
0
0
520093696
520093696
00000123
memtest memory
2
0
0
520093696
520093696
00000162
memtest memory
2
0
0
520093696
520093696
P00>>> kill_diags

➌

P00>>> show_status
➍
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
P00>>>

➊
➋

Starts three memory test processes, run in the background.

➌

The kill_diags command terminates the processes.

➍

The show_status command shows that the processes are no longer
running.

The show_status command shows the status of the executing exercisers.

SRM Command Reference

7-47

7.5.22 Memexer_mp
The memexer_mp command invokes pairs of Gray code memory
exercisers on a multiprocessor system. The exercisers are run in the
background. This command exercises the ability of CPUs to share data
and remain coherent.

Syntax
memexer_mp
Description
The memexer_mp command starts a copy of memexer on each CPU, testing a
different longword in a cache block. Since there are 16 longwords in a cache
block, at most 16 memexers are started. The first memexer runs on CPUs 0
and 16 (if they exist), the second, on CPUs 1 and 17 (if they exist), the third, on
CPUs 2 and 18 (if they exist), and so on.
NOTE: Do not call memexer_mp multiple times, as you will get a stream of
data compare errors. Two copies of each exerciser will be touching the
same areas in memory, but they are not synchronized.
Example
P00>>> memexer_mp
memtest -sa 400000 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 400004 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 400008 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 40000C -t 1 -l 40000 -i 10 -p 0 -z &
P00>>> show_status
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ------------00000001
idle system
0
0
0
0
0
00000984
memtest memory
901
0
0
235929600
235929600
00000998
memtest memory
895
0
0
234356736
234356736
000009ac
memtest memory
886
0
0
231997440
231997440
000009f9
memtest memory
869
0
0
227540992
227540992
P00>>> ps | grep memtest
000009f9 002531a0 2
0 00080008 3
memtest waiting on tqe 682b0
000009ac 00286d80 2
2 00040004 2
memtest waiting on tqe 682b0
00000998 0027f7c0 2
3 00020002 1
memtest ready
00000984 00278200 2
3 00010001 0
memtest waiting on tqe 682b0

7-48

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.23 Migrate Command
The migrate command switches one or all CPUs from one soft partition
to another.

Syntax
migrate [-cpu cpu_id, -all] -partition partition_number
Options
-cpu cpu_id

Specifies that one CPU identified by the soft CPU
number cpu_id (from the show config command) is to
be transferred to the specified soft partition.

-all

Specifies that all CPUs in this hard partition are to be
transferred to the specified soft partition.

-partition
partition_number

Specifies the soft partition to which the CPU(s) are to
be transferred.

Example
P00>>> migrate –cpu 0 –partition 2

➊

Transfer CPU 0 to soft partition 2.

SRM Command Reference

7-49

7.5.24 More Command
The more command displays output one screen at a time.

Syntax
more [ –n ] [ file…]
Option
-n

The number of lines to be displayed before waiting for a prompt. The
default is 23. At the prompt, you can type a space for the next series of
lines, press Enter to display the next line, or Q to quit the more
command.

Argument
file…

Specifies the file(s) to be displayed.

Example
P00>>> help | more -10
➊
NAME
help
FUNCTION
Display information about console commands.
SYNOPSIS
help [<command>...]
Command synopsis conventions:
<item> Implies a placeholder for user specified item.
<item>... Implies an item or list of items.
[] Implies optional keyword or item.
--More-MORE> q
P00>>>

[SPACE –next page, ENTER – next line, Q – quit)

➌
➍

➋

➊

The user pipes the help command into the more command requesting a
screen size of 10 lines. Ten lines of the help output are displayed by more.

➋

The more command displays a line describing what commands are
available at the prompt.

➌

The prompt is displayed and the user types q to quit.

➍

Control returns to the SRM prompt. (This also occurs at the end of file.)

7-50

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.25 Nettest Command
The nettest command tests the network ports by running maintenance
operations protocol (MOP) loopback tests.
Many environment
variables can be set to customize nettest. These may be set from the
SRM console before nettest is started.

Syntax
nettest [-f file] [-mode port_mode] [-p pass_count] [-sv mop_version]
[-to loop_time] [-w wait_time] [port_name]
Options
-f file

Specifies the file containing the list of network station
addresses to loop messages to. The default file name is
lp_nodes_ew*n for Tulip ports. The default file name for
Intel Ethernet controller drivers is lp_nodes_ei*n. In
both cases, * is a letter of the alphabet and n is the
controller number.

-mode port_mode

Specifies the mode to set the port adapter (TGEG). The
default is ex (external loopback), the most likely to be
useful in general network testing.

-p pass_count

Default, use environment variable values
df
External loopback
ex
Internal loopback
in
Normal mode
nm
Normal filter
nf
Promiscuous
pr
Multicast
mc
Internal loopback and promiscuous
ip
Force collisions
fc
nofc Do not force collisions
Do not change mode
nc
Specifies the number of passes for the diagnostic. If 0,
then run forever. The default is 1. Each pass will send
the number of loop messages as set by the environment
variable ewa*_loop_count (Tulip driver) or
ela*_loop_count (Intel Ethernet controller driver). Note

SRM Command Reference

7-51

that this is the number of passes for the diagnostic. Each
pass will send the number of loop messages as set by the
environment variable ew*n_loop_count or
ei*n_loop_count.
-sv mop_version

Specifies the MOP (maintenance operations protocol)
version to use. If 3, then MOP V3 (DECnet Phase IV)
packet format is used. If 4, then MOP V4 (DECnet Phase
V IEEE 802.3) format is used.

-to loop_time

Specifies the time, in seconds, allowed for the loop
messages to be returned. The default is 2 seconds.

-w wait_time

Specifies the time, in seconds, to wait between passes of
the test. The default is 0 (no delay). The network device
can be very CPU intensive. This option will allow other
processes to run.

Related Environment Variables
ew*n_loop_count
or
ei*n_loop_count

Specifies the number, in hex, of loop requests to send.
The default is 0x3E8 (l000 decimal) loop packets.

ew*n_loop_inc
or
ei*n_loop_inc

Specifies the number of bytes (in hex) to increase the
message size by in successive messages. The default is
0xA (10 decimal) bytes.

ew*n_loop_patt
or
ei*n_loop_patt

Specifies the loop messages. The following are legitimate
values:

loop_size

Specifies the size (in hex) of the loop message, in bytes.
The default packet size is 0x2E.

0
All zeros
1
All ones
2
All fives
3
All 0xAs
4
Incrementing data
ffffffff All patterns

Argument
port_name

7-52

The Ethernet port on which to run the test.

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.26 Nvram Script
The system comes with a script (set of commands) named “nvram” that
is stored in EEROM. Nvram is a power-up script that is always invoked
during the power-up sequence. Use the SRM edit command to create or
alter the nvram script.

Examples
P00>>> edit nvram
editing ‘nvram’
0 bytes read in
*10
set mopv3_boot 1
*exit
17 bytes written out to nvram
P00>>> edit nvram
editing ‘nvram’
20 bytes read in
*10
*exit
0 bytes written out to nvram
P00>>>
Description
You can create an nvram script with any commands you want the system to
execute at power-up. You create and edit the nvram script using the SRM edit
command. (See Section 7.5.8 for a description of the edit command.)
In the examples above, an environment variable called mopv3_boot is created
and set to 1 on each power-up. By default, MOP boots send four MOP V4
requests before defaulting to MOP V3. This user-created environment variable
forces the SRM console to bypass MOP V4 requests. This speeds up MOP
booting on networks with MOP V3 software.
CAUTION: An inappropriate command can disable the system. For example,
the init command will cause the system to go into an endless loop.
To correct this error, press the Halt button or issue the SCM halt in
command, then power up or reset the system. When the P00>>>
prompt is displayed, edit the nvram script to remove the illegal
command.

SRM Command Reference

7-53

7.5.27 Power Command
The power command supplies or removes power from a CPU, I/O riser
port, or PCI box. To prevent catastrophic errors, shut down the
operating system before using these commands.
Syntax
power {on | off } {none |-cpu n | -ior n | -pci id }
Options
For hard partitions: On power off, the command stops all CPUs
(except the primary) in the hard partition from executing
instructions, stops and disables all interrupts; and disables all DMA.
Power is then removed from all QBBs in that hard partition. PCI
boxes are not powered off. (Note that powering the partition on
again is done with the SCM power on command.)
Supplies or removes power from the specified CPU, where n is the soft
CPU number (see show config) for the system or hard partition).

none

-cpu n

Supplies or removes power from the specified I/O riser port, where n is
the IOR number (see show config) for the system or hard partition.

-ior n

WARNING: There are two IOR ports on a single IOR module.
You must power off both IOR ports on the module before the
IOR module is safe for removal.
-pci id

Supplies power to or removes power from the specified PCI box,
where id is the setting for that PCI box’s node ID switch.

Example
P00>>> power on –cpu 3
Powering on CPU3 (CPU3 in QBB 0)
System Event QBB summary: 01
System Event reported by QBB 0
QBB 0 System Event Summary: 0000000020000000
Restarting console on CPU3
P00>>>
System Event QBB Summary: 01
System Event reported by QB 0
QBB 0 System Event Summary: 0000000008000000
P00>>>

7-54

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.28 Ps Command
The ps command allows you to display information about process
status and statistics. This information is useful when you are running
diagnostic processes. The most useful fields are process ID, CPU
number, program name, and process state.

Syntax
ps
Example
P00>>> memexer_mp
memtest -sa 400000 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 400004 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 400008 -t 1 -l 40000 -i 10 -p 0 -z &
memtest -sa 40000C -t 1 -l 40000 -i 10 -p 0 -z &
P00>>> ps

➊

➋

➌

ID
PCB
Pri CPU Time Affinity CPU
Program State
-------- -------- --- -------- -------- --- ---------- -------------------000009f9 002531a0 2
0 00080008 3
memtest waiting on tqe 682b0
000009ac 00286d80 2
2 00040004 2
memtest waiting on tqe 682b0
00000998 0027f7c0 2
3 00020002 1
memtest ready
00000984 00278200 2
3 00010001 0
memtest waiting on tqe 682b0
P00>>>

➊

The process ID is needed for kill commands to terminate a specific process.

➋
➌

Indicates the number of the CPU being tested.
State of the executing test.

SRM Command Reference

7-55

7.5.29 Reset command
The reset command is used to reset a hard partition.

Syntax
reset
Description
On the hard partition in which the command was entered, the reset command
stops all CPUs (except the primary) from executing instructions, stops and
disables all interrupts, and disables all DMA.
Example
P00>>> reset

7.5.30 Rm Command
The rm command removes the named file(s) from the file system.

Syntax
rm file…
Argument
file..

The name of the file(s) to be removed.

Example
P00>>> ls
sample
datafile
P00>>> rm sample
P00>>> ls
datafile
P00>>>

7-56

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.31 Run BIOS
Certain PCI options contain a BIOS extension ROM which provides
extended services for the option. The run bios command executes code
on the BIOS extension ROM that invokes the utility that provides the
service.
Syntax
run bios device-name
Arguments
device-name

PCI device designator. (See the show bios command.)

Description
The run bios command invokes code on the BIOS extension ROM on a PCI
option.
A BIOS extension ROM resides on a PCI option and provides one or more
extended services for that option, for example, a RAID configuration utility or a
firmware update utility. Once invoked, the BIOS ROM provides a graphical
menu-driven interface to select the service.
After you issue the run bios command, you type a control sequence specific to
the PCI option to bring up the menu interface. See the documentation supplied
with the option for information on running the utility.
At present, a VGA monitor connected to the system is required for running the
utility. Or, you can use a PC. A future release of the SRM console will support
running the utility on the serial line.

•

If you use a VGA monitor, set the console environment variable to
graphics and issue the init command before issuing run bios.

•

If you use a PC, install the option card into a PCI slot on the PC and then
type the control sequence.

Example
P00>>> set console graphics
P00>>> init
➋
P00>>> show bios
Resetting all I/O buses

➊

SRM Command Reference

7-57

pga0.0.0.5.25 – LINK_DOWN timeout
pza0.4.0.3.0 – I2O
vga0.0.0.2.0 – ELSA Gloria Synergy
eia0.0.0.2.2 – DE600 –AA
pkb0.7.0.5.1 –Qlogic ISP10x0
pkd0.7.0.3.28 – QLOGIC ISP10x0
➌
P00>>> run bios pza0
.
.
.
Hit (CTRL + D) for DPT Setup, Waiting for devices
Resetting all I/O buses

➊

The console environment variable is set to graphics and the system is
initialized to put the graphics setting into effect.

➋

The show bios command displays the names of all devices on the system
(or in the hard partition) that have BIOS extension ROMs.

➌

The run bios command executes code on the BIOS extension ROM on
device pza0. The operator is prompted for a control sequence that allows
entry into the utility.

7-58

AlphaServer GS80/160/320 Firmware Reference Manual

7.5.32 SCM Command
The scm command allows the user to execute an SCM command from
the SRM console prompt.

Syntax
scm scm_command
Argument
scm_command

Any of the SCM commands described in Chapter 6.

Example
P00>>> scm show status

➊

System Management Settings

➋

SCM escape sequence

[ESC][ESC]scm

:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:

57600 / soft
57600 / hard
57600 / hard
Pass-through
Off
Deasserted
Non-Secure
Disabled
Not Connected
Disabled
wffirmware
ate0v0&c1s0=2
atdt915085551212
,,,,,,,5085551212#;
No

➊

The user issues the scm command to display a show status from the SRM
command prompt.

➋

The show status command displays. Control returns to the SRM prompt.

SRM Command Reference

7-59

7.5.33 Set envar Command
The set envar command allows you to set or modify the value of an
environment variable.

Syntax
se[t] envar [value]
Argument
envar [value]

Environment variables and their values are given in Table 7–5.

Table 7–5 Environment Variables
Variable

Attribute

Function

auto_action

Nonvolatile

bootdef_dev

Nonvolatile

boot_file

Nonvolatile

boot_osflags

Nonvolatile

Specifies the action the console will take
following an error halt or power-up. Values are:
restart - Automatically restart the system. If
restart fails, boot the operating system.
boot - Automatically boot the operating system.
Systems will use as the default device that
defined by manufacturing (for factory-installed
software), or a default boot device selected by
setting the bootdef_dev environment variable.
halt (default) - Enter SRM console mode.
Defines the default device or device list from
which booting is attempted when no device
name is specified by the boot command.
Defines the default file name used for the
primary bootstrap when no file name is
specified by the boot command, if appropriate.
Defines additional parameters to be passed to
the system software during booting if none are
specified by the boot command with the -flags
specifier.

7-60

AlphaServer GS80/160/320 Firmware Reference Manual

Table 7-5 Environment Variables (Continued)
Variable

Attribute

Function

com1_baud

Nonvolatile

Sets the default baud rate of the COM1
serial interface. The default is 9600.
Supported values: 1800, 2000, 2400, 3600,
4800, 7200, 9600, 19200, 38400, 57600.

com2_baud

Nonvolatile

Sets the default baud rate of the COM2
port. Select a baud rate to match that of
the device connected to the COM2 port.

com1_flow
com2_flow

Nonvolatile

The com1_flow and com2_flow environment variables indicate the flow control
on the serial ports. Defined values are:
No data flows in or out of the serial
ports. Use this setting for devices
that do not recognize XON/XOFF
or that would be confused by these
signals.
Use XON/XOFF (default).
software
This is the setting for a
standard serial terminal.
hardware Use modem signals CTS/RTS.
Use this setting if you are
connecting a modem to a
serial port.
Specifies the COM1 data flow paths so that
data either flows through the SCM or
bypasses it. See Section 3.6.
Used to tell the operating system whether a
modem is present on the COM1 or COM2
ports, respectively. Values are:
none

com1_mode

Nonvolatile

com1_modem
com2_modem

Nonvolatile

console

Nonvolatile

Modem is present.

off

Modem is not present (default).

Defines the type of console device.
serial A serial console terminal
graphics A graphics console device.
Continued on next page

SRM Command Reference

7-61

Table 7-5 Environment Variables (Continued)
Variable

Attribute

Function

cpu
cpu_enabled

Nonvolatile
Nonvolatile

d_harderr

Volatile

d_report

Volatile

d_softerr

Volatile

d_trace

Nonvolatile

dump_dev

Nonvolatile

Selects the current boot processor.
A bitmask indicating which processors are
enabled to run (leave console mode).
Default is 0xffffffff.
Determines action taken following a hard
error. Values are halt (default) and
continue. Applies only when using test.
Determines level of information provided
by the diagnostic reports. Values are
summary and full (default). Applies only
when using test.
Determines action taken following a soft
error. Values are continue (default) and
halt. Applies only when using test.
Specifies whether or not to display test
trace messages.
off (default) - Disables trace messages
on - Enables trace messages
Device to which dump file is written if the
system crashes, if supported by the
operating system.

enable_audit

Nonvolatile

If set to on (default), enables the
generation of audit trail messages. If set
to off, audit trail messages are suppressed.
Console initialization sets this to on.

ew*0_loop_count

Nonvolatile

Specifies number of times message is
looped for a test command exercising a
PCI network adapter.

ew*0_loop_inc

Nonvolatile

Specifies the amount the message size is
increased from message to message.

7-62

AlphaServer GS80/160/320 Firmware Reference Manual

Table 7-5 Environment Variables (Continued)
Variable

Attribute

Function

ew*0_loop_patt

Nonvolatile

Specifies data pattern used for loopback.
0xffffffff All the patterns
1
All zeros
2
All ones
3
All As
4
Incrementing
5
Decrementing

ew*0_loop_size

Nonvolatile

Size of loop data used.

ew*0_lp_msg_node

Nonvolatile

Number of messages originally sent to
each node.

ew*0__mode

Nonvolatile

Value for the Ethernet port node when it
is started. Allowed values are:
Auto-sensing

BNC

AUI

FastFD (full
duplex)
Auto-negotiate

Twisted-pair
Full duplex, twisted
pair
Number of soft partition (0 – 8)

lp_count

Nonvolatile

lp_cpu_maskn

Nonvolatile

Bit mask identifying CPUs in soft
partition n.

lp_error_target

Nonvolatile

Number identifying soft partition to
which errors are to be logged

lp_io_maskn

Nonvolatile

Bit mask identifying soft QBB numbers
defining I/O for soft partition n.

lp_mem_sizen

Nonvolatile

Memory size of soft partition n.

lp_shared_mem_
size

Nonvolatile

Size of memory shared between all soft
partitions.

os_type

Nonvolatile

Used to store operating system type.
Values are vms, openvms, osf, and
unix.

SRM Command Reference

7-63

7.5.34 Show BIOS
Use the show bios command to display the devices on the system that
have BIOS extension ROMs.

Syntax
show bios
Description
The show bios command displays the names of all devices on the system (or in
the hard partition) that have BIOS extension ROMs. It is used in conjunction
with the run bios command.
A BIOS extension ROM resides on a PCI option and provides one or more
extended services for that option. The service depends on the code on the
extension ROM — for example, a RAID configuration utility or a firmware
update utility. Once invoked, the BIOS ROM provides a graphical menu-driven
interface from which to select the service.

7-64

AlphaServer GS80/160/320 Firmware Reference Manual

Example

➋
P00>>> show bios
Resetting all I/O buses
pga0.0.0.5.25 – LINK_DOWN timeout
pza0.4.0.3.0 – I2O
vga0.0.0.2.0 – ELSA Gloria Synergy
eia0.0.0.2.2 – DE600 –AA
pkb0.7.0.5.1 –Qlogic ISP10x0
pkd0.7.0.3.28 – QLOGIC ISP10x0

SRM Command Reference

7-65

7.5.35 Show Configuration
The show configuration command displays the configuration seen at
the last system initialization.
Syntax
sh[ow] c[onfiguration]
Example
P00>>> show config
Compaq Computer Corporation
Compaq AlphaServer GS80 6/627
SRM Console
V5.8-1, built on May 26, 2000 at 12:15:01
PALcode
OpenVMS PALcode V1.81-1, Tru64 UNIX PALcode V1.75-1
QBB 0
Hard QBB 0
Quad Switch
QSA rev 4, QSD revs 0/0/0/0
Duplicate Tag
Up To 4 MB Caches
DTag revs 1/1/1/1
Processor 0
CPU 0
4 MB Cache
EV67 pass 2.4, 731 MHz
Processor 1
CPU 1
4 MB Cache
EV67 pass 2.4, 731 MHz
Processor 2
CPU 2
4 MB Cache
EV67 pass 2.4, 731 MHz
Memory 0
MPA rev 1, MPD revs 1/1
Memory 1
MPA rev 1, MPD revs 1/1
Memory 2
MPA rev 1, MPD revs 1/1
Memory 3
MPA rev 1, MPD revs 1/1
Directory
DMA rev 1, DMD rev 0
IOP
IOA rev 2, IOD revs 0/0
Local Link 0
IOR 0
NE ML rev 2
Remote Link 0
FE ML rev 2
I/O Port 0
PCA rev 3
PCI Box 0
Riser 0
Right Side
Backplane rev 3
PCI Bus 0
Hose 0
64 Bit, 33 MHz
PCI rev 2.1 compliant
PCI Bus 1
Hose 1
64 Bit, 33 MHz
PCI rev 2.1 compliant
Local Link 1
IOR1
NE ML rev 2
Remote Link 1
FE ML rev 2
I/O Port 1
PCA rev 3
PCI Box 0
Riser 1
Left Side
Backplane rev 3
PCI Bus 0
Hose 2
64 Bit, 33 MHz
PCI rev 2.1 compliant
PCI Bus 1
Hose 3
64 Bit, 33 MHz
PCI rev 2.1 compliant
Local Link 2
IOR2
NE ML rev 2
Remote Link 2
FE ML rev 2
I/O Port 2
PCA rev 3
PCI Box 3
Riser 0
Right Side
Backplane rev 3
PCI Bus 0
Hose 4
64 Bit, 33 MHz
PCI rev 2.1 compliant
PCI Bus 1
Hose 5
64 Bit, 33 MHz
PCI rev 2.1 compliant
Local Link 3
IOR3
NE ML rev 2
Remote Link 3
FE ML rev 2
I/O Port 3
PCA rev 3
PCI Box 3
Riser 1
Left Side
Backplane rev 3
PCI Bus 0
Hose 6
64 Bit, 33 MHz
PCI rev 2.1 compliant
PCI Bus 1
Hose 7
64 Bit, 33 MHz
PCI rev 2.1 compliant
Global Port
GPA rev 0, GPD revs 0/0

7-66

AlphaServer GS80/160/320 Firmware Reference Manual

➊
➋

➌

➍

➊

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

➋

QBB 0. 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

SRM Command Reference

7-67

Show Config Example (Continued)
QBB 1
Hard QBB 1
Quad Switch
Duplicate Tag
Processor 1
CPU 5
Processor 2
CPU 6
Memory 0
Memory 3
Directory
IOP
Local Link 0
IOR 4
Remote Link 0
I/O Port 0
PCI Box 1
Riser 0
PCI Bus 0
Hose 8
PCI Bus 1
Hose 9
Local Link 1
IOR5
Remote Link 1
I/O Port 1
PCI Box 1
Riser 1
PCI Bus 0
Hose 10
PCI Bus 1
Hose 11
Local Link 2
IOR6
Local Link 3
IOR7
Global Port
QBB
0
1

Size
8 GB
4 GB

Hose
0
4
8

IOP
0
0
1

QSA rev 4, QSD revs 0/0/0/0
Up To 4 MB Caches
DTag revs 1/1/1/1
4 MB Cache
EV67 pass 2.4, 731 MHz
4 MB Cache
EV67 pass 2.4, 731 MHz
MPA rev 1, MPD revs 1/1
MPA rev 1, MPD revs 1/1
DMA rev 1, DMD rev 1
IOA rev 2, IOD revs 0/0
NE ML rev 2
FE ML rev 2
PCA rev 3
Right Side
Backplane rev 3
64 Bit, 33 MHz
PCI rev 2.1 compliant
64 Bit, 33 MHz
PCI rev 2.1 compliant
NE ML rev 2
FE ML rev 2
PCA rev 3
Left Side
Backplane rev 3
64 Bit, 33 MHz
PCI rev 2.1 compliant
64 Bit, 33 MHz
PCI rev 2.1 compliant
NE ML rev 2
NE ML rev 2
GPA rev 0, GPD revs 0/0

Interleave
32-Way
16-Way
PCI Box
0
3
1

System Memory 12 GB

Primary

Standard I/O Modules
Acer Labs M1543C rev A1-E
Acer Labs M1543C rev A1-E
Acer Labs M1543C rev A1-E

➎

➏

➐
➑

System Memory 12 GB
Board
Set
Array
0
0
0
1
0
1
2
0
2
3
0
3
0
1
4
1
1
5
2
1
6
3
1
7
Total Available

Size
1 GB
1 GB
1 GB
1 GB
1 GB
1 GB
1 GB
1 GB
8 GB

Address
QBB 0 Memory
00000000000
00000000000
00000000000
00000000000
00000000000
00000000000
00000000000
00000000000
32-Way Interleave

Board
Set
Array
0
0
0
3
0
3
0
1
4
3
1
7
Total Available

Size
1 GB
1 GB
1 GB
1 GB
4 GB

Address
QBB 1 Memory
01000000000
01000000000
01000000000
01000000000
16-Way Interleave

7-68

AlphaServer GS80/160/320 Firmware Reference Manual

➒

➎

QBB1. QBB1 components are listed.

➏

PCI I/O information, PCI box 1. QBB1 is connected to only one PCI box,
PCI box 1.
QBB1 I/O port 0 is linked to remote I/O riser 0 located on the right side of
PCI box 1. Logical hose numbers are 8 and 9.
QBB1 I/O port 1 is linked to remote I/O riser 1 located on the left side of
PCI box 1. Logical hose numbers are 10 and 11.

➐

The total system memory size is reported.
QBB0 has 8 GB in a 32-way interleave; QBB1 has 4 GB in a 16-way
interleave.

➑

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

➒

System memory shown by board, set, array, and size.
Continued on next page

SRM Command Reference

7-69

Show Config Example (Continued)

➓

PCI Box
0

Riser
0

0
0
0
0
0

0
0
0
1
1

2
3
7
1
2

0
0
1

1
1
0

6
7
1

1
1
1

0
0
0

1
1
1
1
1
3

3
3
3

➆

Slot
1

Slot
1
2
3

7-70

0
1
1
1
1
0

➇

1
1
1

2
3
5
7
1
2
3
7
1

1
2
7

➀

➁

Option
Hose
Standard I/O Module
0
+ Acer Labs M1543C
0
+ Acer Labs M1543C IDE
0
+ Acer Labs M1543C IDE
0
+ Acer Labs M1543C USB
0
+ QLogic ISP10x0
0
DE500-BA Network Con
0
ELSA GLoria Synergy
0
DEGPA-SA
1
QLogic ISP10x0
2
NCR 53C896
2
+ NCR 53C896
2
09608086
2
+ 19608086/0415129A
2
DEC KZPSA
3
DEC PCI FDDI
3
Standard I/O Module
8
+ Acer Labs M1543C
8
+ Acer Labs M1543C IDE
8
+ Acer Labs M1543C IDE
8
+ Acer Labs M1543C USB
8
+ QLogic ISP10x0
8
DEC KZPSA
8
PowerStorm 350
8
DECchip 21154-AA
9
+ DE602-AA
9
+ DE602-AA
9
DEC PCI MC
9
QLogic ISP10x0
10
DEC KZPSA
10
DEC KZPSA
10
DEGPA-SA
11
Standard I/O Module
4
+ Acer Labs M1543C
4
+ Acer Labs M1543C IDE
4
+ Acer Labs M1543C IDE
4
+ Acer Labs M1543C USB
4
+ QLogic ISP10x0
4
DE500-BA Network Con
6
PBXNP-AA Token Ring
6
001B1011/001B1011
7

Option
QLogic ISP10x0
DE500-BA Network Con
ELSA GLoria Synergy

➈

Hose 0, Bus 0, PCI
pka0.7.0.1.0
dka0.0.0.1.0
dka400.4.0.1.0
ewa0.0.0.2.0

➂

➃

Bus

Slot

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

7
15
15
19
1
2
3
7
1
2
2
3
3
6
7

0
0
0
0
0
0
0
0
2
2
0
0
0
0
0

7
15
15
19
1
2
3
5
4
5
7
1
2
3
7

0
0
0
0
0
0
0
0

7
15
15
19
1
1
2
7

➄

Function

dqa
dqb
pka
ewa
vga
0
1
0
1

SCSI Bus ID 7 ➉
COMPAQ BB00921B91
RRD46
08-00-2B-C3-C3-B9

AlphaServer GS80/160/320 Firmware Reference Manual

➅

Name

pkb
pkc
pkd
pke
fwa
dqe
dqf
pkg
pkh
vgb
eia
eib
mca
pki
pkj
pkk

dqc
dqd
pkf
ewb
dwa

Show Config Example (Continued)
7
15

Acer Labs M1543C
Acer Labs M1543C IDE

Acer Labs M1543C USB

Bridge to Bus 1, ISA
dqa.0.0.15.0
dqb.0.1.15.0
dqa0.0.0.15.0

COMPAQ CDR-8435

➓

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 is identified 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), as described in Section 2.7. 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 multifunction devices, the function ID is displayed.

➅

Name. Device names are listed.

➆

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

➇
➈

The option name appears next.

➉

Because the standard I/O module is multifunctional, the next devices
shown are the controllers and devices connected to the module. COMPAQ
BB00921B91 and RRD46 are devices on SCSI bus ID 7.
Continued on next page

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.

SRM Command Reference

7-71

Show Config Example (Continued)
Slot
7

Option
DEGPA-SA

Hose 1, Bus 0, PCI

Slot
1

Option
QLogic ISP10x0

2/0
2/1
3/0
3/1
Slot
6

NCR 53C896
NCR 53C896
09608086
19608086/0415129A
Option
DEC KZPSA

Hose 2, Bus 0, PCI
pkb0.7.0.1.2
dkb0.0.0.1.2
dkb100.1.0.1.2
dkb200.2.0.1.2
dkb400.4.0.1.2
dkb500.5.0.1.2
dkb600.6.0.1.2
pkc0.7.0.2.2
pkd0.7.0.102.2

Hose 3, Bus 0, PCI
pke0.7.0.6.3
dke100.1.0.6.3
dke200.2.0.6.3
dke300.3.0.6.3
dke400.4.0.6.3
fwa0.0.0.7.3

DEC PCI FDDI

Slot
1

Option
QLogic ISP10x0

7
15

Acer Labs M1543C
Acer Labs M1543C IDE

Acer Labs M1543C USB

Slot
4

Option
QSW ELan3

Hose 5, Bus 0, PCI

Slot
1
2

Option
DE500-BA Network Con
PBXNP-AA Token Ring

Hose 6, Bus 0, PCI
ewb0.0.0.1.6

Slot
7
Slot
1

Option
001B1011/001B1011
Option
QLogic ISP10x0

Hose 7, Bus 0, PCI

DEC KZPSA

Hose 4, Bus 0, PCI
pkf0.7.0.1.4
dkf0.0.0.1.4
dqc.0.0.15.4
dqd.0.1.15.4
dqc0.0.0.15.4

Hose 8, Bus 0, PCI
pkg0.7.0.1.8
dkg0.0.0.1.8
pkh0.7.0.2.8
dkh100.1.0.2.8
dkh200.2.0.2.8
dkh300.3.0.2.8
dkh400.4.0.2.8

SCSI Bus ID 7
RZ1CB-CA
RZ1CB-CS
RZ1CB-CS
COMPAQ BB00911CA0
RZ1DF-CB
RZ1DF-CF
SCSI Bus ID 7
SCSI Bus ID 7
Bridge to Bus 2, PCI

SCSI Bus ID 7
RZ1CF-CF
RZ1CF-CF
COMPAQ BB00911CA0
RZ1CF-CF
00-00-F8-48-56-7A

➊

SCSI Bus ID 7
RZ1DF-BF
Bridge to Bus 1, ISA
TOSHIBA CD-ROM XM-6302B

08-00-2B-C3-C0-38

SCSI Bus ID 7
RZ1DF-BF
SCSI Bus ID 7
RZ1CF-CF
RZ1CB-CS
COMPAQ BB00911CA0
COMPAQ BB00911CA0

Continued on next page

7-72

AlphaServer GS80/160/320 Firmware Reference Manual

Show Config Example (Continued)
3
7
15

PowerStorm 350
Acer Labs M1543C
Acer Labs M1543C IDE

Acer Labs M1543C USB

Slot
5
7

Option
DECchip 21154-AA
DEC PCI MC

Hose 9, Bus 0, PCI

Slot
4
5

Option
DE602-AA
DE602-AA

Hose 9, Bus 2, PCI
eia0.0.0.2004.9
eib0.0.0.2005.9

00-50-8B-6F-2F-92
00-50-8B-6F-2F-93

Slot
1
2

Option
QLogic ISP10x0
DEC KZPSA

Hose 10, Bus 0, PCI
pki0.7.0.1.10
pkj0.7.0.2.10
dkj100.1.0.2.10
dkj200.2.0.2.10
dkj300.3.0.2.10
dkj400.4.0.2.10
pkk0.7.0.3.10

SCSI Bus ID 7
SCSI Bus ID 7
RZ1CF-CF
RZ1CB-CS
RZ1CF-CF
RZ1CB-CS
SCSI Bus ID 7

DEC KZPSA

Slot
7

Option
DEGPA-SA

Bridge to Bus 1, ISA
dqe.0.0.15.8
dqf.0.1.15.8
dqe0.0.0.15.8

COMPAQ CDR-8435

Bridge to Bus 2, PCI
Rev: 22, mca0

Hose 11, Bus 0, PCI

➋

P00>>>

➊

Looking back at the information presented under ➓ helps to 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.

SRM Command Reference

7-73

7.5.36 Show Device
The show device command displays device information for devices on
the system.

Syntax
sh[ow] dev[ice] [dev_name]
Argument
dev_name

Any adapter name (wildcarding is allowed). For example,
show device dk* will display information on all SCSI devices
on the system. If dev_name is omitted, the display shows all
devices in the system.

Example
P00>>> sho dev
dka0.0.0.1.0
dkb0.0.0.7.1
dkb100.1.0.7.1
dkb200.2.0.7.1
dkb300.3.0.7.1
dqa0.0.0.15.0
dqc0.0.0.15.6
dqe0.0.0.15.8
eia0.0.0.3.8
fwa0.0.0.4.1
fwb0.0.0.5.7
fwc0.0.0.1.10
pga0.0.0.7.7
pka0.7.0.1.0
pkb0.7.0.7.1
pkc0.7.0.1.2

7-74

DKA0
DKB0
DKB100
DKB200
DKB300
DQA0 ➊
DQC0
DQE0
EIA0
FWA0
FWB0
FWC0
PGA0
PKA0
PKB0
PKC0

RZ1DF-BF
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0
COMPAQ BB00911CA0
TOSHIBA CD-ROM XM-6302B
TOSHIBA CD-ROM XM-6302B
TOSHIBA CD-ROM XM-6302B
08-00-2B-C3-BD-00
00-00-F8-CD-1F-39
00-00-F8-CD-22-E0
00-00-F8-CD-22-FB
WWN 1000-0000-c920-da1e
SCSI Bus ID 7
SCSI Bus ID 7
SCSI Bus ID 7

AlphaServer GS80/160/320 Firmware Reference Manual

1614
3B05
3B05
3B05
3B05
1017
1017
1017

5.57
5.57
5.57

Table 7–6 Device Naming Conventions

➊