Digital PDFs

EK-4000A-UG-C01

June 1997

272 pages

Original

0.6MB

Document:	AlphaServer 4000 System Drawer User's Guide
Order Number:	EK-4000A-UG
Revision:	C01
Pages:	272
Original Filename:

OCR Text

AlphaServer 4000
System Drawer User’s Guide

Order Number:

EK–4000A–UG. C01

This manual is for anyone who manages, operates, or services the
BA30B system drawer in a DIGITAL AlphaServer 4000 system. It
covers operation, firmware, initial troubleshooting, and component
installation.

Digital Equipment Corporation
Maynard, Massachusetts

First Printing, June 1997
Digital Equipment Corporation makes no representations that the use of its products in the
manner described in this publication will not infringe on existing or future patent rights, nor
do the descriptions contained in this publication imply the granting of licenses to make, use, or
sell equipment or software in accordance with the description.
The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation.
Digital Equipment Corporation assumes no responsibility for any errors that may appear in
this document.
The software, if any, described in this document is furnished under a license and may be used
or copied only in accordance with the terms of such license. No responsibility is assumed for
the use or reliability of software or equipment that is not supplied by Digital Equipment
Corporation or its affiliated companies.
Copyright  1997 by Digital Equipment Corporation. All rights reserved.
The following are trademarks of Digital Equipment Corporation: AlphaServer, OpenVMS,
StorageWorks, VAX, and the DIGITAL logo.
The following are third-party trademarks: Lifestyle 28.8 DATA/FAX Modem is a trademark
of Motorola, Inc. UNIX is a registered trademark in the U.S. and other countries, licensed
exclusively through X/Open Company Ltd. U.S. Robotics and Sportster are registered
trademarks of U.S. Robotics. Windows NT is a trademark of Microsoft, Inc. All other
trademarks and registered trademarks are the property of their respective holders.
FCC Notice: The equipment described in this manual generates, uses, and may emit radio
frequency energy. The equipment has been type tested and found to comply with the limits for
a Class A digital device pursuant to Part 15 of FCC Rules, which are designed to provide
reasonable protection against such radio frequency interference. Operation of this equipment
in a residential area may cause interference, in which case the user at his own expense will be
required to take whatever measures are required to correct the interference.
Shielded Cables: If shielded cables have been supplied or specified, they must be used on the
system in order to maintain international regulatory compliance.
Warning! This is a Class A product. In a domestic environment this product may cause radio
interference, in which case the user may be required to take adequate measures.
Achtung! Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei
Betrieb dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für
entsprechende Gegenmaßnahmen verantwortlich ist.
Avertissement! Cet appareil est un appareil de Classe A. Dans un environnement résidentiel,
cet appareil peut provoquer des brouillages radioélectriques. Dans ce cas, il peut être demandé
à l'utilisateur de prendre les mesures appropriées.

Contents

Preface ................................................................................................................xi
Part 1: System Drawer
Chapter 1
1.1
1.2
1.3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4

Characteristics ......................................................................................... 1-2
Architecture ............................................................................................. 1-4
Parts of the System Drawer ...................................................................... 1-6
System Motherboard ......................................................................... 1-8
CPU Module ................................................................................... 1-10
Memory Pair ................................................................................... 1-12
Power Control Module .................................................................... 1-14
System Bus to PCI Bus Bridge Module ........................................... 1-16
PCI Motherboard ............................................................................ 1-18
Server Control Module .................................................................... 1-20
Control Panel .................................................................................. 1-22
Power Supply.................................................................................. 1-24
Console Terminal .................................................................................. 1-26

Chapter 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.9.1
2.9.2

System Drawer Overview

Operation

Powering Up the System Drawer ............................................................. 2-2
Power-Up Display.................................................................................... 2-4
Booting DIGITAL UNIX ......................................................................... 2-8
Installing DIGITAL UNIX..................................................................... 2-14
Booting OpenVMS ................................................................................ 2-16
Installing OpenVMS .............................................................................. 2-22
Booting Windows NT ............................................................................ 2-24
Installing Windows NT .......................................................................... 2-26
Updating Firmware ................................................................................ 2-28
Updating Firmware from the Internal CD-ROM .............................. 2-30
Updating Firmware from the Internal Floppy Disk — Creating
the Diskettes ................................................................................... 2-34

iii

2.9.3
2.9.4
2.9.5
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10.5
2.10.6
2.10.7

Updating Firmware from the Internal Floppy Disk — Performing
the Update....................................................................................... 2-36
Updating Firmware from a Network Device .................................... 2-40
LFU Commands.............................................................................. 2-44
Operating the System Remotely ............................................................. 2-47
Modem Usage ................................................................................. 2-48
Entering and Leaving Command Mode ........................................... 2-51
RCM Commands ............................................................................ 2-52
Dial-Out Alerts ............................................................................... 2-62
Resetting the RCM to Factory Defaults ........................................... 2-65
Troubleshooting Guide.................................................................... 2-66
Modem Dialog Details .................................................................... 2-69

Chapter 3
3.1
3.2
3.3

System Drawer Does Not Power Up......................................................... 3-2
Control Panel Display Is Blank ................................................................ 3-4
Control Panel Display Indicates an Error ................................................. 3-6

Chapter 4
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8

Troubleshooting

Installing Components

Exposing the System Drawer in a Pedestal ............................................... 4-2
Exposing the System Drawer in a Cabinet ................................................ 4-4
Removing Covers from the System Drawer ............................................. 4-6
Installing a CPU Module.......................................................................... 4-8
Installing a Memory Pair........................................................................ 4-10
Installing a PCI or EISA Card ................................................................ 4-12
Installing a Power Supply ...................................................................... 4-16
Upgrading the I/O System ...................................................................... 4-19

Part 2: User Interface
Chapter 5
5.1
5.2
5.3
5.4
5.4.1
5.4.2
5.4.3
5.5
5.6
5.7
5.8
iv

SRM Console

Switching from SRM to the AlphaBIOS Console ..................................... 5-2
Displaying the System Configuration ....................................................... 5-4
Booting the Operating System ............................................................... 5-12
Configuring the System ......................................................................... 5-14
Configuring DSSI ........................................................................... 5-14
Configuring a PCI NVRAM Module ............................................... 5-16
Configuring EISA and RAID .......................................................... 5-17
Testing the System................................................................................. 5-18
Stopping and Starting CPUs ................................................................... 5-20
Updating Firmware ................................................................................ 5-22
Forcing a System Crash Dump ............................................................... 5-24

5.9
5.10
5.11
5.12
5.13
5.14
5.15

Using Environment Variables ................................................................ 5-25
Depositing and Examining Data ............................................................. 5-28
Reading a File........................................................................................ 5-31
Initializing the System ........................................................................... 5-32
Finding Help.......................................................................................... 5-34
Command Summary .............................................................................. 5-35
Environment Variable Summary ............................................................ 5-40

Chapter 6
6.1
6.2
6.3
6.4
6.4.1
6.4.2
6.4.3
6.4.4
6.4.5
6.4.6
6.4.7
6.4.8
6.5
6.6
6.6.1
6.6.2
6.7
6.8
6.9
6.10
6.10.1
6.10.2

Switching from AlphaBIOS to the SRM Console ..................................... 6-2
Starting AlphaBIOS ................................................................................. 6-4
Keyboard Conventions and Help .............................................................. 6-6
Displaying the System Configuration ....................................................... 6-8
System Board Configuration ........................................................... 6-10
Hard Disk Configuration ................................................................. 6-12
PCI Configuration ........................................................................... 6-14
EISA Configuration ........................................................................ 6-17
SCSI Configuration......................................................................... 6-18
System Bus Configuration............................................................... 6-20
Memory Configuration.................................................................... 6-21
Integrated Peripherals ..................................................................... 6-22
Updating Firmware ................................................................................ 6-24
Setting up the Hard Disk ........................................................................ 6-26
Manually Creating and Deleting Partitions ...................................... 6-28
Formatting a FAT Partition ............................................................. 6-30
Performing Setup Tasks ......................................................................... 6-32
Installing Windows NT .......................................................................... 6-36
Running Utility Programs ...................................................................... 6-38
Selecting the Version of Windows NT ................................................... 6-40
Designating a Primary Operating System ........................................ 6-42
Primary Operating System and the Auto Start Option ...................... 6-44

Chapter 7
7.1
7.2

AlphaBIOS Console

Utilities

Running Utilities from a Graphics Monitor .............................................. 7-2
Running Utilities from a Serial Terminal ................................................. 7-4

Appendix A

How to Find Firmware Updates

Appendix B

Hard Disk Partitioning for AlphaBIOS and
Windows NT

B.1
B.1.1

Hard Disk Error Conditions .................................................................... C-1
Disk Initialization Failed .................................................................. C-1
v

B.1.2
B.1.3
B.2
B.3

No Hard Disks Found....................................................................... C-2
No Partitions on Disk ....................................................................... C-2
System Partitions .................................................................................... C-2
How AlphaBIOS Works with System Partitions ...................................... C-3

Appendix C
C.1
C.2
C.3
C.4
C.5
C.6
C.7
C.8

Differences Between AlphaBIOS and ARC
Firmware

Revamped User Interface ........................................................................ C-1
Hard Disk Setup...................................................................................... C-1
Changing CMOS and NVRAM Values ................................................... C-2
Working with Operating Systems ............................................................ C-3
Running a Program from the BIOS ......................................................... C-3
Differences in System Configuration Display .......................................... C-3
Resetting to Factory Defaults .................................................................. C-4
Multilingual Support............................................................................... C-4

Appendix D

Acoustical Data

Index

Examples
2–1
2–2
2–3
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
vi

Power-Up Display.................................................................................... 2-4
Booting DIGITAL UNIX from a Local Disk ............................................ 2-8
Booting DIGITAL UNIX from a Disk on a Cluster ................................ 2-10
Booting DIGITAL UNIX from a Remote Disk....................................... 2-12
Installing DIGITAL UNIX..................................................................... 2-14
Booting OpenVMS from a Local Disk ................................................... 2-16
Booting OpenVMS from a Disk on a Cluster ......................................... 2-18
Booting OpenVMS from a Remote Disk ................................................ 2-20
Installing OpenVMS .............................................................................. 2-22
Starting LFU from the SRM Console ..................................................... 2-28
Booting LFU from the CD-ROM ........................................................... 2-29
Updating Firmware from the Internal CD-ROM ..................................... 2-30
Creating Update Diskettes on an OpenVMS System .............................. 2-35
Updating Firmware from the Internal Floppy Disk ................................. 2-36
Selecting AS4X00FW to Update Firmware from the Internal
Floppy Disk ........................................................................................... 2-39
Updating Firmware from a Network Device ........................................... 2-40
Sample Remote Dial-In Dialog .............................................................. 2-50
Entering and Leaving RCM Command Mode ........................................ 2-51
Configuring the Modem for Dial-Out Alerts .......................................... 2-62

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

Typical RCM Dial-Out Command ......................................................... 2-62
Switching to the AlphaBIOS Console ...................................................... 5-2
Show Config Command ........................................................................... 5-4
Show CPU Command .............................................................................. 5-5
Show Device Command........................................................................... 5-6
Show FRU Command .............................................................................. 5-8
Show Memory Command ........................................................................ 5-9
Show Network Command ........................................................................ 5-9
Show PAL Command ............................................................................ 5-10
Show Power Command.......................................................................... 5-10
Show Version Command ....................................................................... 5-11
Boot Command...................................................................................... 5-12
Set Host Command ................................................................................ 5-14
Prcache Command ................................................................................. 5-16
Test Command....................................................................................... 5-18
Start, Halt, and Continue Commands ..................................................... 5-20
Lfu Command........................................................................................ 5-22
Crash Command .................................................................................... 5-24
Set envar and Show envar commands .................................................... 5-25
Edit Command ....................................................................................... 5-27
Deposit Command ................................................................................. 5-28
Examine Command ............................................................................... 5-28
More Command ..................................................................................... 5-31
Initialize Command ............................................................................... 5-32
Help (or Man) Command ....................................................................... 5-34

Figures
1–1
1–2
1–3
1–4
1–5
1–6
1–7
1–8
1–9
1–10
1–11
1–12
1–13
2–1
2–2

BA30B System Drawer............................................................................ 1-2
System Drawer Block Diagram ................................................................ 1-4
System Drawer Sections .......................................................................... 1-6
System Motherboard ................................................................................ 1-8
CPU Modules ........................................................................................ 1-10
Memory Module .................................................................................... 1-12
Power Control Module ........................................................................... 1-14
Bridge Module ....................................................................................... 1-16
PCI Motherboard (PCI 0 and 1) ............................................................. 1-18
PCI Motherboard (PCI 2 and 3) ............................................................. 1-19
Server Control Module........................................................................... 1-20
Control Panel ......................................................................................... 1-22
Power Supply......................................................................................... 1-24
Power Button and Control Panel Display ................................................. 2-2
AlphaBIOS Boot Screen ........................................................................ 2-24
vii

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

Installing Windows NT .......................................................................... 2-26
Starting LFU from the AlphaBIOS Console ........................................... 2-28
RCM Connections.................................................................................. 2-48
Location of Cover Interlocks .................................................................... 3-2
Power Control Module LEDs ................................................................... 3-3
CPU and Bridge Module LEDs ................................................................ 3-4
Control Panel Display .............................................................................. 3-6
Pedestal Door and Cover Removal ........................................................... 4-2
Pedestal Tray Removal ............................................................................ 4-3
Exposing System Drawer in Cabinet ........................................................ 4-4
System Drawer Covers............................................................................. 4-6
CPU Module Slots ................................................................................... 4-8
CPU Module Installation.......................................................................... 4-9
Memory Pair Slots ................................................................................. 4-10
Memory Module Installation .................................................................. 4-11
PCI and EISA Slots (PCI 0 and 1) .......................................................... 4-12
PCI Slots (PCI 2 and 3) .......................................................................... 4-13
PCI/EISA Card Installation .................................................................... 4-15
Power System Cabling ........................................................................... 4-16
Power Control Module LEDs ................................................................. 4-18
Configuring EISA and RAID Devices .................................................... 5-17
Switching to the SRM Console ................................................................ 6-2
Boot Screen ............................................................................................. 6-4
AlphaBIOS Setup Screen ......................................................................... 6-5
Typical First-Level Help Screen .............................................................. 6-6
Second-Level Help Screen ....................................................................... 6-7
Display System Configuration Screen ...................................................... 6-8
System Board Configuration .................................................................. 6-10
Hard Disk Configuration ........................................................................ 6-12
PCI Configuration.................................................................................. 6-14
Advanced PCI Information .................................................................... 6-16
EISA Configuration ............................................................................... 6-17
SCSI Configuration................................................................................ 6-18
System Bus Configuration ..................................................................... 6-20
Memory Configuration .......................................................................... 6-21
Integrated Peripherals ............................................................................ 6-22
Updating Firmware ................................................................................ 6-24
Hard Disk Setup Screen ......................................................................... 6-26
Create New Partition Dialog Box ........................................................... 6-28
Delete Partition Dialog Box ................................................................... 6-29
Formatting a FAT Partition .................................................................... 6-30
Standard Formatting .............................................................................. 6-31
Standard CMOS Setup Screen................................................................ 6-32
Advanced CMOS Setup Screen .............................................................. 6-34

6–24
6–25
6–26
6–27
6–28
7–1
7–2
B–1

Installing Windows NT .......................................................................... 6-36
Run Maintenance Program Dialog Box .................................................. 6-38
Operating System Selections .................................................................. 6-40
Primary Operating System ..................................................................... 6-42
Operating System Selection Setup ......................................................... 6-44
Running a Utility from a Graphics Monitor .............................................. 7-2
Run Maintenance Program Dialog Box .................................................... 7-3
System Partition Not Defined.................................................................. B-3

Tables
1
1–1
1–2
1–3
2–1
2–2
2–3
2–4
2–5
2–6
3–1
4–1
5–1
5–2
5–3
5–4
5–5
5–6
7–1
C–1
D–1
D–2

AlphaServer 4000/4100 Documentation .................................................... xii
BA30B System Drawer Characteristics .................................................... 1-3
PCI Bus Slot Numbering........................................................................ 1-19
Comparison of Console Terminals ......................................................... 1-26
File Locations for Creating Update Diskettes on a PC ............................ 2-34
LFU Command Summary ...................................................................... 2-44
RCM Command Summary ..................................................................... 2-52
RCM Status Command Fields ................................................................ 2-61
RCM Troubleshooting ........................................................................... 2-66
RCM/Modem Interchange Summary ...................................................... 2-71
Control Panel Display .............................................................................. 3-7
PCI Upgrade Kit Contents...................................................................... 4-20
Device Naming Convention ..................................................................... 5-7
Summary of SRM Console Commands .................................................. 5-35
Syntax for SRM Console Commands ..................................................... 5-37
Special Characters for SRM Console ..................................................... 5-38
Environment Variable Summary ............................................................ 5-40
Settings for boot_osflags Bootflags (OpenVMS) .................................... 5-44
AlphaBIOS Option Key Mapping ............................................................ 7-4
Differences Between AlphaBIOS and ARC Menu Selections .................. C-2
Acoustics - Declared Values per ISO 9296 and ISO 7779 ...................... D-1
Schallemissionswerte - Werteangaben nach ISO 9296 und
ISO 7779/DIN EN27779 ......................................................................... D-2

Preface

Intended Audience
This manual is for anyone who manages, operates, or services the BA30B system
drawer in an AlphaServer 4000 system.

Document Structure
This manual uses a structured documentation design. Topics are organized into small
sections for efficient online and printed reference. Each topic begins with an
abstract. You can quickly gain a comprehensive overview by reading only the
abstracts. Next is an illustration or example, which also provides quick reference.
Last in the structure are descriptive text and syntax definitions.
This manual has seven chapters and four appendixes, as follows:
Part 1: System Drawer
•

Chapter 1, System Drawer Overview, describes the components in the BA30B
system drawer.

•

Chapter 2, Operation, gives instructions for powering up the system drawer,
booting the operating system, updating firmware, and operating the system
remotely.

•

Chapter 3, Troubleshooting, provides basic troubleshooting information for the
system drawer.

•

Chapter 4, Installing Components, gives instructions for adding CPU,
memory, PCI, and EISA cards to the system drawer.
Part 2: User Interface

•

Chapter 5, SRM Console, describes commands in the SRM console, for
DIGITAL UNIX and OpenVMS systems.

•

Chapter 6, AlphaBIOS Console, describes menu selections in the AlphaBIOS
console, for Windows NT systems.

•

Chapter 7, Utilities, shows how to run the EISA and RAID configuration
utilities on an AlphaServer 4000 system.

•

Appendix A, How to Find Firmware Updates, explains the process for
downloading AlphaServer firmware from the Internet.

•

Appendix B, Hard Disk Partitioning for AlphaBIOS and Windows NT,
describes the concept of partitioning for AlphaBIOS and Windows NT.

•

Appendix C, Differences Between AlphaBIOS and ARC Firmware, describes
the differences.

•

Appendix D, Acoustical Data, lists values for the system drawer in various
configurations.

Documentation Titles
Table 1 lists the books in the AlphaServer 4000/4100 documentation set.

Table 1 AlphaServer 4000/4100 Documentation
Title

Order Number

User and Configuration Documentation Kit

QZ–00VAB–GZ

System Drawer User’s Guide

EK–4000A–UG

Configuration and Installation Guide

EK–4100A–CG

Service Information
Service Manual (hard copy)

EK–4100A–SV

Service Manual (diskette)

AK–QXBJA–CA

System Drawer Upgrades

EK–4041A–UI

PCI Upgrade

EK–4000A–UI

Reference Information

xii

KN30n CPU Installation Card

EK–KN300–IN

MS3n0 Memory Installation Card

EK–MS300–IN

H7291 Power Supply Installation Card

EK–H7291–IN

ServerWORKS Manager Administrator User’s Guide

ER–4QXAA–UA

Part 1
System Drawer

Chapter 1
System Drawer Overview
The BA30B system drawer is the enclosure for AlphaServer 4000 processor and
memory modules, system bus, and PCI bus. The same drawer is used in various
AlphaServer 4000 models, such as the pedestal system and the cabinet system.
This chapter provides an overview of the BA30B system drawer in these sections:
•

Characteristics

•

Architecture

•

Parts of the System Drawer

•

Console Terminal

System Drawer Overview

1-1

1.1 Characteristics
The illustration shows the BA30B system drawer with covers in place. The table
lists characteristics of the drawer.

Figure 1–1 BA30B System Drawer

PK-0701B-96

1-2

System Drawer User’s Guide

Table 1–1 BA30B System Drawer Characteristics
Characteristic

Specification

Size

30 cm H x 45 cm W x 69 cm D (11.8 in. x 17.7 in.
x 27.2 in.)

Weight

45.5 kg (100 lb) fully configured

Clearance

20 cm (7.9 in.) front and rear

Maximum heat dissipation

1100 w (3754 Btu/hr)

Electrical
Voltage

100–120/200–240 Vac

Phase

Single

Frequency

50–60 Hz

Maximum rated current
(single cord set)

8.4 A at 100–120 V
4.2 A at 200–240 V

Maximum rated current
(multiple cord sets)

8.0 A at 100–120 V
4.0 A at 200–240 V

Maximum power consumption

700 w

Environmental
Temperature

Operating: 10° to 35°C (50 to 95°F)
Not operating: -40° to 66°C (-40° to 150.8°F)
Storage (60 days): -40° to 66°C (-40° to 150.8°F)
Rate of change: 11° to 19°C per hour
(20° to 35°F per hour)

Humidity

Operating: 20% to 90% (noncondensing)
Not operating: 10% to 95%
Storage (60 days): 10% to 95%

Altitude

Operating: 2000 m (6560 ft)
Not operating: 3600 m (11808 ft)

System Drawer Overview

1-3

1.2 Architecture
The system bus, with its logic on the system motherboard, connects the CPU,
memory, and system bus to PCI bus bridge modules. The four 64-bit PCI buses
each have four slots for PCI options. (Three of the 16 slots can be used for either
PCI or EISA options.)

Figure 1–2 System Drawer Block Diagram

CPU

Memory
Pair

System Bus

Bridge 0

Bridge 1

Bridge 2

Bridge 3

PCI Bus 0

PCI Bus 1

PCI Bus 2

PCI Bus 3

PCI Slot

PCI/EISA
Slot

PCI Slot

PCI/EISA
Slot

PCI Slot

PCI/EISA
Slot

PCI Slot

EISA
Bridge

1-4

System Drawer User’s Guide

16-PCI slot
drawer only

PK-0700B-96

The system bus is a 144-bit data bus (128 bits for data and 16 for ECC) and a
separate 40-bit command/address bus. The logic is on the system motherboard. This
bus connects CPU modules, memory modules, and the system bus to PCI bus bridge
modules. The clock for the system bus is on the module in CPU slot 0.
The system drawer supports up to two CPU modules.
A memory pair is two modules of the same size and type, which together make one
memory option. Memory pairs can be 128 or 512 MB, or 1 or 2 GB. Each module in
the pair drives 72 bits of the 144-bit system bus. The system drawer can have up to
two memory pairs.
Each system bus to PCI bus bridge module has two PCI bridges. Each bridge
supports one 64-bit PCI bus. The system can have up to two bridge modules, for a
total of four PCI buses. The first PCI bus has one dedicated PCI slot and three slots
that can be used for either PCI or EISA options.The other PCI buses each have four
slots for PCI options.

System Drawer Overview

1-5

1.3 Parts of the System Drawer
The system drawer consists of the system card cage, PCI card cages, control
panel, and power and cooling section.

Figure 1–3 System Drawer Sections

4
PK-0702C-96

1-6

System Drawer User’s Guide

The callouts in Figure 1–3 point to these components of the BA30B system drawer:

²
³
´
µ
¶
·

System card cage, which holds the system motherboard and the CPU,
memory, bridge, and power control modules. Refer to Sections 1.3.1 through
1.3.5 for information about these modules.
PCI card cage, which holds the motherboard for PCI 0 and PCI 1, option
cards, and the server control module. Refer to Section 1.3.6 for information
about the motherboard.
Server control module, which holds the I/O connectors and remote console
monitor. Refer to Section 1.3.7.
Control panel assembly, which includes the control panel, a floppy drive, and
a CD-ROM drive. Refer to Section 1.3.8.
NOTE: When the system drawer is mounted in a pedestal cabinet, the control
panel is mounted in a tray at the top of the drawer.
Power and cooling section, which contains one to three power supplies (refer
to Section 1.3.9) and three fans.
PCI card cage, which holds the motherboard for PCI 2 and PCI 3 and their
option cards (16-PCI slot drawers only). Refer to Section 1.3.6 for
information about the motherboard.

System Drawer Overview

1-7

1.3.1 System Motherboard
The system motherboard is on the floor of the system card cage. It has slots for
the CPU, memory, power control, and bridge modules.

Figure 1–4 System Motherboard
5

1
2
2
1
2
2

1-8

System Drawer User’s Guide

PK-0763A-96

The system motherboard has the logic for the system bus. It is the backplane that
holds the CPU, memory, bridge, and power control modules. Figure 1–4 shows the
locations of these modules and of connectors on the motherboard.

²
³
´
µ
¶

CPU module
Memory module
Bridge module (PCI 0 and 1)
Power control module
Bridge module (PCI 2 and 3 — 16-PCI slot drawer only)

System Drawer Overview

1-9

1.3.2 CPU Module
Each CPU module has a fan for cooling. The BA30B system drawer can have up
to two CPU modules.

Figure 1–5 CPU Modules
System Motherboard
1
CPU Module Slots
0

PK-0709C-96

1-10

System Drawer User’s Guide

Description
The system drawer can have one or two CPU modules. Each CPU module has a fan
for cooling.
Configuration
•

The first CPU module must be in CPU slot 0 to provide the system clock.

•

The second CPU module, if present, is installed in CPU slot 1.

•

All CPU modules must have the same clock frequency.

System Drawer Overview

1-11

1.3.3 Memory Pair
Memory modules are used only in pairs — two modules of the same size and
type. Each module provides either the low half or the high half of the memory
space. The system drawer can hold up to two memory module pairs.

Figure 1–6 Memory Module
System Motherboard

1 High
1 Low
0 High
0 Low

Typical Synchronous Memory Module

C56

Typical EDO Memory Module

Memory Module Slots

PK-0708B-96

1-12

System Drawer User’s Guide

Description
Memory modules are used only in pairs. A memory module pair is two modules of
the same size and type; one module in the pair provides the low half and the other
the high half of that pair’s memory region. Two types of memory modules are
available: synchronous and extended data out (EDO).
Configuration
•

Memory modules are installed and used in pairs. Both modules in a memory pair
must be of the same size and type.

•

Memory must be configured in descending order. That is, the larger memory
pair must be in slots 0 Low and 0 High, and the second pair, if present, in 1 Low
and 1 High. (The first memory pair defines the size of the memory region for
each pair.)

System Drawer Overview

1-13

1.3.4 Power Control Module
The power control module controls power sequencing and monitors power
supply voltage, temperature, and fans.

Figure 1–7 Power Control Module
System Motherboard

Power Control
Module Slot

PK-0710B-96

1-14

System Drawer User’s Guide

The power control module performs these functions:
•

Controls power sequencing.

•

Monitors the combined output of power supplies and shuts down power if it is
not in range.

•

Monitors system temperature and shuts off power if it is out of range.

•

Monitors the fans in the system drawer and on the CPU modules and shuts down
power if a fan fails.

•

Provides visual indication of faults through LEDs.

System Drawer Overview

1-15

1.3.5 System Bus to PCI Bus Bridge Module
The bridge module is the physical interconnect between the system motherboard
and the PCI motherboard.

Figure 1–8 Bridge Module
System Motherboard
System Bus-to-PCI Bus
Bridge Module Slot (PCI 2 & 3)

System Bus-to-PCI Bus
Bridge Module Slot (PCI 0 & 1)

PK-0707B-96

1-16

System Drawer User’s Guide

The 16-PCI slot system drawer has two bridge modules; the 8-PCI slot drawer has
one.
Each bridge module is the physical interconnect between the system motherboard
and a PCI motherboard. Each side of a bridge module connects to one PCI bus.
The bridge module converts system bus commands and data addressed to I/O space
to PCI commands and data, and it converts PCI bus commands and data addressed to
system memory or CPUs to system bus commands and data.

System Drawer Overview

1-17

1.3.6 PCI Motherboard
Each PCI motherboard has the logic for two PCI buses. PCI 0 consists of one
dedicated PCI slot and three shared PCI/EISA slots; PCI 1, 2, and 3 each have
four PCI slots.

Figure 1–9 PCI Motherboard (PCI 0 and 1)

PCI 1 slot 5
PCI 1 slot 4
PCI 1 slot 3
PCI 1 slot 2
PCI 0 slot 5
EISA slot 3 or
PCI 0 slot 4
EISA slot 2 or
PCI 0 slot 3
EISA slot 1 or
PCI 0 slot 2
PK-0704-96

The PCI 0 and 1 motherboard is used in all BA30B system drawers. The PCI 2 and 3
motherboard is found only in 16-PCI slot system drawers.
The logic for two 64-bit PCI buses is on each PCI motherboard. PCI 0 has one
dedicated PCI slot and three shared PCI/EISA slots, and PCI 1, 2, and 3 each have
four PCI slots. The PCI 0 and 1 motherboard has cable connections to remote I/O
(mouse, keyboard, serial port, and parallel port) and to an internal floppy drive, an
internal CD-ROM drive, the control panel, and 5V power. Also on this module are
the chips for the PCI to EISA bridge and the internal CD-ROM controller.

1-18

System Drawer User’s Guide

Figure 1–10 PCI Motherboard (PCI 2 and 3 — 16-PCI Slot Drawer
Only)

PCI 3 slot 5
PCI 3 slot 4
PCI 3 slot 3
PCI 3 slot 2
PCI 2 slot 5
PCI 2 slot 4
PCI 2 slot 3
PCI 2 slot 2

PK-0764-96

Table 1–2 PCI Bus Slot Numbering
Slot

PCI 0

PCI 1

PCI 2

PCI 3

Reserved

PCI to EISA
bridge

Internal CD-ROM
controller

Reserved

PCI or EISA slot

PCI slot

PCI or EISA slot

PCI slot

PCI or EISA slot

PCI slot

System Drawer Overview

1-19

1.3.7 Server Control Module
The server control module enables remote connections to the system drawer’s
console. It also holds the standard I/O connectors.

Figure 1–11 Server Control Module

Standard I/O

Remote Console
Monitor

PK-0702B-96

1-20

System Drawer User’s Guide

The server control module has two sections: the remote console monitor and the
standard I/O connectors.
The remote console monitor connects to a modem through the modem port on the
bulkhead, and it receives power through the 12V power connector.
The standard remote I/O ports (keyboard, mouse, COM1 and COM2 serial, and
parallel ports) are on the same bulkhead.

System Drawer Overview

1-21

1.3.8 Control Panel
The control panel includes the Power, Halt, and Reset buttons and a display. In
a pedestal system the control panel is located in a tray at the top of the system
drawer. In a cabinet system it is at the bottom of the system drawer with the
CD-ROM drive and the floppy drive.

Figure 1–12 Control Panel

Cabinet

Pedestal

Control Panel

CD-ROM Drive
CD-ROM
Drive

1-22

Floppy Drive

System Drawer User’s Guide

PK-0751B-97

The callouts in Figure 1–12 point to these components of the control panel:

²
³

´
µ
¶

Power button — Powers on or off the system drawer. When the LED at the top
of the button is lit, the power is on.
NOTE: The LEDs on some modules are on when the line cord is plugged in,
regardless of the position of the Power button.
Halt button — Pressing this button in (so the LED at the top of the button is lit)
does the following:
•

If DIGITAL UNIX or OpenVMS is running, halts the operating system
and returns to the SRM console. (The Halt button has no effect on
Windows NT.)

•

If the Halt button is in when the system is reset or powered up, the system
halts in the SRM console, regardless of the operating system. DIGITAL
UNIX and OpenVMS systems that are configured for autoboot will not
boot if the Halt button is in. Windows NT systems halt in the SRM
console; AlphaBIOS is not loaded and started.

Reset button — Initializes the system drawer.
Potentiometer — Controls the intensity of the control panel display. It is
accessed through a small hole above the Reset button.
Control panel display — Indicates status during power-up and testing. See
Table 3–1 for the messages that are displayed and their meanings.
While the operating system is running, the control panel displays the system
type as a default. (This message can be changed by the user with the ocp_text
SRM environment variable — see Section 5.15.)

System Drawer Overview

1-23

1.3.9 Power Supply
The system drawer power supplies provide power only to components in the
drawer. One or two power supplies are required, depending on the number of
PCI slots. A second or third power supply can be added for redundancy.

Figure 1–13 Power Supply
Power Supply 2
Power Supply 1
Power Supply 0

PK-0715C-96

1-24

System Drawer User’s Guide

Description
One to three power supplies provide power to components in the system drawer.
(They supply power only for the drawer in which they are located.)
These power supplies share the load, and redundant configurations are supported.
They autoselect line voltage (120V to 240V). Each has 450 W output and supplies
up to 75A of 3.43V, 50A of 5.0V, 11A of 12V, and small amounts of -5V, -12V, and
auxiliary voltage (Vaux).
NOTE: The LEDs on some modules are on when the line cord is plugged in,
regardless of the position of the Power button.
Configuration
•

The number of power supplies required depends on the number of PCI slots in
the drawer. An 8-PCI slot drawer requires one power supply. A 16-PCI slot
drawer requires two power supplies. In each case, one extra power supply can be
added for redundancy.

•

Power supply 0 is installed first, power supply 2 second, and power supply 1
third. See Figure 1–13. (The power supply numbering shown here corresponds
to the numbering displayed by the SRM show power command.)

System Drawer Overview

1-25

1.4 Console Terminal
The console terminal can be either a serial terminal or a graphics monitor. The
power-up display prints to this terminal.

Table 1–3 Comparison of Console Terminals
Condition

Serial
Terminal

Graphics
Monitor

Does the SROM power-up display print?

Yes

Does the XSROM power-up display print?

Yes

Does the SRM console power-up display print?

Yes

Is it supported by the SRM console?

Yes

Is it supported by the AlphaBIOS console?

Yes

Is it supported by the DIGITAL UNIX operating system?

Yes

Is it supported by the OpenVMS operating system?

Yes

Is it supported by the Windows NT operating system?

Yes

1-26

System Drawer User’s Guide

The console terminal can be a serial (character cell) terminal connected to the
COM1 port or a graphics monitor connected to either a TGA adapter or a VGA
adapter on PCI 0. If the console terminal is connected to COM1, the entire power-up
display prints. (See Section 2.2 for information about the power-up display.) If the
console terminal is either a TGA or VGA monitor, console power-up messages are
sent to either of those devices but SROM and XSROM power-up messages are lost.
When the console terminal is a serial terminal, the console environment variable is
set to serial. When it is a graphics monitor, console is set to graphics. (See Section
5.15 for information about environment variables.)
NOTE: Regardless of the setting of the console environment variable, all three
power-up programs send messages to the control panel display.
If the console environment variable is set to serial, os_type is set to unix or
openvms, and no terminal is attached to COM1, pressing a carriage return on a
graphics terminal attached to the keyboard port makes it the console device and the
console prompt is sent to it.
If the console environment variable is set to graphics and no graphics monitor is
attached to the keyboard port, pressing a carriage return on a serial terminal attached
to COM1 makes it the console device and the console prompt is sent to it.
NOTE: The console prompt displays only after the entire power-up sequence is
complete. This can take up to several minutes if the memory is very large.

System Drawer Overview

1-27

Chapter 2
Operation
This chapter provides basic operating instructions, including powering up the system
drawer and booting the operating system. It also provides information about updating
firmware and operating the system from a remote location.
Sections in this chapter are:
•

Powering Up the System Drawer

•

Power-Up Display

•

Booting DIGITAL UNIX

•

Installing DIGITAL UNIX

•

Booting OpenVMS

•

Installing OpenVMS

•

Booting Windows NT

•

Installing Windows NT

•

Updating Firmware

•

Operating the System Remotely

Operation

2-1

2.1 Powering Up the System Drawer
To power up the system drawer, press the Power button (the LED at the top of
the button lights). Testing begins, and status shows on the screen and in the
control panel display.

Figure 2–1 Power Button and Control Panel Display
Power Switch

Display

PK-0706C-96

2-2

System Drawer User’s Guide

Power up the system drawer by pressing the Power button (see Figure 2–1). Testing
begins, and screen text similar to that in Example 2–1 displays (if the console
terminal is a serial terminal connected to the COM1 port), along with status
messages in the control panel display. (See Figure 2–1 for display location. Refer to
Table 3–1 for information about the messages in the control panel display.)
NOTE: If the console terminal is a graphics monitor, only the last few lines of the
power-up display print. See Section 2.2 for more information.

Operation

2-3

2.2 Power-Up Display
The entire power-up display prints to a serial terminal (if the console
environment variable is set to serial); the last several lines print to either a serial
terminal or a graphics monitor. Power-up status also displays on the control
panel display.

Example 2–1 Power-Up Display
P00>>> initialize
Initializing…
SROM V2.0 on cpu0
SROM V2.0 on cpu1
XSROM V3.0 on cpu1
XSROM V3.0 on cpu0
BCache testing complete on cpu1
BCache testing complete on cpu0
mem_pair0 - 128 MB
20..20..21..21..23..
please wait 3 seconds for T24 to complete
24..24..
Memory testing complete on cpu1
Memory testing complete on cpu0

²
³
´
µ
¶

Continued on next page

2-4

System Drawer User’s Guide

On power-up, the SROM code on each CPU module loads into that module’s Icache and tests the processor chip. If all tests pass, the module’s LED lights. If
any test fails, the LED remains clear and power-up terminates.
The primary CPU is determined for the first of three times. The primary CPU
then executes a loopback test on each PCI bridge. If this test passes, the bridge
LED lights. If it fails, the LED remains clear and power-up continues. The
EISA system controller, PCI-to-EISA bridge, COM1 port, and control panel
port are all initialized.
Each CPU prints an SROM message to the device attached to the COM1 port
and to the control panel display. (The banner prints to the COM1 port if the
console environment variable is set to serial. If it is set to graphics, nothing
. See
prints to the console terminal, only to the control panel display, until
Section 5.15 for information about environment variables.)

´
µ
¶

The S-cache on each CPU module is initialized, and the XSROM code in the
FEPROM on the PCI 0 and 1 motherboard is unloaded into them. (If the unload
is not successful, the SROM unloads XSROM code from a different FEPROM
sector. If the second try fails, the CPU hangs.) Each CPU starts the XSROM
code, which prints an XSROM message to the COM1 port and to the control
panel display.
The three S-cache banks on each CPU are enabled, and the B-cache is tested.
If a failure occurs, a message is printed to the COM1 port and to the control
panel display immediately. Each CPU prints a B-cache completion message to
COM1.
The primary CPU is determined for the second time. It then sizes memory.
Information on memory pairs is printed to the COM1 port. If an illegal
memory configuration is detected, a warning message is printed to the COM1
port and the control panel display.
Memory is initialized and tested, and test traces are printed to the COM1 port
and the control panel display. The numbers for tests 20 and 21 might appear
interspersed; this is normal behavior. Test 24 can take several minutes if the
memory is very large; the message preceding the test 24 trace indicates an
estimate of the time this test will take. If a failure occurs, a message is printed
to the COM1 port and to the control panel display immediately. Each CPU
prints a test completion message to the COM1 port.
Continued on next page

Operation

2-5

Example 2–1 Power-Up Display (Continued)

·
¸

starting console on CPU 0
sizing memory
0
128 MB SYNC
starting console on CPU 1
probing IOD1 hose 1
bus 0 slot 1 - NCR 53C810
probing IOD0 hose 0
bus 0 slot 1 - PCEB
probing EISA Bridge, bus 1
bus 0 slot 2 - S3 Trio64/Trio32
bus 0 slot 3 - DECchip 21040-AA
bus 0 slot 5 - NCR 53C810
probing IOD3 hose 3
probing IOD2 hose 2
bus 0 slot 2 - PCI-PCI Bridge
probing PCI-PCI Bridge, bus 2
bus 2 slot 0 - ISP1020
configuring I/O adapters...
ncr0, hose 1, bus 0, slot 1
floppy0, hose 0, bus 1, slot 0
tulip0, hose 0, bus 0, slot 3
ncr1, hose 0, bus 0, slot 5
isp0, hose 2, bus 2, slot 0
System temperature is 23 degrees C
AlphaServer 4000 Console V3.0-10, 19-NOV-1996 13:57:07
P00>>>

2-6

System Drawer User’s Guide

¸
¹
º

The primary CPU is determined for the last time. The primary CPU unloads
PALcode and decompression code from the FEPROM on the PCI motherboard
to its B-cache. The primary CPU then jumps to the PALcode to start the SRM
console.
The primary CPU prints a message indicating that it is running the console.
Starting with this message, the power-up display is printed to any console
terminal, regardless of the state of the console environment variable. (If
console is set to graphics, the display from here to the end is saved in a
memory buffer and printed to the graphics monitor after the PCI buses are
sized and the VGA device is initialized.)
The size and type of each memory pair is determined.
The console is started on each of the secondary CPUs. A status message prints
for each CPU.
The PCI bridges (indicated as IOD n) are probed and the devices are reported.
I/O adapters are configured.
The SRM console banner and prompt are printed. (The SRM prompt is shown
in this manual as P00>>>. It can, however, be P01>>>. The number indicates
the primary processor.) If the auto_action environment variable is set to boot
or restart and the os_type environment variable is set to unix or openvms, the
DIGITAL UNIX or OpenVMS operating system boots.
If the system is running the Windows NT operating system (the os_type
environment variable is set to nt), the SRM console loads and starts the
AlphaBIOS console.
Refer to Chapter 5 for information about the SRM console and to Chapter 6 for
AlphaBIOS.

Operation

2-7

2.3 Booting DIGITAL UNIX
®

DIGITAL UNIX can be booted from a local disk, a disk connected through a
cluster, or a remote disk through an Ethernet connection. Refer to the
documentation shipped with the operating system for booting instructions.

Example 2–2 Booting DIGITAL UNIX from a Local Disk

P00>>> show device
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling ncr1 (NCR 53C810) slot 3, bus 0 PCI, hose 1 SCSI Bus ID 7
dkb100.1.0.3.1
DKb100
RZ29B 0007
dkb200.2.0.3.1
DKb200
RZ29B 0007
dkb400.4.0.3.1
DKb400
RZ29B 0007
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0
DVA0
RX23
polling tulip0 (DECchip 21040-AA) slot 2, bus 0 PCI, hose 1
ewa0.0.0.2.1: 08-00-2B-E5-B4-1A

P00>>> boot -file vmunix -flags a dkb400
(boot dkb4.4.0.3.1 -file vmunix -flags a)
Building FRU table
block 0 of dkb4.4.0.3.1 is a valid boot block
reading 16 blocks from dkb4.4.0.3.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

OSF boot - Mon Aug 5 21:56:39 EDT 1996
Loading vmunix ...
.
.
.
Continued on next page

2-8

System Drawer User’s Guide

Example 2–2 Booting DIGITAL UNIX from a Local Disk
(Continued)
The system is ready.

DIGITAL UNIX Version 3.2D

²
³
´

The show device command displays device information, including name and
type of connection to the system. See Section 5.2 for a description of the show
device command and the device naming convention.
The operating system is on the third disk connected to the system through the
controller in slot 3 of PCI1. The name of this device, dkb400, is used as an
argument to the boot command.
This command loads DIGITAL UNIX from the disk dkb400, using the boot file
vmunix and autobooting to multiuser mode. See Section 5.3 for a description
of the boot command.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner displays.

Operation

2-9

Example 2–3 Booting DIGITAL UNIX from a Disk on a Cluster
P00>>> show boot*
boot_arg0
boot_arg1
boot_dev
boot_file
boot_osflags
boot_reset
bootdef_dev
booted_dev
booted_file
booted_osflags

dkb0.0.0.5.1
vmunix
a
OFF
dkb0.0.0.5.1

P00>>> boot
(boot dkb0.0.0.5.1 -flags a)
halted CPU 1
halt code = 1
operator initiated halt
PC = fffffc0000264600
Building FRU table
block 0 of dkb0.0.0.5.1 is a valid boot block
reading 16 blocks from dkb0.0.0.5.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
Configuring I/O adapters...
jumping to bootstrap code

OSF boot - Mon Jul 29 21:56:39 EDT 1996
Loading vmunix ...
.
.
.
The system is ready.

DIGITAL UNIX Version 3.2D

2-10

System Drawer User’s Guide

²
³

The show boot* command lists all environment variables that begin with the
string “boot.” In this example, the bootdef_dev environment variable sets the
default boot device to dkb0.0.0.5.1, and boot_osflags indicates that the system
will autoboot to multiuser mode. See Section 5.15 for descriptions of these
environment variables.
The boot command needs no options, since the environment variables pass all
necessary information.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner displays.

Operation

2-11

Example 2–4 Booting DIGITAL UNIX from a Remote Disk

P00>>> show device
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0
DVA0
RX23
polling kzpsa0 (DEC KZPSA) slot 3, bus 0 PCI, hose 0 TPwr 1 Fast 1 Bus ID 7
kzpsa0.7.0.3.0
dkb
TPwr 1 Fast 1 Bus ID 7 N01 A09
dkb100.1.0.3.0
DKb100
RZ29B 0007
dkb200.2.0.3.0
DKb200
RZ29B 0007
dkb300.3.0.3.0
DKb300
RZ29B 0007
dkb500.5.0.3.0
DKb500
RZ29B 0007
polling ncr1 (NCR 53C810) slot 5, bus 0 PCI, hose 0 SCSI Bus ID 7
dkc400.4.0.5.0
DKc400
RZ29B 0007
polling tulip0 (DECchip 21040-AA) slot 4, bus 0 PCI, hose 1
ewa0.0.0.4.1: 08-00-2B-E5-B4-1A
polling tulip1 (DECchip 21041-AA) slot 5, bus 0 PCI, hose 1
ewb0.0.0.5.1: 00-00-F8-00-AC-B4

³
´

P00>>> boot -flags an -protocols bootp ewa0
(boot ewa0.0.0.4.1 -flags an)
Building FRU table
Trying BOOTP boot.

Broadcasting BOOTP Request...
Received BOOTP Packet File Name: /var/adm/ris/ris0.alpha/hvmunix
local inet address: 16.122.128.26
remote inet address: 16.122.128.59
TFTP Read File Name: /var/adm/ris/ris0.alpha/hvmunix
.....................................................................
.....................................................................
.................
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 9a0fa0
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Secondary boot program - Thu Aug 1 22:33:13 EST 1996
Loading vmunix ...
.
.
.
Continued on next page
2-12

System Drawer User’s Guide

Example 2–4 Booting DIGITAL UNIX from a Remote Disk
(Continued)
The system is ready.

DIGITAL UNIX Version 3.2D

²
³
´

The show device command displays device information, including name and
type of connection to the system. See Section 5.2 for a description of the show
device command and the device naming convention.
The operating system is on a remote disk accessed through the Ethernet
controller in slot 4 of PCI1. The name of this device, ewa0, is used as an
argument to the boot command.
This command loads DIGITAL UNIX from ewa0, autobooting to multiuser
mode. See Section 5.3 for a description of the boot command.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner displays.

Operation

2-13

2.4 Installing DIGITAL UNIX
DIGITAL UNIX is installed from the internal CD-ROM. Refer to the
documentation shipped with the CD-ROM for installation instructions.

Example 2–5 Installing DIGITAL UNIX
P00>>> boot dka500
(boot dka500.5.0.1.1 -flags a)
Building FRU table
block 0 of dka500.5.0.1.1 is a valid boot block
reading 16 blocks from dka500.5.0.1.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

²
³

OSF boot - Mon Jul 24 21:56:39 EDT 1995
Loading hupdate ...
Starting hupdate at 0x20000000
Using hvmunix
Loading hvmunix ...
Current PAL Revision <0x20000000010111>
Switching to OSF PALcode Succeeded
New PAL Revision <0x20000000020115>
Loading into KSEG Address Space
Sizes:
text = 4460352
data = 5555024
bss = 1498368
Starting at 0xfffffc0000239290
Continued on next page

2-14

System Drawer User’s Guide

Example 2–5 Installing DIGITAL UNIX (Continued)
Alpha boot: available memory from 0x2dfe000 to 0x7fff6000
physical memory = 2048.00 megabytes.
available memory = 2001.96 megabytes.
using 7856 buffers containing 61.37 megabytes of memory
Firmware revision: 2.0
PALcode: DIGITAL-UNIX/OSF version 1.21
AlphaServer 4000
pci1 at mcbus0 slot 5
psiop0 at pci1 slot 1
.
.
.
Printer service started
The system is ready.

DIGITAL UNIX Version 3.2D
login: root
Password:

²
³

Use the boot command to install the operating system from the internal
CD-ROM, which is always dka500.
See your operating system documentation for installation instructions.

Operation

2-15

2.5 Booting OpenVMS
OpenVMS can be booted from a local disk, a disk connected through a cluster,
or a remote disk through an Ethernet connection. Refer to the documentation
shipped with the operating system for booting instructions.

Example 2–6 Booting OpenVMS from a Local Disk

P00>>> show device
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling ncr1 (NCR 53C810) slot 2, bus 0 PCI, hose 1 SCSI Bus ID 7
dkb0.0.0.2.1
DKb0
RZ29B 0016
dkb100.1.0.2.1
DKb100
RZ29B 0016
.
.
.
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0
DVA0
RX23
polling tulip0 (DECchip 21040-AA) slot 3, bus 0 PCI, hose 0
ewa0.0.0.3.0: 00-00-F8-20-14-61
P00>>> show boot_reset
boot_reset
OFF
P00>>> show bootdef_dev
bootdef_dev
dkb0.0.0.2.1
P00>>> boot
SROM V2.0 on cpu0
SROM V2.0 on cpu1
XSROM V2.0 on cpu1
XSROM V2.0 on cpu0
.
.
.
System temperature is 24 degrees C
AlphaServer 4000 Console V3.0-10, 20-NOV-1996 15:17:48

³
´
µ
³

Continued on next page

2-16

System Drawer User’s Guide

Example 2–6 Booting OpenVMS from a Local Disk (Continued)
CPU 0 booting
(boot dkb0.0.0.2.1 -flags 0)
Building FRU table
block 0 of dkb0.0.0.2.1 is a valid boot block
reading 1002 blocks from dkb0.0.0.2.1
bootstrap code read in
.
.
.
Welcome to OpenVMS Alpha (TM) Operating System, Version V6.2-1H3

²
³
´
µ

The show device command displays device information, including name and
type of connection to the system. See Section 5.2 for a description of the show
device command and the device naming convention.
The boot_reset environment variable was previously set to “on,” causing the
power-up trace to display when the system initializes (see Section 2.2). See
Section 5.9 for commands used with environment variables.
The bootdef_dev environment variable specifies the default boot device. In
this example, the default boot device was previously set to dkb0.0.0.2.1.
No boot device is specified in the boot command; the default boot device was
set with the environment variable. See Section 5.3 for a description of the boot
command.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner displays.

Operation

2-17

Example 2–7 Booting OpenVMS from a Disk on a Cluster

²
³

P00>>> show bootdef_dev
bootdef_dev
dua1.8.0.5.1
P00>>> show device
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling dac0 (Mylex DAC960) slot 4, bus 0 PCI, hose 1
dra0.0.0.4.1
DRA0
1 Member JBOD
dra1.0.0.4.1
DRA1
1 Member JBOD
dra2.0.0.4.1
DRA2
4 Member RAID 5
polling cipca0 (CIPCA) slot 5, bus 0 PCI, hose 1 cixcd_poll_comp
cipca_a.4.0.5.1
dua
CI Bus ID 4
dua24.2.0.5.1
$22$DUA24 (HSC702)
RA92
dua30.2.0.5.1
$22$DUA30 (HSC702)
RA92
.
.
.
dua0.8.0.5.1
$22$DUA0 (RAWHSJ)
HSX1
dua1.8.0.5.1
$22$DUA1 (RAWHSJ)
HSX1
.
.
.
P00>>>boot
(boot dua1.8.0.5.1 -flags 0)
Building FRU table
.
.
.
Welcome to OpenVMS Alpha (TM) Operating System, Version V6.2-1H3

´
µ
¶

2-18

System Drawer User’s Guide

²
³
´
µ

The bootdef_dev environment variable specifies the default boot device. In
this example, the default boot device was previously set to dua1.8.0.5.1. See
Section 5.9 for commands used with environment variables.
The show device command displays device information, including name and
type of connection to the system. See Section 5.2 for a description of the show
device command and the device naming convention.
The disk dua1.8.0.5.1 is on the CI cluster that includes this system.
No boot device is specified in the boot command; the default boot device was
set with the environment variable. See Section 5.3 for a description of the boot
command.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner prints.

Operation

2-19

Example 2–8 Booting OpenVMS from a Remote Disk

P00>>> show device
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling kzpsa0 (DEC KZPSA) slot 2, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5
kzpsa0.5.0.2.1
dkb
TPwr 1 Fast 1 Bus ID 5
N01 A10
polling kzpsa1 (DEC KZPSA) slot 3, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5
kzpsa1.5.0.3.1
dkc
TPwr 1 Fast 1 Bus ID 5
N01 A10
polling kzpsa2 (DEC KZPSA) slot 4, bus 0 PCI, hose 1 TPwr 1 Fast 1 Bus ID 5
kzpsa2.5.0.4.1
dkd
TPwr 1 Fast 1 Bus ID 5
P01 A10
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0
DVA0
RX23
polling kzpsa3 (DEC KZPSA) slot 3, bus 0 PCI, hose 0 TPwr 1 Fast 1 Bus ID 5
kzpsa3.5.0.3.0
dke
TPwr 1 Fast 1 Bus ID 5
P01 A10
polling kzpsa4 (DEC KZPSA) slot 4, bus 0 PCI, hose 0 TPwr 1 Fast 1 Bus ID 5
kzpsa4.5.0.4.0
dkf
TPwr 1 Fast 1 Bus ID 5
P01 A10
polling kzpsa5 (DEC KZPSA) slot 5, bus 0 PCI, hose 0 TPwr 1 Fast 1 Bus ID 5
kzpsa5.5.0.5.0
dkg
TPwr 1 Fast 1 Bus ID 5
F01 A10
dkg0.0.0.5.0
DKg0
RZ26J 589H
mkg300.3.0.5.0
MKg300
TLZ09 0165
polling tulip0 (DECchip 21140-AA) slot 5, bus 0 PCI, hose 1
ewa0.0.0.5.1: 00-00-F8-00-42-04
P00>>> boot ewa0 -flags 0
(boot ewa0.0.0.5.1 -flags 0)
Building FRU table

²
³

Trying MOP boot.
.............
Network load complete.
.
.
.
Welcome to OpenVMS Alpha (TM) Operating System, Version V6.2-1H3

2-20

System Drawer User’s Guide

²
³

The show device command displays device information, including name and
type of connection to the system. In this example the Ethernet connection is
ewa0. See Section 5.2 for a description of the show device command and the
device naming convention.
The boot command specifies ewa0 as the boot device. See Section 5.3 for a
description of the boot command.
The boot command accepts the name of a boot device, a boot file name
through the -file option, and boot flags through the -flags option. The
environment variables bootdef_dev, boot_file, and boot_osflags can also be
used to specify the default boot device or device list, the default boot file, and
flag information. When an option and the corresponding environment variable
are both in a command string, the option overrides the environment variable.
The value of the environment variable, however, is not changed. See Section
5.15 for information about environment variables.
The operating system banner prints.

Operation

2-21

2.6 Installing OpenVMS
OpenVMS is installed from the internal CD-ROM. Refer to the documentation
shipped with the CD-ROM for complete installation instructions.

Example 2–9 Installing OpenVMS
P00>>> boot -flags 0,0 dka500
Initializing...
SROM V1.0 on cpu0
.
. [The initialization display prints. See Section 2.2.]
.

AlphaServer 4000 Console V1.0-1, 2-APR-1996 15:17:48
CPU 0 booting
(boot dka500.5.0.1.1 -flags 0,0)
Building FRU table
block 0 of dka500.5.0.1.1 is a valid boot block
reading 1002 blocks from dka500.5.0.1.1
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 7d400
initializing HWRPB at 2000
initializing page table at 1f2000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
OpenVMS (TM) Alpha Operating System, Version 6.2-1H3

%SMP-I-SECMSG, CPU #01 message: P01>>>START
%SMP-I-CPUBOOTED, CPU #01 has joined the PRIMARY CPU in
multiprocessor operation
Continued on next page

2-22

System Drawer User’s Guide

Example 2–9 Installing OpenVMS (Continued)
Installing required known files...
Configuring devices...
****************************************************************
You can install or upgrade the OpenVMS Alpha operating system
or you can install or upgrade layered products that are included
on the OpenVMS Alpha operating system CD-ROM.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1)
2)
3)
4)
5)

Install or upgrade OpenVMS Alpha Version 6.2-1H3
List layered product kits that this procedure can install
Install or upgrade layered product(s)
Execute DCL commands and procedures
Shut down this system

Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?)

²
³

Use the boot command to install the operating system from the internal
CD-ROM, which is always dka500.
See your operating system documentation for installation instructions.

Operation

2-23

2.7 Booting Windows NT
Microsoft Windows NT is started from the AlphaBIOS Boot screen.

Figure 2–2 AlphaBIOS Boot Screen
AlphaBIOS 5.29
Please select the operating system to start:
Windows NT Server 3.51

Use
and
to move the highlight to your choice.
Press Enter to choose.

AlphaServer 4000
Family

Press <F2> to enter SETUP
PK-0728B-96

2-24

System Drawer User’s Guide

The setting of the SRM os_type environment variable determines if AlphaBIOS is
loaded and started on reset and power-up. If os_type is set to nt, after the power-up
display (see Section 2.2) the SRM console is loaded and started, and it then loads
and starts the AlphaBIOS console. AlphaBIOS must be running before Windows NT
can be booted.
The method used for booting Windows NT is determined by the setting of Auto
Start in the AlphaBIOS Standard CMOS Setup screen (see Section 6.7).
•

If Auto Start is enabled, the primary version of Windows NT starts
automatically.

•

If Auto Start is disabled, use the arrow keys to select the Windows NT version
to start. Press Enter to boot Windows NT.

NOTE: The SRM console environment variable must be set to graphics before
booting Windows NT. (This setting is not necessary to run AlphaBIOS.)
If the Halt button is in (the LED on the button is lit), the SRM console will
not load AlphaBIOS. This is true even when the os_type environment variable is set
to nt.

Operation

2-25

2.8 Installing Windows NT
Windows NT is installed from CD-ROM. Insert the CD-ROM in the drive, start
AlphaBIOS Setup, select the menu item Install Windows NT, and follow the
prompts.

Figure 2–3 Installing Windows NT
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup...
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

Press ENTER to install Windows NT.

ESC=Exit
PK-0726B-96

2-26

System Drawer User’s Guide

Up to four versions of Windows NT can be resident in a system at one time.
If this is a new Windows NT installation, start with this procedure:
1.

Start AlphaBIOS. If the system is in the SRM console, issue the command
alphabios.

From the AlphaBIOS Boot screen, enter AlphaBIOS Setup by pressing the F2
key.

From AlphaBIOS Setup select CMOS Setup, and press Enter.

From CMOS Setup set the system date and time.

Return to the AlphaBIOS Setup screen by pressing the F10 key.

Select Hard Disk Setup, and press Enter.

Perform an express hard disk setup by pressing the F7 key to enter Express
Setup.

Continue the setup by pressing the F10 key.

Go to the procedure below.

This procedure is for all Windows NT installations:
1.

Put the Windows NT CD into the CD-ROM drive.

Start AlphaBIOS Setup.

Select Install Windows NT and press Enter.

Follow the prompts to complete the installation. For more information on
installing Windows NT, refer to the Installation Guide in your Windows NT
software package.

Operation

2-27

2.9 Updating Firmware
Start the Loadable Firmware Update (LFU) utility by issuing the lfu command
at the SRM console prompt, booting it from the CD-ROM while in the SRM
console, or selecting Update AlphaBIOS in the AlphaBIOS Setup screen.

Example 2–10 Starting LFU from the SRM Console
P00>>> lfu
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: cda0
.
.
.
UPD>

Figure 2–4 Starting LFU from the AlphaBIOS Console
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

Press ENTER to upgrade your AlphaBIOS from floppy or CD-ROM.

ESC=Exit
PK-0726A-96

2-28

System Drawer User’s Guide

Use the Loadable Firmware Update (LFU) utility to update system firmware.
You can start LFU from either the SRM console or the AlphaBIOS console.
•

From the SRM console, start LFU by issuing the lfu command (see
Example 2–10). Also from the SRM console, LFU can be booted from the Alpha
CD-ROM (V3.7 or later), as shown in Example 2–11.

•

From the AlphaBIOS console, select Update AlphaBIOS from the AlphaBIOS
Setup screen (see Figure 2–4).

A typical update procedure is:
1.

Start LFU.

Use the LFU list command to show the revisions of modules that LFU can
update and the revisions of update firmware.

Use the LFU update command to write the new firmware.

Use the LFU exit command to exit back to the console.

The sections that follow show examples of updating firmware from the local CDROM, the local floppy, and a network device. Following the examples is an LFU
command reference.

Example 2–11 Booting LFU from the CD-ROM
P00>>> show dev ncr0
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1 SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
P00>>> boot dka500
(boot dka500.5.0.1.1 -flags 0,0)
block 0 of dka500.5.0.1.1 is a valid boot block
.
.
.
jumping to bootstrap code
The default bootfile for this platform is
[AS4X00]AS4X00_LFU.EXE
Hit <RETURN> at the prompt to use the default bootfile.
Bootfile: <CR>
Starting Firmware Update Utility
***** Loadable Firmware Update Utility *****
.
.
.
UPD>

Operation

2-29

2.9.1 Updating Firmware from the Internal CD-ROM
Insert the update CD-ROM, start LFU, and select cda0 as the load device.

Example 2–12 Updating Firmware from the Internal CD-ROM
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: cda0

Please enter the name of the options firmware files list, or
Press <return> to use the default filename [AS4X00FW]: AS4X00CP

Copying AS4X00CP from DKA500.5.0.1.1 .
Copying [as4x00]RHREADME from DKA500.5.0.1.1 .
Copying [as4x00]RHSRMROM from DKA500.5.0.1.1 ....................
Copying [as4x00]RHARCROM from DKA500.5.0.1.1 .............
----------------------------------------------------------------Function
Description
----------------------------------------------------------------Display
Displays the system’s configuration table.
Exit
Done exit LFU (reset).
List
Lists the device, revision, firmware name, and
update revision.
Lfu
Restarts LFU.
Readme
Lists important release information.
Update
Replaces current firmware with loadable data image.
Verify
Compares loadable and hardware images.
? or Help Scrolls this function table.
-----------------------------------------------------------------

UPD> list
Device
AlphaBIOS
srmflash

Current Revision
V5.12-2
V1.0-9

Filename
arcrom
srmrom

Update Revision
V6.40-1
V2.0-3
Continued on next page

2-30

System Drawer User’s Guide

²
³

´
µ

Select the device from which firmware will be loaded. The choices are the
internal CD-ROM, the internal floppy disk, or a network device. In this
example, the internal CD-ROM is selected.
Select the file that has the firmware update, or press Enter to select the default
file. The file options are:
AS4X00FW
(default)

SRM console, AlphaBIOS console, and I/O adapter
firmware.

AS4X00CP

SRM console and AlphaBIOS console firmware only.

AS4X00IO

I/O adapter firmware only.

In this example the file for console firmware (AlphaBIOS and SRM) is
selected.
The LFU function table and prompt (UPD>) display.
Use the LFU list command to determine the revision of firmware in a device
and the most recent revision of that firmware available in the selected file. In
this example, the resident firmware for each console (SRM and AlphaBIOS) is
at an earlier revision than the firmware in the update file.
Continued on next page

Operation

2-31

Example 2–12 Updating Firmware from the Internal CD-ROM
(Continued)
UPD> update *
WARNING: updates may take several minutes to complete for each
device.
Confirm update on: AlphaBIOS
AlphaBIOS

[Y/(N)] y

DO NOT ABORT!
Updating to V2.0-3... Verifying V2.0-3...

UPD> exit

2-32

DO NOT ABORT!
Updating to V6.40-1... Verifying V6.40-1... PASSED.

Confirm update on: srmflash
srmflash
PASSED.

[Y/(N)] y

System Drawer User’s Guide

¶
·
¸

The update command updates the device specified or all devices. In this
example, the wildcard indicates that all devices supported by the selected
update file will be updated.
For each device, you are asked to confirm that you want to update the
firmware. The default is no. Once the update begins, do not abort the
operation. Doing so will corrupt the firmware on the module.
The exit command returns you to the console from which you entered LFU
(either SRM or AlphaBIOS).

Operation

2-33

2.9.2 Updating Firmware from the Internal Floppy Disk —
Creating the Diskettes
Create the update diskettes before starting LFU. See Section 2.9.3 for an
example of the update procedure.

Table 2–1 File Locations for Creating Update Diskettes on a PC
Console Update Diskette

I/O Update Diskette

AS4X00FW.TXT

AS4X00IO.TXT

AS4X00CP.TXT

RHREADME.SYS

CIPCA214.SYS

RHSRMROM.SYS

DFPAA246.SYS

RHARCROM.SYS

KZPAAA10.SYS

To update system firmware from floppy disk, you first must create the firmware
update diskettes. You will need to create two diskettes: one for console updates, and
one for I/O.
1.

Download the update files from the Internet (see Appendix A).

On a PC, copy files onto two FAT-formatted diskettes as shown in Table 2–1.
From an OpenVMS system, copy files onto two ODS2-formatted diskettes as
shown in Example 2–13.

2-34

System Drawer User’s Guide

Example 2–13 Creating Update Diskettes on an OpenVMS
System
Console update diskette
$ inquire ignore "Insert blank HD floppy in DVA0, then continue"
$ set verify
$ set proc/priv=all
$ init /density=hd/index=begin dva0: rhods2cp
$ mount dva0: rhods2cp
$ create /directory dva0:[as4x00]
$ copy as4x00fw.sys dva0:[as4x00]as4x00fw.sys
$ copy as4x00cp.sys dva0:[as4x00]as4x00cp.sys
$ copy rhreadme.sys dva0:[as4x00]rhreadme.sys
$ copy as4x00fw.txt dva0:[as4x00]as4x00fw.txt
$ copy as4x00cp.txt dva0:[as4x00]as4x00cp.txt
$ copy rhsrmrom.sys dva0:[as4x00]rhsrmrom.sys
$ copy rharcrom.sys dva0:[as4x00]rharcrom.sys
$ dismount dva0:
$ set noverify
$ exit
I/O update diskette
$ inquire ignore "Insert blank HD floppy in DVA0, then continue"
$ set verify
$ set proc/priv=all
$ init /density=hd/index=begin dva0: rhods2io
$ mount dva0: rhods2io
$ create /directory dva0:[as4x00]
$ create /directory dva0:[options]
$ copy as4x00fw.sys dva0:[as4x00]as4x00fw.sys
$ copy as4x00io.sys dva0:[as4x00]as4x00io.sys
$ copy rhreadme.sys dva0:[as4x00]rhreadme.sys
$ copy as4x00fw.txt dva0:[as4x00]as4x00fw.txt
$ copy as4x00io.txt dva0:[as4x00]as4x00io.txt
$ copy cipca214.sys dva0:[options]cipca214.sys
$ copy dfpaa246.sys dva0:[options]dfpaa246.sys
$ copy kzpsaA10.sys dva0:[options]kzpsaa10.sys
$ dismount dva0:
$ set noverify
$ exit

Operation

2-35

2.9.3 Updating Firmware from the Internal Floppy Disk —
Performing the Update
Insert an update diskette (see Section 2.9.2) into the internal floppy drive. Start
LFU and select dva0 as the load device.

Example 2–14 Updating Firmware from the Internal Floppy Disk
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: dva0

Please enter the name of the options firmware files list, or
Press <return> to use the default filename [AS4X00IO,(AS4X00CP)]:
AS4X00IO

Copying AS4X00IO from DVA0 .
Copying RHREADME from DVA0 .
Copying CIPCA214 from DVA0 .
Copying DFPAA252 from DVA0 ...
Copying KZPSAA11 from DVA0 ...
.
. [The function table displays, followed by the UPD> prompt, as
. shown in Example 2–12.]

UPD> list
Device
AlphaBIOS
pfi0
srmflash

Current Revision
V5.12-3
2.46
T3.2-21

Filename
arcrom
dfpaa_fw
srmrom
cipca_fw
kzpsa_fw

Update Revision
Missing file
2.52
Missing file
A214
A11
Continued on next page

2-36

System Drawer User’s Guide

²
³

Select the device from which firmware will be loaded. The choices are the
internal CD-ROM, the internal floppy disk, or a network device. In this
example, the internal floppy disk is selected.
Select the file that has the firmware update, or press Enter to select the default
file. When the internal floppy disk is the load device, the file options are:
AS4X00CP (default)

SRM console and AlphaBIOS console firmware only.

AS4X00IO

I/O adapter firmware only.

The default option in Example 2–12 (AS4X00FW) is not available, since the
file is too large to fit on a 1.44 MB diskette. This means that when a floppy
disk is the load device, you can update either console firmware or I/O adapter
firmware, but not both in the same LFU session. If you need to update both,
after finishing the first update, restart LFU with the lfu command and insert the
diskette with the other file.

In this example the file for I/O adapter firmware is selected.
Use the LFU list command to determine the revision of firmware in a device
and the most recent revision of that firmware available in the selected file. In
this example, the update revision for console firmware displays as “Missing
file” because only the I/O firmware files are available on the floppy disk.
Continued on next page

Operation

2-37

Example 2–14 Updating Firmware from the Internal Floppy Disk
(Continued)
UPD> update pfi0
WARNING: updates may take several minutes to complete for each
device.
Confirm update on: pfi0

[Y/(N)] y

µ
¶

DO NOT ABORT!
Updating to 2.52... Verifying to 2.52... PASSED.

pfi0

UPD> lfu
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: dva0

Please enter the name of the options firmware files list, or
Press <return> to use the default filename [AS4X00IO,(AS4X00CP)]:

.
. (The function table displays, followed by the UPD> prompt.
. Console firmware can now be updated.)
UPD> exit

2-38

System Drawer User’s Guide

µ
¶
·
¸
¹

The update command updates the device specified or all devices.
For each device, you are asked to confirm that you want to update the
firmware. The default is no. Once the update begins, do not abort the
operation. Doing so will corrupt the firmware on the module.
The lfu command restarts the utility so that console firmware can be updated.
(Another method is shown in Example 2–15, where the user specifies the file
AS4X00FW and is prompted to insert the second diskette.)
The default update file, AS4X00CP, is selected. The console firmware can now
be updated, using the same procedure as for the I/O firmware.
The exit command returns you to the console from which you entered LFU
(either SRM or AlphaBIOS).

Example 2–15 Selecting AS4X00FW to Update Firmware from the
Internal Floppy Disk
P00>>> lfu
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: dva0
Please enter the name of the firmware files list, or
Press <return> to use the default filename [AS4X00IO,(AS4X00CP)]: as4x00fw
Copying AS4X00FW from DVA0 .
Copying RHREADME from DVA0 .
Copying RHSRMROM from DVA0 ..........................
Copying RHARCROM from DVA0 ...............
Copying CIPCA214 from DVA0
Please insert next floppy containing the firmware,
Press <return> when ready. Or type DONE to abort.
Copying CIPCA214 from DVA0 .
Copying DFPAA246 from DVA0 ...
Copying KZPSAA10 from DVA0 ...
.
.
.

Operation

2-39

2.9.4 Updating Firmware from a Network Device
Copy files to the local MOP server’s MOP load area, start LFU, and select ewa0
as the load device.

Example 2–16 Updating Firmware from a Network Device
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: ewa0

Please enter the name of the options firmware files list, or
Press <return> to use the default filename [AS4X00FW]:

Copying AS4X00FW from EWA0 .
Copying RHREADME from EWA0 .
Copying RHSRMROM from EWA0 ...........................
Copying RHARCROM from EWA0 ............
Copying CIPCA214 from EWA0 .
Copying DFPAA246 from EWA0 ...
Copying KZPSAA11 from EWA0 ...
.
. [The function table displays, followed by the UPD> prompt, as
. shown in Example 2–12.]

UPD> list
Device
AlphaBIOS
kzpsa0
kzpsa1
srmflash

Current Revision
V5.12-2
A10
A10
V1.0-9

Filename
arcrom
kzpsa_fw
kzpsa_fw
srmrom
cipca_fw
dfpaa_fw

Update Revision
V6.40-1
A11
A11
V2.0-3
A214
2.46
Continued on next page

2-40

System Drawer User’s Guide

Before starting LFU, download the update files from the Internet (see Appendix A).
You will need the files with the extension .SYS. Copy these files to your local MOP
server’s MOP load area.

²
³

Select the device from which firmware will be loaded. The choices are the
internal CD-ROM, the internal floppy disk, or a network device. In this
example, a network device is selected.
Select the file that has the firmware update, or press Enter to select the default
file. The file options are:
AS4X00FW
(default)

SRM console, AlphaBIOS console, and I/O adapter
firmware.

AS4X00CP

SRM console and AlphaBIOS console firmware only.

AS4X00IO

I/O adapter firmware only.

In this example the default file, which has both console firmware (AlphaBIOS
and SRM) and I/O adapter firmware, is selected.
Use the LFU list command to determine the revision of firmware in a device
and the most recent revision of that firmware available in the selected file. In
this example, the resident firmware for each console (SRM and AlphaBIOS)
and I/O adapter is at an earlier revision than the firmware in the update file.
Continued on next page

Operation

2-41

Example 2–16 Updating Firmware from a Network Device
(Continued)
UPD> update * -all
WARNING: updates may take several minutes to complete for each
device.

AlphaBIOS

DO NOT ABORT!
Updating to V6.40-1... Verifying V6.40-1... PASSED.

kzpsa0

DO NOT ABORT!
Updating to A11
... Verifying A11... PASSED.

kzpsa1

DO NOT ABORT!
Updating to A11
... Verifying A11... PASSED.

srmflash

DO NOT ABORT!
Updating to V2.0-3... Verifying V2.0-3... PASSED.

UPD> exit

2-42

System Drawer User’s Guide

µ
¶

The update command updates the device specified or all devices. In this
example, the wildcard indicates that all devices supported by the selected
update file will be updated. Typically LFU requests confirmation before
updating each console’s or device’s firmware. The -all option eliminates the
update confirmation requests.
The exit command returns you to the console from which you entered LFU
(either SRM or AlphaBIOS).

Operation

2-43

2.9.5 LFU Commands
The commands summarized in Table 2–2 are used to update system firmware.

Table 2–2 LFU Command Summary
Command

Function

display

Shows the physical configuration of the system.

exit

Terminates the LFU program.

help

Displays the LFU command list.

lfu

Restarts the LFU program.

list

Displays the inventory of update firmware on the selected device.

readme

Lists release notes for the LFU program.

update

Writes new firmware to the module.

verify

Reads the firmware from the module into memory and compares it
with the update firmware.

These commands are described in the following pages.

2-44

System Drawer User’s Guide

display
The display command shows the physical configuration of the system. Display is
equivalent to issuing the SRM console command show configuration. Because it
shows the slot for each module, display can help you identify the location of a
device.

exit
The exit command terminates the LFU program, causes system initialization and
testing, and returns the system to the console from which LFU was called.

help
The help (or ?) command displays the LFU command list, shown below.
--------------------------------------------------------------------Function
Description
--------------------------------------------------------------------Display
Displays the system’s configuration table.
Exit
Done exit LFU (reset).
List
Lists the device, revision, firmware name, and update
revision.
Lfu
Restarts LFU.
Readme
Lists important release information.
Update
Replaces current firmware with loadable data image.
Verify
Compares loadable and hardware images.
? or Help Scrolls this function table.
---------------------------------------------------------------------

lfu
The lfu command restarts the LFU program. This command is used when the update
files are on a floppy disk. The files for updating both console firmware and I/O
firmware are too large to fit on a 1.44 MB disk, so only one type of firmware can be
updated at a time. Restarting LFU enables you to specify another update file.

Operation

2-45

list
The list command displays the inventory of update firmware on the CD-ROM,
network, or floppy. Only the devices listed at your terminal are supported for
firmware updates.
The list command shows three pieces of information for each device:
•

Current Revision — The revision of the device’s current firmware

•

Filename — The name of the file used to update that firmware

•

Update Revision — The revision of the firmware update image

readme
The readme command lists release notes for the LFU program.

update
The update command writes new firmware to the module. Then LFU automatically
verifies the update by reading the new firmware image from the module into
memory and comparing it with the source image.
To update more than one device, you may use a wildcard but not a list. For example,
update k* updates all devices with names beginning with k, and update * updates
all devices. When you do not specify a device name, LFU tries to update all devices;
it lists the selected devices to update and prompts before devices are updated. (The
default is no.) The -all option eliminates the update confirmation requests, enabling
the update to proceed without operator intervention.
CAUTION: Never abort an update operation. Aborting corrupts the firmware on
the module.

verify
The verify command reads the firmware from the module into memory and
compares it with the update firmware. If a module already verified successfully
when you updated it, but later failed tests, you can use verify to tell whether the
firmware has become corrupted.

2-46

System Drawer User’s Guide

2.10 Operating the System Remotely
The remote console monitor (RCM) is used to monitor and control the system
remotely. The RCM resides on the server control module (see Section 1.3.7) and
allows the system administrator to connect remotely to a managed system
through a modem, using a serial terminal or terminal emulator.

RCM Console Overview
The RCM has special console firmware that is used to remotely control an
AlphaServer system. The RCM firmware resides on an independent microprocessor.
It is not part of the SRM console that resides in the flash ROM. The RCM firmware
has its own command interface that allows the user to perform the tasks that can
usually be done from the system’s serial console terminal. RCM console commands
are used to reset, halt, and power the system on or off, regardless of the operating
system or hardware state. The RCM console commands are also used to monitor the
power supplies, temperature, and fans.
The user can enter the RCM console either remotely or through the local serial
console terminal. Once in command mode, the user can enter commands to control
and monitor the system.
•

To enter the RCM console remotely, the user dials in through a modem, enters a
password, and then types a special escape sequence that invokes RCM command
mode. You must set up the modem before you can dial in remotely. See
Section 2.10.1.

•

To enter the RCM console locally, the user types the escape sequence at the
SRM console prompt on the local serial console terminal.

The RCM also provides an autonomous dial-out capability when it detects a power
failure within the system. When triggered, the RCM dials a paging service at 30minute intervals until the administrator clears the alert within the RCM.

Operation

2-47

2.10.1 Modem Usage
To use the RCM to monitor a system remotely, first make the connections to the
server control module, as shown below. Then configure the modem port for
dial-in.

Figure 2–5 RCM Connections

ConsoleTerminal

PhoneJack
External
Power
Supply

Modem

2-48

System Drawer User’s Guide

PK-0762-96

Modem Selection
The RCM requires a Hayes-compatible modem. The controls that the RCM sends to
the modem have been selected to be acceptable to a wide selection of modems. The
modems that have been tested and qualified include:
Motorola LifeStyle Series 28.8
AT&T DATAPORT 14.4/FAX
Zoom Model 360
The U.S. Robotics Sportster DATA/FAX MODEM is also supported, but requires
some modification of the modem initialization and answer strings. See Section
2.10.7.
Modem Configuration Procedure
1.

Connect a Hayes-compatible modem to the RCM as shown in Figure 2–5, and
power up the modem.

From the local serial console terminal, enter the RCM firmware console by
typing the following escape sequence:
^]^]rcm
The character “^” is created by simultaneously holding down the Ctrl key and
pressing the ] key (right square bracket). The firmware prompt, RCM>, should
now be displayed.

Enter a modem password with the setpass command. See Section 2.10.3.

Enable the modem port with the enable command. See Section 2.10.3.

Enter the quit command to leave the RCM console.

You are now ready to dial in remotely.

Operation

2-49

Dialing In to the RCM Modem Port
1.

Dial the modem connected to the server control module. The RCM answers the
call and after a few seconds prompts for a password with a “#” character.

Enter the password that was loaded using the setpass command. The user has
three tries to correctly enter the password. On the third unsuccessful attempt,
the connection is terminated, and as a security precaution, the modem is not
answered again for 5 minutes.
On successful entry of the password, the RCM banner message “RCM V1.0” is
displayed, and the user is connected to the system COM1 port. At this point the
local terminal keyboard is disabled except for entering the RCM console
firmware. The local terminal displays all the terminal traffic going out to the
modem.

To connect to the RCM firmware console, type the RCM escape sequence.

Refer to Example 2–17 for an example of the modem dial-in procedure.
A sample dial-in dialog would look similar to the following:

Example 2–17 Sample Remote Dial-In Dialog
ATQ0V1E1S0=0
OK
ATDT30167
CONNECT 9600
#
RCM V1.0
^]^]rcm
RCM>

!When modem dial-in connection is made, a screen display
similar to this appears.
!Enter password at this prompt.
!RCM banner is displayed.
!Enter the escape sequence after the banner is displayed.
The escape sequence is not echoed on the terminal.
!RCM prompt is displayed. Commands to control and
monitor the system can be entered.

Terminating a Remote Console (Modem) Session
Terminate the modem session by executing a hangup command from the RCM
console firmware. This will cleanly terminate the modem connection.
If the modem connection is terminated without using the hangup command, or if the
line is dropped due to phone line problems, the RCM will detect carrier loss and
initiate an internal hangup command. This process can take a minute or more, and
the local terminal will be locked out until the auto hangup process completes.
If the modem link is idle for more than 20 minutes, the RCM initiates an auto
hangup.
2-50

System Drawer User’s Guide

2.10.2 Entering and Leaving Command Mode
Use the default escape sequence to enter RCM command mode for the first time.
You can enter RCM command mode from the SRM console level, the operating
system level, or an application. The RCM quit command reconnects the
terminal to the system console port.

Example 2–18 Entering and Leaving RCM Command Mode

^]^]rcm
RCM>

RCM> quit
Focus returned to COM port

Entering the RCM Firmware Console
To enter the RCM firmware console, enter the RCM escape sequence. See
Example 2–18 for the default sequence.

² in

The escape sequence is not echoed on the terminal or sent to the system. Once in the
RCM firmware console, the user is in RCM command mode and can enter RCM
console commands.
Leaving Command Mode
To leave RCM command mode and reconnect to the system console port, enter the
quit command, then press Return to get a prompt from the operating system or
system console. (See ).

Operation

2-51

2.10.3 RCM Commands
The RCM commands summarized below are used to control and monitor a
system remotely.

Table 2–3 RCM Command Summary
Command

Function

alert_clr

Clears alert flag, stopping dial-out alert cycle

alert_dis

Disables the dial-out alert function

alert_ena

Enables the dial-out alert function

disable

Disables remote access to the modem port

enable

Enables remote access to the modem port

hangup

Terminates the modem connection

halt

Halts server

help or ?

Displays the list of commands

poweroff

Turns off power to server

poweron

Turns on power to server

quit

Exits console mode and returns to system console port

reset

Resets the server

setesc

Changes the escape sequence for entering command mode

setpass

Changes the modem access password

status

Displays server’s status and sensors

2-52

System Drawer User’s Guide

Command Conventions
•
•
•

The commands are not case sensitive.
A command must be entered in full.
If a command is entered that is not valid, the command fails with the message:
*** ERROR - unknown command ***

Enter a valid command.
The RCM commands are described on the following pages.

Operation

2-53

alert_clr
The alert_clr command clears an alert condition within the RCM. The alert enable
condition remains active, and the RCM will again enter the alert condition when it
detects a system power failure. See Section 2.10.4.
RCM>alert_clr

alert_dis
The alert_dis command disables RCM dial-out capability. It also clears any out standing alerts. See Section 2.10.4. The alert disable state is nonvolatile. Dial-out
capability remains disabled until the alert_enable command is issued.
RCM>alert_dis

alert_ena
The alert_ena command enables the RCM to automatically dial out when it detects
a power failure within the system. The RCM repeats the dial-out alert at 30-minute
intervals until the alert is cleared. The alert enable state is nonvolatile. Dial-out
capability remains enabled until the alert_disable command is issued.
RCM>alert_ena
In order for the alert_enable command to work, two conditions must be met:
•

A modem dial-out string must be entered with the system console.

•

Remote access to the RCM modem port must be enabled with the enable
command.

See Section 2.10.4.
If the alert_enable command is entered when remote access is disabled, the
following message is returned:
*** error ***

2-54

System Drawer User’s Guide

disable
The disable command disables remote access to the RCM modem port.
RCM>disable
The module’s remote access default state is DISABLED. The modem enable state is
nonvolatile. When the modem is disabled, it remains disabled until the enable
command is issued. If a modem connection is in progress, entering the disable
command terminates it.

enable
The enable command enables remote access to the RCM modem port. It can take up
to 10 seconds for the enable command to be executed.
RCM>enable
The module’s remote access default state is DISABLED.
The modem enable state is nonvolatile. When the modem is enabled, it remains
enabled until the disable command is issued.
The enable command can fail for two reasons:
•

There is no modem access password configured.

•

The modem is not connected or is not working properly.

If the enable command fails, the following message is displayed:
*** ERROR - enable failed ***

hangup
The hangup command terminates the modem session. When this command is
issued, the remote user is disconnected from the server. This command can be
issued from either the local or remote console.
RCM>hangup

Operation

2-55

halt
The halt command attempts to halt the managed system. It is functionally
equivalent to pressing the Halt button on the system operator control panel to the
“in” position and then releasing it to the “out” position. The RCM console firm ware
exits command mode and reconnects the user’s terminal to the server’s COM1 serial
port.
RCM>halt
Focus returned to COM port
NOTE: Pressing the Halt button has no effect on systems running Windows NT.

help or ?
The help or ? command displays the RCM firmware command set.

poweroff
The poweroff command requests the RCM module to power off the system It is
functionally equivalent to turning off the system power from the operator control
panel.
RCM>poweroff
If the system is already powered off, this command has no effect.
The external power to the RCM must be connected in order to power off the system
from the RCM firmware console. If the external power supply is not connected, the
command will not power the system down, and displays the message:
*** ERROR ***

2-56

System Drawer User’s Guide

poweron
The poweron command requests the RCM module to power on the system. For the
system power to come on, the following conditions must be met:
•

AC power must be present at the power supply inputs.

•

The DC On/Off button must be in the “on” position.

•

All system interlocks must be set correctly.

The RCM firmware console exits command mode and reconnects the user’s terminal
to the system console port.
RCM>poweron
Focus returned to COM port
NOTE: If the system is powered off with the DC On/Off button, the syste m will not
power up. The RCM will not override the “off” state of the DC On/Off button. If the
system is already powered on, the poweron command has no effect.

quit
The quit command exits the user from command mode and reconnects the user’s
terminal to the system console port. The following message is displayed:
Focus returned to COM port
The next display depends on what the system was doing when the RCM was
invoked. For example, if the RCM was invoked from the SRM console prompt, the
console prompt will be displayed when you enter a carriage return. Or, if the RCM
was invoked from the operating system prompt, the operating system prompt will be
displayed when you enter a carriage return.

Operation

2-57

reset
The reset command requests the RCM module to perform a hardware reset. It is
functionally equivalent to pressing the Reset button on the system operator control
panel.
RCM>reset
Focus returned to COM port
The following events occur when the reset command is executed:
•

The system restarts and the system console firmware reinitializes.

•

The console exits RCM command mode and reconnects the user’s terminal to
the server’s COM1 serial port.

•

The power-up messages are displayed, and then the console prompt is displayed
or the operating system boot messages are displayed, depending on the state of
the Halt button.

setesc
The setesc command allows the user to reset the default escape sequence for entering
console mode. The escape sequence can be any character string. A typical sequence
consists of 2 or more characters, to a maximum of 15 characters. The escape
sequence is stored in the module’s on-board NVRAM.
NOTE: If you change the escape sequence, be sure to record the new sequence.
Although the module factory defaults can be restored if the user has forgotten the
escape sequence, this involves accessing the server control module and moving a
jumper.
The following sample escape sequence consists of five iterations of the Ctrl key and
the letter “o”.
RCM>setesc
^o^o^o^o^o
RCM>

2-58

System Drawer User’s Guide

If the escape sequence entered exceeds 15 characters, the command fails with the
message:
*** ERROR ***
When changing the default escape sequence, avoid using special characters that are
used by the system’s terminal emulator or applications.
Control characters are not echoed when entering the escape sequence. To verify the
complete escape sequence, use the status command.

setpass
The setpass command allows the user to change the modem access password that is
prompted for at the beginning of a modem session. The password is stored in the
module’s on-board NVRAM.
RCM>setpass
new pass>*********
RCM>
The maximum password length is 15 characters. If the password entered exceeds 15
characters, the command fails with the message:
***

ERROR ***

The minimum password length is one character, followed by a carriage return. If
only a carriage return is entered, the command fails with the message:
*** ERROR - illegal password ***
If the user has forgotten the password, a new password can be entered.

Operation

2-59

status
The status command displays the current state of the server’s sensors, as well as the
current escape sequence and alarm information.
RCM>status
Firmware Rev: V1.0
Escape Sequence: ^]^]RCM
Remote Access: ENABLE/DISABLE
Alerts: ENABLE/DISABLE
Alert Pending: YES/NO (C)
Temp (C): 26.0
RCM Power Control: ON/OFF
External Power: ON
Server Power: OFF
RCM>
The status fields are explained in Table 2–4.

2-60

System Drawer User’s Guide

Table 2–4 RCM Status Command Fields
Item

Description

Firmware Rev:

Revision of RCM firmware.

Escape Sequence:

Current escape sequence to enter RCM firmware
console.

Remote Access:

Modem remote access state. (ENABLE/DISABLE)

Alerts:

Alert dial-out state. (ENABLE/DISABLE)

Alert Pending:

Alert condition triggered. (YES/NO)

Temp (C):

Current system temperature in degrees Celsius.

RCM Power Control:

Current state of RCM system power control.
(ON/OFF)

External Power:

Current state of power from external power supply
to server control module. (ON/OFF)

Operation

2-61

2.10.4 Dial-Out Alerts
The RCM can be configured to automatically dial out through the modem
(usually to a paging service) when it detects a power failure within the system.
When a dial-out alert is triggered, the RCM initializes the modem for dial-out,
sends the dial-out string, hangs up the modem, and reconfigures the modem for
dial-in. The RCM and modem must continue to be powered, and the phone line
must remain active, for the dial-out alert function to operate.

Example 2–19 Configuring the Modem for Dial-Out Alerts
P00>>> set rcm_dialout “ATDTstring#;”

RCM>enable
RCM>status
.
.
Remote Access:
.
RCM>alert_ena

³
´

Enable

Example 2–20 Typical RCM Dial-Out Command
P00>>> set rcm_dialout “ATXDT9,15085553333,,,,,,5085553332#;”
Use the show command to verify the RCM dial-out string:
P00>>> show rcm_dialout
rcm_dialout
ATXDT9,15085553333,,,,,,5085553332#;

2-62

System Drawer User’s Guide

Enabling the Dial-Out Alert Function:
1.

Enter the set rcm_dialout command, followed by a dial-out alert string, from
in Example 2–19).
the SRM console (see

The string is a modem dial-out character string, not to exceed 47 characters, that
is used by the RCM when dialing out through the modem. See the next topic for
details on composing the modem dial-out string.
2.

Enter the RCM firmware console and enter the enable command to enable
remote access dial-in. The RCM firmware status command should display
“Remote Access: ENABLE.” (See .)

Enter the RCM firmware alert_ena command to enable outgoing alerts. (See

´.)

Operation

2-63

Composing a Modem Dial-Out String
The modem dial-out string emulates a user dialing an automatic paging service.
Typically, the user dials the pager phone number, waits for a tone, and then enters a
series of numbers.
The RCM dial-out string (Example 2–20) has the following requirements:
•

The entire string following the set rcm_dialout command must be enclosed by
quotation marks.

•

The characters ATDT must be entered after the opening quotation marks. Do
not mix case. Enter the characters either in all uppercase or all lowercase.

•

Enter the character X if the line to be used also carries voice mail. Refer to the
example that follows.

•

The valid characters for the dial-out string are the characters on a phone keypad:
0–9, *, and #. In addition, a comma (,) requests that the modem pause for 2
seconds, and a semicolon (;) is required to terminate the string.

Elements of the Dial-Out String
ATXDT

AT = Attention
X = Forces the modem to dial “blindly” (not look for a dial tone).
Enter this character if the dial-out line modifies its dial tone when
used for services such as voice mail.
D = Dial
T = Tone (for touch-tone)
, = Pause for 2 seconds.

In the example, “9” gets an outside line. Enter the number for an
outside line if your system requires it.

15085553333

Dial the paging service.

,,,,,,

Pause for 12 seconds for paging service to answer

5085553332#

“Message,” usually a call-back number for the paging service.

;

Return to console command mode. Must be entered at end of
string.

2-64

System Drawer User’s Guide

2.10.5 Resetting the RCM to Factory Defaults
If the escape sequence has been forgotten, you can reset the controller to factory
settings.

Reset Procedure
1.

Power down the server and access the server control module, as follows:
Expose the PCI bus card cage. Remove three Phillips head screws holding the
cover in place and slide it off the drawer. If necessary, remove several PCI and
EISA options from the bottom of the PCI card cage until you have enough space
to access the server control module.

Unplug the external power supply to the server control module.
Locate the password and option reset jumper. The jumper number, which is
etched on the board, depends on the revision of the server control module.
NOTE: If the RCM section of the server control module does not have an
orange relay, the jumper number is J6. If the RCM section of the
server control module has an orange relay, the jumper number is J7.

Move the jumper so that it is sitting on both pins.

Replace any panels or covers as necessary so you can power up the system. Press
the Halt button and then power up the system to the SRM console prompt.
Powering up with the password and option reset jumper in place resets the escape
sequence, password, and modem enable states to the factory default.

When the console prompt is displayed, power down the system and move the
password and option reset jumper back onto the single pin.

Replace any PCI or EISA modules you removed and replace the PCI bus card
cage cover.

Power up the system to the SRM console prompt and type the default escape
sequence to enter RCM command mode:
^]^]RCM

Configure the module as desired. You must reset the password and modem
enable states in order to enable remote access.

Operation

2-65

2.10.6 Troubleshooting Guide
Table 2–5 lists a number of possible causes and suggested solutions for
symptoms you might see.

Table 2–5 RCM Troubleshooting
Symptom

Possible Cause

Category

Description

Driver ID

Two-letter designator of port or class driver
dk

SCSI disk

FDDI device

RAID set device

SCSI tape

DSSI disk

DSSI tape

Diskette drive

SCSI port

Ethernet port

DSSI port

Storage adapter ID

One-letter designator of storage adapter (a, b, c...).

500

Device unit number

Unique number (MSCP unit number). SCSI unit
numbers are forced to 100 X node ID.

Bus node number

Bus node ID.

Channel number

Used for multi-channel devices.

Logical slot number

Corresponds to PCI slot number, as shown in
Table 5–2.

Hose number

0 — PCI 0
1 — PCI 1

2 — PCI 2
3 — PCI 3

Table 5–2 PCI Slot Numbers
Slot

PCI 0

PCI 1

PCI 2

PCI 3

Reserved

EISA bridge

Embedded SCSI
CD-ROM

Reserved

PCI device

PCI or EISA device

PCI device

PCI or EISA device

PCI device

PCI or EISA device

PCI device

SRM Console

5-7

Example 5–5 Show FRU Command
P00>>> show fru
Digital Equipment Corporation
AlphaServer 4000
Console V3.0-10 OpenVMS PALcode V1.19-2, DIGITAL UNIX PALcode V1.21-14
Module
System Motherboard
Memory 128 MB SYNC
CPU (2MB Cache)
CPU is disabled
Bridge (IOD0/IOD1)
PCI Motherboard
Bridge (IOD2/IOD3)
PCI Motherboard
Bus 0
Slot
1
2
3
5

Part #
B2001-AA
N/A
B2001-AA
B2001-AA
B2001-AA
B2001-AA
B2001-AA
B2001-AA

iod0 (PCI0)
Option Name
PCEB
S3 Trio64/Trio32
DECchip 21040-AA
NCR 53C810

Type
0
0
2
0
600
8
600
0

Rev
0000
0000
0004
0000
0021
0002
0021
0000

Type
Rev
4828086 0005
88115333 0000
21011
0023
11000
0002

Name
Serial #
mthrbrd0 AY12345678
mem0
N/A
cpu0
AY12345678
cpu1
AY12345678
iod0/iod1 AY12345678
saddle0 AY12345678
iod2/iod3 AY12345678
saddle1 AY12345678
Name
pceb0
vga0
tulip0
ncr1

Bus 1 pceb0 (EISA Bridge connected to iod0, slot 1)
Slot Option Name
Type
Rev
Name
Bus 0 iod1 (PCI1)
Slot Option Name
1
NCR 53C810

Type
11000

Rev
0002

Name
ncr0

Bus 0 iod2 (PCI2)
Slot Option Name
2
PCI-PCI Bridge

Type
11011

Rev
0002

Name
pcb0

Bus 2 pcb0 (PCI-PCI Bridge connected to iod2, slot 2)
Slot Option Name
Type
Rev
Name
0
ISP1020
10201077 0002 isp0
Bus 0 iod3 (PCI3)
Slot Option Name
P00>>>

Type

Rev

Name

The show fru command displays information for CPU, memory, PCI, and EISA.
This information is based on data in the serial control bus EPROM. The syntax is:
show fru

5-8

System Drawer User’s Guide

Example 5–6 Show Memory Command
P00>>> show memory
Slot
---0
1

Type
---EDO
EDO

Total
P00>>>

MB
---256
128

Base
-------0
10000000

384

The show memory command displays information about each memory pair: slot
number (see Figure 1–6 for memory slots), type (synchronous or EDO), size of the
memory pair in megabytes, and the starting address of the pair. The syntax is:
show memory

Example 5–7 Show Network Command
P00>>> show network
polling tulip0 (DECchip 21040-AA) slot 2, bus 0 PCI, hose 1
ewa0.0.0.2.1: 08-00-2B-E5-B4-1A
P00>>>
The show network command displays the assigned network device names and other
information about network (FDDI and Ethernet) cards. The syntax is:
show network

SRM Console

5-9

Example 5–8 Show PAL Command
P00>>> show pal
pal OpenVMS PALcode V1.17-9, DIGITAL UNIX PALcode V1.21-5
P00>>>
The show pal command displays the versions of DIGITAL UNIX and OpenVMS
PALcode. PALcode is the Alpha Privileged Architecture Library code, written to
support Alpha processors. It implements architecturally defined processor behavior.
The syntax is:
show pal

Example 5–9 Show Power Command
P00>>> show power
Power Supply 0
Power Supply 1
Power Supply 2
System Fans
CPU Fans
Temperature

Status
good
not present
good
good
good
good

The system was last reset via a system software reset
0 Environmental events are logged in nvram
P00>>>
The show power command displays status information about the power supplies,
system fans, CPU fans, and temperature. This command is useful for displaying the
error state of a DIGITAL UNIX or OpenVMS system that shuts down because of a
fan, temperature, or power supply failure. If the system can be restarted, use this
command. (If it cannot, use the RCM status command; see Section 2.10.3.)
The syntax is:
show power

5-10

System Drawer User’s Guide

Example 5–10 Show Version Command
P00>>> show version
version
P00>>>

V3.0-10 20-NOV-1996 13:59:28

The show version command displays the version of the SRM console program that is
installed on the system. The syntax is:
show version

SRM Console

5-11

5.3 Booting the Operating System
The boot command is used to boot the operating system.

Example 5–11 Boot Command
P00>>> boot dkb0
SROM V2.0 on cpu0
SROM V2.0 on cpu1
XSROM V3.0 on cpu1
XSROM V3.0 on cpu0
BCache testing complete on cpu1
BCache testing complete on cpu0
mem_pair0 - 128 MB
20..20..21..21..23..
please wait 3 seconds for T24 to complete
24..24..
Memory testing complete on cpu1
Memory testing complete on cpu0
starting console on CPU 0
sizing memory
0
128 MB SYNC
starting console on CPU 1
probing IOD1 hose 1
bus 0 slot 1 - NCR 53C810
probing IOD0 hose 0
bus 0 slot 1 - PCEB
probing EISA Bridge, bus 1
bus 0 slot 2 - S3 Trio64/Trio32
bus 0 slot 3 - DECchip 21040-AA
bus 0 slot 5 - NCR 53C810
probing IOD3 hose 3
probing IOD2 hose 2
bus 0 slot 2 - PCI-PCI Bridge
probing PCI-PCI Bridge, bus 2
bus 2 slot 0 - ISP1020
configuring I/O adapters...
ncr0, hose 1, bus 0, slot 1
floppy0, hose 0, bus 1, slot 0
tulip0, hose 0, bus 0, slot 3
ncr1, hose 0, bus 0, slot 5
isp0, hose 2, bus 2, slot 0
Continued on next page

5-12

System Drawer User’s Guide

Example 5–11 Boot Command (Continued)
System temperature is 23 degrees C
AlphaServer 4000 Console V3.0-10, 19-NOV-1996 13:57:07
CPU 0 booting
(boot dkb0.0.0.2.1 -flags 0)
Building FRU table
.
.
.
setting affinity to the primary CPU
jumping to bootstrap code
OpenVMS (TM) Alpha Operating System, Version 6.2-1H3

The boot command initializes the processor, loads a program image from the
specified boot device, and transfers control to that image. The syntax is:
boot [-file filename] [-flags [value]] [-halt] [-protocols enet_protocol] [boot_dev]
-file filename

The boot file.

-flags [value]

Specifies additional information to the loaded image or
operating system. In DIGITAL UNIX, specifies boot flags. In
OpenVMS, specifies system root number and boot flags. This
qualifier overrides the setting of the boot_osflags environment
variable. See the boot_osflags environment variable for a list of
settings and their meanings.

-halt

Forces the bootstrap operation to halt and invoke the console
program once 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 image by entering the
continue command.

-protocols
enet_protocol

Either mop (default) or bootp. This qualifier overrides the
setting of the ew*0_protocols environment variable.

boot_dev

A device path or list of devices from which the console program
attempts to boot, or a saved boot specification in the form of an
environment variable. This qualifier overrides the setting of the
bootdef_dev environment variable. Use the bootdef_dev
environment variable to define the default boot device string.

SRM Console

5-13

5.4 Configuring the System
5.4.1 Configuring DSSI
The set host command is used for system configuration when a DSSI device is in
the system.

Example 5–12 Set Host Command
P00>>> show device kfpsa0
dud0.0.0.3.0
R2YQYA$DIA0
P00>>> set mode diag
P00>>> config kfpsa*
P00>>> set host -dup dud0
starting DIRECT on pud0.0.0.3.0 (R2YQYA)

RF72

Copyright (C) 1995 Digital Equipment Corporation
PRFMON V1.0 D 2-NOV-1995 10:30:58
DKCOPY V1.0 D 2-NOV-1995 10:30:58
DRVEXR V2.0 D 2-NOV-1995 10:30:58
DRVTST V2.0 D 2-NOV-1995 10:30:58
HISTRY V1.0 D 2-NOV-1995 10:30:58
DIRECT V1.0 D 2-NOV-1995 10:30:58
ERASE V2.0 D 2-NOV-1995 10:30:58
VERIFY V1.0 D 2-NOV-1995 10:30:58
DKUTIL V1.0 D 2-NOV-1995 10:30:58
PARAMS V2.0 D 2-NOV-1995 10:30:58
Total of 10 programs.
Task?
P00>>> set host -dup -task params dud0
starting PARAMS on pud0.0.0.3.0 (R2YQYA)
Copyright (C) 1995

Digital Equipment Corporation

PARAMS> show allclass
Parameter
Current
Default
Type
Radix
--------- ------------- ------------ ------- -----ALLCLASS
0
0
Byte
Dec
PARAMS> exit
Exiting...
P00>>>

5-14

System Drawer User’s Guide

The set host command connects the console program to another DUP server on an
MSCP DSSI device. You can use the DUP protocol to examine and modify
parameters of a DSSI device. The syntax is:
set host -dup [-task task_name] device
-dup

Connect to an MSCP DUP server. The DUP service may be used
to examine and modify parameters of a DSSI device.

-task task_name

Specifies the DUP utility to invoke. If -task is not specified, a
directory of utilities displays.

device

The device to attach to the console program.

SRM Console

5-15

5.4.2 Configuring a PCI NVRAM Module
The prcache command is used for system configuration when a PCI NVRAM
module is in the system. Used only with DIGITAL UNIX systems.

Example 5–13 Prcache Command
P00>>> prcache -f
PCI NVRAM Disk Cache: passed
Size:
4MB
PCI Memory Address: 40000000
System ID: 12000000
State: - not valid
Battery Status: good (Charging)
Battery Disconnect Circuit Status: enabled
P00>>> prcache -z
This command will zero the PCI NVRAM Disk Cache
Do you really want to continue [Y/N] ? : y
clearing disk cache
P00>>>

The prcache command is used to check PCI NVRAM configuration information and
battery status, to clear data from the NVRAM module, and to set the date of the next
battery replacement. This command is used only with DIGITAL UNIX systems. The
syntax is:
prcache -{f,z,b}
-f

Checks configuration information and battery status.

-z

Clears valid data; writes zeros to memory.

-b

Sets the date (month and year) for battery replacement.

5-16

System Drawer User’s Guide

5.4.3 Configuring EISA and RAID
EISA and RAID devices are configured from the AlphaBIOS console.

Figure 5–1 Configuring EISA and RAID Devices
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard D
Run Maintenance Program
CMOS S
Instal
Program Name: swxcrmgr.exe
Utilit
About
Location: A:

ENTER=Execute

A:
CD:
Disk 0, Partition 1
Disk 0, Partition 2
Disk 1, Partition 1
PK-0747-96

Configure EISA and RAID devices from the AlphaBIOS console. Figure 5–1 shows
the AlphaBIOS Setup screen, from which you run the configuration utilities. See
Chapter 7 for more information about running utility programs.

SRM Console

5-17

5.5 Testing the System
The test command runs firmware diagnostics for components of the system
drawer. This command is used to test Windows NT systems as well as DIGITAL
UNIX and OpenVMS systems.

Example 5–14 Test Command
P00>>>test
Console is in diagnostic mode
System test, runtime 1200 seconds
Type ^C if you wish to abort testing once it has started
Configuring adapters..
polling ncr0 (NCR 53C810) slot 1, bus 0 PCI, hose 1
SCSI Bus ID 7
dka500.5.0.1.1
DKa500
RRD45 1645
polling floppy0 (FLOPPY) PCEB - XBUS hose 0
dva0.0.0.1000.0
DVA0
RX23
polling ncr1 (NCR 53C810) slot 5, bus 0 PCI, hose 0
SCSI Bus ID 7
dkb0.0.0.5.0
DKb0
RZ29B 0014
dkb400.4.0.5.0
DKb400
RZ29B 0014
polling isp0 (ISP1020) slot 0, bus 2 PCI, hose 2
SCSI Bus ID 7
dkc0.0.0.2000.2
DKc0
RZ29B 0007
dkc100.1.0.2000.2 DKc100
RZ29B 0007
dkc200.2.0.2000.2 DKc200
RZ29B 0007
dkc300.3.0.2000.2 DKc300
RZ29B 0007
polling tulip0 (DECchip 21040-AA) slot 3, bus 0 PCI, hose 0
ewa0.0.0.3.0
08-00-2B-E5-C3-21
Testing Ethernet device(s)
Testing VGA (alphanumeric mode only)
Starting phase 1 background cache/memory tests, affinity to all CPUs..
Starting phase 1 processor/cache thrasher on CPU1..
Starting phase 1 processor/cache thrasher on CPU0..
Testing SCSI disks
Testing floppy drive (dva0, read-only)
ID
Program Device
Pass Hard/Soft
-------- -------- ----------- ---- --------0000197b
memtest memory
3
0
0
000019be
memtest memory
212
0
0
000019ec
memtest memory
142
0
0
00001a26 exer_kid dka500.5.0.1
0
0
0
00001a29 exer_kid dkb0.0.0.5.0
0
0
0
00001a2c exer_kid dkb400.4.0.5
0
0
0
00001a4f exer_kid dkc0.0.0.200
0
0
0
00001a50 exer_kid dkc100.1.0.2
0
0
0
00001a51 exer_kid dkc200.2.0.2
0
0
0
00001a52 exer_kid dkc300.3.0.2
0
0
0
00001a8f exer_kid dva0.0.0.100
0
0
0

Bytes Written
------------325058560
221222528
147831168
0
0
0
0
0
0
0
0

Bytes Read
---------325058560
221222528
147831168
1441792
7061504
7045120
2588672
2588672
2588672
2588672
0

Continued on next page
5-18

System Drawer User’s Guide

Example 5–14 Test Command (Continued)
.
.
.
Shutting down phase 1 background cache/memory tests..
Starting phase 2 background cache/memory tests, affinity to all CPUs..
ID
Program Device
Pass Hard/Soft
-------- -------- ----------- ---- --------000019be
memtest memory
6371
0
0
000019ec
memtest memory
4893
0
0
00001a26 exer_kid dka500.5.0.1
0
0
0
00001a29 exer_kid dkb0.0.0.5.0
0
0
0
00001a2c exer_kid dkb400.4.0.5
0
0
0
00001a4f exer_kid dkc0.0.0.200
0
0
0
00001a50 exer_kid dkc100.1.0.2
0
0
0
00001a51 exer_kid dkc200.2.0.2
0
0
0
00001a52 exer_kid dkc300.3.0.2
0
0
0
00001a8f exer_kid dva0.0.0.100
2
0
0
0000298c
memtest memory
1
0
0
0000298e
memtest memory
1
0
0
00002991
memtest memory
1
0
0
000029cd
memtest memory
1
0
0
000029ec
memtest memory
1
0
0
.
.
.
Testing aborted. Shutting down tests.
Please wait..
System test complete
^C
P00>>>

Bytes Written
------------6678613760
5129007616
0
0
0
0
0
0
0
0
0
0
0
0
0

Bytes Read
---------6678613760
5129007616
48037888
245055488
245039104
91439104
91439104
91439104
91439104
6594560
0
0
0
0
0

The test command runs console-based exercisers for devices in the system drawer.
Testing can be aborted by Ctrl/C.
NOTE: If you are running the Microsoft Windows NT operating system, switch from
AlphaBIOS to the SRM console in order to enter the test command. From
the AlphaBIOS console, press in the Halt button (the LED on the button
lights) and reset the system, or select DIGITAL UNIX (SRM) or OpenVMS
(SRM) from the Advanced CMOS Setup screen and reset the system.
The syntax is:
test [-t time] [-q] [option]
-t time

Specifies the run time in seconds. The default for system test is 1200
seconds (20 minutes).

-q

Disables the display of status messages as exerciser processes are
started and stopped during testing. Sets the environment variable
d_verbose to zero.

option

Either cpun, memn, or pcin, where n is 0, 1, or *. If nothing is
specified, the entire system is tested.
SRM Console

5-19

5.6 Stopping and Starting CPUs
The start, halt, and continue commands are used to stop and start a program on
the specified CPU.

Example 5–15 Start, Halt, and Continue Commands
P00>>> start &p1
P00>>> halt 1
halted CPU 1
CPU 2 is not halted
CPU 3 is not halted
halt code = 1
operator initiated halt
PC = ffffffff8007cc68
P00>>> continue &p1
continuing CPU 1

5-20

System Drawer User’s Guide

start
The start command starts a program that was previously loaded on the processor
specified. If none is specified, the program is started on the primary processor. The
syntax is:
start [&pn] [address]
&pn

Specifies the processor. n is 0 or 1.

address

The starting address of the program.

halt (or stop)
The halt (or stop) command stops program execution on a secondary CPU that is
still running a booted program. The syntax is:
halt (or stop) processor_number
processor_number is the logical CPU number displayed by the show cpu command.

continue
The continue command resumes program execution on the specified processor or on
the primary processor if none is specified. The processor begins executing
instructions at the address that is currently in the program counter (PC). The
processor is not initialized.
The continue command is valid only if you have not disturbed the system state and
if you halted the system by pressing the Halt button on the control panel or, for
OpenVMS systems only, by entering Ctrl/P on the console terminal. The syntax is:
continue [&pn] [address]
&pn

Specifies the processor. n is 0 or 1.

address

The starting address of the program.

NOTE: Some console commands, for example, boot, can alter the machine state so
that program mode cannot be successfully resumed (unless you include -halt
in the boot command). If program mode cannot be resumed, reboot the
operating system.
Other commands that alter machine state are lfu, show device, show
network, test, and start.

SRM Console

5-21

5.7 Updating Firmware
The lfu command is used to update firmware from the SRM console prompt.

Example 5–16 Lfu Command
P00>>> lfu
***** Loadable Firmware Update Utility *****
Select firmware load device (cda0, dva0, ewa0), or
Press <return> to bypass loading and proceed to LFU: cda0
Please enter the name of the options firmware files list, or
Press <return> to use the default filename [AS4X00FW]: AS4X00CP
Copying AS4X00CP from DKA500.5.0.1.1 .
Copying [as4x00]RHREADME from DKA500.5.0.1.1 .
Copying [as4x00]RHSRMROM from DKA500.5.0.1.1 ........................
Copying [as4x00]RHARCROM from DKA500.5.0.1.1 .............
--------------------------------------------------------------------Function
Description
--------------------------------------------------------------------Display
Displays the system’s configuration table.
Exit
Done exit LFU (reset).
List
Lists the device, revision, firmware name, and update
revision.
Lfu
Restarts LFU.
Readme
Lists important release information.
Update
Replaces current firmware with loadable data image.
Verify
Compares loadable and hardware images.
? or Help Scrolls this function table.
--------------------------------------------------------------------UPD> list
Device
Revision
AlphaBIOS
srmflash

Current Revision
V5.12-2
V1.0-9

Filename
arcrom
srmrom

Update
V6.40-1
V2.0-3

UPD> update *
Continued on next page

5-22

System Drawer User’s Guide

Example 5–16 Lfu Command (Continued)
WARNING: updates may take several minutes to complete for each
device.
Confirm update on: AlphaBIOS
AlphaBIOS

DO NOT ABORT!
Updating to V6.40-1... Verifying V6.40-1... PASSED.

Confirm update on: srmflash
srmflash

[Y/(N)] y

DO NOT ABORT!
Updating to V2.0-3... Verifying V2.0-3... PASSED.

UPD> exit

The lfu command starts the Loadable Firmware Update (LFU) Utility. The syntax is:
lfu
NOTE: If the system has been shut down from a booted program (most commonly,
the operating system) or in some other way halted back to the SRM console,
the system must be reset before running LFU.
See Chapter 2 for more information about LFU.

SRM Console

5-23

5.8 Forcing a System Crash Dump
The crash command forces a crash dump to the selected device on DIGITAL
UNIX and OpenVMS systems.

Example 5–17 Crash Command
P00>>> crash
CPU 0 restarting
DUMP: 401408 blocks available for dumping.
DUMP: 38535 required for a partial dump.
DUMP: 0x805001 is the primary swap with 401407, start our
last 38534
: of dump at 362873, going to end (real end is one
more, for header)
DUMP.prom: dev SCSI 1 3 0 4 400 0 0, block 131072
DUMP: Header to 0x805001 at 401407 (0x61fff)
DUMP.prom: dev SCSI 1 3 0 4 400 0 0, block 131072
DUMP: Dump to 0x805001: ..................: End 0x805001
DUMP.prom: dev SCSI 1 3 0 4 400 0 0, block 131072
DUMP: Header to 0x805001 at 401407 (0x61fff)
succeeded
halted CPU 0
halt code = 5
HALT instruction executed
PC = fffffc00004e2d64
P00>>>

The crash command forces a crash dump at the operating system level (DIGITAL
UNIX or OpenVMS). This command is used when an error has caused the system to
hang and can be halted by the Halt button or the RCM halt command. This
command restarts the operating system and forces a crash dump to the selected
device.The syntax is:
crash [device]
device is the name of the device to which the crash dump is written.

5-24

System Drawer User’s Guide

5.9 Using Environment Variables
The set envar and show envar commands are used to set and view environment
variables. The edit command can be used to create a user-defined nonvolatile
environment variable.

Example 5–18 Set envar and Show envar commands
P00>>> show console
console
graphics
P00>>> set console serial
P00>>> show console
console
serial
P00>>>

Environment variables pass configuration information between the console and the
operating system. Their settings determine how the system powers up, boots the
operating system, and operates. Environment variables are set or changed with the
set envar command and set to default values with the set -default envar command.
Their values are viewed with the show envar command. User-defined nonvolatile
environment variables are created with the edit command.

SRM Console

5-25

set envar
The set command sets or modifies the value of an environment variable. It can also
be used to create a new environment variable if the name used is unique. Environ ment variables are used to pass configuration information between the console and
the operating system. The setting of these variables determines how the system
powers up, boots the operating system, and operates. The syntax is:
set [-default] envar value
-default

Restores an environment variable to its default setting.

envar

The name of the environment variable to be modified.

value

The new value of the environment variable.

Whenever you modify the value of any of the following environment variables, the
new value takes effect only after you reset the system by pressing the Reset button or
issuing the initialize command:
console
kbd_hardware_type
language
ocp_text
os_type

show envar
The show envar command displays the current value (or setting) of an environment
variable. The syntax is:
show envar
envar

5-26

The name of the environment variable to be displayed. The wildcard *
displays all environment variables.

System Drawer User’s Guide

Example 5–19 Edit Command
P00>>> edit nvram
editing ‘nvram’
0 bytes read in
*10 set mopv3_boot 1
*exit
17 bytes written out to nvram
P00>>>

The edit command invokes a console editor that behaves much like the line editor
for BASIC. Used to add, insert, or delete lines in a RAM file or the “nvram” powerup script or to create a new environment variable.
In Example 5–19 the nvram script is edited so that an environment variable called
“mop3_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.
The syntax is:
edit file
file is the name of the file to be edited.
The editing commands are:
help

Displays the brief help file.

list

Lists 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 text.

NOTE: It is possible to disable the system by editing the nvram script. For example,
including the command initialize in the script will put the system into an
endless loop.

SRM Console

5-27

5.10 Depositing and Examining Data
The deposit command stores data in a specified location. The examine command
displays the contents of a memory location, a register, or a device.

Example 5–20 Deposit Command
P00>>> dep -b -n 1ff pmem:0 0 # Clear first 512 bytes of
# physical memory.
P00>>> d -l -n 3 vmem:1234 5

# Deposit 5 into four
# longwords starting at
# virtual memory address
# 1234.

P00>>> d -n 8 r0 ffffffff

# Load GPRs R0 through R8
# with -1.

P00>>> d -l -n 10 -s 200 pmem:0 8
# Deposit 8 in the first
# longword of the first 17
# pages in physical memory.
P00>>> d -l pmem:0 0

# Deposit 0 to physical
# memory address 0.

P00>>> d + ff

# Deposit FF to physical
# memory address 4.

P00>>> d scbb 820000

# Deposit 820000 to SCBB.

Example 5–21 Examine Command
P00>>> examine pc
PC psr: 0 (

PC)

P00>>> examine sp
gpr:
F0 (
R30)

# Examine the program
# counter.
0000000000001170
# Examine the stack pointer.
0000000000072A60

P00>>> e -n 6 r4

# Examine register R4 and
# the next six registers.
Continued on next page

5-28

System Drawer User’s Guide

Example 5–21 Examine Command (Continued)
grp: 20 (
grp: 28 (
grp: 30 (
grp: 38 (
grp: 40 (
grp: 48 (
grp: 50 (

R4) 0000000000005000
R5) 000000000FFFE000
R6) 00000003F8000C00
R7) 0000000053F761AE
R8) 0000010000000000
R9) 00000003F7800100
R10) 00000000000C7FFC

P00>>> examine pmem:400EC
# Examine physical memory.
pmem: 400EC A49D0078A47D0070

deposit
The deposit command stores data in the location specified. If no options are given
with a deposit command, the system uses the options from the preceding deposit
command.
If the specified value is too large to fit in the data size listed, the console ignores the
command and issues an error response. If the data is smaller than the data size, the
higher order bits are filled with zeros. The syntax is shown below.
examine
The examine command displays the contents of a memory location, a register, or a
device.
If no options are given with an examine command, the system uses the options from
the preceding examine command. If conflicting address space or data sizes are
specified, the console ignores the command and issues an error.
For data lengths longer than a longword, each longword of data should be separated
by a space.
The syntax for both commands is:
deposit [-{b,w,l,q,o,h}] [-{n value, s value}] [space:] address data
examine [-{b,w,l,q,o,h}] [-{n value, s value}] [space:] address
-b

Defines data size as byte.

-w

Defines data size as word.

-l (default)

Defines data size as longword.

-q

Defines data size as quadword.
Continued on next page
SRM Console

5-29

-o

Defines data size as octaword.

-h

Defines data size as hexword.

-d

Instruction decode (examine command only)

-n value

The number of consecutive locations to modify.

-s value

The address increment size. The default is the data size.

space:

Device name (or address space) of the device to access.

address

Offset within a device to which data is deposited. Can be:

data

dev_name

A device name.

fpr- name

The floating-point register set; name is F0 to F31.

gpr- name

The general register set; name is R0 to R31.

ipr- name

The internal processor registers.

pt- name

The PALtemp register set; name is PT0 to PT23.

pmem

Physical memory (default).

vmem

Virtual memory.

Data to be deposited.

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, 4 for
longword). For other address spaces, the address is the last referenced address
plus 1.

The location immediately preceding the last location referenced in a 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 addressed by the last location referenced in a deposit or examine
command.

5-30

System Drawer User’s Guide

5.11 Reading a File
The more command displays a file one screen at a time.

Example 5–22 More Command
P00>>> more el

#Display the contents of the
#SRM console’s event log one
# screen at a time.

P00>>> help * | more

#Display the contents of online
#help one screen at a time.

The more command is similar to that used in the MS-DOS and UNIX operating
systems. It is useful for displaying output that scrolls too quickly to be viewed. For
example, when you power up the system, the system startup messages scroll, and the
messages are logged to an event log. When the P00>>> prompt displays, you can use
the more command to display the contents of the event log file. The syntax is:
more [file...]
file is the name of the file to be displayed.

SRM Console

5-31

5.12 Initializing the System
The initialize command resets the system and executes the power-up tests.

Example 5–23 Initialize Command
P00>>> initialize
Initializing…
SROM V2.0 on cpu0
SROM V2.0 on cpu1
XSROM V3.0 on cpu1
XSROM V3.0 on cpu0
BCache testing complete on cpu1
BCache testing complete on cpu0
mem_pair0 - 128 MB
20..20..21..21..23..
please wait 3 seconds for T24 to complete
24..24..
Memory testing complete on cpu1
Memory testing complete on cpu0
starting console on CPU 0
sizing memory
0
128 MB SYNC
starting console on CPU 1
probing IOD1 hose 1
bus 0 slot 1 - NCR 53C810
probing IOD0 hose 0
bus 0 slot 1 - PCEB
probing EISA Bridge, bus 1
bus 0 slot 2 - S3 Trio64/Trio32
bus 0 slot 3 - DECchip 21040-AA
bus 0 slot 5 - NCR 53C810
probing IOD3 hose 3
probing IOD2 hose 2
bus 0 slot 2 - PCI-PCI Bridge
probing PCI-PCI Bridge, bus 2
bus 2 slot 0 - ISP1020
configuring I/O adapters...
ncr0, hose 1, bus 0, slot 1
floppy0, hose 0, bus 1, slot 0
tulip0, hose 0, bus 0, slot 3
ncr1, hose 0, bus 0, slot 5
isp0, hose 2, bus 2, slot 0
System temperature is 23 degrees C
AlphaServer 4000 Console V3.0-10, 19-NOV-1996 13:57:07
P00>>>
5-32

System Drawer User’s Guide

The initialize command resets the system. Issuing this command is equivalent to
pressing the Reset button. The syntax is:
initialize
After self-tests are executed, the system autoboots unless one of the following is
true:
•

The Halt button on the control panel is pushed in.

•

The auto_action environment variable is set to halt.

If the auto_action environment variable is set to boot or restart and the Halt button
is not pushed in, the system autoboots. In all other cases, the system stops in console
mode and does not attempt to boot.

SRM Console

5-33

5.13 Finding Help
The help (or man) command displays basic information about a command.

Example 5–24 Help (or Man) Command
P00>>> help set
# or man set
NAME
set
FUNCTION
Set an option or modify the value of an environment
variable.
SYNOPSIS
set <option> <value> or <envar> [-] <value>
where
<option>={host,mode}
where
<envar>={auto_action,bootdef_dev,boot_osflags,...}
[-default]

The help (or man) command displays basic information about the use of console
commands when the system is in console mode. The syntax is:
help (or man) [command . . . ]
command . . .

5-34

Command or topic for which help is requested. The options are:
none

Displays the complete list of commands
for which you can receive help.

command_name

Displays information about the console
command.

argument_string
(such as “sh”)

Displays information about all commands
that begin with that string.

System Drawer User’s Guide

5.14 Command Summary
The SRM (Alpha System Reference Manual) console is a command line interface
used when the operating system is either DIGITAL UNIX or OpenVMS.
Console commands enable the user to examine and modify the system state.

The commands listed in Table 5–3 are described in the previous sections.
Table 5–4 lists command syntax, and Table 5–5 shows special characters.

Table 5–3 Summary of SRM Console Commands
Command

Function

alphabios

Loads and starts the AlphaBIOS console.

boot

Loads and starts the operating system.

clear envar

Resets an environment variable to its default value.

continue

Resumes program execution.

crash

Forces a crash dump at the operating system level.

deposit

Writes data to the specified address.

edit

Invokes the console line editor on a RAM file or on the nvram file
(power-up script).

examine

Displays the contents of a memory location, register, or device.

halt

Halts the specified processor. (Same as stop.)

help

Displays information about the specified console command.

initialize

Resets the system.

lfu

Runs the Loadable Firmware Update Utility.

man

Displays information about the specified console command.

Displays a file one screen at a time.

prcache

Utility that initializes and displays status of the PCI NVRAM.
Continued on next page

SRM Console

5-35

Table 5–3 Summary of SRM Console Commands (Continued)
Command

Function

set envar

Sets or modifies the value of an environment variable.

set host

Connects to a MSCP DUP server on a DSSI device.

show envar

Displays the state of the specified environment variable.

show config

Displays the configuration at the last system initialization.

show cpu

Displays the state of each processor in the system.

show device

Displays a list of controllers and their devices in the system.

show fru

Displays the serial number and revision level of system bus
options.

show memory

Displays memory module information.

show network

Displays the state of network devices in the system.

show pal

Displays the version of the privileged architecture library code
(PALcode).

show power

Displays information about the power supplies, system fans, CPU
fans, and temperature.

show version

Displays the version of the console program.

start

Starts a program that was previously loaded on the processor
specified

stop

Halts the specified processor. (Same as halt.)

test

Runs firmware diagnostics for the system.

5-36

System Drawer User’s Guide

Table 5–4 Syntax for SRM Console Commands
Parameter

Attribute or Action

Length

Up to 255 characters, not including the terminating carriage return
or any characters deleted as the command is entered. A command
longer than 80 characters and without the backslash character (see
Table 5–5) causes display of an error message.

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 in console commands are in decimal notation. Two
exceptions, both of which use hexadecimal notation, are addresses
and numbers used in the deposit command. The default radix can
be overridden by inserting %d before numbers you want to express
in decimal, %b before binary, %o before octal, or %x before
hexadecimal. Register names (for example, R0) are not considered
numbers and use decimal notation.

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 console supports
command line recall and editing.

Spaces or tabs

Multiple adjacent spaces and tabs are compressed and treated as a
single space. The console program ignores leading and trailing
spaces.

SRM Console

5-37

Table 5–5 Special Characters for SRM Console
Character

Function

Return or Enter

Terminates a command line. No action is taken on a
command until it is terminated. If no characters are entered
and this key is pressed, the console just redisplays the
prompt.

Backslash (\)

Continues a command on the next line. Must be the last
character on the line to be continued.

Delete

Deletes the previous character.

Help

By itself, displays first-level help. When pressed after part of
a command, displays options available.

Ctrl/A or F14

Toggles between insert and overstrike modes. The default is
overstrike.

Ctrl/B or up-arrow

Recalls previous command or commands. The last 16
commands are stored in the recall buffer.

Ctrl/C or Ctrl/P

Terminates the process that is running. 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.

Ctrl/D or left-arrow

Moves the cursor left one position.

Ctrl/E

Moves the cursor to the end of the line.

Ctrl/F or right-arrow

Moves the cursor right one position.

Ctrl/H or Backspace
or F12

Moves the cursor to the beginning of the line.

Ctrl/J

Deletes the previous word.

Ctrl/O

Stops output to the console terminal for the current
command. Toggles between enable and 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.

Ctrl/Q

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

5-38

System Drawer User’s Guide

Table 5–5 Special Characters for SRM Console (Continued)
Character

Function

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 commands such as show.

Double quotes enable you to denote a string for environment
variable assignment.

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 Console

5-39

5.15 Environment Variable Summary
Environment variables pass configuration information between the console and
the operating system. Their settings determine how the system powers up, boots
the operating system, and operates. Environment variables are set or changed
with the set envar command and returned to their default values with the clear
envar command. Their values are viewed with the show envar command.

Table 5–6 Environment Variable Summary
Environment
Variable

Function

auto_action

Specifies the console’s action at power-up, a failure, or a
reset.

boot_osflags

Specifies the default operating system boot flags.

bootdef_dev

Specifies the default boot device string.

com*_baud

Changes the default baud rate of the COM 1 or the COM2
serial port.

console

Specifies the device on which power-up output is displayed
(serial terminal or graphics monitor).

cpu_enabled

Enables or disables a specific secondary CPU.

ew*0_mode

Specifies the connection type of the default Ethernet
controller.

ew*0_protocols

Specifies network protocols for booting over the Ethernet
controller.

kbd_hardware_
type

Specifies the default console keyboard type.

kzpsa*_host_id

Specifies the default value for the KZPSA host SCSI bus
node ID.

language

Specifies the console keyboard layout.
Continued on next page

5-40

System Drawer User’s Guide

Table 5–6 Environment Variable Summary (Continued)
Environment
Variable

Function

memory_test

Specifies the extent to which memory will be tested. For
DIGITAL UNIX systems only.

ocp_text

Overrides the default OCP display text with specified text.

os_type

Specifies the operating system and sets the appropriate
console interface.

pci_parity

Disables or enables parity checking on the PCI bus.

pk*0_fast

Enables fast SCSI mode.

pk*0_host_id

Specifies the default value for a controller host bus node ID.

pk*0_soft_term

Enables or disables SCSI terminators on systems that use the
QLogic ISP1020 SCSI controller.

tga_sync_green

Specifies the location of the SYNC signal generated by the
DIGITAL ZLXp-E PCI graphics accelerator option.

tt_allow_login

Enables or disables login to the SRM console firmware on
other console ports.

These environment variables are described in the following pages.
NOTE: These environment variables are specific to the SRM console.

SRM Console

5-41

auto_action
Specifies the action the console takes any time the system powers up, fails, or resets.
When the setting involves autobooting, the system boots from the default boot
device specified by the value of the bootdef_dev environment variable. The syntax
is:
set auto_action value
The options for value are:
halt

The system remains in console mode after power-up or a system crash.

boot

The system boots automatically when it is turned on and halts after a
system failure.

restart

The system boots automatically when it is turned on or after it fails.

bootdef_dev
The bootdef_dev environment variable specifies one or more devices for booting the
operating system. When more than one device is listed, the system searches in the
order listed and boots from the first device with operating system software. The
syntax is:
set bootdef_dev boot_device
boot_device

5-42

The name of the device on which the system software has been
loaded. To specify more than one device, separate the names with
commas. Enter the command show bootdef_dev to display the
current default boot device. Enter the command show device for a
list of all devices in the system.

System Drawer User’s Guide

boot_osflags
The boot_osflags environment variable passes information to the boot command.
That information is dependent on the operating system to be booted.
When the operating system is DIGITAL UNIX, the syntax is:
set boot_osflags flags_value
The options for flags_value are:
a

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

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

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

Full dump; implies “s” as well. By default, if DIGITAL UNIX crashes, it
completes a partial memory dump. Specifying “D” forces a full dump if the
system crashes.

When the operating system is OpenVMS, the syntax is:
set boot_osflags root_number,boot_flags
root_number

boot_flags

Directory number of the system disk on which OpenVMS files are
located. For example:
root_number

Root Directory

0 (default)

[SYS0.SYSEXE]

[SYS1.SYSEXE]

[SYS2.SYSEXE]

[SYS3.SYSEXE]

The hexadecimal value of the bit number or numbers set. To specify
multiple boot flags, add the flag values (logical OR). See Table 5–7.

SRM Console

5-43

Table 5–7 Settings for boot_osflags Bootflags (OpenVMS)
Flags_Value

Bit Number

Meaning

Bootstrap conversationally (enables you to modify
SYSGEN parameters in SYSBOOT).

Map XDELTA to running system.

Stop at initial system breakpoint.

Perform diagnostic bootstrap.

Stop at the bootstrap breakpoints.

Omit header from secondary bootstrap image.

Prompt for the name of the secondary bootstrap
file.

100

Halt before secondary bootstrap.

10000

Display debug messages during booting.

20000

Display user messages during booting.

com*_baud
The default baud rate for the AlphaServer 4000 system is 9600. With the
com*_baud environment variable, you can set the baud rate to match that of the
device connected to the port.
Resetting the baud rate of the COM1 port bypasses the RCM (see Section 2.10). You
will be asked to confirm the change, as shown here:
P00>>> set com1_baud 19200
Embedded Remote Console only supports 9600 baud. Continue?
(Y/[N]) n
bad value - com1_baud not modified
P00>>>
The syntax is:
set com*_baud baud_value
baud_value

5-44

The new baud rate. A list of possible values is displayed by attempting
to set this environment variable to an unacceptable value (for
example, set com2_baud xxx).

System Drawer User’s Guide

console
The console terminal can be either a graphics monitor or a serial terminal. The
console environment variable specifies which is used. The syntax is:
set console output_device
The options for output_device are:
graphics
(default)

The console terminal is a graphics monitor or a device connected to the
VGA or TGA module.

serial

The console terminal is the device connected to the COM1 port.

Whenever you change the value of console, you must reset the system by pressing
the Reset button or issuing the initialize command.

cpu_enabled
Sets a bit mask that enables or disables specific CPUs on a multiprocessor system.
Disabled CPUs are prevented from running the console or the operating system. Bit
0 of the mask corresponds to CPU 0, bit 1 to CPU 1, and so on. A zero in the bit
mask prevents the corresponding CPU from running; a one allows it to run. The bit
mask is expressed as a hexadecimal value.
NOTE: The primary CPU cannot be disabled.
The syntax is:
set cpu_enabled hex_digit
The options for hex_digit are 0 – F (hexadecimal).

SRM Console

5-45

ew*0_mode
Sets an Ethernet controller to run an AUI, ThinWire, or twisted-pair Ethernet
network. The default is auto-sense. For the Fast setting, the device defaults to Fast.
The syntax is:
set ew*0_mode value
The options for value are:
aui

Device type is AUI.

auto-sense

Device type is sensed by the console.

bnc

Device type is ThinWire.

fast

Device type is fast 100BaseT.

fastfd

Device type is fast full duplex 100BaseT.

full

Device type is full duplex twisted pair.

twisted-pair

Device type is 10BaseT (twisted pair).

ew*0_protocols
Enables network prococols for booting and other functions. The syntax is:
set ew*0_protocols protocol_value
The options for protocol_value are:
mop (default)

Sets the network protocol to mop (Maintenance Operations
Protocol), the setting typically used with the OpenVMS operating
system.

bootp

Sets the network protocol to bootp, the setting typically used with
the DIGITAL UNIX operating system.

bootp,mop

When both are listed, the system attempts to use the mop protocol
first, regardless of which is listed first. If not successful, it then
attempts the bootp protocol.

5-46

System Drawer User’s Guide

kbd_hardware_type
Used only on systems with the language variant 3C (Français), this environment
variable sets the keyboard hardware type as either PCXAL or LK411 and enables the
system to interpret the terminal keyboard layout correctly.
Whenever you change the value of kbd_hardware_type, you must reset the system
by pressing the Reset button or issuing the initialize command.
The syntax is:
set kbd_hardware_type keyboard_type
The options for keyboard_type are:
pcxal (default)

Selects the default keyboard hardware type.

lk411

Selects the LK411 keyboard layout for use with language variant
3C (Français).

kzpsa*_host_id
See pk*0_host_id.

language
Specifies the keyboard layout, which is language dependent. The setting of the
language environment variable must match the language of the keyboard variant.
Whenever you change the value of language, you must reset the system by pressing
the Reset button or issuing the initialize command.
The syntax is:
set language language_code
The options for language_code are:
0
30
32
34
36
38
3A
3C
3E

No language (cryptic)
Dansk (Danish)
Deutsch (German)
Deutsch (Schweiz) (Swiss)
English (American)
English (British/Irish)
Español (Spanish)
Français (French)
Français (Canadian)

40
42
44
46
48
4A
4C
4E

Français (Suisse Romande)
Italiano (Italian)
Nederlands (Netherlands)
Norsk (Norwegian)
Portuguese (Portuguese)
Suomi (Finnish)
Svenska (Swedish)
Belgisch-Nederlands (Dutch)

SRM Console

5-47

memory_test
Determines the extent of memory testing on the next reset. The syntax is:
set memory_test value
The options for value are:
full (default)

Specifies that the full memory test will be run. Systems using the
OpenVMS operating system must run the full memory test.

partial

Specifies that the first 256 MB of memory will be tested.

none

Specifies that memory will not be tested. (However, tests are always
run on the first 32 MB.)

ocp_text
Specifies a message to display on the control panel after self-tests and diagnostics
have completed.
The value of ocp_text takes effect only after you reset the system by pressing the
Reset button or issuing the initialize command.
The syntax is:
set ocp_text message
The variable message can be up to 16 characters and must be enclosed in quotation
marks.

5-48

System Drawer User’s Guide

os_type
The os_type environment variable specifies the default operating system. This
variable is set at the factory to the setting for the operating system purchased. Use
this command to change the factory default setting.
Whenever you change the value of os_type, you must reset the system by pressing
the Reset button or issuing the initialize command.
The syntax is:
set os_type os_type
The options for os_type are:
unix

DIGITAL UNIX is the default operating system, and the SRM firmware
is started during power-up or reset.

openvms

OpenVMS is the default operating system, and the SRM firmware is
started during power-up or reset.

Windows NT is the default operating system. The SRM firmware is
started, and it loads and starts the AlphaBIOS firmware during powerup or reset. (If the Halt button is pushed in so that the LED on the
button lights, this environment variable is overridden, and the SRM
firmware does not load and start the AlphaBIOS console.)

pci_parity
Disables or enables parity checking on the PCI bus.
Some PCI devices do not implement PCI parity checking, and some have a paritygenerating scheme in which the parity is sometimes incorrect or is not fully
compliant with the PCI specification. A side effect of this aberrant behavior is that
superfluous PCI parity errors are reported by the host PCI bridge. In such cases, the
device can be used as long as parity is not checked; disabling PCI parity checking
prevents false parity errors that can cause system problems.
The syntax is:
set pci_parity value
The options for value are:
on (default)

Enables PCI parity checking.

off

Disables PCI parity checking.

SRM Console

5-49

pk*0_fast
Enables Fast SCSI to perform in either standard or fast mode. If the system has at
least one Fast SCSI device, set the default controller speed to Fast SCSI (1). Devices
on a controller that connects to both standard and Fast SCSI devices will perform at
the appropriate rate for the device. If the system has no Fast SCSI devices, set the
default controller speed to standard SCSI (0). If a Fast SCSI device is on a controller
set to standard, it will perform in standard mode.
The syntax is:
set pk*0_fast scsi_speed
The options for scsi_speed are:
0

The controller is in standard SCSI mode.

1 (default)

The controller is in Fast SCSI mode.

pk*0_host_id
Sets the controller host bus node ID to a value between 0 and 7.
Each SCSI bus in the system requires a controller. Buses can theoretically support up
to eight devices; however, the eighth device must always be a controller. Each
device on the bus, including the controller, must have a unique ID, which is a
number between 0 and 7. This is the bus node ID number.
On each bus, the default bus node ID for the controller is set to 7. You do not need to
change the controller bus node ID unless you place two or more controllers on the
same bus.
To list the controllers on your system, enter the command show device. SCSI
devices begin with the letters “pk” (for example, pka0). The third letter is the adapter
ID for the controller. When entering the command set pk*0_host_id, replace the
asterisk with the adapter ID letter.
The syntax is:
set pk*_host_id scsi_node_id
The value for scsi_node_id is the bus node ID, a number from 0 to 7.

5-50

System Drawer User’s Guide

pk*0_soft_term
Enables or disables SCSI terminators. This command applies to systems that use the
QLogic ISP1020 SCSI controller.
The QLogic ISP1020 SCSI controller implements the 16-bit wide SCSI bus. The
QLogic module has two terminators, one for the low eight bits and one for the high
eight bits.
The syntax is:
set pk*0_soft_term value
The options for value are:
off

Disables termination of all 16 bits.

low (default)

Enables low eight bits and disables high eight bits.

high

Enables high eight bits and disables low eight bits.

Enables all 16 bits.

diff

Places the bus in differential mode.

tga_sync_green
Sets the location of the SYNC signal generated by the optional ZLXp-E PCI graphics
accelerator (PBXGA). The parameter is a bit mask, where the least significant bit
sets the vertical SYNC for the first graphics card found, the second for the second
found, and so on.
The default for this environment variable is ff. The default must be reset to 00 so the
graphics monitor on a system with a ZLXp-E PCI graphics accelerator will
synchronize.
The syntax is:
set tga_sync_green value
The options for value are:
ff (default)

Synchronizes the graphics monitor on systems that do not use a
ZLXp-E PCI graphics accelerator.

Synchronizes the graphics monitor on systems with a ZLXp-E PCI
graphics accelerator.

SRM Console

5-51

tt_allow_login
Enables or disables login to the SRM console firmware on alternate console ports. If
the environment variable console is set to serial, the primary console device is the
terminal connected through the COM1 port. The command set tt_allow_login 1
enables logins through either the COM2 port or a graphics monitor.
The syntax is:
set tt_allow_login value
The options for value are:
0

Disables login through the COM2 port or a graphics monitor.

1 (default)

Enables login through the COM2 port or a graphics monitor

5-52

System Drawer User’s Guide

Chapter 6
AlphaBIOS Console
AlphaBIOS is the graphical interface that supports the Microsoft Windows NT
operating system and some utility programs. This chapter explains how to perform
common system management tasks with AlphaBIOS, and it provides a reference for
the AlphaBIOS screens.
Sections in this chapter are:
•

Switching from AlphaBIOS to SRM Console

•

Starting AlphaBIOS

•

Keyboard Conventions and Help

•

Displaying the System Configuration

•

Updating Firmware

•

Setting up the Hard Disk

•

Performing Setup Tasks

•

Installing Windows NT

•

Running Utility Programs

•

Selecting the Version of Windows NT

NOTE: To run firmware tests on a Windows NT system, switch to the SRM console
and issue the test command.

AlphaBIOS Console

6-1

6.1 Switching from AlphaBIOS to SRM Console
It is necessary to switch to the SRM console to boot DIGITAL UNIX or
OpenVMS or to run firmware-based diagnostics. To switch from AlphaBIOS to
the SRM console, press the Halt button on the control panel (the LED lights)
and reset the system, or select DIGITAL UNIX (SRM) or OpenVMS (SRM)
from the Advanced CMOS Setup screen and reset the system.

Figure 6–1 Switching to the SRM Console
Advanced CMOS Setup

PCI Parity Checking:

Disabled

Power-up Memory Test:

Enabled

AlphaBIOS Password Option:
Console Selection:

F1=Help

Disabled

Digital UNIX Console (SRM)

Console (AlphaBIOS)
Power-up Memory Test Windows
Length: NTFull
OpenVMS Console (SRM)
Digital UNIX Console (SRM)

Press
or
to select the firmware console that will be presented
the next time the system is power-cycled.

ESC=Discard Changes

F10=Save Changes
PK-0750B-96

6-2

System Drawer User’s Guide

DIGITAL UNIX and OpenVMS are booted and firmware-based diagnostics are run
from the SRM console. Follow this procedure to switch from AlphaBIOS to SRM:
1.

Select CMOS Setup and press Enter.

In the CMOS Setup screen press F6. The Advanced CMOS Setup screen
displays.

Select DIGITAL UNIX (SRM) or OpenVMS (SRM) and press F10.

The CMOS Setup screen displays. Press F10 to save the change.

Run the EISA Configuration Utility, using the ECU diskette for DIGITAL
UNIX and OpenVMS. See Chapter 7.
NOTE: ECU must be run before booting DIGITAL UNIX or OpenVMS.

Reset the system.

Alternatively, you can press the Halt button (the LED on the button lights) and reset
the system.
The method you choose depends on how you want the system to function on
subsequent resets:
•

If you make the selection in the Advanced CMOS Setup screen, the system will
continue to stop in the SRM console whenever it is powered-up, reset, or
initialized until the Windows NT operating system is again specified.

•

If you press the Halt button and reset, no system setup information is changed,
and AlphaBIOS will start the next time the system is powered-up, reset, or
initialized with the Halt button out (the LED is off).

To return to the AlphaBIOS console, issue the command alphabios at the SRM
console prompt.

AlphaBIOS Console

6-3

6.2 Starting AlphaBIOS
Start AlphaBIOS Setup by pressing F2 from the Boot screen displayed at powerup or reset.

Figure 6–2 Boot Screen
AlphaBIOS 5.29
Please select the operating system to start:
Windows NT Server 3.51

Use
and
to move the highlight to your choice.
Press Enter to choose.

AlphaServer 4000
Family

Press <F2> to enter SETUP
PK-0728B-96

6-4

System Drawer User’s Guide

The Boot screen shown in Figure 6–2 displays at power-up and reset. Press F2 at this
screen to enter the setup program.
The AlphaBIOS Setup screen (Figure 6–3) displays. From this screen you can select
the tasks to perform. Use the arrow keys to select the menu item you want and press
Enter. (Refer to Section 6.3 for information on navigating through the AlphaBIOS
screens.)

Figure 6–3 AlphaBIOS Setup Screen
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup...
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

Press ENTER to partition or format hard disks.

ESC=Exit
PK-0726-96

AlphaBIOS Console

6-5

6.3 Keyboard Conventions and Help
AlphaBIOS uses universally accepted keys and key combinations for navigating
the interface and selecting items.

Figure 6–4 Typical First-Level Help Screen
Help: CMOS Setup

F1=Key Help

Change color scheme.

Enter Advanced CMOS Setup.

Set factory default CMOS settings.

ESC

Exit CMOS Setup and discard any changes.

F10

Exit CMOS Setup and save changes,
including changes from Advanced CMOS Setup.

ENTER=Continue
PK-0724-96

AlphaBIOS uses DOS and Windows keyboard conventions for navigating the
interface and selecting items. The valid keystrokes are listed in the keyboard help
screens.
Two levels of keyboard help are available. The first level, reached by pressing F1
once, shows explanations of the keystrokes available for the specific part of
AlphaBIOS currently displayed. An example of the help displayed by pressing F1
once, in this case from the CMOS Setup screen, is shown in Figure 6–4.
The second level of keyboard help, reached by pressing F1 from the first help screen,
shows explanations of the keystrokes available for navigating the interface
throughout AlphaBIOS (see Figure 6–5).

6-6

System Drawer User’s Guide

Figure 6–5 Second-Level Help Screen
AlphaBIOS Setup

F1=Help

Help: Action Keys
TAB

Move highlight forward between fields of a dialog.

SHIFT+TAB

Move highlight backward between fields of a dialog.
Move highlight within a menu, or cycle through available field
values in a dialog window.

ALT+

Drop down a menu of choices from a drop-down listbox.
drop-down listbox can be recognized by the
symbol.

HOME

Move to the beginning of a text entry field.

END

Move to the end of a test entry field.

Move to the left or right in a text entry field.
ESC

Discard changes and/or backup to previous screen.

ENTER=Continue

PK-0725-96

AlphaBIOS Console

6-7

6.4 Displaying the System Configuration
The Display System Configuration screen provides information about the
system’s installed processor, memory, attached devices, and option boards.
From the AlphaBIOS Setup screen select Display System Configuration..., then
the category for the requisite information.

Figure 6–6 Display System Configuration Screen
Display System Configuration

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
EISA Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration

System Type:
Processor:
Speed:
Cache:
Memory:

AlphaServer 4000 5/400

Digital Alpha 21164, Revision 7.1 (2 Processors)
400 MHz
4 MB
512 MB

Floppy Drive A:
Floppy Drive B:
Keyboard:

3.5" 1.44 MB
None
U.S. 101-key keyboard

AlphaBIOS Version:
SRM Version:

5.29 970226.1006
V4.8-5, 11-FEB-1997 16:52:39

ESC=Exit
PK-0731C-96

6-8

System Drawer User’s Guide

Use this procedure to display the system configuration.
1.
2.

Start AlphaBIOS, select Display System Configuration, and press Enter.
In the Display System Configuration screen, use the arrow keys to select the
configuration category you want to see.

From this screen, you can view configuration information about these system
components:
•

System motherboard

•

Hard disk

•

PCI bus

•

EISA bus

•

SCSI devices

•

System bus

•

Memory

•

Integrated peripherals

The sections that follow explain the display for each component.

AlphaBIOS Console

6-9

6.4.1 System Board Configuration
Figure 6–7 System Board Configuration
Display System Configuration

F1=Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
EISA Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration

System Type:

AlphaServer 4000 5/400

2 Processor:
3
Speed:
4
Cache:
5
Memory:

Digital Alpha 21164, Revision 7.1
400 MHz
4 MB
512 MB
Floppy Drive A: 3.5" 1.44 MB
Floppy Drive B: None
Keyboard: U.S. 101-key keyboard

6 AlphaBIOS Version:

SRM Version:

(2 Processors)

5.29 970226.1006
V4.8-5, 11-FEB-1997 16:52:39

ESC=Exit
PK-0738C-96

6-10

System Drawer User’s Guide

² System type — The model number of the system.
³ Processor — The model and revision of the processor chip. Revision level

information can be useful in troubleshooting problems with technical support
personnel.

´ Speed — The speed at which the processor runs.
µ Memory — The amount, in megabytes, of main memory in the system.
¶ Cache — The amount, in kilobytes, of static RAM cache memory installed.
· Firmware versions — The versions of AlphaBIOS and SRM currently running
on the system.

AlphaBIOS Console

6-11

6.4.2 Hard Disk Configuration
Figure 6–8 Hard Disk Configuration
Display System Configuration

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
NC Bus Configuration
Memory Configuration
Integrated Peripherals
1

Disk

Partition 1
6
Partition 2
Unused
Disk

NCRC810 #0, SCSI ID 3

NCRC810 #0, SCSI ID 5
DEC
RZ26
(C) DECT386
Partition 1
Partition 2

510 MB
7

200 MB
200 MB
110 MB

NTFS
FAT

1001 MB
995 MB
6 MB

NTFS
FAT
PK-0739A-96

6-12

System Drawer User’s Guide

NOTE: This screen is for information only; it cannot be edited. To make changes to
the hard disk setup, use the Hard Disk Setup screen (Section 6.6).

² Physical disk ID — Based on the SCSI ID. The disk with the lowest SCSI ID is
disk 0, the disk with the next lowest SCSI ID is disk 1, and so on.

³ Controller — The brand and model of SCSI chip used on the SCSI controller.
´ Controller number — Based on how many SCSI controllers of a particular type
are installed in the system. The first controller of a type is always numbered 0.

µ SCSI ID number — A unique number you assign to each SCSI device installed
in the system. This is usually done with jumpers or a thumb wheel attached to
the drive housing.

¶ Size — The raw capacity of the drive. Formatting the drive with different file

systems (for example, FAT and NTFS) may result in different usable sizes
because of the differences in how storage is managed under those file systems.

· Partition number — Within a single drive, partition numbers are assigned in

sequential order: 1, 2, 3, and so on. The partitions populate the drive from the
innermost cylinders to the outermost cylinders. If you have a large hard disk
(over 800 MB) and plan to use the FAT file system, it is a good idea to break the
disk into several smaller partitions because the FAT file system uses disk space
more efficiently at smaller partition sizes. This is not a concern for the NTFS
file system, however, as it uses disk space very efficiently at all partition sizes.

¸ Partition size — The raw (unformatted) storage capacity of the partition. Actual
storage space will differ based on the file system with which the partition is
formatted.

¹ Partition format — The file system (if any) used on a partition. This field
displays FAT, NTFS, or unknown (if the partition is unformatted).

AlphaBIOS Console

6-13

6.4.3 PCI Configuration
Figure 6–9 PCI Configuration
Display System Configuration

F1=Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
EISA Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration
1

Device Name

Device Type

Revision

Physical Slot

5
0
32
2
2
0
0
2
2
0
0

PCI0-Embedded
PCI0-2
PCI0-3
PCI0-5
PCI1-Embedded
PCI1-2
PCI1-3
PCI1-4
PCI1-4-Bridged
PCI2-2
PCI2-3

Intel 82375 PCEB
EISA bridge
S3 Trio32/64
VGA
DIGITAL 21140
Ethernet
NCRC810
SCSI
NCRC810
SCSI
DIGITAL KZPSX
SCSI
DIGITAL KZPSX
SCSI
DIGITAL 21050
PCI bridge
QLogic ISP1020/1040 SCSI
DIGITAL KZPSX
SCSI
DIGITAL KZPSX
SCSI
ENTER=Select

ESC=Exit
PK-0740C-97

6-14

System Drawer User’s Guide

² Device name — The name and model of the device as recorded in the device’s
firmware.

³ Device type — Lists the function of the device in the system.
´ Revision — The revision level of the device signifies the number of times it has
been updated by the manufacturer.

µ Physical slot — Lists the actual PCI slot number to which the device is attached.
You can find additional detail about any of the PCI devices listed in the Advanced
PCI Information screen. Follow this procedure to view this screen:
1.

Press Enter to enable selection in the device list.

Use the arrow keys to select the device for which you want additional detail.

Press Enter, and the detail is displayed.

Press Escape to return to the table of PCI devices.

The Advanced PCI Information screen is shown in Figure 6–10 on the next page.

AlphaBIOS Console

6-15

Figure 6–10 Advanced PCI Information
Advanced PCI Information
2

Bus Number=0, Device Number=7, Function Number=0
4

Configuration Space:
Register Name

Hex Offset

Vendor ID
Device ID
Command
Status
Revision ID
Prog. I/F
Sub Class Code
Class Code
Cache Line Size
Latency Timer
Header Type
BIST
Base Address 0

00
02
04
06
08
09
0A
0B
0C
0D
0E
0F
10

Hex

Value

8086
0482
0047
0200
05
00
00
00
00
20
00
00
00000000

ENTER=Continue
PK-0741A-96

² Bus number — The virtual PCI bus number.
³ Device number — The PCI bus device number.
´ Function number — Represents the number assigned to a particular function on
a multifunction device. For example, a combination Ethernet/SCSI controller
would be listed twice, with the first function listed as 0 and the other as 1.

µ Configuration header space — Displays the information in the selected device’s
PCI configuration space.

6-16

System Drawer User’s Guide

6.4.4 EISA Configuration
Figure 6–11 EISA Configuration
Display System configuration

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration
Integrated Peripherals
1

Device Name

Device Type

Physical Slot

DEC 5301
FLOPPY

Other
DISK

Embedded
Embedded

ENTER=Select

ESC=Exit
PK-0742A-96

² Device name — Includes a three-character manufacturer code, followed by a
three-digit board type, followed by a one-digit revision number.

³ Device type — Identifies the board type (for example, network).
´ Physical slot — Lists the actual EISA slot number to which the device is

attached. The embedded EISA system controller is always first on this list.

AlphaBIOS Console

6-17

6.4.5 SCSI Configuration
Figure 6–12 SCSI Configuration
Display System Configuration

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration
Integrated Peripherals

QLISP1020 #0
KZPSX #0

QLISP1020 #0, SCSI ID 7, SCSI Bus 0
2

SCSI ID

Device

Size

Description

0
1
5

Disk 0
Disk 1
CD-ROM

2047 MB
2049 MB

SEAGATE
SEAGATE
DEC

ST32550W
0021
ST32551W
0526
RRD45 (C) DEC1645
PK-0743A-96

6-18

System Drawer User’s Guide

² SCSI controller information — Describes the physical characteristics of the
selected SCSI controller. This line includes:

Controller — Brand and model of SCSI chip used on the SCSI controller.
Controller number — Based on the number of SCSI controllers of a particular
type in the system. The first controller of a type is always numbered 0.
SCSI ID number — A unique number assigned to the SCSI controller. The
standard controller numbering scheme is for controllers to be SCSI ID 7.
SCSI bus number — Indicates if the controller is first or second in the system.
The first controller is tied to SCSI bus 0, and the second to SCSI bus 1.

³ SCSI ID — A unique number you assign to each SCSI device in the system.
This is usually done with jumpers or a thumb wheel attached to the drive
housing.

´ Device type — Displays whether the device is a hard disk, CD-ROM, scanner ,
or other type of device.

µ Size — The raw capacity of the drive. Formatting the drive with different file

systems (for example, FAT and NTFS) may result in different usable sizes
because of differences in the way those file systems manage storage. This is left
blank if it is not applicable to a device (for example, a scanner).

¶ Description — The name and model of the device as recorded in the device’s
firmware.

AlphaBIOS Console

6-19

6.4.6 System Bus Configuration
Figure 6–13 System Bus Configuration
Display System Configuration

F1=Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration

McBus Module Name

Module Type

Revision

Physical Slot

1
2
3
4
5
6
7

0
3
3
6008
6000
6001
6001

0000
0002
0002
0031
0031
0032
0032

MEM
CPU0
CPU1
IOD0/1
IOD0/1
IOD2/3
IOD2/3

Memory
CPU (EV56 Cached)
CPU (EV56 Cached)
MCBus-PCI Bridge
MCBus-PCI Bridge
MCBus-PCI Bridge
MCBus-PCI Bridge

ESC=Exit
PK-0744C-97

² MC bus number — Identifies the location of a component on the system bus.
³ Module name — The DIGITAL internal identifier for a system component.
´ Module type — Identifies the function of the system component.
µ Revision — A DIGITAL internal number representing the manufacturing
revision level of the system component.

¶ Physical slot — Represents the actual location of the s ystem component on the
bus. Refer to Chapter 1 for more information about the system bus and module
placement.

6-20

System Drawer User’s Guide

6.4.7 Memory Configuration
Figure 6–14 Memory Configuration
Display System Configuration

F1=Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration
Integrated Peripherals

System Memory Configuration

Bank 0: 512 MB (128 MB Per DIMM) -- Starting Address = 0X00000000
Bank 1: 64 MB (16 MB Per DIMM) -- Starting Address = 0X10000000

ESC=Exit
PK-0745-96

AlphaBIOS Console

6-21

6.4.8 Integrated Peripherals
Figure 6–15 Integrated Peripherals
Display System Configuration

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
Eisa Configuration
SCSI Configuration
MC Bus Configuration
Memory Configuration
Integrated Peripherals
1

Serial Port 1: Enabled as COM1:

3F8, IRQ4

Serial Port 2: Enabled as COM2:

2F8, IRQ3

Parallel Port 1: Enabled as LPT1:

3BC, IRQ7
PK-0746A-96

6-22

System Drawer User’s Guide

² Device type — The physical device as it exists on the system board
³ MS DOS name — Shows if the device is enabled, and if it is enabled, the
addressable MS-DOS name for the device.

´ Port address — The physical memory location from and to which data travels as
it is received into the device, and sent from the device, respectively.

µ Interrupt — The interrupt request line (IRQ) used by the device to get the CPU’s
attention.

AlphaBIOS Console

6-23

6.5 Updating Firmware
Insert the CD-ROM or diskette with the updated firmware and select Upgrade
AlphaBIOS from the main AlphaBIOS Setup screen. Use the Loadable
Firmware Update (LFU) utility to perform the update. The LFU exit command
causes a system reset.

Figure 6–16 Updating Firmware
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

Press ENTER to upgrade your AlphaBIOS from floppy or CD-ROM.

ESC=Exit
PK-0726A-96

6-24

System Drawer User’s Guide

As new versions of Windows NT are released, it might be necessary to upgrade
AlphaBIOS to the latest version. Additionally, as improvements are made to
AlphaBIOS, it might be desirable to upgrade to take advantage of new AlphaBIOS
features.
Use this procedure to upgrade from an earlier version of AlphaBIOS:
1.

Insert the diskette or CD-ROM containing the AlphaBIOS upgrade.

If you are not already running AlphaBIOS Setup, start it by restarting your
system and pressing F2 when the Boot screen is displayed.

In the main AlphaBIOS Setup screen, select Upgrade AlphaBIOS and press
Enter.
The system is reset and the Loadable Firmware Update (LFU) utility is started.
See Section 2.9.5 for LFU commands.

When the upgrade is complete, issue the LFU exit command. The system is
reset and you are returned to AlphaBIOS.
If you press the Reset button instead of issuing the LFU exit command, the
system is reset and you are returned to LFU.

AlphaBIOS Console

6-25

6.6 Setting up the Hard Disk
You can perform either an express or a custom hard disk setup. An express
setup, described in this section, creates the recommended partition arrangement
on the first hard disk, but it does not map bad sectors. Custom hard disk setup is
described in Sections 6.6.1 and 6.6.2.

Figure 6–17 Hard Disk Setup Screen
Hard Disk Setup
1

Disk

QLISP1020 #0, SCSI ID 3
6 Partition 1
Unused

7 200 MB

NCRC810 #0, SCSI ID 5
Partition 1
Partition 2

1001 MB
995 MB
6 MB

510 MB
8 NTFS

310 MB

NTFS
FAT

INSERT=New

DEL=Delete

F6=Format

F7=Express

ESC=Exit
PK-0732A-96

CAUTION: Hard disk changes are immediate; the ch anges are made as soon as
they are entered. Unintended data loss could occur, so it is important to
use care when changing your hard disk arrangement.

² Physical disk ID — Based on the SCSI ID. The disk with the lowest SCSI ID is
disk 0, the disk with the next lowest SCSI ID is disk 1, and so on.

³ Controller — Brand and model of SCSI chip used on the SCSI controller.
´ Controller number — Based on how many SCSI controllers of a particular type
are installed in the system. The first controller of a type is always numbered 0.

µ SCSI ID number — A unique number you assign to each SCSI device in the

system. This is usually done with jumpers or a thumb wheel attached to the drive
housing.

¶ Size — The raw capacity of the drive. Formatting the drive with different file

systems (for example, FAT and NTFS) may result in different usable sizes
because of the differences in how storage is managed under those file systems.

6-26

System Drawer User’s Guide

· Partition number — Within a single drive, partition numbers are assigned in

sequential order: 1, 2, 3, and so on. The partitions populate the drive from the
innermost cylinders to the outermost. If you have a large hard disk (over 800
MB) and plan to use the FAT file system, it is a good idea to break the disk into
several smaller partitions because the FAT file system uses disk space more
efficiently at smaller partition sizes. This is not a concern for the NTFS file
system, since it uses disk space very efficiently at all partition sizes.

¸ Partition size — The raw (unformatted) storage capa city of the partition. Actual
storage space will differ based on the file system with which the partition is
formatted.

¹ Partition format — The file system (if any) used on a partition. This field
displays FAT, NTFS, or unknown (if the partition is unformatted).

º Disk setup options

Insert partition (Insert key) — Use this option to create new partitions. Before
creating a new partition, be sure to select an unpartitioned space. Pressing the
Insert key while an already partitioned space is selected causes an informational
error to be displayed.
Delete partition (Delete key) — Use this option to delete existing partitions.
Before deleting a partition, be sure any data you want to save on the partition
has been backed up. Deleting a partition deletes all data on that partition but
leaves the rest of the disk unaffected. Pressing the Delete key while an
unpartitioned space is selected displays an informational error.
Format partition (F6 key) — Format a partitioned space with the FAT file
system.
Express setup (F7 key) — Create the default recommended partition
arrangement for Windows NT.
Exit (Escape key) — Return to the AlphaBIOS Setup screen.
An express hard disk setup creates the recommended partition arrangement on the
first hard disk (disk 0). It does not, however, format the large partition with NTFS,
and it does not map bad sectors on the disk. The NTFS formatting can be done
during Windows NT installation.
To perform an express hard disk setup
1.

If you have any needed information on your disk, back it up before proceeding.

Start AlphaBIOS Setup, select Hard Disk Setup, and press Enter.

Press F7 to enter Express Setup.

Press F10 to continue with the setup.
AlphaBIOS Console

6-27

6.6.1 Manually Creating and Deleting Partitions
Use the Create Partition and Delete Partition options if you need to create a
custom hard disk partition arrangement or otherwise manually manage your
hard disk partitions.

Figure 6–18 Create New Partition Dialog Box
Hard Disk Setup
Disk

Disk

QLISP1020 #0, SCSI ID 3
510 MB
Partition 1
200 MB
Unused
310 MB
Create new partition, Disk 0 Partition 2
NCRC810 #0, SCSI ID 5
1001 MB
Partition 1
995 MB
Partition 2
6 MB
Available space: 310 MB
New Partition Size: 200

ENTER=Continue

NTFS

NTFS
FAT

ESC=Cancel
PK-0733-96

To create a partition
1.

Start AlphaBIOS and select Hard Disk Setup. Press Enter.

Select the disk on which to create the partition.

If one or more partitions already exist on the disk, select the unpartitioned space.

Press Insert. A dialog box displays, similar to Figure 6–18.

Type the size of the partition to create and press Enter.

6-28

System Drawer User’s Guide

To delete a partition
1.

Start AlphaBIOS and select Hard Disk Setup. Press Enter.

Select the partition to be deleted (see

Press F10 to confirm the deletion.

² in Figure 6–19).
3. Press Delete. A dialog box displays (see ³).
Figure 6–19 Delete Partition Dialog Box
Hard Disk Setup
Disk

Disk

QLISP1020 #0, SCSI ID 3
Partition 1
1 Partition 2
Unused

510 MB
200 MB
200 MB
110 MB

NCRC810 #0, SCSI ID 5
1001 MB
Partition 1
995 MB
Delete Disk 0, Partition
Partition 2
6 MB2
2

NTFS
FAT

The delete operation will destroy all
data on partition 2 of disk 0.
Press F10 to continue.
cancel.
F10=Continue

Press ESC to

ESC=Cancel
PK-0734A-96

AlphaBIOS Console

6-29

6.6.2 Formatting a FAT Partition
AlphaBIOS can format partitions with the FAT file system. Use Windows NT to
format a partition using NTFS.

Figure 6–20 Formatting a FAT Partition
Hard Disk Setup
Disk

0
1

Disk

1
2

QLISP1020 #0, SCSI ID 3
Partition 1
Partition 2
Unused
Delete Disk 0, Partition 2

510 MB
200 MB
200 MB
110 MB

NCRC810 #0, SCSI ID 5
Partition 1
Partition
2
Choose Format
Method:

1001 MB
995 MB
6 MB

F1=Help

NTFS
Unrecognized

NTFS
FAT

Format Method: Standard Format
Standard Format
Quick Format
ENTER=Continue

ESC=Cancel
PK-0735A-96

6-30

System Drawer User’s Guide

To format a FAT partition
1.

Start AlphaBIOS and select Hard Disk Setup. Press Enter.

Select the partition to be formatted (see

Press F6. A dialog box displays, asking whether to perform a quick or standard
format (see ). If you select Quick Format, the formatting is completed
immediately, but no bad sectors are mapped. If you select Standard Format, a
dialog box similar to that in Figure 6–21 displays while the drive is formatted,
showing the progress of the formatting. Standard formatting maps bad sectors.

Select a format method, and press Enter.

² in Figure 6–20).

Figure 6–21 Standard Formatting
Hard Disk Setup
Disk

Disk

F1=Help

QLISP1020 #0, SCSI ID 3
Partition 1
Partition 2
Unused

510 MB
200 MB
200 MB
110 MB

NTFS
Unrecognized

NCRC810 #0, SCSI ID 5
Partition 1
Partition 2
Disk 0, Partition 2

1001 MB
995 MB
6 MB
200 MB

NTFS
FAT

Formatting...
25%

ESC=Cancel
PK-0736-96

AlphaBIOS Console

6-31

6.7 Performing Setup Tasks
CMOS Setup is used to configure several system parameters. CMOS Setup has
two modes: Standard CMOS Setup is used to configure basic system
parameters; Advanced CMOS Setup is used for system-specific parameters and
password protection.

Figure 6–22 Standard CMOS Setup Screen
CMOS Setup

1 Date:

Time:

Friday,
13:22:27

May

F1=Help

1996

2 Floppy Drive A: 3.5" 1.44 MB

Floppy Drive B: None
U.S. 101-key keyboard

3 Keyboard:

Auto Start: Enabled
Auto Start Count: 30 Seconds

Press
or
to modify date fields.
take effect immediately.

Date modifications will

F3=Color

F6=Advanced

F7=Defaults

ESC=Discard Changes

F10=Save Changes
PK-0749A-96

To enter Standard CMOS Setup
•

Start AlphaBIOS, select CMOS Setup, and press Enter.

6-32

System Drawer User’s Guide

² Date and time — When setting the time, use the 24-hour format. (For example,
10:00 p.m. is 22:00:00.)

³ Floppy drive — The only drive type supported is 3.5 inch, 1.44 MB.
´ Keyboard — The keyboard setting makes it possible to use most lan guage

keyboards. To ensure correct character mappings, the language of your
keyboard, Windows NT, and the keyboard language selection in CMOS Setup
should all match.

µ Auto start and auto start count — The Auto Start setting determines whether the
primary operating system is automatically started after the system is reset or
power-cycled. The Auto Start Count setting is the amount of time the Boot
screen is displayed before the default system is automatically started. This delay
gives you the opportunity, after resetting or power-cycling the system, to select
another version of Windows NT to start or to enter AlphaBIOS Setup.

¶ Standard CMOS Setup options

Color (F3 key) — Repeatedly cycles through the available AlphaBIOS color
schemes.
Advanced (F6 key) — Displays the Advanced CMOS Setup screen.
Defaults (F7 key) — Restores the default Standard CMOS Setup values
without affecting the Advanced CMOS Setup values.
Discard changes (Escape key) — Restores the settings in effect when you started
CMOS Setup. This option also discards changes made in Advanced CMOS
Setup.
Save changes (F10) — Saves changes made in both the standard and advanced
modes of CMOS Setup.
Continued on next page

AlphaBIOS Console

6-33

Figure 6–23 Advanced CMOS Setup Screen
Advanced CMOS Setup

1 PCI Parity Checking:

Disabled

2 Power-up Memory Test:

Enabled

3 AlphaBIOS Password Option:
4 Console Selection:

F1=Help

Disabled

Windows NT Console (AlphaBIOS)

5 Power-up Memory Test Windows
Length: NTFull
Console (AlphaBIOS)

OpenVMS Console (SRM)
Digital UNIX Console (SRM)

Press
or
to select the firmware console that will be presented
the next time the system is power-cycled.

ESC=Discard Changes

F10=Save Changes
PK-0750A-96

To enter Advanced CMOS Setup
1.

Start AlphaBIOS, select CMOS Setup, and press Enter.

In the Standard CMOS Setup screen, press F6.

6-34

System Drawer User’s Guide

² PCI parity checking — Enables and disables settings for PCI parity checking,

which ensures data integrity across the PCI bus. Because some third-party PCI
options do not correctly implement PCI parity generation, the default is
Disabled.

³ Power-up memory test — Enables and disables settings for the power-up
memory test.

´ Password setup — Enables and disables settings for password setup.
Password protection provides two levels of security for your system: setup,
which requires a password to start AlphaBIOS Setup, and startup, which
requires a password before the system initializes. Startup protection provides
more comprehensive protection than setup protection because the system cannot
be used at all until the correct password is entered.

µ Console selection — Switches from AlphaBIOS to SRM firmware. If you select
OpenVMS (SRM) or DIGITAL UNIX (SRM), the next time you reset your
system, the SRM firmware will be loaded instead of AlphaBIOS. This menu
selection changes the setting of the os_type environment variable in the SRM
console.

¶ Memory test length — Selects the length of memory testing that will be done the
next time the system is power-cycled.

· Advanced CMOS Setup options

Discard changes (Escape key) —Restores those settings in effect when you
started Advanced CMOS Setup. This does not discard changes made to
Standard CMOS Setup.
Save Changes (F10 key) — Saves changes made in Advanced CMOS Setup.
Note that, when exiting CMOS Setup, you must also save your changes at the
Standard CMOS Setup screen for the changes to be stored permanently.

AlphaBIOS Console

6-35

6.8 Installing Windows NT
Install Windows NT from CD-ROM. Up to four versions of the operating system
can be resident in the system at one time.

Figure 6–24 Installing Windows NT
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup...
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

Press ENTER to install Windows NT.

ESC=Exit
PK-0726B-96

6-36

System Drawer User’s Guide

If Windows NT was installed at the factory, Windows NT setup will start
automatically the first time the system powers up. If it was not installed, or if you are
installing another version, you must have a CD-ROM drive attached to your system.
NOTE: Steps 1 and 2 in the following procedure are necessary only when you are
first setting up your system. On subsequent installations and upgrades,
begin at step 3.
1.

Use CMOS Setup to set the system date and time: start AlphaBIOS Setup,
select CMOS Setup, and press Enter.

Perform an express hard disk setup: return to the main AlphaBIOS Setup
screen, select Hard Disk Setup, and press Enter.

Put the Windows NT CD into the CD-ROM drive.

Start AlphaBIOS Setup, select Install Windows NT, and press Enter.

Follow the prompts to complete the installation. For more information on
installing Windows NT, refer to the Installation Guide in your Windows NT
software package.

AlphaBIOS Console

6-37

6.9 Running Utility Programs
Maintenance programs such as RAID and EISA configuration utilities are run
from the AlphaBIOS Utility menu.

Figure 6–25 Run Maintenance Program Dialog Box
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard D
Run Maintenance Program
CMOS S
Instal
Utilit 1 Program Name: swxcrmgr.exe
About
2 Location: A:

ENTER=Execute

A:
CD:
Disk 0, Partition 1
Disk 0, Partition 2
Disk 1, Partition 1
PK-0747A-96

6-38

System Drawer User’s Guide

² Program name — The program to be run. It must be an executable program with
an .EXE filename extension. However, when entering the program name, it is
not necessary to type the extension.
Programs run from AlphaBIOS must be written as ARC compatible images.

³ Location — The location from which the program in the Program Name field

will be run if no path is entered along with the program name. To display a list
of all available disks and partitions, press the Alt and down arrow keys at the
same time. Once the list is displayed, use the plus arrow keys to cycle through
the selections.

See Chapter 7 for directions for running utilities.

AlphaBIOS Console

6-39

6.10 Selecting the Version of Windows NT
Up to four versions of Windows NT can be resident on the system at one time. It
is necessary to select the version that will be started.

Figure 6–26 Operating System Selections
Operating System Selection Setup

Primary Operating System

Windows NT Server 4.0
Windows NT Server 3.51

Boot Name: Windows NT Server 4.0
Boot File: Disk 0, Partition 2
\os\winnt351\osloader.exe
OS Path:
Disk 0, Partition 1
\WINNT351
OS Options:

INSERT=New
DEL=Delete

F6=Edit
F7=Copy

F8=Primary
F9=Validate

ESC=Discard Changes
F10=Save Changes

Operating System Selection Setup

Windows NT Server 3.51
Windows NT Server 4.0

Primary Operating System

Boot Name: Windows NT Server 3.51
Boot File: Disk 0, Partition 2
\os\winnt400\osloader.exe
OS Path:
Disk 0, Partition 1
\WINNT400
OS Options:

INSERT=New
DEL=Delete

F6=Edit
F7=Copy

F8=Primary
F9=Validate

ESC=Discard Changes
F10=Save Changes
PK-0723-96

6-40

System Drawer User’s Guide

NOTE: The term “operating system selection,” as it is used in this context, refers to
a version of Windows NT. It does not pertain to the DIGITAL UNIX and
OpenVMS operating systems.
Each operating system selection is a set of information for a version of Windows
NT. It describes the disk and partition containing the OSLOADER.EXE file
associated with a particular operating system installation, as well as the path to the
operating system itself. In addition, the operating system selection contains any
options passed to the operating system during boot.
By default, one operating system selection displays on the AlphaBIOS Boot screen
for each operating system installed on the system. It is not normally necessary to
modify operating system selections, as the Windows NT installation creates and
modifies operating system selections as needed.
Figure 6–26 shows how operating system selections appear in AlphaBIOS.

AlphaBIOS Console

6-41

6.10.1 Designating a Primary Operating System
Figure 6–27 Primary Operating System
AlphaBIOS 5.29
Please select the operating system to start:

Windows NT Server 3.51
Windows NT Server 3.50
Use
and
to move the highlight to your choice.
Press Enter to choose.
CMOS Setup

Date:
Time:

Friday,
11:26:22

Jan

1997

Floppy Drive A: 3.5" 1.44 MB
Floppy Drive B: None
Keyboard: U.S. 101-key keyboard

Auto Start: Enabled
Auto Start Count: 30 Seconds

Operating System Selection Setup

Windows NT Server 3.51
Windows NT Server 3.50

Primary Operating System

PK-0720C-97

6-42

System Drawer User’s Guide

Multiple versions of Windows NT can be installed at the same time. This can be
very useful in a variety of circumstances for example, when testing application
compatibility across different versions of Windows NT.
Each time you install a separate version of Windows NT, a new operating system
selection is created. Although you can start any of the installed versions of Windows
NT, one of them must be the primary operating system. The version of Windows NT
you select as the primary operating system is the one that automatically starts if the
Auto Start option is enabled in AlphaBIOS.
Figure 6–27 illustrates the relationship between multiple-operating-system
installations, Auto Start, and the primary operating system.

²
³
´

The primary operating system is listed first on the Boot screen.
The primary operating system starts automatically if the Auto Start option is
enabled in CMOS Setup.
The primary operating system can be selected in the Operating System
Selection Setup screen.

Follow this procedure to designate a new primary operating system:
1.

From the AlphaBIOS Setup screen select Utilities. In the selection box that
displays, choose OS Selection Setup.

The Operating System Selections Setup screen displays. Select the primary
operating system from the list displayed.

AlphaBIOS Console

6-43

6.10.2 Primary Operating System and the Auto Start Option
The process of setting up your operating system selections is similar to using an
editor. You can make changes to your operating system selections and then
either save your changes or exit without saving.

Figure 6–28 Operating System Selection Setup
Operating System Selection Setup

Windows NT Workstation 3.51

2
3
4
5

Primary Operating System

Boot Name: Windows NT Workstation 3.51
Boot File: Disk 0, Partition 2
\os\winnt351\osloader.exe
OS Path:
Disk 0, Partition 1
\WINNT351
OS Options:

INSERT=New
DEL=Delete

F6=Edit
F7=Copy

F8=Primary
F9=Validate

ESC=Discard Changes
F10=Save Changes
PK-0737B-96

AlphaBIOS boots Windows NT in two stages. The first stage involves reading an OS
Loader program from a disk. As of Windows NT version 3.51, the name of the OS
Loader program is OSLOADER.EXE. The selection for the operating system must
describe the path where AlphaBIOS will find the OS Loader program. Note that the
OS Loader program must be located on a partition formatted with the FAT file
system.
Once the OS Loader program executes, it uses the services provided by AlphaBIOS
to load the operating system components. After the operating system is loaded, the
OS Loader starts execution of the operating system.

6-44

System Drawer User’s Guide

² Primary operating system — The OS that appears first on the AlphaBIOS Boot
screen. It is also the version of the OS that automatically starts if Auto Start is
selected. Any of the operating system selections can be the primary operating
system.

³ Boot name — Each boot name is associated with an operating system selection.
Windows NT setup automatically creates a boot name each time you install the
operating system. Because the boot name is only a name, you can modify it at
any time without affecting the rest of the operating system selection. Note that
the boot name must have at least one character.

´ Boot file — Describes the disk, partition, path, and name of the file that

AlphaBIOS passes control to during the process of starting the operating system.
This setting is created along with the operating system selection during
Windows NT setup, and it is usually not modified by the user. However, this
setting can be modified if necessary. For example, a developer testing different
versions of OSLOADER.EXE can store the different versions in different
locations and modify this line to start the operating system with the different
versions as needed.

During Operating System Selection Setup, you can select the disk and partition
for the location of the boot file from a list of choices presented in a list box. To
open a list of values for the field, press the Alt and down arrow keys together.
When you select a boot file location and name, AlphaBIOS searches for the
specified program on the specified partition. If the search fails, a warning
displays, saying that the file does not exist. You are given the choice to continue
with the changes anyway or to cancel the operation and fix the problem.
Note that because the boot file must be located in a FAT partition, only FAT
partitions are available as the boot partition within the list box.

µ OS path — Describes the disk, partition, and path to the operating system root
directory for an operating system selection.

During Operating System Selection Setup, you can select the disk and partition
for the location of the boot file from a list of choices presented in a list box. To
open a list of possible values for the field, press the Alt and down arrow keys at
the same time. When you select or enter an OS path, AlphaBIOS searches for
the directory. If the search fails, a warning displays, saying that the directory
does not exist. You are given the choice to continue with the changes anyway or
to cancel the operation and fix the problem.
Continued on next page

AlphaBIOS Console

6-45

¶ OS options — Lists the startup parameters passed to the operating system for an

operating system selection. One example of a startup parameter is whether to
start the operating system in debug mode. By default, Windows NT does not add
any entries to this field. This field can be modified.

· Operating System Selection Setup options — You can use the options listed at
the bottom of the screen to edit operating system selections. When you edit an
OS selection, the fields of the OS selection are validated when you exit the OS
Selection Setup screen. Depending on the option you choose, one of the
following dialog boxes will display.

New OS selection (Insert key) — Displays the Insert New Operating System
Selection dialog box, with default values for the new OS selection already filled
in. You can change these values as necessary.
Delete OS selection (Delete key) — Tags the currently selected OS selection for
deletion. Although the OS selection is removed from the screen, it is not actually
deleted until you save changes.
You can also delete all of your OS selections at once by pressing the Control and
Delete keys at the same time while in the Operating System Selection Setup
screen.
NOTE: If you delete all the OS selections, a dialog box displays informing you
that no OS selections exist and offering three options. You can create a
new OS selection, exit without saving changes, or exit and save
changes.
Edit OS selection (F6 key) — Edit all values of an OS selection by selecting the
OS selection to edit and pressing F6. A dialog box displays with current
information. You can then edit the OS selection fields.
Copy OS selection (F7 key) — Create a new OS selection by using an existing
OS selection as a template. To do this, select the OS selection you want to copy
and press F7. A dialog box displays with the values of your OS selection. You
can then edit the OS selection fields. Note that if you do not make any changes,
a duplicate copy of the OS selection you copied is made.
Primary operating system (F8 key) — Sets the selected OS selection as the
primary operating system. When you make an OS selection primary, it is
displayed first on the Operating System Selection Setup screen with the text
“Primary Operating System.” In addition, the primary operating system is
displayed first on the AlphaBIOS Boot screen and is automatically started if
Auto Start is enabled.

6-46

System Drawer User’s Guide

Validate OS selection (F9 key) — Validates the fields in the currently selected
OS selection. The validation routine checks that the OS loader file and OS
directory fields contain valid paths, and that the OSLOADER.EXE file exists in
the directory specified. At the end of the validation, a dialog box displays
describing the results of the validation. If there is an error in an OS selection, the
validation routine displays a dialog box describing the component of the OS
selection that is in error. At this point you can choose to edit the OS selection to
correct the error, or delete the OS selection altogether.
You can also validate all OS selections at once by pressing the Control and F9
keys at the same time. All OS selections are validated in the order they are listed
on screen.
Discard changes (Escape key) — Returns to the AlphaBIOS Setup screen
without saving changes.
Save changes (F10 key) — Saves changes and returns to the AlphaBIOS Setup
screen.

AlphaBIOS Console

6-47

Chapter 7
Utilities
Utilities that configure EISA options and RAID devices are run from AlphaBIOS.
This chapter gives directions for running utilities from both a graphics monitor and a
serial terminal.
Sections in this chapter are:
•

Running Utilities from a Graphics Monitor

•

Running Utilities from a Serial Terminal

Utilities

7-1

7.1 Running Utilities from a Graphics Monitor
Start AlphaBIOS and select Utilities from the menu. Then select Run
Maintenance Program.

Figure 7–1 Running a Utility from a Graphics Monitor
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard Disk Setup...
CMOS Setup...
Install Windows NT
Utilities
About AlphaBIOS...

F1=Help

Run ECU from floppy...
OS Selection Setup...
Run Maintenance Program...

PK-0729-96

7-2

System Drawer User’s Guide

Start AlphaBIOS Setup. If the system is in the SRM console, set the SRM
console environment variable to graphics and issue the command alphabios.

From AlphaBIOS Setup, select Utilities, then select Run Maintenance
Program from the submenu that displays, and press Enter.

In the Run Maintenance Program dialog box, type the name of the program to
be run in the Program Name field. Then Tab to the Location list box, and select
the hard disk partition, floppy disk, or CD-ROM drive from which to run the
program.

Press Enter to execute the program.

NOTE: If you are running the EISA Configuration Utility, use the appropriate
program for the operating system you intend to boot. If you run the wrong
program, your system will behave unpredictably during booting.
See Section 6.3 for information about navigating through AlphaBIOS screens.

Figure 7–2 Run Maintenance Program Dialog Box
AlphaBIOS Setup

Display System Configuration...
Upgrade AlphaBIOS
Hard D
Run Maintenance Program
CMOS S
Instal
Program Name: swxcrmgr.exe
Utilit
About
Location: A:

ENTER=Execute

A:
CD:
Disk 0, Partition 1
Disk 0, Partition 2
Disk 1, Partition 1
PK-0747-96

Utilities

7-3

7.2 Running Utilities from a Serial Terminal
Utilities are run from a serial terminal in the same way as from a graphics
monitor. The menus are the same, but some keys are different.

Table 7–1 AlphaBIOS Option Key Mapping
AlphaBIOS Key

VTxxx Key

Ctrl/A

Ctrl/B

Ctrl/C

Ctrl/D

Ctrl/E

Ctrl/F

Ctrl/P

Ctrl/R

Ctrl/T

F10

Ctrl/U

Insert

Ctrl/V

Delete

Ctrl/W

Backspace

Ctrl/H

Escape

Ctrl/[

7-4

System Drawer User’s Guide

Start AlphaBIOS Setup by issuing the command alphabios.

Press F2 in the AlphaBIOS Boot screen.

From AlphaBIOS Setup, select Utilities, and select Run Maintenance
Program from the submenu that displays. Press Enter.

In the Run Maintenance Program dialog box, type the name of the program to
be run in the Program Name field. Then tab to the Location list box, and select
the hard disk partition, floppy disk, or CD-ROM drive from which to run the
program.

Press Enter to execute the program.

NOTE: If you are running the EISA Configuration Utility, use the appropriate
program for the operating system.

Utilities

7-5

Appendix A
How to Find Firmware Updates
Firmware for all AlphaServer systems is available for download from the Internet.
You can access the firmware as follows.
•

Using a World Wide Web browser (such as Mosaic or Netscape), follow links to
AlphaServer 4000 and 4100 systems, then technical resources from URL:
http://www.digital.com/info/alphaserver/products.html

•

Using ftp, copy the file:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/

The files are structured as those on the firmware CD and are separated by CD
release. For example, the contents of the V3.6 firmware CD are located at:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/v3.6/
The latest firmware (if released since the last firmware CD) is located at:
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/interim/

How to Find Firmware Updates

A-1

Appendix B
Hard Disk Partitioning for AlphaBIOS
and Windows NT
The recommended hard disk partition arrangement on the first hard disk in your
system is:
•

Partition 1  Six megabytes less than the total size of the drive. This large
partition holds the operating system and the application and data files.

•

Partition 2  The remaining six megabytes. This small partition holds only the
few files necessary for your computer to boot.

This arrangement provides two benefits.
•

Windows NT requires that a boot partition be formatted with the FAT file
system. However, the Windows NT file system (NTFS) provides advantages
over FAT, such as additional security and more efficient use of disk space. By
keeping the FAT boot partition as small as possible, the maximum amount of
space is left available for use as an NTFS partition.

•

Most applications install themselves onto drive C by default. Although the
program installation drive is usually configurable by the user, many people
accept the default of drive C. By making the first partition large, drive C
becomes the larger drive. This arrangement makes program installation easier
and avoids time-consuming insufficient disk space mistakes.

B.1 Hard Disk Error Conditions
B.1.1 Disk Initialization Failed
When you start hard disk setup, if you receive an “Internal error occurred ” message,
it means that a disk was found, but there was an error in communicating with the
disk. The likely conditions that can cause this error are:
•

•

Incompatible or failed disk cables. You may not have the correct cable installed,
or the cable might have a broken lead or connector. Try another cable known to
be good.
Disk controller not configured. You may have to run a configuration utility to
set up your hard disk controller. Check your controller documentation.

Hard Disk Partitioning for AlphaBIOS and Windows NT

B-1

•

Disk controller malfunction. Most controllers come with a diagnostic utility to
test controller functioning. If a controller error is found, call the manufacturer
for a replacement.
Improper SCSI termination. Many SCSI controllers require that the terminating
resistor packs be removed from all drives between the controller and last drive.
Only the controller itself, and the last drive connected to the controller (the ends
of the “chain”), should have terminating resistor packs left on.

B.1.2 No Hard Disks Found
When you start hard disk setup, if you receive a “No hard drives were found
connected to your computer ” message, it means that AlphaBIOS could not locate a
hard drive. The likely conditions that cause this error are:
•

Cable not connected to either the disk or controller. The cable may have worked
loose from the connector on the controller or disk drive. Check the cable
connections, making sure the cable connectors are fully seated.

•

No power to the drive. The power connector may have worked loose from the
receptacle on the drive, or the power cable itself may be malfunctioning. Check
the cable connections, making sure the cable connectors are fully seated. Try
connecting the drive to a different power connector.
Disk drive malfunction. The disk drive itself may be malfunctioning and not
responding to requests from the controller. If this is the problem, then it would
appear as though the disk were absent. Replace the drive with a drive known to
be good. If the known good drive is correctly detected, then your hard drive is
defective. Contact the manufacturer for a replacement.

•

B.1.3 No Partitions on Disk
If hard disk 0 does not have any partitions defined, then a message will appear when
you start hard disk setup, asking if you want to perform an express disk setup.
Express disk setup automatically creates the default disk partition arrangement on
hard disk 0.
For more information on express setup, see Chapter 6.

B.2 System Partitions
To install Windows NT, a system partition must be defined. If no system partition is
found, the user is asked to choose from the available FAT partitions.
The purpose of the system partition is twofold. First, it tells the Windows NT
installation program where to place the OS Loader and hardware support files.
Second, upon subsequent restarts of Windows NT, the system partition definition
tells AlphaBIOS where the OSLOADER.EXE file is so it can successfully hand off
control to the OS Loader and continue the boot process.
B-2

System Drawer User’s Guide

The system partition can be the same partition into which Windows NT is installed,
or it can be separate. However, the system partition must be formatted with the FAT
file system. Because the default recommended partition arrangement on Alpha calls
for the partition into which Windows NT is installed to be an NTFS partition, the
system partition will almost always be a small FAT partition on the same disk onto
which Windows NT is installed.

B.3 How AlphaBIOS Works with System Partitions
If you are installing Windows NT for the first time, AlphaBIOS will determine that a
system partition has not been defined when you select Install Windows NT in the
AlphaBIOS Setup screen (see Figure B–1). When this occurs, AlphaBIOS searches
for all FAT partitions on the system. If only one FAT partition exists, AlphaBIOS
designates that FAT partition as the system partition and continues with the
Windows NT installation. If more than one FAT partition exists on your system,
AlphaBIOS displays the list of FAT partitions from which you can choose the system
partition. After choosing the system partition, the installation process continues.

Figure B–1 System Partition Not Defined
AlphaBIOS Setup

Display System Configuration
Upgrade AlphaBIOS
Hard Disk Setup...
CMOS Se
No System Partition
Install
Utiliti You must designate a FAT disk partition as a System
About A Partition. Windows NT will use the System Partition
to store system specific startup files.
Please select a partition as the System Partition.
System Partition: Disk 0, Partition 1
ENTER=Continue

E Disk 0, Partition 1
Disk 0, Partition 2
Disk 1, Partition 1
Disk 1, Partition 2
PK-0748-96

Hard Disk Partitioning for AlphaBIOS and Windows NT

B-3

Appendix C
Differences Between AlphaBIOS
and ARC Firmware
This appendix is for users of Alpha systems who are experienced with ARC
firmware, and who want an overview of the major differences between ARC and
AlphaBIOS firmware.

C.1 Revamped User Interface
AlphaBIOS has a graphical-style windowed interface. Many of the navigational and
selection keystrokes implemented in Microsoft Windows are present in AlphaBIOS
as well. If you are familiar with navigating Microsoft Windows using a keyboard,
AlphaBIOS navigation will also be simple. Additionally, information and selections
are grouped more logically. Groups of related tasks can often be performed from a
single screen.

C.2 Hard Disk Setup
Using ARC firmware, initial hard disk partitioning and formatting was accomplished
with a utility called ARCINST.EXE. This utility is distributed on the Windows NT
CD-ROM. This utility was run in a manner similar to how a maintenance program is
run with AlphaBIOS; that is, from a command line. Under AlphaBIOS, hard disk
setup functionality is integrated into the menu-based interface.
The following list summarizes the new hard disk setup functionality in AlphaBIOS
but not found in the ARC program:
•
•
•
•
•
•
•

With one keystroke, express disk setup configures your first hard disk with the
recommended partition arrangement.
AlphaBIOS uses the same path descriptions as Windows NT Disk Administrator,
rather than the ARC path names used in ARCINST. For example:
ARC Path Name = scsi(0)disk(0)rdisk(0)partition(1)
AlphaBIOS Path Name = Disk 0, Partition 1
All partitions of all disks can be seen at the same time.
Disk administration is integrated into the BIOS, rather than being a maintenance
program.
No menu hierarchy to navigate.
Differences Between AlphaBIOS and ARC Firmware

C-1

•
•

Detailed display of disk and partition configuration.
Windowed interface.

C.3 Changing CMOS and NVRAM Values
With ARC firmware, a number of settings stored in CMOS and NVRAM are set
using several separate ARC firmware selections. With AlphaBIOS, these settings are
more logically arranged by being integrated into the CMOS Setup program. Table
C–1 summarizes the differences between AlphaBIOS and ARC firmware in this
regard.

Table C–1 Differences Between AlphaBIOS and ARC Menu
Selections
Function

AlphaBIOS Menu

ARC Menu

Set date/time

CMOS Setup

Set System Time

SCSI termination and PCI parity
checking

CMOS Setup

Machine specific setup

Floppy and keyboard

CMOS Setup

Set Default
Configuration

Default system partition

N/A (handled
automatically by hard
disk setup)

Set Default
Environment Variables

SCSI host ID

N/A

Set Default
Configuration

Automatic OS startup

CMOS Setup

Setup AutoBoot

Edit environment variables

N/A (handled
automatically by
AlphaBIOS)

Edit Environment
Variables

Set monitor resolution

N/A

Set Default
Configuration

C-2

System Drawer User’s Guide

C.4 Working with Operating Systems
Because Alpha systems can have multiple versions of Windows NT installed
simultaneously, you can examine, verify, and modify the values associated with each
installed version of Windows NT. With ARC firmware, the group of values
associated with a particular Windows NT installation are collectively known as a
“boot selection.” With AlphaBIOS, these values are known as an “operating system
selection.”
With ARC firmware, working with boot selections is difficult because the various
pieces of information necessary are located on separate screens displayed by using
the Manage Boot Selections menu. In addition, the interface provides no way to
easily see the alternatives available for a given item. For example, if you want to
customize a boot selection to use an OSLOADER.EXE file on a different partition or
disk, there is no way to see the different choices available while in the menu where
you enter that information. This makes it necessary to navigate back and forth
between the separate menus these pieces of information are located under and to
remember the information for entry into the correct menu.
With AlphaBIOS, working with operating system selections has been greatly
simplified by virtue of the revamped user interface. All the functionality available
under ARC firmware has been integrated into a single Operating System Selection
Setup screen. Alternative choices for values, such as disk and partition numbers, are
available with drop-down list boxes, and only valid values are displayed. This makes
processes that were once error-prone and clumsy relatively smooth and error-free.
In addition, a new feature, copying operating system selections, makes creating new
operating system selections even easier by making it possible to use an existing
selection as a template for a new selection.

C.5 Running a Program from the BIOS
The procedure for running configuration programs remains essentially unchanged
with AlphaBIOS. With ARC firmware, the menu selection to run a program was
located on the Boot menu, whereas, with AlphaBIOS, you can select Utilities from
the main AlphaBIOS Setup screen to run configuration programs.
Note that the selection name has changed from “Run a program” under ARC, to
“Run a maintenance program ” under AlphaBIOS.

C.6 Differences in System Configuration Display
The system configuration display in ARC firmware provides general information
about system setup. In contrast, the system configuration display in AlphaBIOS
displays detailed information categorized by major subsystem. In addition, for many

Differences Between AlphaBIOS and ARC Firmware

C-3

of the elements listed, you can select the element and obtain additional detailed
information.

C.7 Resetting to Factory Defaults
With ARC firmware, the option to reset the system to factory defaults is located on
the Setup screen. With AlphaBIOS, the equivalent function is performed by pressing
F7 in the CMOS Setup screen.

C.8 Multilingual Support
Support for multiple languages, which was recently added to ARC firmware, is not
currently a feature of AlphaBIOS.

C-4

System Drawer User’s Guide

Appendix D
Acoustical Data
Table D–1 Acoustics — Declared Values per ISO 9296 and ISO
7779
Sound Power Level
LWAd, B

Sound Pressure Level
LpAm, dBA
(bystander positions)

Product

Idle

Operate

Idle

Operate

BA30B–AA (AlphaServer
4000 drawer as subassembly, 1-2 cpu, 1-2 psu)

6.1

BA30P–AA/AB (BA30B
with 1-2 cpu, 1-2 psu, no
drives, in pedestal cab)

6.0

BA30B with 1-2 cpu, 1-2
psu + 2xBA356 with
2xRZ29B each, in pedestal
cab

6.3

6.4

H9A10 (diskless rack)

6.3

BA30B with 1-2 cpu, 1-2
psu, in H9A10

6.1

BA356 with 2xRZ29B, in
H9A10

6.0

6.1

[Current values for specific configurations are available from Digital Equipment
Corporation representatives. 1 B = 10 dBA.]

Acoustical Data

D-1

Table D–2 Schallemissionswerte — Werteangaben nach ISO
9296 und ISO 7779/DIN EN27779
Schalleistungspegel
LWAd, B

Schalldruckpegel
LpAm, dBA
(Zuschauerpositionen)

Gerät

Leerlauf

Betrieb

Leerlauf

Betrieb

BA30B–AA
(AlphaServer 4100
Einschubbau-gruppe, 1-2
cpu, 1-2 psu)

6,1

BA30P–AA/AB (BA30B
mit 1-4 cpu, 1-2 psu,
ohne Laufwerke, in
Standfußge-häuse)

6,0

BA30B mit 1-2 cpu, 1-2
psu + 2xBA356 jeweils
mit 2xRZ29B, in
Standfußge-häuse

6,3

6,4

H9A10 (Gestell ohne
Laufwerke)

6,3

BA30B mit 1-2 cpu, 1-2
psu, in H9A10

6,1

BA356 mit 2xRZ29B
in H9A10)

6,0

6,1

[Aktuelle Werte für spezielle Ausrüstungsstufen sind über die Digital Equipment
Vertretungen erhältlich. 1 B = 10 dBA.]

D-2

System Drawer User’s Guide

Index

?
? command, RCM, 2-56

A
Advanced CMOS setup screen,
AlphaBIOS, 6-34
alert_clr command, RCM, 2 -54
alert_dis command, RCM, 2 -54
alert_ena command, RCM, 2 -54
alphabios command, SRM, 5 -2, 5-35
AlphaBIOS console, 2-7, 2-27, 6-1 to
6-47
boot screen, 2-24, 2-27, 6-4
checking PCI parity, 6-35
CMOS setup, 2-27
displaying system configuration,
6-8
enabling and disabling settings
for memory test, 6-35
express setup, 2-27
finding help, 6-6
first-level help screen, 6 -6
hard disk setup, 2-27
key conventions, 6-6
running in serial mode, 7 -4
second-level help screen, 6 -7
setting date and time, 6 -33
setting keyboard language, 6 -33
setting password, 6-35
setup screen, 2-27, 6-5
starting, 6-4
switching from SRM, 5-2
switching to SRM, 6-2, 6-35
AlphaBIOS Setup screen, 2-29
Architecture, 1-4

auto_action environment variable,
SRM, 2-7, 5-40, 5-42

B
BA30B. See System drawer
Baud rate, setting for COM* ports,
5-44
B-cache, 2-5, 2-7
Block diagram, 1-4
boot command, SRM, 2-8 to 2-13,
2-15, 2-16 to 2-21, 2-23,
5-12, 5-21, 5-35
passing information to command,
5-43
Boot screen, AlphaBIOS, 2-24, 6-4
boot_file environment variable, SRM,
2-9, 2-11, 2-13, 2-17, 2-19,
2-21
boot_osflags environment variable,
SRM, 2-9, 2-11, 2-13, 2-17,
2-19, 2-21, 5-40, 5-43
DIGITAL UNIX, 5-43
OpenVMS, 5-43, 5-44
boot_reset environment variable,
SRM, 2-17
bootdef_dev environment variable,
SRM, 2-9, 2-11, 2-13, 2-17,
2-19, 2-21, 5-40
Booting
DIGITAL UNIX, 2-8 to 2-13
from cluster disk, 2-10
from local disk, 2-8
from remote disk, 2-12
OpenVMS, 2-16 to 2-21
from cluster disk, 2-18
from local disk, 2-16
from remote disk, 2-20
Index-1

passing information to command,
5-43
Windows NT, 2-24
Bridge module, 1-5, 1-9, 1-16
LEDs, 3-4

C
Cabinet
exposing system drawer, 4-4
Card cages, 1-7
clear envar command, SRM, 5-35
CMOS setup screen, AlphaBIOS,
6-32, 6-34
COM* ports, setting baud rate, 5 -44
com*_baud environment variable,
SRM, 5-40, 5-44
Command syntax, SRM console, 5 -37
Configuration
CPU module, 1-11
memory pair, 1-13
power supply, 1-25
processor module, 1-11
Configuring parameters, AlphaBIOS
console, 6-32
Configuring the system
DIGITAL UNIX system, 5-14
OpenVMS system, 5-14
Console
AlphaBIOS, 2-7
specifying, 6-35
SRM, 2-7, 5-1
switching from AlphaBIOS to
SRM, 6-2
switching from SRM to
AlphaBIOS, 5-2
Console commands, SRM, 5-35
console environment variable, SRM,
2-5, 2-7, 2-25, 5-26, 5-40,
5-45
Console terminal, 1-26
Console terminal, specifying type,
5-45
continue command, SRM, 5 -20, 5-21,
5-35
Control panel, 1-22

Index-2

display, 1-22, 2-2, 2-3, 2-5, 3-7
display indicates an error, 3 -6
display intensity, 1-23
display is blank, 3-4
error, 3-6
halt button, 1-22, 1-23
messages in display, 3-7
power button, 1-22, 1-23, 2-2
reset button, 1-22, 1-23
specifying display message,
SRM, 5-48
Controls
halt button, 1-23
power button, 1-23, 2-2
reset button, 1-23
Cover interlocks, 3-2
Cover removal
pedestal, 4-2
CPU module, 1-5, 1-9, 1-10
configuring, 1-11
enabling and disabling specific
processors, 5-45
installing, 4-8
LEDs, 3-4
slot numbers, 4-8
cpu_enabled environment variable,
SRM, 5-40, 5-45
crash command, SRM, 5-24, 5-35
Crash dump, 5-24

D
Date, setting in AlphaBIOS console,
6-33
deposit command, SRM, 5-28, 5-29,
5-35
Depositing data, 5-28
Device naming conventions, SRM,
5-7
DIGITAL UNIX
booting, 2-8 to 2-13
from cluster disk, 2-10
from local disk, 2-8
from remote disk, 2-12
console for, 5-1
installing, 2-14

specifying as default operating
system, 5-49
disable command, RCM, 2 -55
display command, LFU, 2 -44, 2-45
Display system configuration screen,
AlphaBIOS console, 6-8
Display, control panel, 1 -22
Displaying system configuration, 5 -4
AlphaBIOS console, 6-8
Displaying the value or setting of an
environment variable, 5 -26
Door removal
pedestal, 4-2

E
edit command, SRM, 5 -27, 5-35
EISA configuration screen,
AlphaBIOS, 6-17
EISA options
configuring, 5-17
installing, 4-12
slot numbers, 4-12
Electrical parameters, 1 -3
enable command, RCM, 2 -55
Environment variables, SRM, 5 -25
auto_action, 2-7
boot_file, 2-9, 2-11, 2-13, 2-17,
2-19, 2-21
boot_osflags, 2-9, 2-11, 2-13,
2-17, 2-19, 2-21
boot_reset, 2-17
bootdef_dev, 2-9, 2-11, 2-13,
2-17, 2-19, 2-21
console, 2-5, 2-7
displaying the value or setting,
2-11, 5-26
graphics, 2-5
modifying, 5-26
os_type, 2-7
serial, 2-5
setting, 5-26
summary, 5-40
Environmental parameters, 1 -3
Ethernet, specifying controller type,
5-46

ew*0_mode environment variable,
SRM, 5-40, 5-46
ew*0_protocols environment
variable, SRM, 5-40, 5-46
examine command, SRM, 5 -28, 5-29,
5-35
Examing data, 5-28
exit command, LFU, 2 -29, 2-33,
2-39, 2-43, 2-44, 2-45

F
Finding help
AlphaBIOS console, 6-6
SRM console, 5-34
Firmware
AlphaBIOS console, 6-1
RCM, 2-52
SRM console, 5-1
updating, 2-29
updating from AlphaBIOS, 6-24
updating from CD-ROM, 2-30
updating from floppy disk, 2 -34,
2-36
updating from network device,
2-40
updating from SRM, 5-22
updating, AlphaBIOS selection,
2-28
updating, SRM command, 2 -28
Formatting hard disk, AlphaBIOS,
6-26, 6-28, 6-30

G
Graphics accelerator, setting location
of SYNC signal, SRM, 5-51
graphics environment variable, SRM,
2-5
Graphics monitor, specifying as
console terminal, SRM, 5 -45

H
Halt button, control panel, 1 -22
halt command, RCM, 2 -56
halt command, SRM, 5 -20, 5-21, 5-35
hangup command, RCM, 2-55
Index-3

Hard disk configuration screen,
AlphaBIOS, 6-12
Hard disk setup screen, AlphaBIOS,
6-26
Hard disk, AlphaBIOS
creating and deleting partitions,
6-28
formatting a FAT partition, 6 -30
setting up, 6-26
Help
AlphaBIOS console, 6-6
AlphaBIOS first-level help
screen, 6-6
AlphaBIOS second-level help
screen, 6-7
help command, LFU, 2 -44, 2-45
help command, RCM, 2 -56
help command, SRM, 5-34, 5-35

I
Initialization and answer strings
modifying for modem, 2-71
substitutions, 2-72
initialize command, SRM, 5 -27, 5-32,
5-33, 5-35
Initializing the system, 5 -32
Installing
DIGITAL UNIX, 2-14
OpenVMS, 2-22
Windows NT, 2-26
Installing Windows NT, 6-36
Integrated peripherals screen,
AlphaBIOS, 6-22
Interlocks, 3-2
IOD, 2-7

K
kbd_hardware_type environment
variable, SRM, 5-26, 5-40,
5-47
Key conventions
AlphaBIOS console, 6-6
Key mapping, AlphaBIOS in serial
mode, 7-4
Keyboard

Index-4

setting language, AlphaBIOS,
6-33
specifying hardware type, SRM,
5-47
specifying layout, SRM, 5-47
kzpsa*_host_id environment variable,
SRM, 5-40, 5-47

L
language environment variable, SRM,
5-26, 5-40, 5-47
LEDs
power control module, 4-18
LEDs, CPU and bridge modules, 3 -4
LFU
exit command, 2-45
starting, 2-28, 2-29
starting the utility, 2 -28
typical update procedure, 2 -29
update command, 2-46
updating firmware from
CD-ROM, 2-30
updating firmware from floppy
disk, 2-34, 2-36
updating firmware from network
device, 2-40
lfu command, LFU, 2-37, 2-39, 2-44,
2-45
lfu command, SRM, 2-29, 5-21, 5-22,
5-35
LFU commands
display, 2-44, 2-45
exit, 2-29, 2-33, 2-39, 2-43, 2-44,
2-45
help, 2-44, 2-45
lfu, 2-37, 2-39, 2-44, 2-45
list, 2-29, 2-31, 2-37, 2-39, 2-41,
2-43, 2-44, 2-46
readme, 2-44, 2-46
summary, 2-44
update, 2-29, 2-33, 2-44, 2-46
verify, 2-44, 2-46
list command, LFU, 2 -29, 2-31, 2-37,
2-41, 2-44, 2-46

Loadable Firmware Update utility.
See LFU

M
Maintenance programs, AlphaBIOS,
6-38
man command, SRM, 5-34, 5-35
Memory configuration screen,
AlphaBIOS, 6-21
Memory module, 1-9
Memory pair, 1-5, 1-12
configuring, 1-13
installing, 4-10
slot numbers, 4-10
Memory test
determining extent of testing,
SRM, 5-48
enabling and disabling settings in
AlphaBIOS, 6-35
Memory tests, 2-5
memory_test environment variable,
SRM, 5-40, 5-48
Modem
answer, 2-70
Dial-in procedure, 2-50
dialog details, 2-69
hangup, 2-70
phases of operation, 2-69
ring detection, 2-70
usage in RCM, 2-48
Modifying an environment variable,
SRM, 5-26
Modules
bridge, 1-5, 1-9, 1-16
CPU, 1-5, 1-9, 1-10, 4-8
EISA, 4-12
memory, 1-9
memory pair, 1-5, 1-12, 4-10
PCI, 4-12
PCI bridge, 1-5, 1-16
PCI motherboard, 1-18
power control, 1-9, 1-14
processor, 1-5, 1-9, 1-10, 4-8
server control, 1-20

system bus to PCI bus bridge,
1-5, 1-16
system motherboard, 1-8
more command, SRM, 5-31, 5-35

N
Naming conventions, SRM, 5-7
Network protocols, enabling for
booting and other functions,
SRM, 5-46

O
OCP display, control panel, 1 -22
ocp_text environment variable, SRM,
5-26, 5-41, 5-48
OpenVMS
booting, 2-16 to 2-21
from cluster disk, 2-18
from local disk, 2-16
from remote disk, 2-20
console for, 5-1
installing, 2-22
specifying as default operating
system, 5-49
Operating system
booting DIGITAL UNIX, 2-8 to
2-13
from cluster disk, 2-10
from local disk, 2-8
from remote disk, 2-12
booting OpenVMS, 2-16 to 2-21
from cluster disk, 2-18
from local disk, 2-16
from remote disk, 2-20
booting Windows NT, 2-24
installing DIGITAL UNIX, 2-14
installing OpenVMS, 2-22
installing Windows NT, 2-26,
6-36
specifying default, 5-49
Operating system selection setup
screen, AlphaBIOS, 6-44
Operating system selection, defined,
6-41

Index-5

Operating system selections screen,
AlphaBIOS, 6-40
Operating the system remotely, 2 -47
Operation, system drawer, 2 -1
Options
EISA, 4-12
PCI, 4-12
os_type environment variable, SRM,
2-7, 2-25, 5-26, 5-41, 5-49,
6-35

P
PALcode, 2-7
Parameters, configuring in
AlphaBIOS console, 6-32
Password, setting in AlphaBIOS
console, 6-35
PCI
enabling and disabling parity
checking on bus, SRM,
5-49
finding device information,
AlphaBIOS, 6-16
parity checking in AlphaBIOS,
6-35
PCI bridge module, 1-5, 1-16
PCI card cages, 1-7
PCI configuration screen,
AlphaBIOS, 6-14
PCI motherboard, 1-18
PCI options
installing, 4-12
slot numbers, 4-12, 4-13
pci_parity environment variable,
SRM, 5-41, 5-49
PCM, 1-14
Pedestal
exposing system drawer, 4-2
removing cover, 4-2
removing door, 4-2
tray removal, 4-3
pk*0_fast environment variable,
SRM, 5-41, 5-50
pk*0_host_id environment variable,
SRM, 5-41, 5-50

Index-6

pk*0_soft_term environment
variable, SRM, 5-41, 5-51
Potentiometer, control panel display,
1-23
Power
system drawer does not power
up, 3-2
Power button, 2-2
Power button, control panel, 1 -22
Power control module, 1-9, 1-14
LEDs, 3-3, 4-18
Power supplies, 1-7
Power supply, 1-24
configuring, 1-25
installing, 4-16
Power system cabling, 4-16
Powering up the system drawer, 2 -2
poweroff command, RCM, 2-56
poweron command, RCM, 2-57
Power-up display, 2-4
Power-up, specifying console action,
SRM, 5-42
prcache command, SRM, 5 -16, 5-35
Primary operating system,
AlphaBIOS, 6-42
Processor
enabling and disabling specific
CPUs, 5-45
Processor module, 1-5, 1-9, 1-10
configuring, 1-11
installing, 4-8
LEDs, 3-4
slot numbers, 4-8

Q
quit command, RCM, 2 -57

R
RAID devices, configuring, 5-17
RCM, 1-20, 2-47
command summary, 2-52
dial-out alerts, 2-62
entering and leaving command
mode, 2-51
modem dialog details, 2 -69

modem usage, 2-48
resetting to factory defaults, 2 -65
troubleshooting, 2-66
typical dialout command, 2 -62
RCM commands
?, 2-56
alert_clr, 2-54
alert_dis, 2-54
alert_ena, 2-54
disable, 2-55
enable, 2-55
halt, 2-56
hangup, 2-55
help, 2-56
poweroff, 2-56
poweron, 2-57
quit, 2-57
reset, 2-58
setesc, 2-58
setpass, 2-59
status, 2-60
Reading a file, 5 -31
readme command, LFU, 2 -44, 2-46
Remote console monitor. See RCM
Reset button, control panel, 1 -22
reset command, RCM, 2 -58
Reset, specifying console action,
SRM, 5-42
Running maintenance programs,
AlphaBIOS, 6-38
Running utility programs, 6 -38

S
S-cache, 2-5
SCM, 1-20
SCSI
enabling and disabling
terminators, SRM, 5-51
enabling Fast SCSI, SRM, 5-50
Setting controller host bus node
ID, SRM, 5-50
SCSI configuration screen,
AlphaBIOS, 6-18
serial environment variable, SRM,
2-5

Serial terminal, specifying as console
terminal, SRM, 5-45
Server control module. See SCM
set envar command, SRM, 5-25,
5-26, 5-36
set host command, SRM, 5-14, 5-36
setesc command, RCM, 2 -58
setpass command, RCM, 2-59
Setting an environment variable, 5 -26
Setting up the hard disk, AlphaBIOS,
6-26
Setup screen, AlphaBIOS, 6-5
show config command, SRM, 5-4,
5-36
show cpu command, SRM, 5-5, 5-36
show device command, SRM, 2 -8,
2-9, 2-13, 2-16, 2-17, 2-19,
2-21, 5-6, 5-21, 5-36
show envar command, SRM, 2-16,
5-25, 5-26, 5-36
show fru command, SRM, 5-8, 5-36
show memory command, SRM, 5-9,
5-36
show network command, SRM, 5-9,
5-21, 5-36
show pal command, SRM, 5-10, 5-36
show power command, SRM, 1-25,
5-10, 5-36
show version command, SRM, 5-11,
5-36
Special characters, SRM console,
5-38
SRM console, 2-7, 5-1 to 5-52
command syntax, 5-37
device naming conventions, 5 -7
special characters, 5 -38
summary of commands, 5-35
summary of environment
variables, 5-40
switching from AlphaBIOS, 6-2,
6-35
switching to AlphaBIOS, 5-2
SRM console commands
alphabios, 5-2, 5-35

Index-7

boot, 2-9, 2-11, 2-13, 2-15, 2-17,
2-21, 2-23, 5-12, 5-21,
5-35
clear envar, 5-35
continue, 5-20, 5-21, 5-35
crash, 5-24, 5-35
deposit, 5-28, 5-29, 5-35
edit, 5-27, 5-35
examine, 5-28, 5-29, 5-35
halt, 5-20, 5-21, 5-35
help, 5-34, 5-35
initialize, 5-27, 5-32, 5-33, 5-35
lfu, 2-29, 5-21, 5-22, 5-35
man, 5-34, 5-35
more, 5-31, 5-35
prcache, 5-16, 5-35
set envar, 5-25, 5-26, 5-36
set host, 5-14, 5-36
show config, 5-4, 5-36
show cpu, 5-5, 5-36
show device, 2-9, 2-13, 2-17,
2-19, 2-21, 5-6, 5-21,
5-36
show envar, 5-25, 5-26, 5-36
show fru, 5-8, 5-36
show memory, 5-9, 5-36
show network, 5-9, 5-21, 5-36
show pal, 5-10, 5-36
show power, 1-25, 5-10, 5-36
show version, 5-11, 5-36
start, 5-20, 5-21, 5-36
stop, 5-21, 5-36
summary of commands, 5-35
test, 5-18, 5-19, 5-21, 5-36
SRM console environment variables
auto_action, 5-40, 5-42
boot_osflags, 5-40, 5-43, 5-44
boot_osflags, DIGITAL UNIX,
5-43
boot_osflags, OpenVMS, 5-43
bootdef_dev, 5-40
com*_baud, 5-40, 5-44
commands for displaying the
value or setting, 5-26
commands for modifying, 5-26

Index-8

commands for setting, 5-26
commands for using, 5-25
console, 2-25, 5-45
console, 5-40
cpu_enabled, 5-40, 5-45
displaying the value or setting,
2-11
ew*0_mode, 5-40, 5-46
ew*0_protocols, 5-40, 5-46
kbd_hardware_type, 5-40, 5-47
kzpsa*_host_id, 5-40, 5-47
language, 5-40, 5-47
memory_test, 5-40, 5-48
ocp_text, 5-41, 5-48
os_type, 2-25, 5-41, 5-49, 6-35
pci_parity, 5-41, 5-49
pk*0_fast, 5-41, 5-50
pk*0_host_id, 5-41, 5-50
pk*0_soft_term, 5-41, 5-51
tga_sync_green, 5-41, 5-51
tt_allow_login, 5-41, 5-52
SRM firmware
enabling and disabling login to,
5-52
SROM, 2-5
Standard CMOS setup screen,
AlphaBIOS, 6-32
Standard I/O, 1-20
start command, SRM, 5-20, 5-21,
5-36
Starting AlphaBIOS, 6-4
Starting CPUs, 5-20
status command, RCM, 2-60
stop command, SRM, 5-21, 5-36
Stopping CPUs, 5-20
Syntax
SRM console commands, 5-37
System board configuration screen,
AlphaBIOS, 6-10
System bus, 1-5
System bus configuration screen,
AlphaBIOS, 6-20
System bus to PCI bus bridge module,
1-5, 1-16
System card cage, 1-7

System configuration
displaying in AlphaBIOS
console, 6-8
displaying in SRM console, 5-4
System crash dump, 5-24
System drawer
electrical and environmental
parameters, 1-3
architecture, 1-4
characteristics, 1-2
does not power up, 3-2
exposing in cabinet, 4 -4
exposing in pedestal, 4-2
operation, 2-1
overview, 1-1
parts of, 1-6
powering up, 2-2
power-up display, 2-4
remote operation, 2 -47
removing covers, 4-6
upgrading, 4-20
System failure, specifying console
action, SRM, 5-42
System motherboard, 1-5, 1-8

T
Terminal, console, 1 -26
test command, SRM, 5-18, 5-19,
5-21, 5-36
Testing the system (all operating
systems), 5-18
tga_sync_green environment variable,
SRM, 5-41, 5-51
Time, setting in AlphaBIOS console,
6-33
Tray removal
pedestal, 4-3
Troubleshooting, 3-1
tt_allow_login environment variable,
SRM, 5-41, 5-52

U
Update AlphaBIOS command, 2-29
update command, LFU, 2 -29, 2-33,
2-39, 2-43, 2-44, 2-46
Updating firmware
AlphaBIOS console, 6-24
from AlphaBIOS console, 2-28
from SRM console, 2-28
SRM console, 5-22
Upgrade procedure, system drawer,
4-20
Utility programs, 6-38
running from graphics monitor,
7-2
running from serial terminal, 7 -4

V
Vaux, 1-25
verify command, LFU, 2 -44, 2-46
Version selection, Windows NT, 6 -40

W
Windows NT
auto start, 6-44
booting, 2-24
console for, 6-1
designating primary operating
system, 6-42
installing, 2-26, 6-36
selecting version, 6-40
specifying as default operating
system, 5-49
starting, 6-44
starting automatically, 6 -33

X
XSROM, 2-5

Index-9