Digital PDFs

EK-DS10V-CR-A01

May 1999

214 pages

Original

0.9MB

Document:	AlphaStation XP900 Console Reference
Order Number:	EK-DS10V-CR
Revision:	A01
Pages:	214
Original Filename:

OCR Text

AlphaStation XP900
Console Reference
Order Number: EK–DS10V–CR. A01

This manual describes the general operations of the AlphaStation
XP900 system. It presents the SRM console (the command-line
interface for Tru64 UNIX and OpenVMS operating systems),
AlphaBIOS (the graphics interface for Windows NT and Linux),
and remote console management.

Compaq Computer Corporation

Notice
The information in this publication is subject to change without notice.
COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR
EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING,
PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED
“AS IS” AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE,
GOOD TITLE AND AGAINST INFRINGEMENT.
This publication contains information protected by copyright. No part of this publication may be
photocopied or reproduced in any form without prior written consent from Compaq Computer
Corporation.
© 1999 Compaq Computer Corporation.
All rights reserved. Printed in the U.S.A.
The software described in this guide is furnished under a license agreement or nondisclosure
agreement. The software may be used or copied only in accordance with the terms of the
agreement.
AlphaStation, Compaq, Deskpro, Fastart, Compaq Insight Manager, Systempro, Systempro/LT,
ProLiant, ROMPaq, QVision, SmartStart, NetFlex, OpenVMS, QuickFind, PaqFax, ProSignia,
registered United States Patent and Trademark Office.
Netelligent, Systempro/XL, SoftPaq, QuickBlank, QuickLock are trademarks and/or service
marks of Compaq Computer Corporation.
Linux is a registered trademark of Linus Torvalds in serveral countries. Microsoft, Windows,
and Windows NT are registered trademarks of Microsoft Corporation.
Other product names mentioned herein may be trademarks and/or registered trademarks of their
respective companies.

Warning!
This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may be required to take adequate measures.
Achtung!
Dieses ist ein Gerät der Funkstörgrenzwertklasse A. In Wohnbereichen können bei Betrieb
dieses Gerätes Rundfunkstörungen auftreten, in welchen Fällen der Benutzer für
entsprechende Gegenmaßnahmen verantwortlich ist.
Attention!
Ceci est un produit de Classe A. Dans un environnement domestique, ce produit risque de
créer des interférences radioélectriques, il appartiendra alors à l’utilisateur de prendre les
mesures spécifiques appropriées.

This equipment generates, uses, and may emit radio frequency energy. The equipment has
been type tested and found to comply with the limits for a Class A digital device pursuant to
Part 15 of FCC rules, which are designed to provide reasonable protection against such radio
frequency interference.
Operation of this equipment in a residential area may cause interference in which case the
user at his own expense will be required to take whatever measures may be required to
correct the interference.
Any modifications to this device - unless expressly approved by the manufacturer - can void
the user’s authority to operate this equipment under part 15 of the FCC rules.

Contents

Preface
Chapter 1
1.1
1.2
1.3
1.3.1
1.3.2
1.4
1.5
1.5.1
1.5.2
1.5.3
1.6
1.7
1.8
1.9
1.9.1
1.9.2
1.10
1.10.1
1.10.2
1.10.3
1.10.4
1.10.5
1.11
1.11.1
1.11.2
1.11.3
1.12
1.13

xiii
Operations
Powering Up the System
Power-Up Display
Booting Tru64 UNIX
Booting from a Local Disk
Booting from a Remote Disk
Installing Tru64 UNIX
Booting OpenVMS
Booting OpenVMS from a Local Disk
Booting OpenVMS from a Disk on a Cluster
Booting OpenVMS from a Remote Disk
Installing OpenVMS
Booting Windows NT
Installing Windows NT
Switching Between Operating Systems
Switching to Windows NT
Switching to Tru64 UNIX or OpenVMS
Updating Firmware
Updating Firmware from the CD-ROM
Updating Firmware from Floppy Disks
Performing the Update from Floppy Disks
Updating Firmware from a Network Device
LFU Commands
Hard Disk Partitioning for Windows NT
Hard Disk Error Conditions
System Partitions
How AlphaBIOS Works with System Partitions
Using the Halt Button
Halt Assertion

1-2
1-4
1-6
1-6
1-8
1-10
1-12
1-12
1-14
1-16
1-18
1-20
1-22
1-24
1-24
1-25
1-26
1-28
1-32
1-34
1-38
1-41
1-44
1-44
1-46
1-47
1-48
1-51

Chapter 2
2.1
2.2
2.2.1
2.2.2
2.2.3
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.4
2.5
2.6
2.7
2.8
2.8.1
2.8.2
2.9
2.9.1
2.9.2
2.9.3
2.10
2.11
2.12
2.13
2.13.1
2.13.2
2.14
2.15
2.16
2.17
2.18
2.19
2.19.1
2.19.2
2.19.3
2.19.4
2.19.5

SRM Console
Invoking the SRM Console
Commands
Command Summary
Commands: Syntax
Commands: Special Keystrokes and Characters
Show Commands
Show Config
Show Device
Show Memory
Show PAL
Show Power
Show Version
Creating a Power-Up Script
Booting the Operating System
Configuring a PCI NVRAM Module
Testing the System
Set Commands
Set Password
Set Secure
Secure Mode
Login Command and Secure Mode
Clear Password
Resetting the Password
Stopping and Starting CPU
Updating Firmware
Forcing a System Crash Dump
Using Environment Variables
Set envar
Show envar
Depositing and Examining Data
Reading a File
Initializing the System
Finding Help
Switching from SRM to AlphaBIOS Console
Environment Variable Summary
auto_action
bootdef_dev
boot_osflags
com1_baud
com1_mode

2-2
2-3
2-3
2-5
2-6
2-8
2-8
2-10
2-12
2-12
2-13
2-14
2-14
2-16
2-18
2-19
2-23
2-23
2-24
2-25
2-25
2-26
2-27
2-28
2-28
2-30
2-31
2-31
2-32
2-33
2-34
2-35
2-36
2-37
2-38
2-40
2-40
2-41
2-43
2-43

2.19.6
2.19.7
2.19.8
2.19.9
2.19.10
2.19.11
2.19.12
2.19.13
2.19.14
2.19.15
2.19.16
2.19.17

Chapter 3
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.4
3.5
3.5.1
3.5.2
3.6
3.7
3.8
3.9
3.9.1
3.9.2
3.10
3.11
3.11.1
3.11.2

console
ew*0_mode
ew*0_protocols
kbd_hardware_type
language
os_type
password
pci_parity
pk*0_fast
pk*0_host_id
pk*0_soft_term
tt_allow_login

2-44
2-45
2-45
2-46
2-46
2-47
2-47
2-48
2-48
2-49
2-49
2-50

AlphaBIOS Console
Starting AlphaBIOS
Keyboard Conventions and Help
System Configuration
Displaying the System Configuration
System Board Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
Memory Configuration
Integrated Peripherals
Updating Firmware
Setting Up the Hard Disk
Creating and Deleting Partitions Manually
Formatting a FAT Partition
Performing Setup Tasks
Installing Operating System
Selecting the Version of Windows NT
Designating a Primary Operating System
Selecting a Primary Operating System
Primary Operating System and the Auto Start Option
Switching from AlphaBIOS to SRM Console
Running Utility Programs
Running Utilities from a Graphics Monitor
Running Utilities from a Serial Terminal

3-2
3-4
3-6
3-6
3-8
3-10
3-12
3-15
3-17
3-18
3-19
3-21
3-24
3-26
3-28
3-32
3-34
3-36
3-36
3-38
3-42
3-44
3-45
3-46

vii

Chapter 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
4.14
4.14.1
4.14.2
4.14.3
4.14.4
4.14.5
4.14.6
4.14.7
4.14.8
4.14.9
4.14.10
4.14.11
4.14.12
4.14.13
4.14.14
4.14.15
4.14.16
4.14.17
4.14.18
4.14.19
4.14.20
4.14.21
4.14.22
4.14.23
4.14.24

viii

Remote Console Manager
RMC Components
Terminal Setup
Operating Modes
Entering the RMC
SRM Environment Variables for COM1
Status Monitoring
Remote Power (On/Off)
Remote Halt (In/Out)
Configuring Remote Dial-In
Configuring Dial-Out Alert
Dialing In
Resetting the RMC to Factory Defaults
Troubleshooting Tips
RMC Commands
clear alert
clear port
disable alert
disable remote
enable alert
enable remote
halt (in/out)
hangup
help or ?
power off
power on
quit
reset
send alert
set alert
set com1_mode
set dial
set escape
set init
set logout
set password
set user
set wdt
status

4-2
4-3
4-4
4-6
4-6
4-7
4-9
4-10
4-12
4-14
4-17
4-18
4-19
4-21
4-23
4-23
4-23
4-24
4-24
4-25
4-26
4-27
4-27
4-27
4-28
4-28
4-29
4-29
4-30
4-31
4-32
4-33
4-34
4-35
4-35
4-36
4-36
4-36

Appendix A
A.1
A.2
A.3
A.4
A.5
A.6

Setting Jumpers

Warnings and Cautions ........................................................................ A-2
Remove Power from the System ........................................................... A-3
Open the System ................................................................................... A-4
Remove the Floppy Disk Enclosure ...................................................... A-5
Set Jumpers .......................................................................................... A-6
Restore Power ....................................................................................... A-8

Examples
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
1–14
1–15
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

Power-Up Display ..................................................................................1-4
Booting Tru64 UNIX from a Local Disk ................................................1-6
Booting Tru64 UNIX from a Remote Disk .............................................1-8
Installing Tru64 UNIX.........................................................................1-10
Booting OpenVMS from a Local Disk ..................................................1-12
Booting OpenVMS from a Disk on a Cluster .......................................1-14
Booting OpenVMS from a Remote Disk...............................................1-16
Installing OpenVMS ............................................................................1-18
Starting LFU from the SRM Console...................................................1-26
Booting LFU from the CD-ROM ..........................................................1-27
Updating Firmware from the CD-ROM ...............................................1-28
Creating Update Diskettes on an OpenVMS System ..........................1-33
Updating Firmware from the Floppy Disk ..........................................1-34
Selecting DS10FW to Update Firmware from Internal Floppy Disk ....1-37
Updating Firmware from a Network Device........................................1-38
Show Config Command ..........................................................................2-8
Show Device Command........................................................................2-10
Show Memory Command .....................................................................2-12
Show PAL Command ...........................................................................2-12
Show Power Command ........................................................................2-13
Show Version Command ......................................................................2-14
Editing the nvram Script .....................................................................2-15
Clearing the nvram Script ...................................................................2-15
Boot Command.....................................................................................2-17
Prcache Command ...............................................................................2-18
Test Command .....................................................................................2-19
Set Password Command ......................................................................2-23
Set Secure Command ...........................................................................2-24
Secure Mode and Login Command ......................................................2-26
Clear Password Command...................................................................2-26

2–16
2–17
2–18
2–19
2–20
2–21
2–22
2–23
2–24
2–25
2–26
4–1
4–2

Lfu Command.......................................................................................2-28
Crash Command ..................................................................................2-30
Setting and Showing Environment Variables......................................2-32
Creating a User-Defined Environment Variable .................................2-32
Deposit Command................................................................................2-33
Examine Command..............................................................................2-33
More Command....................................................................................2-34
Initialize Command..............................................................................2-35
Help Command ....................................................................................2-36
Switching to the AlphaBIOS Console ..................................................2-37
Changing Baud Rate ............................................................................2-43
Dial-In Configuration...........................................................................4-12
Dial-Out Alert Configuration ...............................................................4-14

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

Check Power Setting ..............................................................................1-2
Location of Control Panel and On/Off Button........................................1-3
Physical Numbering for PCI Slots .........................................................1-4
AlphaBIOS Boot Screen .......................................................................1-20
Installing Windows NT ........................................................................1-22
Starting LFU from the AlphaBIOS Console .......................................1-26
System Partition Not Defined..............................................................1-47
Halt/Reset Button ................................................................................1-48
Halt/Reset Jumper ...............................................................................1-49
Boot Screen ............................................................................................3-2
AlphaBIOS Setup Screen .......................................................................3-3
Typical First-Level Help Screen ............................................................3-4
Second-Level Help Screen......................................................................3-5
Display System Configuration Screen ...................................................3-6
System Board Configuration..................................................................3-8
Hard Disk Configuration .....................................................................3-10
PCI Configuration ................................................................................3-12
PCI Slots ..............................................................................................3-13
Advanced PCI Information ..................................................................3-14
SCSI Configuration ..............................................................................3-15
Memory Configuration .........................................................................3-17
Integrated Peripherals.........................................................................3-18
Updating Firmware .............................................................................3-19
Hard Disk Setup Screen.......................................................................3-21
Create New Partition Dialog Box.........................................................3-24

3–17
3–18
3–19
3–20
3–21
3–22
3–23
3–24
3–25
3–26
3–27
3–28
4–1
4–2
4–3
4–4
4–5
4–6
4–7
A–1
A–2
A–3
A–4
A–5

Delete Partition Dialog Box .................................................................3-25
Formatting a FAT Partition.................................................................3-26
Standard Formatting ...........................................................................3-27
Standard CMOS Setup Screen.............................................................3-28
Advanced CMOS Setup Screen ............................................................3-30
Installing Windows NT ........................................................................3-32
Operating System Selections ...............................................................3-34
Primary Operating System ..................................................................3-36
Operating System Selection Setup.......................................................3-38
Switching to the SRM Console.............................................................3-42
Run Maintenance Program Dialog Box ...............................................3-44
AlphaBIOS Utilities Menu...................................................................3-45
Location of RMC Components on Motherboard .....................................4-2
Setups for RMC Mode ............................................................................4-3
Bypass Mode ..........................................................................................4-4
Power Button .........................................................................................4-9
Halt/Reset Jumper ...............................................................................4-10
Halt/Reset Button ................................................................................4-11
RMC Jumpers (Default Positions) .......................................................4-18
Removing Power from the System ........................................................ A-3
Opening the System Cabinet ................................................................ A-4
Removing the Floppy Disk Enclosure ................................................... A-5
Setting Jumpers on the Motherboard ................................................... A-6
Restoring Power .................................................................................... A-8

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

Documentation .......................................................................................xiv
Control Panel Functions ........................................................................1-3
File Locations for Creating Update Diskettes on a PC........................1-32
LFU Command Summary ....................................................................1-41
Summary of SRM Console Commands ..................................................2-3
Syntax for SRM Console Commands .....................................................2-5
Special Characters for SRM Console .....................................................2-6
Device Naming Convention..................................................................2-11
PCI Address Assignments....................................................................2-11
Environment Variable Summary.........................................................2-38
Settings for boot_osflags Bootflags (OpenVMS)...................................2-42
AlphaBIOS Option Key Mapping.........................................................3-46
SRM Environment Variables for COM1 ................................................4-6
Status Command Fields.........................................................................4-7

4–3
4–4
4–5
A–1

xii

Halt/Reset Button Function under Operating Systems.......................4-11
Elements of Dial String and Alert String ............................................4-16
RMC Troubleshooting ..........................................................................4-19
Jumpers and Factory Default Positions................................................ A-7

Preface
Intended Audience
This manual is for anyone who manages, operates, or services an AlphaStation
XP900 system.

Document Structure
This manual uses a structured documentation design. Topics are organized into
small sections for efficient reference. Each topic begins with an abstract. You
can quickly gain a comprehensive overview by reading only the abstracts. Next
is an illustration, table, or example, also providing quick reference. Last in the
structure are descriptive text and syntax definitions.
This manual has four chapters, one appendix, and an index:
•

Chapter 1, Operations, provides basic operating instructions, including
powering up the system, booting, and operating system installation.

•

Chapter 2, SRM Console, presents the command-line interface that
supports the Tru64 UNIX and OpenVMS operating systems. (NT uses the
SRM test command, only.) The SRM console is used to bootstrap the
operating system, configure and test the system hardware, examine system
options for errors, and set or change environment variables.

•

Chapter 3, AlphaBIOS Console, details 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.

•

Chapter 4, Remote Management Console, describes how to manage the
system from a remote location.

•

Appendix A, Setting System Jumpers, describes how to check and reset
if necessary the Halt/Reset select jumper and remote management console
jumper.

xiii

Conventions
In examples of SRM console output, commands the user enters are presented in
boldface type, while the system’s output is in regular type. Comments on the
examples are either called out with circled numbers (➊➋➌) or are preceded by a
pound sign (#) and are given in boldface italics.

NOTE: Screens and printouts shown throughout this Guide are for example
only; the actual system name and other information may vary.

Documentation Titles
This lists the AlphaStation XP900 documentation.

Table 1 AlphaStation XP900 Documentation
Title

Order No.

Console Reference Guide

EK-DS10V-CR

Maintenance/Service Guide

AK-DS10S-MS

Safety Booklet

296382-021

User Reference Card

EK-DS10V-UR

Quick Setup Poster

EK-DS10V-CP

xiv

Chapter 1
Operations

This chapter provides basic operating instructions, including powering up the
system, booting, and operating system installation. Note that your choice of
operating system has already been installed at the factory; this information is
provided so that should you decide to change operating systems, you may. It
also provides information about updating firmware.
Sections in this chapter are:
•

Powering Up the System

•

Power-Up Display

•

Booting Tru64 UNIX

•

Installing Tru64 UNIX

•

Booting Open VMS

•

Installing OpenVMS

•

Booting Windows NT

•

Installing Windows NT

•

Switching Between Operating Systems

•

Updating Firmware

•

Hard Disk Partitioning for Windows NT

•

Using the Halt Button

•

Halt Assertion

Operations 1-1

1.1

Powering Up the System
To power up the system, check your power setting (see Figure 1–
1). Then press the On/Off button to the On position (Figure 1–2).
The button is in the lower right hand corner of the front of the
system. Check the control panel LEDs.

Figure 1–1 Check Power Setting

115V

230V

PK1047a

1-2

XP900 Console Reference

Figure 1–2 Location of Control Panel and On/Off Button

PK1043b

Table 1–1 Control Panel Functions
Symbol

Function
Halt button. Under OpenVMS and Tru64 UNIX, suspends the operating
system and returns control to the SRM console. Under Windows NT, this
button initiates a system reset.
Environmental amber LED. On indicates Temperature or Fan LEDs are
on. Flashes when operating system invokes it as an alert.
Temperature amber LED. On indicates internal temperature exceeds
operating conditions. The system shuts down 30 seconds after this LED
lights.
Fan amber LED. On indicates that at least one of the three fans in the
system has failed. The system shuts down 30 seconds after this LED lights.
Disk Activity green LED. Flashes when internal system disks are
accessed.
Power Present green LED. On when power is present in the system.
Power button. Push in to start the system and connect power. Push again
to remove power and stop the system.

Operations 1-3

1.2

Power-Up Display
Testing begins after pressing the On/Off button, and screen text
similar to that in Example 1–1 displays (if the console terminal is
a serial terminal connected to the COM1 port), along with status
messages in the control panel display. If the console terminal is
a graphics monitor, only the last few lines of the power-up
display print.

Example 1–1 Power-Up Display
256 Meg of system memory ➊
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1 ➋
probing PCI-to-PCI bridge, bus 2 ➋
bus 0, slot 9 -- ewa -- DE500-BA Network Controller
bus 0, slot 11 -- ewb -- DE500-BA Network Controller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
bus 0, slot 14 ➌-- vga -- DEC PowerStorm
bus 2,➍slot 0 -- pka -- NCR 53C875
bus 2,➍slot 1 -- pkb -- NCR 53C875
bus 2,➍slot 2 -- ewc -- DE500-AA Network Controller
bus 0,➎ slot 16 -- pkc -- QLogic ISP1020
bus 0,➏ slot 17 -- dra -- Mylex DAC960
Testing the System
Testing the Disks (read only)

>>> ➐

Figure 1–3 Physical Numbering for PCI Slots

PCI Slot 4

64 Bit

PCI Slot 3

64 Bit

PCI Slot 2

64 Bit

PCI Slot 1

32 Bit

PK1045-99

1-4

XP900 Console Reference

➊
➋

Memory size is determined.

➌

Power-up slot 14 corresponds to the bottom physical slot, slot 0. See Figure
1–3.

The PCI bridges and attendant buses (indicated as IODn by the console)
are probed and the devices are reported. I/O adapters are configured.

Slot Location

Physical Slot Number

Logical Slot Number

Top

Second from top

Second from bottom

Bottom

➍

These devices are behind bridge of the card in logical slot 15, physical slot
1, second from the bottom.

➎
➏
➐

This device in is logical slot 16, physical slot 3.
Logical slot 17 is physical slot 4, the top slot.
The SRM console banner and prompt (>>>) are printed.
The SRM console is a command-line interface you use to set or read system
parameters.
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 Tru64 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.
See Section 2.19 for information on environment variables. See Chapter 2
for SRM console, and Chapter 3 for AlphaBIOS information.

Operations 1-5

1.3

Booting Tru64 UNIX
Tru64 UNIX® can be booted from a local disk or a remote disk
through an Ethernet connection. Refer to the documentation
shipped with the operating system for booting instructions.

1.3.1

Booting from a Local Disk

Example 1–2 Booting Tru64 UNIX from a Local Disk
>>> sho device ➊
dka100.1.0.2000.0
dka300.3.0.2000.0
dka500.5.0.2000.0
dkb0.0.0.2001.0
dkb200.2.0.2001.0
dkb400.4.0.2001.0
dkc0.0.0.16.0
dkc200.2.0.16.0
dqa1.1.0.13.0
dra1.0.0.17.0
dra2.0.0.17.0
dva0.0.0.0.0
ewa0.0.0.9.0
ewb0.0.0.11.0
ewc0.0.0.2002.0
pka0.7.0.2000.0

DKA100
DKA300
DKA500
DKB0
DKB200
DKB400
DKC0
DKC200
DQA1
DRA1
DRA2
DVA0
EWA0
EWB0
EWC0
PKA0

RZ1CB-CA
RZ1CB-CA
RZ1EF-AB
RZ1CB-CA
RZ1DB-CS
RZ1CB-CA
RZ1CB-BA
RZ1CB-BA
CD-532E
1 Member JBOD
1 Member JBOD
08-00-2B-86-1B-BA
08-00-2B-86-1B-BB
00-06-2B-00-26-1C
SCSI Bus ID 7

>>> boot -file vmunix -flags a dkc0
(boot dkc0.0.0.9.0 -file vmunix -flags a)
block 0 of dkc0.0.0.9.0 is a valid boot block
reading 16 blocks from dkc0.0.0.9.0
bootstrap code read in
base = 1ee000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1fff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

➌

Tru64 UNIX boot - Fri Aug 7 20:30:19 EDT 1999
Loading vmunix ...
. . .
The system is ready.
Tru64 UNIX Version V4.0E (sabl28.eng.pko.dec.com) console
login:

1-6

XP900 Console Reference

LYJ0 ➋
LYJ0
0370
LYJ0
0307
LYJ0
LYG0
LYG0
1.0A

************************************************************************
* Starting Desktop Login on display :0...
* Wait for the Desktop Login screen before logging in.
➍
************************************************************************

➊

The show device command displays device information, including
name and type of connection to the system. See Section 2.3.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 the PCI. The name of this device,
dkc0, is used as an argument to the boot command.

➌

This command loads Tru64 UNIX from the disk dkc0, using the boot
file vmunix and autobooting to multiuser mode. See Section 2.5 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 2.19
for information about environment variables.

➍

The operating system banner displays.

Operations 1-7

1.3.2

Booting from a Remote Disk

Example 1–3 Booting Tru64 UNIX from a Remote Disk
>>> show device
. . .
ewa0.0.0.8.0

➊
EWA0

08-00-2B-E2-9C-60

>>>
>>> boot -flags an -protocols bootp ewa
(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 1999
Loading vmunix ...
.
.
.
The system is ready.
Tru64 UNIX Version V4.0E (sabl28.eng.pko.dec.com) console

1-8

XP900 Console Reference

➍

➊

➋

The operating system is on a remote disk accessed through the
Ethernet controller in slot 4 of the PCI. The name of this device,
ewa0, is used as an argument to the boot command.

➌

This command loads Tru64 UNIX from ewa0, autobooting to
multiuser mode. See Section 2.5 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 2.19
for information about environment variables.

➍

The operating system banner displays.

Operations 1-9

1.4

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

Example 1–4 Installing Tru64 UNIX
>>> show device
. . .
dka500.5.0.7.1

DKA500

RRD47

1337 ➊

. . .
>>>

➊

>>> boot dka500
(boot dka500.5.0.7.1 -flags A)
block 0 of dka500.5.0.7.1 is a valid boot block
reading 16 blocks from dka500.5.0.7.1
bootstrap code read in
base = 1ee000, image_start = 0, image_bytes = 2000
initializing HWRPB at 2000
initializing page table at 1fff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
Tru64 UNIX boot - Thu Jul 16 16:59:31 EDT 1999
Loading vmunix ...
.
.
.
INIT: SINGLE-USER MODE
Initializing system for Tru64 UNIX installation.

Please wait...

*** Performing CDROM Installation
Loading installation process and scanning system hardware.
[The “Welcome to the Tru64 UNIX Installation Procedure” appears.] ➋

1-10 XP900 Console Reference

➊

Use the boot command to install the operating system from the CDROM, which is either dka500 or dqa0.

➋

See your operating system documentation for further installation
instructions.

Operations 1-11

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

1.5.1

Booting OpenVMS from a Local Disk

Example 1–5 Booting OpenVMS from a Local Disk

➊

>>> show device
. . .
dka200.2.0.7.1

DKA200

RZ1CB-CA

LYJ0

. . .
>>>

➋

>>> show boot_reset
boot_reset

>>> show bootdef_dev
bootdef_dev

dka200.2.0.7.1

➌

>>> boot
(boot dka200.2.0.7.1 -flags 0,0)
block 0 of dka200.2.0.7.1 is a valid boot block
reading 893 blocks from dka200.2.0.7.1
bootstrap code read in
base = 1fa000, image_start = 0, image_bytes = 6fa00
initializing HWRPB at 2000
initializing page table at 1fff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

➍

OpenVMS (TM) Alpha Operating System, Version 7.1-2
$!Copyright(c) 1999 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, OpenVMS startup begun at 30-JUL-1999 11:47:11.04
%MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving

Continued on next page

1-12 XP900 Console Reference

Example 1–5 Booting OpenVMS from a Local Disk (Continued)
. . .
The OpenVMS system is now executing the site-specific startup commands.
. . .
Welcome to OpenVMS (TM) Alpha Operating System, Version V7.1-2 ➎
Username:

➊

The show device command displays device information. See Section
2.3.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 1.2). See Section 2.19 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
dka200.2.0.7.1.

➍

No boot device is specified in the boot command; the default boot
device was set with the environment variable. See Section 2.5 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 2.19
for information about environment variables.

➎

The operating system banner displays.

Operations 1-13

1.5.2

Booting OpenVMS from a Disk on a Cluster

Example 1–6 Booting OpenVMS from a Disk on a Cluster

➊

>>> show bootdef_dev
bootdef_dev
dua110.0.0.8.0

➋

>>> show device

. . .
dua110.0.0.8.0

$1$DIA110 (DENVER)

RF74

➌

. . .
>>> boot

➍

(boot dua110.0.0.8.0 -flags 0)
Building FRU table
.
.
.
Welcome to OpenVMS Alpha (TM) Operating System, Version V7.1-2 ➎

1-14 XP900 Console Reference

➊

The bootdef_dev environment variable specifies the default boot
device.

➋

➌
➍

The disk dua110.0.0.8.0 is on the 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 2.5 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 2.19
for information about environment variables.

➎

The operating system banner prints.

Operations 1-15

1.5.3

Booting OpenVMS from a Remote Disk

Example 1–7 Booting OpenVMS from a Remote Disk
>>> show device
. . .
ewa0.0.0.8.0
EWA0
08-00-2B-E2-9C-60
. . .
>>>
>>> boot ewa0 -flags 0
(boot ewa0.0.0.2.0 -flags 0)
Building FRU table

➊
➊
➋

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

1-16 XP900 Console Reference

➊

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 2.3.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 2.5
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 2.19
for information about environment variables.

➌

The operating system banner prints.

Operations 1-17

1.6

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

Example 1–8 Installing OpenVMS
>>> boot -flags 0,0 dka500
Initializing...
SROM V3.0 on cpu0
.
. [The initialization display prints. See Section 1.2.]
.
AlphaStation XP900 Console V5.4-x, 2-APR-1999 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 7.1x

➋

%SMP-I-SECMSG, CPU #01 message: P01>>>START
%SMP-I-CPUBOOTED, CPU #01 has joined the PRIMARY CPU in multiprocessor operation
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.

Continued on next page

1-18 XP900 Console Reference

Example 1–8 Installing OpenVMS (Continued)
Please choose one of the following:
1)
2)
3)
4)
5)

Install or upgrade OpenVMS Alpha Version 7.1x
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 CDROM, which is either dka500 or dqa0.

➋

See your operating system documentation for installation
instructions.

Operations 1-19

1.7

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

Figure 1–4 AlphaBIOS Boot Screen
AlphaBIOS Setup
Display System
AlphaBIOS Upgrade…
Hard Disk Setup…
CMOS Setup…
Network Setup…
Install Operating System
Utilities
About AlphaBIOS…

Press ENTER to install Windows NT.

ESC = Exit

1-20 XP900 Console Reference

F1= Help

Two SRM environment variables must be set properly for Windows NT to boot.
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 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. Windows NT requires a graphics monitor as its console. Setting
the SRM console environment variable to graphics and having a graphics
monitor attached to your system meets this requirement. After setting these
two variables, you have to power-down and power-up your system for them to
take effect.
The method used for booting Windows NT is determined by the setting of Auto
Start in the AlphaBIOS Standard CMOS Setup screen (see Chapter 3).
•

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, though this setting is not necessary to run
AlphaBIOS. At the SRM console prompt, >>>:
>>> set console graphics

The Halt/Reset jumper on the motherboard must be set to the Windows NT
position for the Halt button to operate (see Section 1.12). If the Halt/Reset
jumper is set in the OpenVMS/Tru64 UNIX position, the Halt button will be
ignored by the Windows NT operating system and have no effect. Properly set,
the Halt button will initiate a system reset.

Operations 1-21

1.8

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

Figure 1–5 Installing Windows NT
AlphaBIOS Setup
Display System
AlphaBIOS Upgrade…
Hard Disk Setup…
CMOS Setup…
Network Setup…
Install Windows NT
Utilities
About AlphaBIOS…

F1= Help

Press ENTER to install Windows NT.

ESC = Exit

1-22 XP900 Console Reference

Windows NT requires a partitioned and formatted hard disk drive. If your
drive is not partitioned or formatted, follow the instructions in Section 3.5
before installing the Windows NT operating system.
Up to three 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. Use CMOS Setup to set the system date and time: start AlphaBIOS
Setup, select CMOS Setup, and press Enter.
2. Perform an express hard disk setup: return to the main AlphaBIOS Setup
screen, select Hard Disk Setup, and press Enter.
3.

Perform an express hard disk setup by pressing F7 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.
2. 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.

Operations 1-23

1.9

Switching Between Operating Systems
The system supports multiple operating systems on different
system and data disks not in the machine at the same time. That
is, you can have a set of disks for each operating system.

CAUTION: This operation is not for the faint hearted especially if you have a
shadow system disk and shadow arrays. The file structures of each
of the three operating systems are incompatible and therefore all
disks must be removed from the system and upon reinstallation
must be replaced in exactly the same physical locations. It is
therefore necessary to keep track of the location of each disk in the
system.

1.9.1

Switching to Windows NT

Use the following procedure:
1. Shut down the operating system and power off the system.
2. Remove and mark the physical location of each disk in the system.
3. Check your Halt/Reset jumper position (see Section 1.12).
4. Either place blank disks or your Windows NT disk set into the system. (If
you are placing a Windows NT disk set into the system, be sure that each
disk is replaced in the same physical location from which it was removed.)
5. Power on the system.
6. Enter the following commands at the SRM console prompt:
>>> set os_type nt
>>> init
7. Either install Windows NT, see Section 1.8, or at the AlphaBIOS boot
screen, start AlphaBIOS setup (F2), select CMOS Setup, and press Enter.
8. Set the system date and time.
9. In CMOS Setup, check that the setup for the floppy and other basic
parameters is accurate. Set system-specific parameters, such as the
memory test and password, in Advanced CMOS Setup as needed. Press
F10 to save the changes.

1-24 XP900 Console Reference

10. From the AlphaBIOS Setup screen select Utilities. In the selection box,
choose OS Selection Setup. Make sure the selections (boot name, boot
file, and so on) are what you want. Press F10 to save the changes.
11. Return to the boot screen and boot Windows NT.

1.9.2

Switching to Tru64 UNIX or OpenVMS

Use the following procedure:
1. Shut down the operating system and power off the system.
2. Remove and mark the physical location of each disk in the system.
3. Either place blank disks or your Tru64 UNIX or OpenVMS disk set into the
system. No matter which disk set you are placing into the system, be
sure that each disk is placed in the same physical location from
which it was removed.
4. Power on the system.
5. In AlphaBIOS, access the Advanced CMOS Setup screen and change the
Console Selection to Tru64 UNIX or OpenVMS (both use SRM) as
appropriate. Press F10 to save the change. This menu selection changes
the os_type environment variable to either UNIX or VMS so that the SRM
console does not load AlphaBIOS but remains in the system when you reset
the system.
6. Press the Halt/Reset button to reset the system.
7. Either install Tru64 UNIX (see Section 1.4) or OpenVMS (see Section 1.6) or
boot the operating system.

Operations 1-25

1.10 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 1–9 Starting LFU from the SRM Console
>>> 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 1–6 Starting LFU from the AlphaBIOS Console

PK1461-98

1-26 XP900 Console Reference

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 1–9). Also from the SRM console, LFU can be booted from the
Alpha CD-ROM (V5.4 or later), as shown in Example 1–10.

•

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

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 go back to the console.

The sections that follow show examples of updating firmware from the local CDROM, the local floppy, and a network device.

Example 1–10 Booting LFU from the CD-ROM
>>> show device
. . .
dka500.5.0.7.1
DKA500
RRD47 1645
. . .
>>> boot dka500
(boot dka500.5.0.7.1 -flags 0,0)
block 0 of dka500.5.0.7.1 is a valid boot block
..
jumping to bootstrap code
The default bootfile for this platform is
[DS10]DS10_LFU.EXE
Hit <RETURN> at the prompt to use the default bootfile.
Bootfile: <CR>
Starting Firmware Update Utility
***** Loadable Firmware Update Utility *****
...
UPD>

Operations 1-27

1.10.1

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

Example 1–11 Updating Firmware from the 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 [DS10FW]: DS10CP

➋

Copying DS10CP from DKA500.5.0.1.1 .
Copying [DS10]TCREADME from DKA500.5.0.1.1 .
Copying [DS10]TCSRMROM from DKA500.5.0.1.1 ....................
Copying [DS10]TCARCROM 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>

1-28 XP900 Console Reference

➊

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
Example 1–11, 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:
DS10FW (default)

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

DS10CP

SRM console and AlphaBIOS console firmware
only.

DS10IO

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.
Continued on next page

Operations 1-29

Example 1–11 Updating Firmware from the CD-ROM (Continued)

➍

UPD> list
Device
Fsb
Nt
Pkx0
Srm
Pua

Current Revision
Filename
3.1-x
fsb_fw
5.69
nt_fw
A11
kzpsa_fw
5.4-x
srm_fw
A214
cipca_fw

Update Revision
3.x
5.xx
A11
5.4-xx
A2xx

➎
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 V6.40-1... Verifying V6.40-1... PASSED.

Confirm update on: srmflash

[Y/(N)] y

srmflash

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

UPD> exit

➐

1-30 XP900 Console Reference

➍

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.

➎

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

Operations 1-31

1.10.2

Updating Firmware from Floppy Disks
Create two update diskettes before starting LFU: one for console
updates and one for I/O. See Section 1.10.3 for an example of the
update procedure.

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

I/O Update Diskette

DS10FW.TXT

DS10IO.TXT

DS10CP.TXT

TCREADME.SYS

CIPCA315.SYS

TCSRMROM.SYS

DFPAA310.SYS

TCARCROM.SYS

KZPAAA11.SYS

1. Download the update files from the Internet.
2. On a PC, copy files onto two FAT-formatted diskettes as shown
in Table 1–2.
3. From an OpenVMS system, copy files onto two ODS2-formatted diskettes as
shown in Example 1–12.

1-32 XP900 Console Reference

Example 1–12 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: tcods2cp
$ mount dva0: tcods2cp
$ create /directory dva0:[ds10]
$ copy tcreadme.sys dva0:[ds10]tcreadme.sys
$ copy DS10fw.txt dva0:[ds10]ds10fw.txt
$ copy DS10cp.txt dva0:[ds10]ds10cp.txt
$ copy tcsrmrom.sys dva0:[ds10]tcsrmrom.sys
$ copy tcarcrom.sys dva0:[ds10]tcarcrom.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: tcods2io
$ mount dva0: tcods2io
$ create /directory dva0:[ds10]
$ create /directory dva0:[options]
$ copy tcreadme.sys dva0:[ds10]tcreadme.sys
$ copy DS10fw.txt dva0:[ds10]ds10fw.txt
$ copy DS10io.txt dva0:[ds10]ds10io.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

Operations 1-33

1.10.3

Performing the Update from Floppy Disks
Insert an update diskette (see Section 1.10.2) into the floppy
drive. Start LFU and select dva0 as the load device.

Example 1–13 Updating Firmware from the 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 [DS10IO,(DS10CP)]: DS10IO ➋
Copying DS10IO from DVA0 .
Copying TCREADME 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 1–11.]

➌

UPD> list
Device
Fsb
Nt
Pkx0
Srm
Pua

Current Revision
3.1-x
5.69
A11
5.4-x
A214

Filename
fsb_fw
nt_fw
kzpsa_fw
srm_fw
cipca_fw

Update Revision
3.x
5.xx
A11
5.4-xx
A2xx

Continued on next page

1-34 XP900 Console Reference

➊

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:
DS10CP (default)

SRM console and AlphaBIOS console firmware
only.

DS10IO

I/O adapter firmware only.

The default option in Example 1–11 (DS10FW) 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.

Operations 1-35

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

pfi0

[Y/(N)] y

➎

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

➏

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 [DS10IO,(DS10CP)]:

➐

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

1-36 XP900 Console Reference

➑

➍

The update command updates the device specified or all devices.

➎

➏

The lfu command restarts the utility so that console firmware can be
updated. (Another method is shown in Example 1–14, where the user
specifies the file DS10FW and is prompted to insert the second
diskette.)

➐

The default update file, DS10CP, 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 1–14 Selecting DS10FW to Update Firmware from the
Internal Floppy Disk
>>> 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 [DS10IO,(DS10CP)]: DS10fw
Copying DS10FW from DVA0 .
Copying TCREADME from DVA0 .
Copying TCSRMROM from DVA0 ..........................
Copying TCARCROM 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 ...
.
.

Operations 1-37

1.10.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 1–15 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 [DS10FW]:

➋

Copying DS10FW from EWA0 .
Copying TCREADME from EWA0 .
Copying TCSRMROM from EWA0 ...........................
Copying TCARCROM 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 1–11.]

➌

UPD> list

Device
Fsb
Nt
Pkx0
Srm
Pua

Current Revision
3.1-x
5.69
A11
5.4-x
A214

Filename
fsb_fw
nt_fw
kzpsa_fw
srm_fw
cipca_fw

Update Revision
3.x
5.xx
A11
5.4-xx
A2xx

Continued on next page

1-38 XP900 Console Reference

Before starting LFU, download the update files from the Internet. 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 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:
DS10FW (default)

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

DS10CP

SRM console and AlphaBIOS console firmware
only.

DS10IO

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

Operations 1-39

Example 1–15 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 V6.0-3... Verifying V6.0-3... PASSED.

UPD> exit

➎

➍

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

1-40 XP900 Console Reference

1.10.5

LFU Commands
The commands summarized in Table 1–3 are used to update
system firmware.

Table 1–3 LFU Command Summary
Command

display

Function

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.

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.

Operations 1-41

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

1-42 XP900 Console Reference

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.

Operations 1-43

1.11 Hard Disk Partitioning for Windows NT
The recommended hard disk partition on the first hard disk in
your system is:
Partition 1 should be 6 megabytes less than the total size of
the drive, but no more than 4095 MB. This large partition holds
the operating system and the application and data files.
Partition 2 should be the remaining 6 megabytes. This small
partition holds only the few files necessary for your computer to
boot.
This arrangement provides two benefits:
•

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

1.11.1

Hard Disk Error Conditions

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.

1-44 XP900 Console Reference

•

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.

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.

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

Operations 1-45

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

1-46 XP900 Console Reference

1.11.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 1–7). 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 1–7 System Partition Not Defined
AlphaBIOS Setup
Display System Configuration
Upgrade AlphaBIOS
Hard Disk Setup
No System Partition
CMOS s
Instal
Utilit You must designate a FAT disk partition as a System
Partition. Windows NT will use the System Partition
About
to store system specific startup files.
Please select a partition as the System Partition.
System Partition:

ENTER

=Con

Disk 0, Partition 1

Disk 0, Partition 1
Disk 0, Partition 2
Disk 1, Partition 1
Disk 1, Partition 2

Operations 1-47

1.12 Using the Halt Button
Under OpenVMS and Tru64 UNIX, the halt button pauses the
operating system. Under Windows NT, the Halt button resets
the system, generating power-up tests and output to the console
terminal.

Figure 1–8 Halt/Reset Button

PK1043b

Figure 1–9 Halt/Reset Jumper

1
Setting for
OpenVMS
& Tru64 UNIX

1
Setting for
Windows NT
PK0246c

1-48 XP900 Console Reference

Use the Halt button to halt the Tru64 UNIX or OpenVMS operating system
when it hangs, clear the SRM console password (see Section 2.9.2), or force a
halt assertion (see Section 1.13). The Halt button operates like issuing an SRM
halt command.
Windows NT does not recognize a HALT, so the jumper on the motherboard is
set differently for Windows NT (see Figure 1–9). When the jumper is in the NT
setting, pressing the Halt button is like issuing an SRM initialize command—
the system goes through power-up tests (as shown in Section 1.2).
Your system is shipped with the halt/reset jumper set in the correct position for
your operating system. If you are installing Windows NT after you have
purchased your system, or if you are switching between Windows NT and other
operating systems, you must check your jumper, and possibly have it reset. See
Appendix A for resetting the jumper.
Using Halt to Shut Down the Operating System
You can use the Halt button if the Tru64 UNIX or OpenVMS operating system
hangs. Pressing the Halt button halts the operating system back to the SRM
console firmware. From the console, you can use the crash command to force a
crash dump at the operating system level. See Section 2.12 for an example.
The Windows NT operating system does not support halts on this system.
Pressing the Halt button during a Windows NT session will initiate a system
reset.
Using Halt to Clear the Console Password
The SRM console firmware allows you to set a password to prevent unauthorized access to the console. If you forget the password, the Halt button, with the
login command, lets you clear the password and regain control of the console.
Section 2.9.2 describes the procedure.

Operations 1-49

1.13 Halt Assertion
A halt assertion allows you to disable automatic boots of the
operating system so that you can perform tasks from the SRM
console.
Under certain conditions, you might want to force a “halt assertion.” A halt
assertion differs from a simple halt in that the SRM console “remembers” the
halt. The next time you power up, the system ignores the SRM power-up script
(nvram) and ignores any environment variables that you have set to cause an
automatic boot of the operating system. The SRM console displays this
message:
Halt assertion detected
NVRAM power-up script not executed
AUTO_ACTION=BOOT/RESTART and OS_TYPE=NT ignored, if applicable

Halt assertion is useful for disabling automatic boots of the operating system
when you want to perform tasks from the SRM console. It is also useful for
disabling the SRM power-up script if you have accidentally inserted a command
in the script that will cause a system problem. These conditions are described
in the sections “Disabling Autoboot” and “Disabling the SRM Power-Up Script.”
You can force a halt assertion using the Halt button, the RCM halt command,
or the RMC haltin command. Observe the following guidelines for forcing a
halt assertion.
Halt Assertion with Halt Button or RMC Halt Command
Press the Halt button on the local system (or enter the RMC halt command
from a remote system) approximately five seconds after starting power up or
when the SRM console is running. The system halts at the SRM console, and
the halt status is saved. The next time the system powers up, the saved halt
status is checked.
NOTE: Wait 5 seconds after the system begins powering up before pressing the
Halt button or remotely entering the RMC halt command. Press the
button for several seconds.

1-50 XP900 Console Reference

Halt Assertion with RMC Haltin Command
Enter the RMC haltin command at any time except during power-up. For
example, enter haltin during an operating system session or when the
AlphaBIOS console is running.
If you enter the RMC haltin command during a Tru64 UNIX or OpenVMS
session, the system halts back to the SRM console, and the halt status is saved.
The next time the system powers up, the saved halt status is checked.
If you enter the RMC haltin command when Windows NT or AlphaBIOS is
running, the interrupt is ignored. However, you can enter the RMC haltin
command followed by the RMC reset command to force a halt assertion. Upon
reset, the system powers up to the SRM console, but the SRM console does not
load the AlphaBIOS console.
Clearing a Halt Assertion
Clear a halt assertion as follows:
•

If the halt assertion was caused by pressing the Halt button or remotely
entering the RMC halt command, the console uses the halt assertion once,
then clears it.

•

If entering the RMC haltin command caused the halt assertion, enter the
RMC haltout command or cycle power on the local system.

Disabling Autoboot
The system automatically boots the selected operating system at power-up or
reset if the following environment variables are set:
•

For Tru64 UNIX and OpenVMS, the SRM environment variables os_type,
auto_action, bootdef_dev, boot_file, and boot_osflags

•

For Windows NT, the SRM os_type environment variable and the Auto
Start selection in the AlphaBIOS Standard CMOS Setup screen

You might want to prevent the system from autobooting so you can perform
tasks from the SRM console. Use one of the methods described previously to
force a halt assertion. When the SRM console prompt is displayed, you can enter
commands to configure or test the system. Chapter 2 describes the SRM
console commands and environment variables.

Operations 1-51

Disabling the SRM Power-Up Script
The system has a power-up script (file) named “nvram” that runs every time the
system powers up. If you accidentally insert a command in the script that will
cause a system problem, disable the script by using one of the methods described
previously to force a halt assertion. When the SRM console prompt is displayed,
edit the script to delete the offending command. See Section 2.4 for more
information on editing the nvram script.

1-52 XP900 Console Reference

Chapter 2
SRM Console

The SRM console is the command-line interface that supports the Tru64 UNIX
and OpenVMS operating systems. (Windows NT uses the SRM test command,
only.) The SRM console is used to bootstrap the operating system, configure
and test the system hardware, examine system options for errors, and set or
change environment variables.
This chapter describes the SRM commands and environment variables.
Sections in this chapter are:
•

Invoking the SRM Console

•

Updating Firmware

•

Commands

•

Forcing a System Crash Dump

•

Show Commands

•

Using Environment Variables

•

Creating a Power-Up Script

•

Depositing and Examining Data

•

Booting the Operating System

•

Reading a File

•

Configuring a PCI NVRAM
Module

•

Initializing the System

•

Finding Help

Testing the System

•

Set Commands

Switching from SRM to
AlphaBIOS Console

•

Secure Mode

•

Stopping and Starting CPU

Environment Variable
Summary

SRM Console

2-1

2.1

Invoking the SRM Console
When a system is powered up, the SRM console runs and either
remains running or passes control to another console or an
operating system. If the system is already running, invoke the
SRM console by shutting down the operating system or by
pressing the Halt button on the control panel.

If you are running Tru64 UNIX or OpenVMS Alpha operating system
To invoke the SRM console, do one of the following steps:
•

Shut down the operating system according to the procedure described in
your operating system documentation.
--or--

•

Press the Halt button on the control panel, if your system is running either
OpenVMS or Tru64 UNIX.

Following one of these steps, the console prompt, >>>, will be displayed. You
are now at the SRM console.

If you are running AlphaBIOS
To switch to the SRM console, do one of the following steps:
•

Select either OpenVMS console (SRM) or Tru64 UNIX console (SRM)
from the Console Selection in the Advanced CMOS Setup screen. Save
the setting by pressing the F10 key. Push the system Halt/Reset button to
start the SRM console.
--or--

•

Press the Halt/Reset button, wait 5 seconds, and then press the Halt button.
The SRM console will boot.

After you have performed tasks in the console mode, you must boot the
operating system with the boot command to go back to the operating mode.

2-2 XP900 Console Reference

2.2

Commands
This section presents a command summary (Table 2–1), Gives
the syntax for the console commands (Table 2–2), and explains
the special keystrokes and characters available in SRM console
mode (Table 2–3).

2.2.1

Command Summary

Table 2–1 Summary of SRM Console Commands
Command

alphabios
boot
clear envar
clear password
continue
crash
deposit

Function

Loads and starts the AlphaBIOS console.
Loads and starts the operating system.
Resets an environment variable to its default value.
Sets the password to zero.
Resumes program execution.
Forces a crash dump at the operating system level.
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
lfu
login

Resets the system to a known state.
Runs the Loadable Firmware Update Utility.
Turns off secure mode, enabling access to all SRM console
commands during the current session.
Continued on next page.

SRM Console

2-3

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

Function
Displays a file one screen at a time.

prcache

Utility that initializes and displays status of the
optional PCI NVRAM device.

set envar

Sets or modifies the value of an environment
variable.

set host

Connects to an MSCP DUP server on a DSSI device.

set password

Sets the console password for the first time or
changes an existing password.

set secure

Enables secure mode without requiring a restart of
the console.

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 memory
show pal

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

show power

Displays information about the power supply, system
and PCI fans, CPU fan, and temperature.

show version

Displays the version of the console program.

stop

Halts the processor. (Same as halt.)

test

Runs firmware diagnostics for the system.

2-4 XP900 Console Reference

2.2.2

Commands: Syntax

Table 2–2 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 2–3) 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

2-5

2.2.3

Commands: Special Keystrokes and Characters

Table 2–3 Special Characters for SRM Console
Character

Return or
Enter

Function

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.

←Backspace

Moves the cursor left one position, deleting one
character.

Delete
Help

Deletes the previous character.
Entered at the console prompt without arguments, it
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 ↑

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

Ctrl/C

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/E

Moves the cursor to the end of the line.

Ctrl/F or →

Moves the cursor right one position.

Ctrl/H

Moves the cursor to the beginning of the line.

Ctrl/J

Deletes the previous word.
Continued next page.

2-6 XP900 Console Reference

Character

Ctrl/O

Function

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/P

Halts the machine.

Ctrl/Q

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

Ctrl/R

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

Ctrl/S

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

Ctrl/U

Deletes the current line.

*
"... "
#

Wildcarding for 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

2-7

2.3

Show Commands
Several commands are used to display the system configuration:
show config, show cpu, show device, show memory, show
network, show pal, show power, and show version.

2.3.1

Show Config
The show config command displays a list of devices found on the
system interconnect and I/O buses. This is the configuration at
the most recent initialization.

Syntax:

show config

Example 2–1 Show Config Command
>>> show config
AlphaStation XP900 466 MHz
SRM Console:
PALcode:
Processors
CPU 0

V5X-XXX
OpenVMS PALcode V1.56-45, Tru64 UNIX PALcode V1.50-48
Alpha 21264-4 466 MHz
Bcache size: 2 MB

Core Logic
Cchip
Dchip
Pchip 0

DECchip 21272-CA Rev 2
DECchip 21272-DA Rev 2
DECchip 21272-EA Rev 2

TIG
Arbiter

Rev 2.1
Rev 3.30 (0x7E)

MEMORY
Array #
------0

Size
---------256 MB

SROM Revision: V1.8.208

Base Addr
--------000000000

Total Bad Pages = 0
Total Good Memory = 256 MBytes
PCI Hose 00
Bus 00

Slot 01: Acer Labs M1543C USB

Bus 00

Slot 03: Acer Labs M1543C PMU

Bus 00

Slot 07: Acer Labs M1543C

Bus 00

Slot 09: DE500-BA Network Controller
ewa0.0.0.9.0

Bridge to Bus 1, ISA

2-8 XP900 Console Reference

08-00-2B-86-1B-BA

Bus 00

Slot 11: DE500-BA Network Controller
ewb0.0.0.11.0
Slot 13: Acer Labs M1543C IDE
dqa.0.0.13.0
dqa1.1.0.13.0
Slot 14: DEC PowerStorm

Bus 00

Slot 15: DECchip 21152-AA

Bus 00

Slot 16: QLogic ISP1020
pkc0.6.0.16.0
dkc0.0.0.16.0
dkc200.2.0.16.0
Slot 17: Mylex DAC960
dra.0.0.17.0
dra0.0.0.17.0
dra1.0.0.17.0
dra2.0.0.17.0
dra3.0.0.17.0
Slot 00: NCR 53C875
pka0.7.0.2000.0
dka100.1.0.2000.0
dka300.3.0.2000.0
dka500.5.0.2000.0
Slot 01: NCR 53C875
pkb0.7.0.2001.0
dkb0.0.0.2001.0
dkb200.2.0.2001.0
dkb400.4.0.2001.0
Slot 02: DE500-AA Network Controller
ewc0.0.0.2002.0

Bus 00

08-00-2B-86-1B-BB

CD-532E

Bridge to Bus 2, PCI

Bus 00

Bus 02

ISA
Slot
0

Device

Name

Type

0
1
2
3
4
5

MOUSE
KBD
COM1
COM2
LPT1
FLOPPY

Embedded
Embedded
Embedded
Embedded
Embedded
Embedded

SCSI Bus ID 6
RZ1CB-BA
RZ1CB-BA

1 Member JBOD
1 Member JBOD
1 Member JBOD
1 Member JBOD
SCSI Bus ID 7
RZ1CB-CA
RZ1CB-CA
RZ1EF-AB
SCSI Bus ID 7
RZ1CB-CA
RZ1DB-CS
RZ1CB-CA
00-06-2B-00-26-1C

Enabled

BaseAddr

IRQ

DMA

Yes
Yes
Yes
Yes
Yes
Yes

60
60
3f8
2f8
3bc
3f0

12
1
4
3
7
6

>>>

SRM Console

2-9

2.3.2

Show Device
The show device command displays status for devices and
controllers in the system: SCSI and MSCP devices, the internal
floppy drive, and the network.

Syntax:

show device [controller_name]

controller_name

The controller name or abbreviation. When abbreviations
or wildcards are used, all controllers that match the type
are displayed. If no name is given, the display is a list of all
devices and controllers in the system.

Example 2–2 Show Device Command
>>> sho device
dka0.0.0.14.0
dka100.1.0.14.0
dqa0.0.0.13.0
dva0.0.0.0.0
ewa0.0.0.9.0
ewb0.0.0.11.0
pka0.7.0.14.0
>>>

DKA0
DKA100
DQA0
DVA0
EWA0
EWB0
PKA0

RZ2CA-KA N1H1
RZ2CA-KA N1H1
CD-532E- A 1.0A
08-00-2B-86-1F-71
08-00-2B-86-1F-70
SCSI Bus ID 7 5.57

An example of a device name is dka200.2.0.7.1. Table 2-4 shows the
interpretation of this device name.

2-10 XP900 Console Reference

Table 2–4 Device Naming Convention

Category

Description

Driver ID

Two-letter designator of port or class driver
dk

SCSI disk

FDDI device

ATAPI CD-ROM

SCSI tape

RAID set device

DSSI tape

DSSI disk

SCSI port

Diskette drive

DSSI port

Ethernet port

Storage adapter
ID

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

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 2–5.

Hose number

0 — PCI 0

a
200

1 — PCI 1

Table 2–5 PCI Address Assignments
Physical
Slot #

Logical
Slot #

PCI
ID_SEL

Description/Position

AD 28

64-bit slot (top slot)

AD 27

64-bit slot (second from top)

AD 26

64-bit slot (second from bottom)

AD 25

32-bit slot (bottom slot)

SRM Console

2-11

2.3.3

Show Memory
The show memory command displays information about each
memory bank: slot number, size in megabytes, and the starting
address.

Syntax:

show memory

Example 2–3 Show Memory Command
>>> show memory
Array #
------0
1
2
3

Size
---------128 MB
128 MB
128 MB
128 MB

Base Addr
--------000000000
008000000
010000000
018000000

Total Bad Pages = 0
Total Good Memory = 512 MBytes
>>>

2.3.4

Show PAL
The show pal command displays the versions of Tru64 UNIX and
OpenVMS PALcode. PALcode is the Alpha Privileged
Architecture Library code, written to support Alpha processors.
It implements architecturally defined processor behavior.

Syntax:

show pal

Example 2–4 Show PAL Command
>>> show pal
pal OpenVMS PALcode V1.56-45, Tru64 UNIX PALcode V1.50-48
>>>

2-12 XP900 Console Reference

2.3.5

Show Power
The show power command displays status information about the
power supply, the system, PCI and CPU fans, and temperature.
This command is useful for displaying the error state of a Tru64
UNIX or OpenVMS system that shuts down because of a fan,
temperature, or power supply failure.

Syntax:

show power

If the system can be restarted, use this command. (If it cannot, use the RMC
status command. See Chapter 4.)

Example 2–5 Show Power Command
>>> show power
Power Supply
System Fan
PCI Fan
CPU Fan
Temperature

Status
good
good
good
good
good

Current ambient temperature is 34 degrees C
System shutdown temperature is set to 55 degrees C
2 Environmental events are logged in nvram
Do you want to view the events? (Y/<N>) y
Total Environmental Events: 2 (2 logged)
1
2

000
000

0
0

0:00
0:00

Temperature, Fans, Power Supplies Normal
Temperature, Fans, Power Supplies Normal

Do you want to clear all events from nvram? (Y/<N>) y
>>>

SRM Console

2-13

2.3.6

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

Syntax:

show version

Example 2–6 Show Version Command
>>> show version
version
>>>

2.4

V5.4-2 MAY 19 1999 14:24:16

Creating a Power-Up Script
A special nonvolatile file named “nvram” is stored in EEROM,
and is always invoked during the power-up sequence. You can
create an nvram script to include any commands you want the
system to execute at power-up. You alter, create and edit the
nvram script using the SRM edit command. With edit, lines can
be added, overwritten, or deleted.

Syntax:
edit file
where 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.

2-14 XP900 Console Reference

NOTE: It is possible to disable the system by editing the nvram script. For
example, if you include the initialize command in the script, the
system will go into an endless loop. To fix this, press the Halt button
while the system is powering up. You can then edit the script to delete
the offending command.
Example 2–7 shows how to modify the user-created power-up script, “nvram.”
The pound sign (#) indicates explanatory comments. In this example the script
is edited to include a command that allows you to boot the Tru64 UNIX
operating system over the network.

Example 2–7 Editing the nvram Script
>>> edit nvram
editing ‘nvram’
0 bytes read in
*10 set ewa0_protocols bootp
*list
10 set ewa0_protocols bootp
*exit
27 bytes written out to nvram
>>> nvram

#Modify user power-up script, nvram.

#List current file with line numbers.
#Close file and save changes.
#Execute the script.

To clear the script, enter line numbers without any text. This deletes the lines.
See Example 2–8.

Example 2–8 Clearing the nvram Script
>>> edit nvram
editing ‘nvram’
20 bytes read in
*10
*exit
0 bytes written out to nvram
>>>

SRM Console

2-15

2.5

Booting the Operating System
The boot command is used to boot the operating system. The boot
command initializes the processor, loads a program image from
the specified boot device, and transfers control to that image.

Syntax: 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 Tru64 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.

2-16 XP900 Console Reference

Example 2–9 Boot Command
>>> b dkc0
(boot dkc0.0.0.16.0 -flags 0)
block 0 of dkc0.0.0.16.0 is a valid boot block
reading 898 blocks from dkc0.0.0.16.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 70400
initializing HWRPB at 2000
initializing page table at ffb6000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
OpenVMS (TM) Alpha Operating System, Version V7.1-2
%SYSINIT-I- waiting to form or join an OpenVMS Cluster
%VMScluster-I-LOADSECDB, loading the cluster security database
%EWA0, Fast(100baseTX) mode set by console
%EWB0, Fast(100baseTX) mode set by console
. . .
%CNXMAN, Completing VMScluster state transition
$! Copyright (c) 1998 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, OpenVMS startup begun at 23-APR-1999 11:31:48.97
%MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving
. . .
The OpenVMS system is now executing the site-specific startup commands.
. . .
Welcome to OpenVMS (TM) Alpha Operating System, Version V7.1-2
Username:

SRM Console

2-17

2.6

Configuring a PCI NVRAM Module
The prcache command is used for system configuration 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. The command is used only with
Tru64 UNIX systems.

Syntax:

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.

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

2-18 XP900 Console Reference

2.7

Testing the System
The test command runs console-based exercisers for devices in
the system. Ctrl/C can abort testing.
test [-t time] [-q] [option]

Syntax:
-t time

Specifies the run time in seconds. The default for system test is
120 seconds (2 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.

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. Select
Tru64 UNIX Console (SRM) or OpenVMS Console (SRM) from the
Advanced CMOS Setup of the AlphaBIOS console screen, save the setting by
pressing the F10 key, and then reset the system.

Example 2–11 Test Command
>>> test
environment variable t_cnt created
System test, runtime 150 seconds
Type ^C if you wish to abort testing once it has started
Default zone extended at the expense of memzone.
Use INIT before booting
Testing Ethernet device(s)
Testing VGA
Testing Memory
Testing IDE/ATAPI disks (read-only)
Testing SCSI disks (read-only)
Testing DKA* devices (read-only)..
No other SCSI disks to test
Testing floppy drive (dva0, read-only)
No diskette present, skipping floppy test

SRM Console

2-19

ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
4
0
0
310378496
310378496
00001aea
memtest memory
4
0
0
306184192
306184192
00001b07
memtest memory
3
0
0
310378496
310378496
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
215040
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
8732672
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
8732672
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
6
0
0
549453824
549453824
00001aea
memtest memory
6
0
0
545259520
545259520
00001b07
memtest memory
6
0
0
545259520
545259520
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
421888
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
14434304
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
14434304
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
8
0
0
780140544
780140544
00001aea
memtest memory
8
0
0
780140544
780140544
00001b07
memtest memory
8
0
0
780140544
780140544
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
631808
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
20168704
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
20168704
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
11
0
0
1019215872
1019215872
00001aea
memtest memory
10
0
0
1019215872
1019215872
00001b07
memtest memory
10
0
0
1019215872
1019215872
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
835584
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
27066368

2-20 XP900 Console Reference

00001b7b
exer_kid dka100.1.0.1
0
0
0
0
27066368
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
13
0
0
1254096896
1254096896
00001aea
memtest memory
13
0
0
1249902592
1249902592
00001b07
memtest memory
12
0
0
1254096896
1254096896
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
1043456
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
32800768
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
32784384
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
15
0
0
1488977920
1488977920
00001aea
memtest memory
15
0
0
1484783616
1484783616
00001b07
memtest memory
14
0
0
1488977920
1488977920
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
1241088
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
39665664
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
39649280
ID
Program
Device
Pass Hard/Soft Bytes Written Bytes Read
-------- ------------ ------------ ------ --------- ------------- ----------00001ae5
memtest memory
17
0
0
1723858944
1723858944
00001aea
memtest memory
17
0
0
1723858944
1723858944
00001b07
memtest memory
16
0
0
1723858944
1723858944
00001b54
exer_kid dqa0.0.0.13.
0
0
0
0
1445888
00001b74
exer_kid dka0.0.0.14.
0
0
0
0
45350912
00001b7b
exer_kid dka100.1.0.1
0
0
0
0
45350912
Test time has expired...
System test complete
>>>
System test, runtime 1200 seconds
Type ^C if you wish to abort testing once it has started

SRM Console

2-21

Default zone extended at the expense of memzone.
Use INIT before booting
Testing Ethernet device(s)
Testing VGA
Testing Memory
Testing IDE/ATAPI disks (read-only)
Testing SCSI disks (read-only)
Testing floppy drive (dva0, read-only)
Test time has expired...
System test complete

>>>

2-22 XP900 Console Reference

2.8

Set Commands

2.8.1

Set Password
The set password command sets the console password for the
first time or changes an existing password. It is necessary to set
the password only if the system is going to operate in secure
mode.

Syntax:

set password

The password length must be between 15 and 30 alphanumeric characters.
If a password has not been set and the set password command is issued, the
console prompts for a password and verification.
If a password has been set and the set password command is issued, the
console prompts for the new password and verification, then prompts for the old
password. The password is unchanged if the validation password entered does
not match the existing password in the NVRAM.

Example 2–12 Set Password Command
>>> set password
# Password is not echoed.
Please enter the password:
Please enter the password again: # Validation is not echoed.
>>>
>>> set password
# Changing a password.
Please enter the password:
Please enter the password again:
Now enter the old password:
>>>
>>> set password
# Password entered is
Please enter the password:
# too short.
Password length must be between 15 and 30 characters

>>>

SRM Console

2-23

2.8.2

Set Secure
The set secure command enables secure mode without requiring
a restart of the console. If the password has been set, the console
will be secured and only a small subset of commands can be
performed. If a password has not been set, you are prompted to
do so.

Syntax:

set secure

Example 2–13 Set Secure Command
>>> set secure

# In this example a password
# has been set.

Console is secure. Please login.
>>> b dkb0
Console is secure - parameters are not allowed.
>>> login
Please enter the password:
# Password is not echoed.
>>> b dkb0
(boot dkb0.0.0.3.1)
.
.
>>> set secure
# Password has not been set.
Secure not set. Please set the password.
>>>

2-24 XP900 Console Reference

2.9

Secure Mode
When the console is in secure mode, the only commands
recognized are boot, login, continue, and start. Placing the console
in secure mode ensures that unauthorized persons cannot gain
access to the system. The commands for console security are set
password, clear password, and set secure. The login command
turns off security features during the current console session.

The boot command does not accept command line parameters in secure mode.
The console boots using the environment variables stored in NVRAM
(boot_file, bootdef_dev, boot_flags). After a successful boot, the console is
secured if there is a valid password.
The start and continue commands are valid on a secure console. After either
command is executed, the console is secured if there is a valid password. This
prevents an intruder from accessing the system.

2.9.1

Login Command and Secure Mode
The login command turns off the security features, enabling
access to all SRM console commands during the current session.
The system automatically returns to secure mode as soon as the
boot, continue, or start command is entered or when the system is
initialized.

When the login command is entered, the user is prompted for the current
system password. If a password has not been set, a message is displayed
indicating that there is no password in NVRAM. If a password has been set, this
prompt is displayed:
Please enter the password:

If the password entered matches the password in NVRAM when the prompt is
redisplayed, the console is no longer in secure mode and all console commands
can be performed.
NOTE:

If you enter the login command when a halt assertion exists, the
command fails, even if you enter the correct password. See Section 1.13
for information on halt assertion.

SRM Console

2-25

Example 2–14 Secure Mode and Login Command
>>> login
# System is not in secure mode.
>>>
Secure not set. Please set the password.
>>> login
Please enter the password:
>>>

# System is in secure mode.
# Password is not echoed.

>>> login
Please enter the password:

# System is in secure mode.
# Incorrect password is
# entered.

Invalid password
>>>

2.9.2

Clear Password
The clear password command clears the password environment
variable, setting it to zero. This command is used when you want
access to all the SRM console commands, but the system is in
secure mode. In order to use clear password, you must know the
current password.

To clear the password without knowing the current password, use the login
command, with the Halt button or RMC halt command, as described in the
section on the login command.

Example 2–15 Clear Password Command
>>> clear password
Please enter the password:
Password successfully cleared.
>>>
>>> clear password
Please enter the password:
Console is secure
>>>

2-26 XP900 Console Reference

# Password is not echoed.

# Invalid password entered.

2.9.3

Resetting the Password

If you have forgotten the current password, clear the password as follows:
From the Local Console Terminal
1. Enter the login command: >>> login
2. At the Enter Password: prompt, press the Halt button, then press the Return
key.
The password is now cleared and the console cannot be put into secure mode
unless a new password is set.
From the RMC
1. Enter the login command: >>> login
2. At the Enter Password: prompt, enter the RMC escape sequence.
3. At the RMC>>> prompt, enter the halt command and then the quit
command:
RMC>>> halt
RMC>>> quit
4. At the SRM console, clear the password:
>>> clear password

SRM Console

2-27

2.10 Stopping and Starting CPU
The halt (or stop) command stops program execution on a CPU
that is still running a booted program.
Syntax:
halt (or stop) 0
where 0 is the number of the CPU to halt.
For the DS10 system, this command has no effect because the single CPU is
halted when the system is at the console prompt.

2.11 Updating Firmware
The lfu command is used to update firmware from the SRM
console prompt. The lfu command starts the Loadable Firmware
Update (LFU) Utility.

The syntax is: lfu
Example 2–16 Lfu Command
>>> lfu
Checking dqa0.0.0.13.0 for the option firmware files. . .
Checking dva0 for the option firmware files. . .
Option firmware files were not found on CD or floppy.
If you want to load the options firmware,
please enter the device on which the files are located(ewa0),
or just hit <return> to proceed with a standard console update: dva0
Please enter the name of the options firmware files list, or
Hit <return> to use the default filename (ds10fw.txt) :
Copying ds10fw.txt from dva0. . .
Copying PC264NT.ROM from dva0. . .
Copying DS10SRM.ROM from dva0. . .

2-28 XP900 Console Reference

***** Loadable Firmware Update Utility *****
-----------------------------------------------------------------Function
Description
-----------------------------------------------------------------Display
Displays the system’s configuration table.
Exit
Done exit LFU (reset).
List
Lists the device, revision, firmware name, and update
revision.
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> update *
Confirm update on:
nt
srm
[Y/(N)]y
WARNING: updates may take several minutes to complete for each device.
DO NOT ABORT!
nt

Updating to 5.69...

Verifying 5.69...

PASSED.

srm

Updating to 5.4-2...

Verifying 5.4-2...

PASSED.

UPD> exit

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 1 for more information about LFU.

SRM Console

2-29

2.12 Forcing a System Crash Dump
The crash command forces a crash dump at the operating system
level (Tru64 UNIX or OpenVMS; has no effect on Windows NT).
This command is used when an error has caused the system to
hang and can be halted with the Halt button or the RMC halt
command. This command restarts the operating system and
forces a crash dump to the selected device.
Syntax:

crash [device]

where device is the name of the device to which the crash dump is written.

Example 2–17 Crash Command
>>> 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
>>>

2-30 XP900 Console Reference

2.13 Using Environment Variables
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.
You issue an init command to activate a new
environment variable.
Environment variables are set or changed with the set envar command (where
envar is a placeholder for the environment to be changed) 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 described in Section 2.4. Section 2.19 describes
the environment variables in detail.

2.13.1

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

Syntax:

-default

set [-default] envar value

Restores an environment variable to its default setting.

envar

The name of the environment variable to be displayed. The
wildcard * displays all environment variables, which are:
console, kbd_hardware_type, language, ocp_text
and os_type

value

The new value of the environment variable.

Whenever you modify the value of any environment variables, the new value
takes effect only after you reset the system by pressing the Halt/Reset button or
issuing the initialize command.

SRM Console

2-31

2.13.2

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

Syntax:

envar

The name of the environment variable to be displayed. The
wildcard * displays all environment variables, which are:
console, kbd_hardware_type, language, ocp_text
and os_type.

Example 2–18 Setting and Showing Environment Variables
>>> show console
console
>>> set console serial
>>> show console
console
>>> init

graphics
serial
# The system must be init’ed for
the new parameters to take effect

Example 2–19 Creating a User-Defined Environment Variable
>>> edit nvram
editing ‘nvram’
0 bytes read in
*10 set mopv3_boot 1
*exit
17 bytes written out to nvram
>>>

In Example 2–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
boot sends four MOP V4 requests before defaulting to MOP V3. This usercreated environment variable forces the SRM console to bypass MOP V4
requests. This speeds up MOP booting on networks with MOP V3 software.

2-32 XP900 Console Reference

2.14 Depositing and Examining Data
Example 2–20 Deposit Command
>>> dep -b -n 1ff pmem:0 0

# Clear 1st 512 bytes of physical mem.

>>> d -l -n 3 vmem:1234 5

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

>>> d -n 8 r0 ffffffff

# Load GPRs R0 through R8 with -1.

>>> d -l -n 10 -s 200 pmem:0 8

# Deposit 8 in the 1 longword of the
# first 17 pages in physical memory

>>> d -l pmem:0 0

# Deposit 0 to physical mem address 0.

>>> d + ff

# Deposit FF to physical mem address 4.

>>> d scbb 820000

# Deposit 820000 to SCBB.

Example 2–21 Examine Command
>>> examine pc
PC psr: 0 (
PC)

# Examine the program counter.
0000000000001170

>>> examine sp
gpr:
F0 (
R30)

# Examine the stack pointer.
0000000000072A60

>>> e -n 6 r4
grp: 20 (
R4) 0000000000005000
grp: 28 (
R5) 000000000FFFE000
grp: 30 (
R6) 00000003F8000C00
grp: 38 (
R7) 0000000053F761AE
grp: 40 (
R8) 0000010000000000
grp: 48 (
R9) 00000003F7800100
grp: 50 (
R10) 00000000000C7FFC

# Examine register R4 & the next 6 registers.

>>> examine pmem:400EC
pmem: 400EC A49D0078A47D0070

# Examine physical memory.

SRM Console

2-33

2.15 Reading a File
The more command displays a file one screen at a time.
Syntax:

more [file...]

where file is the name of the file to be displayed.
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 >>> prompt displays, you can use the more command to display the
contents of the event log file.

Example 2–22 More Command
>>> more el
# Display SRM console’s event log one screen at a time.
. . .
--More-- (SPACE - next page, ENTER - next line, Q - quit)
# Display online help one screen at a time.
>>> help * | more
. . .
--More-- (SPACE - next page, ENTER - next line, Q - quit)

2-34 XP900 Console Reference

2.16 Initializing the System
The initialize command resets the system and executes powerup tests.
Syntax:

initialize

After self-tests are executed, the system autoboots unless:
•

A halt assertion condition exists (see Section 1.13) –or–

•

The auto_action environment variable is set to halt (see Section 2.19.1).

If the auto_action environment variable is set to boot or restart and no halt
assertion condition exists, the system autoboots. In all other cases, the system
stops in console mode and does not attempt to boot.

Example 2–23 Initialize Command
>>> init
Initializing...
256 Meg of system memory
probing hose 0, PCI
probing PCI-to-ISA bridge, bus 1
probing PCI-to-PCI bridge, bus 2
bus 0, slot 9 -- ewa -- DE500-BA Network Controller
bus 0, slot 11 -- ewb -- DE500-BA Network Controller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
bus 0, slot 14 -- vga -- DEC PowerStorm
bus 2, slot 0 -- pka -- NCR 53C875
bus 2, slot 1 -- pkb -- NCR 53C875
bus 2, slot 2 -- ewc -- DE500-AA Network Controller
bus 0, slot 16 -- pkc -- QLogic ISP1020
bus 0, slot 17 -- dra -- Mylex DAC960
Testing the System
Testing the Disks (read only)
Testing the Network
System Temperature is 34 degrees C
CPU 0
Alpha 21264-4 466 MHz
SROM Revision: V1.8.208
TIG
Rev 2.1
Arbiter
Rev 3.30 (0x7E)
Array #
Size
Base Addr
---------------- --------0
512 MB
000000000
1
512 MB
020000000
2
128 MB
050000000
3
256 MB
040000000
Total Bad Pages = 0
Total Good Memory = 1408 MBytes
AlphaStation XP900 466 MHz Console V5.4-2 MAY 19 1999 14:24:16
>>>

SRM Console

2-35

2.17 Finding Help
The help command displays basic information about the use of
console commands when the system is in console mode.
Syntax:

help [command . . . ]

Command . . .

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.

Example 2–24 Help Command
>>> help 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]

2-36 XP900 Console Reference

2.18 Switching from SRM to AlphaBIOS Console
The alphabios command loads and starts the AlphaBIOS console.
This is necessary for running AlphaBIOS-based utilities (such as
the RAID configuration utility). To switch from SRM to
AlphaBIOS, issue the alphabios command.
Syntax:

alphabios

To return to the SRM console:
•

If the os_type environment variable is set to unix or openvms, reset the
system by pressing the Halt/Reset button,--or--

•

If the os_type environment variable is set to nt, select Tru64 UNIX
console (SRM) or OpenVMS console (SRM) from the Advanced CMOS
Setup screen, save the setting by pressing key F10 and then reset the
system.

To switch permanently to the AlphaBIOS console:
If the permanent operating system is changed to Windows NT, you will want to
switch permanently to the AlphaBIOS console. To accomplish this:
1. Set the SRM os_type environment variable to nt.
2. Set the SRM console environment variable to graphics.
3. Reset the system with the initialize command, the Halt/Reset button, or by
power cycling.

Example 2–25 Switching to the AlphaBIOS Console
>>> alphabios

SRM Console

2-37

2.19 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 2–6 lists the environment variables. Detailed descriptions follow. The
environment variables are specific to the SRM console.

Table 2–6 Environment Variable Summary
Environment Variable

Function

auto_action

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

bootdef_dev

Specifies the default boot device string.

boot_osflags

Specifies the default operating system boot flags.

com*_baud
console

Changes the default baud rate of the COM1 or COM2
serial port.
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.

language

Specifies the console keyboard layout.

2-38 XP900 Console Reference

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

Function

ocp_text

Overrides the default OCP display text with specified
text.

os_type

Specifies the operating system. Valid entries are:
openvms, unix, and nt.

password

A password stored in the NVRAM used to secure the
console.

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 ISP1040 SCSI controller.

tt_allow_login

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

SRM Console

2-39

2.19.1

auto_action
Specifies the action the console takes any time the system
powers up, fails, or resets. When the setting involves autoboot,
the system boots from the default boot device specified by the
value of the bootdef_dev environment variable.
set auto_action value

Syntax:

where value can be:
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.

NOTE: If a halt assertion exists, the console ignores the auto_action setting and
halts at the SRM console. See Section 1.13 for information on halt
assertion.

2.19.2

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.

Syntax:

set bootdef_dev boot_device

Where boot_device is 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.

2-40 XP900 Console Reference

2.19.3

boot_osflags
The boot_osflags environment variable passes information to the
boot command. That information is dependent on the operating
system to be booted.

Syntax for Tru64 UNIX:

set boot_osflags flags_value

where flags_value can be:
a

Load operating system software from the specified boot device
(autoboot). Boot to multi-user 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 Tru64 UNIX crashes, it
completes a partial memory dump. Specifying “D” forces a full
dump if the system crashes.

Syntax for OpenVMS: set boot_osflags root_number, boot_flags
Where root_number is the 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]

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

SRM Console

2-41

Table 2–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.

2-42 XP900 Console Reference

2.19.4

com1_baud
The default baud rate for the system is 9600. With the com1_baud
environment variable, you can set the baud rate to match that of
the device connected to the port.

Syntax:

set com1_baud baud_value

where baud_value is 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).
NOTE: Disable the RMC to select a baud rate other than 9600. See Chapter 4.
You will be asked to confirm the change, as shown in Example 2–26.

Example 2–26 Changing Baud Rate
>>> set com1_baud 19200
Embedded Remote Console only supports 9600 baud. Continue? (Y/[N]) n
bad value - com1_baud not modified
>>>

2.19.5

com1_mode
The set com1_mode command sets the bypass modes of the
remote management console (see Chapter 4)

For modem connections, you can set the com1_mode variable to allow data to
partially or completely bypass the RMC. The bypass modes are snoop mode, soft
bypass mode, and firm bypass mode.
•

In snoop mode, you can type an escape sequence to enter RMC mode. RMC
mode provides a command-line interface for issuing commands to monitor
and control the system.

•

In soft bypass mode, you cannot enter RMC mode. But if an alert condition
or loss of carrier occurs, the RMC switches into snoop mode. From snoop
mode you can enter RMC mode.

SRM Console

2-43

•

In firm bypass mode, you cannot enter RMC mode. To enter RMC mode
from firm bypass mode, reset the com1_mode variable from the SRM
console.
set com1_mode value

Syntax:

where value can be:
snoop

Data partially bypasses RMC, but RMC taps into the data lines
and listens passively for the RMC escape sequence.

soft_bypass

Data bypasses RMC, but RMC switches automatically into snoop
mode if an alert condition or loss of carrier occurs.

firm_bypass

Data bypasses RMC. RMC is effectively disabled.

Example:
>>> set com1_mode
COM1_MODE (SNOOP, SOFT_BYPASS, FIRM_BYPASS)

2.19.6

console
The console terminal can be either a graphics monitor or a
serial terminal. The console environment variable specifies
which is used. Whenever you change the value of console, you
must reset the system by pressing the Halt/Reset button or
issuing the initialize command.

Syntax:

set console output_device

where output_device can be:
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.

2-44 XP900 Console Reference

2.19.7

ew*0_mode
Sets an Ethernet controller to run an AUI, ThinWire, or twistedpair Ethernet network. The default is auto-sense. For the fast
setting, the device defaults to fast.
set ew*0_mode value

Syntax:

where value can be:
aui

Device type is AUI.

auto-sense

Device type is sensed by the console.

twisted-pair

Device type is 10BaseT (twisted pair).

fast duplex,
twisted-pair

Device type is duplex 10BaseT.

fast
fast FD
BNC
auto-negotiate

2.19.8

Device type is fast SCSI.
Device type is fast full duplex SCSI.
Device type is BNC.
DE500-BA

ew*0_protocols
Enables network protocols for booting and other functions.

Syntax:

set ew*0_protocols protocol_value

where protocol_value can be:
mop (default)

bootp
bootp,mop

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

Sets the network protocol to bootp, the setting typically
used with the Tru64 UNIX operating system.
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.

SRM Console

2-45

2.19.9

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.
set kbd_hardware_type keyboard_type

Syntax:

where keyboard_type can be:
pcxal
(default)

lk411

Selects the default keyboard hardware type.

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

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

2.19.10 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
Halt/Reset button or issuing the initialize command.
Syntax:

set language language_code

where language_code can be:
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)

2-46 XP900 Console Reference

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)

2.19.11 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 Halt/Reset
button or issuing the initialize command.
set os_type os_type

Syntax:

where os_type can be:
unix

Tru64 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
power-up or reset. (If a halt assertion condition exists, this
environment variable is overridden, and the SRM firmware does
not load and start the AlphaBIOS console.)

2.19.12 password
Sets or clears the console password stored in NVRAM.
Syntax:

set password

where the password is not an argument to the set password command; the
console prompts the user for the string, which must be between 15 and 30
characters.

SRM Console

2-47

2.19.13 pci_parity
Disables or enables parity checking on the PCI bus.
set pci_parity value

Syntax:

where value can be:

(default) on

Enables PCI parity checking.

off

Disables PCI parity checking.

Some PCI devices do not implement PCI parity checking, and some have a
parity-generating scheme in which the parity is sometimes incorrect or is not
fully compliant with the PCI specification. A side effect of this 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.

2.19.14 pk*0_fast
Enables fast SCSI to perform in either standard or fast mode.
set pk*0_fast scsi_speed

Syntax:

where scsi_speed can be:
(default) 1

The controller is in fast SCSI mode.

The controller is in standard SCSI 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.

2-48 XP900 Console Reference

2.19.15 pk*0_host_id
Sets the controller host bus node ID to a value between 0 and 7.
set pk*_host_id scsi_node_id

Syntax:

where scsi_node_id is the bus node ID, a number from 0 to 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.

2.19.16 pk*0_soft_term
Enables or disables SCSI terminators. This command applies to
systems that use the QLogic ISP1040 SCSI controller. The
QLogic ISP1040 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.
set pk*0_soft_term value

Syntax:

where value can be:
Off

Disables termination of all 16 bits.

(default) low

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.

SRM Console

2-49

2.19.17 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.
set tt_allow_login value

Syntax:

where value can be:
(default) 1

Enables login through the COM2 port or a graphics monitor.

Disables login through the COM2 port or a graphics monitor.

2-50 XP900 Console Reference

Chapter 3
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.
Sections in this chapter are:
•

Starting AlphaBIOS

•

Keyboard Conventions and Help

•

System Configuration

•

Updating Firmware

•

Setting Up the Hard Disk

•

Performing Setup Tasks

•

Installing Operating System

•

Selecting the Version of Windows NT

•

Designating a Primary Operating System

•

Switching from AlphaBIOS to SRM Console

•

Running Utility Programs

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

AlphaBIOS Console

3-1

3.1

Starting AlphaBIOS
Start AlphaBIOS Setup by pressing F2 from the Boot screen
displayed at power-up or reset.

Figure 3–1 Boot Screen

PK1450 - 98

3-2 XP900 Console Reference

The boot screen shown in Figure 3–1 is displayed at power-up and reset. Press
F2 at this screen to enter the setup program.
The AlphaBIOS Setup screen (Figure 3–2) is displayed. 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 3.2 for information on navigating the
AlphaBIOS screens.)

Figure 3–2 AlphaBIOS Setup Screen
AlphaBIOS Setup

F1= Help

Display System
AlphaBIOS Upgrade…
Hard Disk Setup…
CMOS Setup…
Network Setup…
Install NT
Operating System
Utilities
About AlphaBIOS…

Press ENTER to partition or format hard disks.

ESC = Exit

AlphaBIOS Console

3-3

3.2

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

Figure 3–3 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

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 is reached by pressing
F1 once, and 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 3–3.
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 3–4).

3-4 XP900 Console Reference

Figure 3–4 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

AlphaBIOS Console

3-5

3.3

System Configuration

3.3.1

Displaying the System Configuration
The Display System Configuration screen gives 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
information you need.

Figure 3–5 Display System Configuration Screen
Display System Configuration
Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals
System Type:

AlphaStation XP900

Processor: Alpha 21264-4, Revision V1.8.208 (1 Processor)
Speed:
466 MHz
Cache:
2 MB
Memory:
512 MB
Floppy Drive A:
Floppy Drive B:
Keyboard:

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

AlphaBIOS Version: 6.40-1

ESC = Exit

3-6 XP900 Console Reference

990121.1130

F1= Help

Display the system configuration as follows:
1. Start AlphaBIOS, select Display System Configuration, and press Enter.
2. 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:
•

System board

•

Hard disk

•

PCI bus

•

SCSI configuration

•

ISA configuration (detected ISA devices)

•

Memory

•

Integrated peripherals

The sections that follow explain the display for each component.

AlphaBIOS Console

3-7

3.3.2

System Board Configuration

Figure 3–6 System Board Configuration
Display System Configuration
Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals

➊

System Type:

➋ Processor:
➌
Speed:
➍
Cache:
➎ Memory:

AlphaStation XP900

Alpha 21264-4, Revision V1.8.208 (1 Processor)
466 MHz
2 MB
512 MB

Floppy Drive A:
Floppy Drive B:
Keyboard:

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

➏ AlphaBIOS Version: 6.40-1
ESC = Exit

3-8 XP900 Console Reference

990121.1130

F1= Help

➊ System type — The model number of the system.
➋ Processor — The model and revision of the processor chip. Revisionlevel information can be useful in troubleshooting problems with
technical support personnel.

➌ Speed — The speed of the processor.
➍ Cache — The amount of static RAM cache memory installed.
➎ Memory — The amount of main memory in the system.
➏ Firmware version — The version of AlphaBIOS currently running on
the system.

AlphaBIOS Console

3-9

3.3.3

Hard Disk Configuration

Figure 3–7 Hard Disk Configuration
Display System Configuration

F1= Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals

➊

➋

Disk 0

ATAPI #0, SCSI ID 0
8063 MB
QUANTUM FIREBALL SE8 API.
Partition 1
4095 MB
FAT
➐
Partition 2
➏
6 MB ➑ FAT
Partition 3
3962 MB
FAT

➌

➍

➎

ENTER =Select ESC = Exit

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.

3-10 XP900 Console Reference

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

➋ Controller – The brand and model of the 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, FAT or NTFS, may result in different usable
capacity because of the differences in storage management 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, 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, since 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 unrecognized (if the partition is
unformatted).

AlphaBIOS Console

3-11

3.3.4

PCI Configuration

Figure 3–8 PCI Configuration
Display System Configuration

F1= Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals

➊

➋

➌

➍

Device Name
AcerLabs USB 5237
AcerLabs PCI-ISA
DIGITAL
DIGITAL
AcerLabs IDE
Matrox Millenium

Device Type
USB
ISA bridge
Ethernet
Ethernet
IDE
VGA

Revision
3
195
65
65
193
0

Physical Slot
Embedded
Embedded
Embedded
Embedded
Embedded
Slot 3

ENTER = Select ESC =Exit

3-12 XP900 Console Reference

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

Figure 3–9 PCI Slots

PCI Slot 4

64 Bit

PCI Slot 3

64 Bit

PCI Slot 2
PCI Slot 1

64 Bit
32 Bit

PK1045-99

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.
2. Use the arrow keys to select the device for which you want additional detail.
3. Press Enter, and the detail is displayed.
4. Press Escape to return to the table of PCI devices.
The Advanced PCI Information screen is shown in Figure 3–10.

AlphaBIOS Console

3-13

Figure 3–10 Advanced PCI Information
Display System Configuration
Advanced PCI Information

➊

➋

F1=Help

➌

Bus Number=0, Device Number=1, Function Number=0

➍
Configuration Space:
Register

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

ENTER

00
02
04
06
08
09
0a
0b
0c
0d
0e
0f
10

Hex
1090
5237
0280
0280
03
10
03
0c
08
20
00
00
03884000



=Continue

➊ 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.
Press ESC to return to the list of PCI devices.

3-14 XP900 Console Reference

3.3.5

SCSI Configuration

Figure 3–11 SCSI Configuration
Display System Configuration
Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
 ISA Configuration
Memory Configuration
Integrated Peripherals

F1= Help

ATAPI #0
ATAPI #1

➊
ATAPI #0, SCSI ID 255, SCSI Bus 0

➋

➌

➍

➎

SCSI

Device

Size

Description

Disk 0

8063

Quantum Fireball SE8 API

ENTER = Select ESC =Exit

AlphaBIOS Console

3-15

➊ 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 scheme in numbering controllers 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 controlled
by the controller. This is usually done with jumpers or a thumb wheel
attached to the drive housing.

➌ Device type —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 field 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.

3-16 XP900 Console Reference

3.3.6

Memory Configuration

Figure 3–12 Memory Configuration
Display System Configuration

F1= Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals

System Memory Configuration
Bank 0: 64 MB (32 MB per DIMM)

-- Starting Address = 0x00000000

Bank 1: 64 MB (32 MB per DIMM)

-- Starting Address = 0x40000000

ESC =Exit

AlphaBIOS Console

3-17

3.3.7

Integrated Peripherals

Figure 3–13 Integrated Peripherals
Display System Configuration

F1=Help

Systemboard Configuration
Hard Disk Configuration
PCI Configuration
SCSI Configuration
ISA Configuration
Memory Configuration
Integrated Peripherals

Integrated Peripheral State

➊

➋

➌

➍

Serial 0:
Enabled [ port 0x3f8, IRQ 4 ]
Serial 1:
Enabled [ port 0x2f8, IRQ 3]
Parallel:
Enabled [ port 0x3bc, IRQ 7]
Floppy Ctrl: Enabled [ port 0x3f0, IRQ 6, DMA2]
Kbd/Mouse: Enabled [ port 0x60, kbd IRQ 1, mouse IRQ 12]
Acer IDE Chnl 0: Enabled [ port 0x1f0, IRQ 14]

ESC

=Exit

➊ 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 for data 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.

3-18 XP900 Console Reference

3.4

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 Utility (LFU) to
perform the update. The LFU exit command causes a system
reset.

Figure 3–14 Updating Firmware
AlphaBIOS Setup

F1=Help

Display System
AlphaBIOS upgrade…
Hard Disk Setup…
CMOS Setup…
Network Setup…
Install Windows NT…
Utilities
About AlphaBIOS…

Press ENTER to install new firmware image(s) from floppy, CD-ROM, or
Network.

ESC

=Exit

AlphaBIOS Console

3-19

As new versions of Windows NT are released, it might be necessary to upgrade
AlphaBIOS to the latest version. Also, as improvements are made to
AlphaBIOS, you may wish to upgrade to take advantage of new features.
Use this procedure to upgrade from an earlier version of AlphaBIOS:
1. Insert the diskette or CD-ROM containing the AlphaBIOS upgrade.
2. If you are not already running AlphaBIOS Setup, restart your system and
press F2 when the Boot screen is displayed.
3. In the main AlphaBIOS Setup screen, select AlphaBIOS Upgrade and
press Enter.
The system is reset and the Loadable Firmware Update (LFU) utility is
started.
4. When the upgrade is complete, issue the LFU exit command. The system is
reset and you are returned to AlphaBIOS.

3-20 XP900 Console Reference

3.5

Setting Up the Hard Disk
Either execute an express or a custom hard disk setup. An
express setup, described here, creates the recommended
partitions on the first hard disk, but it does not map bad sectors.
Custom hard disk setup is described in Sections 3.5.1 and 3.5.2.

Figure 3–15 Hard Disk Setup Screen
Hard Disk Setup

➊

➋

➌

➍

Disk 0

AIC78XX #0, SCSI ID 0
DEC
RZ1CB-CS (C)
Partition 1
Partition 2
➏

Disk 1

AIC78XX #0, SCSI ID 1
DEC
RZ1CB-CS (C)
Partition 1

F1= Help

➎
4091 MB

➐

4085 MB
FAT
6 MB ➑ FAT
4091 MB
4091 MB

NTFS

➒
INSERT =New DEL = Delete

F6 =Format

F7 =Express ESC

=Exit

CAUTION: Hard disk changes are immediate; unintended data loss could
occur, 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.

AlphaBIOS Console

3-21

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

➎ 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. 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 necessary for the NTFS file system, since 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 unrecognized (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 to back up any data you
want to save on the partition. 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.

3-22 XP900 Console Reference

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 once Windows NT has been installed.
To perform an express hard disk setup
1. If you have any needed information on your disk, back it up before
proceeding.
2. Start AlphaBIOS Setup, select Hard Disk Setup, and press Enter.
3. Press F7 to enter Express Setup.
4. Press F10 to continue with the setup.

AlphaBIOS Console

3-23

3.5.1

Creating and Deleting Partitions Manually
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 3–16 Create New Partition Dialog Box
Hard Disk Setup
Disk 0

QLISP1040 #0, SCSI ID 3
510 MB
Partition 1
200 MB
Unused
310 MB
Create new partition, Disk 0 Partition 2

NTFS

Disk 1
NTFS
FAT
Available space:

310 MB

New Partition Size:

200

ENTER

= Continue

ESC

= Cancel

To create a partition
1. Start AlphaBIOS and select Hard Disk Setup. Press Enter.
2. Select the disk on which to create the partition.
3. If one or more partitions already exist on the disk, select the unpartitioned
space.
4. Press Insert. A dialog box is displayed, similar to Figure 3–16.
5. Type the size of the partition to create and press Enter.

3-24 XP900 Console Reference

To delete a partition
1. Start AlphaBIOS and select Hard Disk Setup. Press Enter.
2. Select the partition to be deleted (see ➊ in Figure 3–17).
3. Press Delete. A dialog box is displayed (see ➋).
4. Press F10 to confirm the deletion.

Figure 3–17 Delete Partition Dialog Box
Hard Disk Setup
Disk 0

➊
Disk 1

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

510 MB
200 MB
200 MB
100 MB

NCRC810 #0, SCSI ID 5
Partition 1
Parti

1001
995

MB
MB

NTFS
FAT

Delete Disk 0, Partition 2
The delete operation will destroy all
data on partition 2 of Disk 0. ➋
Press F10 to continue. Press ESC to
Cancel.
F10

=Continue

ES C

=Cancel

AlphaBIOS Console

3-25

3.5.2

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

Figure 3–18 Formatting a FAT Partition
Hard Disk Setup
Disk 0

➊
Disk 1

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

510
200
200
100

MB
MB
MB
MB

NCRC810 #0, SCSI ID 5
Partition 1
Parti

1001
995

MB
MB

➋

Choose Format Method:
Format Method

Standard
Format
Standard Format
Quick Format

F10

=Continue

3-26 XP900 Console Reference

ES C

=Cancel

NTFS
Unrecognized

NTFS
FAT

To format a FAT partition
1. Start AlphaBIOS and select Hard Disk Setup. Press Enter.
2. Select the partition to be formatted (see ➊ in Figure 3–18).
3. Press F6. A dialog box is displayed, 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 3–19 is displayed
while the drive is formatted, showing the progress of the formatting.
Standard formatting maps bad sectors.
4. Select a format method and press Enter.

Figure 3–19 Standard Formatting
Hard Disk Setup
Disk
0

Disk
1

QLISP1040 #0,
510
MB
Partition 1
Partition 2
Unused
NCRC810

#0,

Partition
Partition

SCSI

1
2

3
200
200
100

MB
MB
MB

1001

995 MB
6 MB

NTFS
Unrecognized

NTFS
FAT

Formatting…
25%
ESC

=Cancel

AlphaBIOS Console

3-27

3.6

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 3–20 Standard CMOS Setup Screen
CMOS Setup

1 Date: Friday,

Time:

April
1999

F1=Help

1999

13:22:27

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-0749d

To enter Standard CMOS Setup
Start AlphaBIOS, select CMOS Setup, and press Enter.

3-28 XP900 Console Reference

➊ 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
language 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 key) — Saves changes made in both the standard
and advanced modes of CMOS Setup.

Continued on next page

AlphaBIOS Console

3-29

Figure 3–21 Advanced CMOS Setup Screen
CMOS Setup

Advanced CMOS Setup

➊ PCI Parity Checking:
➋ Power-up Memory Test:
➌ AlphaBIOS Password Option:
➍ Console Selection:

Disabled
Full
Disabled
Windows NT Console
(AlphaBIOS)

➎ Warm Reboot:

Enabled



Press ∏ or  to to enable or disable detection of PCI bus parity error.
Some non-compliant PCI option boards do not work properly with PCI parity
checking enabled.

➏
ESC

= Discard Changes

F10

= Save Changes

To Enter Advanced CMOS Setup
1. Start AlphaBIOS, select CMOS Setup, and press Enter.
2. In the Standard CMOS Setup screen, press F6.

3-30 XP900 Console Reference

➊ 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 powerup 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 Tru64 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.

➎ Warm Reboot — Enable (the default) results in the system restarting
normally on a shutdown and restart from the operating system.
Disable results in the necessity to restart the machine by pressing
reset or power-cycling.

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

3-31

3.7

Installing Operating System
Install your operating system from the CD-ROM. Up to three
versions of the operating system can be resident in the system at
one time. Read the instructions carefully; it is easy to install
the wrong CD-ROM driver.

Figure 3–22 Installing Windows NT
AlphaBIOS Setup
Display System Configuration…
AlphaBIOS Upgrade…
Hard Disk Setup…
CMOS Setup…
Network Setup…
Install Operating System
Utilities
About AlphaBIOS…

Press ENTER to install Windows NT.

ESC =Exit

3-32 XP900 Console Reference

F1= Help

If Windows NT was installed at the factory, Windows NT setup will start
automatically the first time the system powers up.
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.
2. Perform an express hard disk setup: return to the main AlphaBIOS Setup
screen, select Hard Disk Setup, and press Enter.
3. Put the Windows NT CD into the CD-ROM drive.
4. 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

3-33

3.8

Selecting the Version of Windows NT
Up to three versions of Windows NT can reside on the system at
one time. Select the version that will be started from the
Operating System Selection Setup screen.

Figure 3–23 Operating System Selections
Operating System Selection Setup
Primary Operating System

Windows NT Client 4.0
Windows NT Client 5.0
Boot Name:
Boot File:
OS Path:
OS Options:
INSERT = New
DEL = Delete

Windows NT Client
4.0
Disk 0, partition 2

\os\winnt40\osloader.exe

Disk 0,

\WINNT4

partition 1

= Edit

= Primary

= Copy

= Validate

ES
C
F10

= Discard Changes

= Save Changes

Operating System Selection Setup
Windows NT Client 5.0
Windows NT Client 4.0
Boot Name:
Boot File:
OS Path:
OS Options:
INSERT
DEL

= New

= Delete

Primary Operating System

Windows NT Client
5.0
Disk 0, partition 2
Disk 0, partition 1

\os\winnt50\osloader.exe
\WINNT5

= Edit

= Primary

= Copy

= Validate

3-34 XP900 Console Reference

ES
C
F10

= Discard Changes

= Save Changes

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 Tru64 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 is displayed on the AlphaBIOS
Boot screen for each operating system installed on the system. It is not
normally necessary to modify operating system selections, since the Windows
NT installation creates and modifies operating system selections as needed. If
you add SCSI controllers after the installation of Windows NT, it may be
necessary to modify operating system selections. Depending on what kind of
SCSI controller is added, in which slot it is placed, and where its driver is in the
startup order relative to other existing controllers, the disk numbering may
change and modification of operating system selections may be required.

AlphaBIOS Console

3-35

3.9

Designating a Primary Operating System

3.9.1

Selecting a Primary Operating System

Figure 3–24 Primary Operating System
AlphaBIOS 5.29
Please select the operating system to start:

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

Date:
Time:

Friday,
11:26:22

Nov

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 4.0
Windows NT Server 5.0

Primary Operating System

PK-0720D-97

3-36 XP900 Console Reference

Three versions of Windows NT can reside on the system at the same time. This
is 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 that you select as the primary operating system is the one that
automatically starts if the Auto Start option is enabled in AlphaBIOS.
Figure 3–24 illustrates the relationship between multiple installations of the
operating-system, 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 is displayed, choose OS Selection Setup.
2. The Operating System Selection Setup screen is displayed. Select the
primary operating system from the list displayed.

AlphaBIOS Console

3-37

3.9.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 3–25 Operating System Selection Setup
Operating System Selection Setup

Windows NT Server 4.0

2
3
4
5

Primary Operating System

Boot Name: Windows NT Server 4.0
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-0737C-97

AlphaBIOS boots Windows NT in two stages. The first stage involves reading
an OS Loader program from a disk. The OS Loader program is named
OSLOADER.EXE. The selection for the operating system must describe the
path where AlphaBIOS will find the OS Loader program. 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.

3-38 XP900 Console Reference

➊ 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. 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 the user does not usually modify it.
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 is displayed, 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.

➍ 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 is displayed, 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.

AlphaBIOS Console

3-39

➎ 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 is displayed
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 is
displayed 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. Select the OS selection you want to
copy and press F7. A dialog box is displayed with the values of your OS
selection. You can then edit the OS selection fields. If you do not make
any changes, a duplicate copy of the OS selection you copied is made.

3-40 XP900 Console Reference

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.
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 is displayed 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

3-41

3.10 Switching from AlphaBIOS to SRM Console
You can run firmware-based diagnostics from the SRM console.
You must be in the SRM to boot OpenVMS or UNIX. To switch
from AlphaBIOS to the SRM console, press the Halt/Reset button
on the control panel, and the system will power up. Press the
Halt/Reset button as the system is going through self-tests and
you will be at the SRM console.
Alternatively, select Tru64 UNIX (SRM) or OpenVMS (SRM) from
the Advanced CMOS Setup screen and reset the system.

Figure 3–26 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

3-42 XP900 Console Reference

Firmware-based diagnostics are run from the SRM console. To boot Tru64
UNIX or OpenVMS, you need to change the Halt/Reset jumper on the
motherboard (see Appendix A).
Follow this procedure to switch from AlphaBIOS to SRM:
1. In AlphaBIOS, select CMOS Setup and press Enter.
2. In the CMOS Setup screen press F6. The Advanced CMOS Setup screen
is displayed.
3. Select Tru64 UNIX console (SRM) or OpenVMS console (SRM) and
press F10.
4. The CMOS Setup screen is displayed. Press F10 to save the change.
5. Reset the system by powering off and then on again for the changes to take
effect.
To return to the AlphaBIOS console, issue the alphabios or nt command at the
SRM console prompt.

AlphaBIOS Console

3-43

3.11 Running Utility Programs
Maintenance programs such as RAID configuration utilities are
run from the AlphaBIOS Utilities menu.

Figure 3–27 Run Maintenance Program Dialog Box

PK14656-98

➊ Program name — The program to be run. It must be an executable
program with an .EXE extension. 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 available disks and partitions, press the Alt and down
arrow keys at the same time. Once the list is displayed, use the arrow
keys to cycle through the selections.
3-44 XP900 Console Reference

3.11.1

Running Utilities from a Graphics Monitor

1. Start AlphaBIOS Setup. If the system is in the SRM console, set the SRM
console environment variable to graphics and issue the command
alphabios.
2. From AlphaBIOS Setup, select Utilities, then select Run Maintenance
Program from the submenu that is displayed, and press Enter. See Figure
3–28.
3. In the Run Maintenance Program dialog box (Figure 3–27), 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.
4. Press Enter to execute the program.

Figure 3–28 AlphaBIOS Utilities Menu

PK1467-98

AlphaBIOS Console

3-45

3.11.2

Running Utilities from a Serial Terminal

Utilities are run from a serial terminal in the same way as from a monitor with
graphics capabilities enabled. The menus are the same, but some keys are
different.

Table 3-1 AlphaBIOS Option Key Mapping
AlphaBIOS Key

VTxxx Key

F1
F2
F3
F4
F5
F6
F7
F8
F9
F10
Insert
Delete
Backspace
Escape

Ctrl/A
Ctrl/B
Ctrl/C
Ctrl/D
Ctrl/E
Ctrl/F
Ctrl/P
Ctrl/R
Ctrl/T
Ctrl/U
Ctrl/V
Ctrl/W
Ctrl/H
Ctrl/[

1. Start AlphaBIOS Setup by issuing the command alphabios.
2. Press F2 in the AlphaBIOS Boot screen.
3. From AlphaBIOS Setup, select Utilities, and select Run Maintenance
Program from the submenu that is displayed. Press Enter.
4. 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.
5. Press Enter to execute the program.

3-46 XP900 Console Reference

Chapter 4
Remote Management Console

The remote management console (RMC) provides a command-line user interface
for entering commands to monitor and control the system. In addition to doing
routine monitoring, you can invoke the command-line interface to perform
remote power on/off, halt, and reset.
The RMC can detect alert conditions such as overtemperature, fan failure, and
power supply failure and automatically dial a pager phone number or another
computer system to notify the remote operator of the alert condition.
This chapter explains the operation and use of the RMC. Sections are:
•

RMC Components

•

Remote Halt (In/Out)

•

Terminal Setup

•

Configuring Remote Dial-In

•

Operating Modes

•

Configuring Dial-Out Alert

•

Entering the RMC

•

Dialing In

•

SRM Environment
Variables for COM1

•

Resetting RMC to Factory
Defaults

•

Status Monitoring

•

Troubleshooting Tips

•

Remote Power (On/Off)

•

RMC Commands

Remote Management Console

4-1

4.1

RMC Components
The RMC resides in an independent microprocessor on the
system motherboard and allows a remote operator to connect to
the system COM1 port from a modem or from a serial terminal
or terminal emulator.

Figure 4–1 Location of RMC Components on Motherboard

RMC PIC
Processor

1
1

RMC
Jumper

Halt/Reset
Jumper
PK0246b

The RMC logic is implemented using an 8-bit microprocessor, PIC17C44, as the
primary control device. The RMC PIC is programmed with code to control
access to various environmental status bits.
You can gain access to the RMC as long as AC power is available to the system
(through the wall outlet). Thus, if the system fails, you can still access the RMC
and gather information about the failure. The jumper position shown in Figure
4–1 is the default position set in manufacturing which enables the RMC.

4-2

XP900 Console Reference

4.2

Terminal Setup
Remote connection is made through a modem connected to the
COM1 port. To set up the modem, you first use a local terminal
on the COM1 port to set up the parameters of the modem and
RMC connection. You then disconnect the terminal and connect
the modem.

Figure 4–2 Setups for RMC Mode

PK1051

You can connect a terminal or a modem to the COM1 port, but not both at the
same time. You use the terminal to set RMC parameters for the connection,
then connect the modem. See Section 4.9.

Remote Management Console

4-3

4.3

Operating Modes
RMC runs in three modes on this system: Snoop, soft bypass, and
firm bypass. The bypass modes are set with the set com1_mode
command from the SRM console.

Figure 4–3 Bypass Mode
System
COM1

SRM/AlphaBIOS
Consoles
Operating System

DUART
COM1 Port
UART

RMC PIC
Processor

Bypass
Modem Port
UART

RMC COM1
Port (Local)

Modem

RMC>

Local Serial Terminal
(MMJ Port)

RMC>

Remote Serial Terminal
or Terminal Emulator

PK0908b

NOTE: The internal system COM1 port should not be confused with the
external COM1 serial port on the back of the system. The internal
COM1 port is used by software to send data either to the COM1 port on
the system or to the RMC modem port if a modem is connected.

4-4

XP900 Console Reference

Snoop Mode (Default Mode)
In snoop mode data partially bypasses the RMC. The data and control signals
are routed from the system COM1 port to the external modem port, but the
RMC taps into the data lines and listens passively for the RMC escape
sequence. If it detects the escape sequence, it enters RMC mode.
The escape sequence is also delivered to the system on the bypassed data lines.
If you decide to change the default escape sequence, be sure to choose a unique
sequence so that the system software does not interpret characters intended for
the RMC.
Because snoop mode does not filter every piece of data, it is useful when you
want to monitor the system but also ensure optimum COM1 performance.
Bypass Modes
In bypass modes, note that the internal system COM1 port is connected directly
to the modem port. The RMC passively listens to the escape sequence from the
external COM1 port, when the RMC escape sequence is captured.
Soft Bypass Mode
In soft bypass mode all data and control signals are routed directly from the
system COM1 port to the external modem port, and the RMC does not listen to
traffic on the COM1 data lines. If an alert condition or loss of carrier occurs,
however, the RMC detects it and switches automatically into snoop mode. In
soft bypass mode, the RMC also initializes the modem for dialing in and dials
out when an alert is detected.
Soft bypass mode is useful if management applications need the COM1 channel
to perform a binary download, because it ensures that RMC does not
accidentally interpret some binary data as the escape sequence.
Firm Bypass Mode
Firm bypass mode effectively disables the RMC. All data and control signals
are routed directly from the system COM1 port to the external modem port. In
firm bypass mode, the RMC dial-in and call-out features are disabled. Firm
bypass mode is useful if you want the system, or an application (such as Insight
Manager or ServerWorks)—not the RMC—to fully control the modem port and
you want to disable RMC features.

Remote Management Console

4-5

4.4

Entering the RMC

You type an escape sequence to invoke the RMC. You can enter
RMC from a modem or the local serial console terminal. You can
enter the RMC from the local terminal regardless of the current
operating mode. You can set up RMC parameters.
1. Invoke the RMC from a serial terminal by typing the following default
escape sequence:
^[^[ rmc
This sequence is equivalent to typing Ctrl/left bracket, Ctrl/left bracket, and
rmc. On some keyboards, the Esc key functions like the Ctrl/left bracket
combination.
To exit RMC, enter the quit command. This action returns you to
whatever you were doing before you invoked the RMC.

4.5

SRM Environment Variables for COM1
Several SRM environment variables allow you to set up the
COM1 serial port for use with the RMC.

You may need to set the following environment variables from the SRM console,
depending on how you decide to set up the RMC. See Chapter 2 for information
on setting SRM environment variables.

Table 4–1 SRM Environment Variables for COM1
Variable

Function

com1_baud

Sets the baud rate of the COM1 serial/modem port. The
default is 9600.

com1_flow

Specifies the flow control on the serial port. The default is
software.

com1_mode

Specifies the COM1 data flow paths so that data either
flows through the RMC or bypasses it. This environment
variable can be set from either the SRM or the RMC.

com1_modem

Specifies to the operating system whether or not a modem
is present.

4-6

XP900 Console Reference

4.6

Status Monitoring
Use the RMC status command to check the current state of the
system’s sensors as well as the current escape sequence and
alarm information.

PLATFORM STATUS
Firmware Revision: V1.0
System Power: ON
RMC Halt: Deasserted
RMC Power Control: ON
Power Supply: OK
System Fans: OK
CPU Fan: OK
Temperature: 31.0°C (warnings at 55.0°C, power-off at 60.0°C)
Escape Sequence: ^[^[RMC
Remote Access: Disabled
RMC Password: set
Alert Enable: Disabled
Alert Pending: YES
Init String: AT&F0E0V0S0=2
Dial String: ATXDT8,18007598888
Alert String: ,,,,,,,1066278#,,,,,,,,1#,,,,30140#;
Com1_mode: SNOOP
Last Alert: AC Loss
Watchdog Timer: 00 seconds
Autoreboot: OFF
Logout Timer: 20 minutes
User String:

Table 4–2 Status Command Fields
Field
Firmware Revision
System Power
RMC Halt

Meaning
Revision of RMC firmware on the microcontroller.
On = System is on.
Off = System is off.
Asserted = System has been halted.
Deasserted = Halt has been released from halt.

Continued on next page.

Remote Management Console

4-7

Table 4–2 Status Command Fields (Continued)
Power Control On = System has powered on from RMC.

Off = System has powered off from RMC.

Power Supply

OK = Auxiliary 5V is working.

System Fans

OK = PCI and system fan are operating.
FAIL = PCI or system fan failure has been detected.

CPU Fan
Temperature
Escape Sequence

Reports current temperature and system limits.
Current escape sequence for access to RMC console.

Remote Access

Enable = Modem for remote access is enabled.
Disable = Modem for remote access is disabled.

RMC Password

Set = Password set for modem access.
Not set = No password set for modem access.

Alert Enable

Enabled = Dial-out enabled for sending alerts.
Disabled = Dial-out is disabled for sending alerts.

Alert Pending

Yes = Alert has been triggered.
No = No alert has been triggered.

Init String

Initialization string that was set for modem access.

Dial String

Phone number dialed when an alert occurs.

Alert String

Identifies the system that triggered the alert to the paging
service. Usually the phone number of the monitored system.

Com1_mode

Can be set to snoop, soft-bypass, or firm-bypass.
See Section 4.3.

Last Alert

Type of alert (for example, power supply failed).

Watchdog timer

Autoreboot
Logout Timer
User String

4-8

OK = Fan on CPU chip is operating.
FAIL = CPU fan failure has been detected.

Reports time set by user using set wdt command; can be up
to 60 seconds in increments of 10. When it times out, alert is
sent.
ON = Autoreboot feature enabled.
OFF = Autoreboot feature disabled.
The amount of time before the RMC terminates an inactive
modem connection. The default is 20 minutes.
Notes supplied by user.

XP900 Console Reference

4.7

Remote Power (On/Off)
You can power a monitored system on or off from the RMC using
console monitor commands.

Figure 4–4 Power Button

PK1043b

Remote Power-On
The RMC power {on, off} commands can be issued remotely to power the
system on or off. They have the same function as the Power button on the
control panel. The Power button, however, has precedence.
•

If the system has been powered off with the Power button, the RMC cannot
power the system on.

•

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

When you issue the power on command, the terminal exits the RMC and
reconnects to the system’s COM1 port.
RMC> power on
Returning to COM port
RMC> power off

Remote Management Console

4-9

4.8

Remote Halt (In/Out)
You can issue a halt to a monitored system from the RMC using
console monitor commands. Under OpenVMS and Tru64 UNIX,
the system will halt. Under Windows NT, the command will be
ignored.

Figure 4–5 Halt/Reset Jumper

Setting for
OpenVMS
& Tru64 UNIX

Setting for
Windows NT
PK0246c

The RMC halt in command can be issued remotely to halt the system.
The RMC halt out command can be issued to deassert the halt.
These commands have the same function as the Halt button on the control
panel (see Figure 4–6) for OpenVMS and Tru64 Unix. The Halt button under
Windows NT operates differently because the Halt/Reset jumper is set
differently (see Figure 4–5).

4-10

XP900 Console Reference

Figure 4–6 Halt/Reset Button

PK1043c

Table 4–3 Halt/Reset Button Function under Operating Systems
Operating System

OpenVMS and
Tru64 UNIX
Windows NT

Function

Suspends the operating system and
returns control to the SRM or RMC console.
Resets the system.

The Halt button, however, does not override the halt {in, out} commands. If
you halt the system with halt in, you must use halt out to deassert the halt
state.
When you issue either the halt in or halt out command under OpenVMS or
Tru64 UNIX, the terminal exits the RMC and reconnects to the system’s COM1
port.
RMC> halt in
Returning to COM port
RMC> halt out
Returning to COM port

Remote Management Console

4-11

4.9

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

Connect your serial terminal to the COM1 port and turn it on. Set up the RMC
parameters. Then disconnect the serial terminal, connect the modem, and
check your configuration.

Example 4–1 Dial-In Configuration
RMC> set password
➊
RMC Password: ****
Verification: ****
➋
RMC> set init
Init String: AT&F0E0V0X0S0=2
➌
RMC> enable remote
Modem will be enabled when it is connected ➍
RMC> status
➎
.
.
Remote Access: Enabled

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

Initialization String

Motorola 3400 Lifestyle 28.8

AT&F0E0V0X0S0=2

AT &T Dataport 14.4/FAX

AT&F0E0V0X0S0=2

Hayes Smartmodem Optima 288
V-34/V.FC + FAX

AT&FE0V0X0S0=2

4-12

XP900 Console Reference

➊

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

➋

Sets the initialization string. The string is limited to 31 characters and
can be modified depending on the type of modem used. Because the
modem commands disallow mixed cases, the RMC automatically converts
all alphabetic characters entered in the init string to uppercase.
The RMC automatically configures the modem’s flow control according to
the setting of the SRM com1_flow environment variable. The RMC also
enables the modem carrier detect feature to monitor the modem
connectivity.

➌

Enables remote access to the RMC modem port by configuring the modem
with the setting stored in the initialization string.

➍

Because you have the serial terminal connected and not the modem, the
system responds that the modem will be enabled when it is connected.

➎

Verify the settings and check that the Remote Access field is set to
Enabled, ready for the modem to be connected.

➏

Disconnect the serial terminal, connect the modem and check that the
modem’s TR light is lit. See Section 4.11 for dialing in instructions.

Remote Management Console

4-13

4.10 Configuring Dial-Out Alert
When you are not monitoring the system through a modem
connection, you can use the RMC dial-out alert feature to
remain informed of system status. If dial-out alert is enabled,
and the RMC detects alarm conditions within the managed
system, it can call a preset pager number.
You must configure remote dial-in for the dial-out feature to be enabled. See
Section 4.9. To set up the dial-out alert feature, enter the RMC from the local
serial terminal.

Example 4–2 Dial-Out Alert Configuration
RMC> set dial
➊
Dial String: ATXDT9,15085553333
RMC> set alert
➋
Alert String: ,,,,,,5085554444#;
RMC> enable alert
➌
Modem will be enabled when it is connected
RMC> clear alert
➍
RMC> send alert
➎
Alert detected!
# Disconnect the serial terminal and connect the modem at COM1 port.
# You should receive an alert within 30 minutes of modem connection.
# Once the alert is received, reconnect the serial terminal and clear the test alert.
RMC> clear alert
➏
RMC> status
➐
. . .
Alert Enable: Enabled

A typical alert situation might be as follows:
•

The RMC detects an alarm condition caused by excessive temperature.

•

The RMC dials the operator’s pager and sends a message identifying the
system.

•

The operator dials the system from a remote serial terminal.

•

The operator invokes the RMC, checks system status, and powers down the
managed system.

4-14

XP900 Console Reference

•

When the problem is resolved, the operator powers up and reboots the
system.

•

The dial-out alert feature is enabled as part of the dial-in setup. See
Section 4.9.

The elements of the dial string and alert string are shown in Table 4–4. Paging
services vary, so you need to become familiar with the options provided by the
paging service you will be using. The RMC supports only numeric messages.

➊

Sets the string to be used by the RMC to dial out when an alert condition
occurs. The dial string must include the appropriate modem commands to
dial the number. In this example, 1-508-555-3333 is the pager number.

➋

Sets the alert string, typically the phone number of the modem connected
to the remote system. The alert string is appended after the dial string,
and the combined string is sent to the modem when an alert condition is
detected. In this example, the system’s modem number is 1-508-555-4444.

➌

Enables the RMC to page a remote system operator.
Because the modem is not connected at the COM1 port at this time, the
RMC notifies you that the alert will be enabled at connection.

➍

Clears any alert that may be pending. This ensures that the send alert
command will generate an alert condition.

➎

Forces an alert condition. This command is used to test the setup of the
dial-out alert function. It must be issued from the local serial terminal.
The RMC tries to send the alert immediately. Because the modem is not
connected at the COM1 port at this time, the RMC resets the paging
interval to at most 30 minutes, and will send the alert again. If the pager
does not receive the alert within 30 minutes, re-check your setup.

➏

Clears the current alert so that the RMC can capture a new alert. The last
alert is stored until a new event overwrites it. The Alert Pending field of
the status command becomes NO after the alert is cleared.

➐

Verifies the settings. Check that the Alert Enable field is set to Enabled.

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

Remote Management Console

4-15

Table 4–4 Elements of Dial String and Alert String
Dial String
The dial string is case sensitive. The RMC automatically converts all
alphabetic characters to uppercase

ATXDT

AT = Attention.
X = Forces the modem to dial “blindly” (not seek the 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)

The number for an outside line (in this example, 9). Enter
the number for an outside line if your system requires it.
, = Pause for 2 seconds.

15085553333

Phone number of the paging service.

Alert String

,,,,,,

Each comma (,) provides a 2-second delay. In this example,
a delay of 12 seconds is set to allow the paging service to
answer.

5085553332#

A call-back number for the paging service. The alert string
must be terminated by the pound (#) character.

;

A semicolon (;) must be used to terminate the entire string.

4-16

XP900 Console Reference

4.11 Dialing In
To start a remote monitoring session, dial in, using the dial
string you entered during the setup procedure. Enter the RMC
modem password, and then type the escape sequence.
1. After completing the setup procedure, dial in, enter the RMC password at
the Modem password: prompt. When a prompt is displayed, type the escape
sequence. In the following example, the system is at the SRM console when
the modem connection is made.
ATDT15085554444
RINGING
RINGING
CONNECT 9600/ARQ/V32/LAPM
Modem password: *********
Welcome to RMC V1.0
>>> ^[^[rmc
RMC>

(sequence is not echoed)

2. At the RMC> prompt, enter commands to monitor and control the remote
system.
3. When you have finished your modem session, enter the hangup command
to cleanly terminate the modem session and disconnect from the system.

Remote Management Console

4-17

4.12 Resetting the RMC to Factory Defaults
If the RMC escape sequence is set to something other than the
default, and the sequence has been lost or forgotten, the RMC
must be reset to factory settings to restore the default escape
sequence. See Appendix A.

Figure 4–7 RMC Jumpers (Default Positions)

RMC PIC
Processor

1
RMC
Jumper

PK0246c

WARNING: To prevent injury, access is limited to persons who have
appropriate technical training and experience. Such persons are expected
to understand the hazards of working within this equipment and take
measures to minimize danger to themselves or others.

4-18

XP900 Console Reference

4.13 Troubleshooting Tips
Table 4–5 lists possible causes and suggested solutions for
symptoms you might see.

Table 4–5 RMC Troubleshooting
Symptom

Possible Cause