This manual describes the general operation of Compaq
AlphaServer DS10, Al phaSer ver DS10L and AlphaStation DS10
systems. It presents the SRM console (the command-line
interface for Tru64 UNIX and OpenVMS operating systems),
AlphaBIOS (the graphics interface for Linux), and remote
console management.
Compaq Computer Corporation
September, 2000
2000 Compaq Comput er Corporation.
Compaq and the Compaq logo registered in U.S. Pat ent and Trademark Office.
AlphaServer, AlphaStat ion, and OpenVMS are trademarks of Compaq Computer Corporation.
Tru64 is a trademark of Compaq Information Technologies Group, L.P. in t he U nited States and/ or other
countries.
UNIX is a trademark of the OPEN GROUP in the United States and other countries.
All other pr oduct names mention ed herein may be the t rademarks or registered trademar ks of their respective
companies.
Compaq shall not be liable for technical or editorial errors or om issions contained herein. T he information
in this document is subject to change without notice.
The information in this publication is subject to change without notice and
is provided "AS IS" WITHOUT WARRANTY OF ANY KIND. THE
ENTIRE RISK ARISING OUT OF THE USE OF THIS INFORMATION
REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE
LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL,
SPECIAL, PUNITIVE OR OTHER DAMAGES WHATSOEVER
(INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF
BUSINESS PROFITS, BUSINESS INTERRUPTION OR LOSS OF
BUSINESS INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL
APPLY REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF
EITHER PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY
SOUNDS IN CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER
THEORY OF LEGAL LIABILITY, AND NOTWITHSTANDING ANY
FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.
The limited warranties for Compaq products are exclusively set forth in the
documentation accompanying such products. Nothing herein should be
construed as constituting a further or additional warranty.
FCC Notice: See Appendix - "Regulatory Co m pliance Notic es".
A–2Jumpers and Factory Default Positions..............................................A-11
ix
Preface
Intended Audience
This manual is for service providers, managers and operators of Compaq
AlphaServer DS 10, AlphaServer DS10L, and AlphaStati on DS10 systems.
Document Structure
This manual uses a structured documentation design. Topics are organized into
small sections, usually consisting of two facing pages. Most topics begin with an
abstract that provides an overview of the section, followed by an illustration or
example. The facing page contains descriptions, procedures, and syntax
definitions.
This manual has three chapters, two appendices, and an index:
•Chapter 1, Operations, provides basic operating instructions, including
powering up the system, booting, and operating system installation.
•Chapter 2, SRM and AlphaBIOS Consoles, presents the command-line
interface that supports the Tru64 UNIX and OpenVMS operating systems
and the graphical interface that supports some utility programs. 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. AlphaBIOS is used to run utilities.
•Chapter 3, 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.
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.
Revision levels, dates and devices listed in examples are for example only; your
results may vary according to the configuration of your system.
NOTE: In many ways DS10 and DS10L systems are identical. This manual
uses DS10 systems for most illustrations and examples; DS10 screen
examples may have more devices shown than equivalent DS10L
screens, and other minor differences may appear. Where significant
differences exist, an illustration or example of a DS10L is presented
separately.
Documentation Titles
This following DS10/DS10L documentation is available.
DS10 Quick Setup PosterEK-DS10S-CP
DS10 User Reference Card
DS10 Rackmount Guide
DS10 User Information CDAG-RHD8B-BE
DS10L Quick Setup PosterEK-DS10L-CP
DS10L User R eference C ard
DS10L User Information CDAG-RLD4A-BE
Information on the Internet
Visit the Compaq Web site at www.compaq.com for service tools and more
information about the AlphaServer DS10 / DS10L, AlphaStation DS10 systems.
xii
296382-021
EK-DS10S-UR
EK-DS10S-RM
EK-DS10L-UR
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 OpenVMS
• Installing OpenVMS
• Switching Between Operating Systems
• Updating Firmware
• Using the Halt Button
• Halt Assertion
NOTE: In many ways the DS10 and DS10L systems are identical. This
manual uses DS10 systems for most illustrations and examples. Where
significant differences exist, an illustration or example of a DS10L is
presented separately.
Operations 1-1
1.1 Powering Up the System
To power up the system, check your power setting (DS10 only),
then press the On/Off button ❶ to the On position. Check the
control panel LEDs. See Figure 1–1 and Figure 1–2 for the DS10,
and Figure 1–3 for the DS10L.
Figure 1–1 Check Power Setting – DS10
115V
230V
PK1047a
DS10 / DS10L Console Reference
1-2
Figure 1–2 Location of DS10 Control Panel and On/Off Button
PK1043b
Table 1–1 Control Panel Functions – DS10
SymbolFunction
Halt button. Under OpenVMS an d T ru6 4 U N IX , suspe nds the operating
system and returns control to the SRM conso le.
Environmental amber LE D . O n indicate s Temperature or Fan LE D s ar e
on. Flashes when oper at ing s ystem invokes it as an ale rt.
Temperature amber LED. On indicates internal temperature exceeds
operating condit ion s. T he sys te m shu ts d ow n 30 seconds after this LED
lights.
Fan amber LED. On indicates th at at least one of the th re e fans in the
system has failed. The system shuts down 30 s econds after this LED lig ht s.
Disk Activity green LED . F las hes w hen interna l system disks are
accessed.
Power Present green LED. On when power is present in the system.
Power button. Push in to star t th e system and connect power. Push aga in
to remove power and s to p the s ystem.
Operations 1-3
Figure 1–3 Location of DS10L Control Panel and On/Off Button
1
PK2216
Table 1–2 Control Panel Functions - DS10L
SymbolFunction
Halt button. Under OpenVMS an d T ru6 4 U N IX , suspe nds the operating
system and returns control to the SRM conso le.
Environmental amber LE D . O n indicate s Temperature or Fan LE D s ar e
on. Flashes when oper at ing s ystem invokes it as an ale rt.
Temperature amber LED. On indicates internal temperature exceeds
operating condit ion s. T he sys te m shu ts d ow n 30 seconds after this LED
lights.
Fan amber LED. On indicates th at at least one of the th re e fans in the
system has failed. The system shuts down 30 s econds after this LED lig ht s.
Disk Activity green LED . F las hes w hen interna l 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 po wer. Push
again to remove pow er a nd s top th e system.
DS10 / DS10L Console Reference
1-4
1.2 Power-Up Display
DS10 systems have four physical PCI slots; the DS10L system
has one, hence the different power-up displays shown below.
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 – DS10
256 Meg of sys te m memory ➊
probin g ho se 0, PCI
probing PCI-to-ISA bridge, bus 1
probing PCI-to-PCI bridge, bus 2 ➋
bus 0, slo t 9 -- ew a -- DE500-BA Ne twork Cont roller
bus 0, slo t 11 -- ew b -- DE500-B A Network Co ntroller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
➊Memory size is determined.
➋The PCI bridges and attendant buses (indicated as IODn by the console)
are probed and the devices are reported. I/O adapters are configured.
➌
Power-up slot 14 corresponds to the bottom physical slot, slot 1.
Slot LocationPhysical Slot NumberLogical Slot Number
Top417
Second from top316
Second from bottom215
Bottom114
➍These devices are behind bridge of the card in logical slot 15, physical slot
2, 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 theos_type environment variable is set to unix or openvms, the Tru64 UNIX
or OpenVMS operating system boots. See Section 2.18 for information on
environment variables.
DS10 / DS10L Console Reference
1-6
Example 1–2 Power-Up Display - DS10L Serial and Graphics
Consoles
Note: There is only one PCI slot on the DS10L; its logical slot number is 17.
Serial Console
256 Meg of sys te m memory ➊
probin g ho se 0, PCI
probing PCI-to-ISA bridge, bus 1
bus 0, slo t 9 -- ew a -- DE500-BA Ne twork Cont roller
bus 0, slo t 11 -- ew b -- DE500-B A Network Co ntroller
bus 0, slot 13 -- dqa -- Acer Labs M1543C IDE
bus 0, slot 13 -- dqb -- Acer Labs M1543C IDE
bus 0,
Testin g th e Sy stem
Testin g th e di sks (read on ly)
Testing the Network
System Temperature is 36 degrees C
Initializing GCT/FRU at 1f6000
Memory size is determined.
The PCI bridges and attendant buses (indicated as IODn by the console)
are probed and the devices are reported. I/O adapters are configured.
➋
➌The power-up logical slot is always 17 on the DS10L.
➍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 theos_type environment variable is set to unix or openvms, the Tru64 UNIX
or OpenVMS operating system boots.
See Section 2.18 for information on environment variables. See Chapter 2
for SRM console and AlphaBIOS information.
Operations 1-7
Graphics Console
Os_type UNIX-console CIPCA drive not started
Testin g th e Sy stem
Testin g th e di sks (read on ly)
Testing the Network
System Temperature is 36 degrees C
Initializing GCT/FRU at 1f6000
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.
(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:
************************************************************************
* Starting Desktop Login on display :0...
* Wait for the Desktop Login screen before logging in.
************************************************************************
➍
Operations 1-9
➊
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, andboot_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.18
for information about environment variables.
➍The operating system banner displays.
DS10 / DS10L Console Reference
1-10
1.3.2 Booting from a Remote Disk
Example 1–4 Booting Tru64 UNIX from a Remote Disk
>>> show device➊
. . .
ewa0.0.0.8.0 EWA0 08-00-2B-E2-9C-60
>>>
>>> boot -flags an -p rotocols bootp ewa ➌
(boot ewa0.0.0.4.1 -f lags an)
Building FRU table
➋
Trying BOOTP boot
Broadcasting BOOTP Re quest...
Received BOOTP Packet File Name: /var/adm/ris/ris0. alpha/hvmunix
local inet address: 1 6.122.128.26
remote inet address: 16.122.128.59
TFTP Read File Name: /var/adm/ris/ris0.alpha/ hvmunix
bootstrap code read i n
base = 200000, image_ start = 0, image_bytes = 9a0fa0
initializing HWRPB at 2000
initializing page tab le at 1f2000
initializing machine state
setting affinity to t he primary CPU
jumping to bootstrap code
Secondary boot progra m - Thu Aug 1 22:33:13 E ST 1999
Loading vmunix ...
.
.
.
The system is ready.
Tru64 UNIX Version V4.0E (sabl28.eng.pko.dec.com) console
.
➍
Operations 1-11
➊
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 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, andboot_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.18
for information about environment variables.
➍
The operating system banner displays.
DS10 / DS10L Console Reference
1-12
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–5 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.]
➋
Operations 1-13
➊
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.
DS10 / DS10L Console Reference
1-14
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–6 Booting OpenVMS from a Local Disk
>>> show device➊
dka200.2.0.7.1 DKA200 RZ1CB-CA LYJ0
>>>
>>> show boot_reset➋
boot_reset ON
>>> 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
Operations 1-15
Example 1–6 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.18 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, andboot_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.18
for information about environment variables.
➎
➎
The operating system banner displays.
DS10 / DS10L Console Reference
1-16
1.5.2 Booting OpenVMS from a Disk on a Cluster
Example 1–7 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
➎
Operations 1-17
➊
The bootdef_dev environment variable specifies the default boot
device.
➋
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 disk dua110.0.0.8.0is 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, andboot_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.18
for information about environment variables.
➎The operating system banner prints.
DS10 / DS10L Console Reference
1-18
Loading...
+ 152 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.