For booting the OpenVMS Alpha system disk, first follow the
preparatory steps listed in the following section. Then, to boot
the disk, follow the steps in
How to Boot the New System Disk.
Preparing to Boot
the New System Disk
Before you boot the new system disk, you must do the following:
At the console prompt (>>>),
enter the SET BOOTDEF_DEV command in the following format:
SET BOOTDEF_DEV target-drive
Substitute the device name of the system disk for target-drive. The SET BOOTDEF_DEV command tells the system which
disk to boot from. For example, if the system disk has the device
name DKA400, enter the following command and press Return:
>>>SET BOOTDEF_DEV DKA400
If the system disk
is connected to a hierarchical storage device (HSx), the format for specifying that drive is different.
For example, on a DEC 7000 series system connected to an HSC device,
the command is similar to the following:
If you have configured
your system with a boot option for your system disk,
you will see your system disk as the first boot option in the EFI
Boot Manager menu, as in the following example. You can either press
Return to boot the system disk or wait 10 seconds, at which point
the system disk boots automatically.
If you have not
configured your system with a boot option for your disk,
then follow these steps:
Press
Return or any other key (you might see text that instructs you to
"hit any key to cold reboot"), and the machine displays several
boot-related messages and then the EFI Boot Manager menu, as in the
following example:
Go to the EFI Shell prompt by selecting the EFI
Shell [Built-in] option from the EFI Boot Manager menu (this is
the default choice if you do not select one within 10 seconds).
A display similar to the following appears. An explanation of the
two types of devices shown (blk and fs) follows.
fs
fs devices are file-structured
logical partitions on physical disks included with your Integrity
server system. Generally, fs0: corresponds to the target disk on
which you installed OpenVMS I64 (unless the DVD was not removed,
in which case fs1: would correspond to the target disk). For example,
if the target disk is DKA0, then fs0: most likely corresponds to
the target disk. On the other hand, if the target disk is a DKA100
or DKB200 or similar, then the corresponding EFI device depends
on what partitions are configured on the target disk.
blk
The blk devices listed are
block devices. These may include the DVD device as well as the diagnostic
partitions on OpenVMS system disks. Diagnostic partitions are intended
for use with the HP IPF Offline Diagnostics and Utilities CD provided with
the purchase of your Integrity server. (For more information about this partition,
see
Alternative Ways to Initialize the System Disk.)
To boot the OpenVMS I64 system
disk, type the following command at the EFI Shell prompt, where fs
n: is the device associated with the system disk (it
probably will be fs0:):
Shell> fsn:\efi\vms\vms_loader.efi
The OpenVMS I64 operating system will start booting. A display
similar to the following appears, followed by the prompt for user
name and password:
HP OpenVMS Industry Standard 64 Operating System, Version 8.2
(c) Copyright 1976-2004 Hewlett-Packard Development Company, L.P.
Note that HP Integrity servers maintain a System Event Log
(SEL) within system console storage, and OpenVMS I64 automatically
transfers the contents of the SEL into the OpenVMS error log. During
a successful boot operation while using a console, you might see
a message indicating that the Baseboard Management Controller (BMC)
SEL is full. You can safely continue when the BMC SEL is full by
following the prompts; OpenVMS will process the contents of the
SEL. If you want to clear the SEL manually, enter the clearlogs SEL command at the EFI Shell prompt as in the following example:
Shell> clearlogs SEL
This command deletes the contents of the SEL. The command
is available only with current system firmware versions.
If your Integrity server is configured with a Management Processor
(MP) and you see a BMC event log warning while connected to the
MP console, you can also clear the BMC event log by using MP. Press
Ctrl/B to revert to the MP> prompt. At the MP> prompt,
enter SL (from the main menu) and use the C option to clear the
log.
HP recommends that you load and use the most current system
firmware. For more information about updating the system firmware,
see
Firmware on Integrity Server Systems.
Next Steps
When you boot OpenVMS from a new system disk, a special startup
procedure runs that does the following:
Gives you the opportunity to configure the
system for standalone or OpenVMS Cluster operation (see
Joining an OpenVMS Cluster).
Runs AUTOGEN to evaluate
your hardware configuration, estimate typical work loads, and set
system parameters (see
Running AUTOGEN).