E-4Boot Sequence from an FC System Disk......................................................................................295
14List of Examples
Preface
About this document
This document explains how to install, or upgrade to, Version 8.4 of the HP OpenVMS Alpha
or OpenVMS for Integrity servers operating system. Also included are the prerequisites for
installing and upgrading your software and the required and optional tasks you can perform
after you complete the software installation or upgrade.
Intended Audience
This manual is intended for anyone responsible for installing or upgrading the OpenVMS Alpha
or OpenVMS Integrity servers operating system, and for the startup, shutdown, and backup
operations required on Alpha or Integrity servers running this software.
When to Use This Manual
Use this manual if you need to install or upgrade the OpenVMS operating system software
yourself or if you need to perform certain startup, shutdown, or backup operations. If you received
factory-installed software (FIS) with your Alpha system or Integrity servers, see the release notes
provided with the software, anduse this manual for any informationnot coveredin those release
notes.
New and Changed Information in this Edition
The following information is new or revised for OpenVMS Version 8.4:
•With this release, the operating environments (OEs) providing OpenVMS Integrity server
elements have been changed:
—Beginning with OpenVMSVersion 8.4, the Base Operating Environment (BOE) replaces
the Foundation OperatingEnvironment (FOE) as the tier of the Operating Environment
for OpenVMS for Integrity servers. The BOE offers the base operating system and
networking transport products and more.
—The High Availability Operating Environment (HA-OE) includes some of the OpenVMS
products that were formerly included with the Mission Critical Operating Environment
(MCCOE) and Enterprise Operating Environment (EOE). The HA-OE additionally offers
the products included with the BOE like the following (they were formerly part of the
EOE and are now part of the BOE):
◦DECram
◦OpenVMS Management Station
For more information, see the HP Operating Environments for OpenVMS for Integrity serversSoftware Product Description (SPD 82.34.xx).
•OpenVMS Integrity servers now support a power management interface from the Integrity
Lights Out (iLO) console and from the Insight Power Manager (IPM) software. The power
management interface isavailable only onsystems thatsupport the iLO powermanagement
interface. For more information about iLO power management interface available for your
Integrity servers, see the iLO MP Operations Guide. IPM provides centralized monitoring
and control of server power consumption and thermal output. (Although OpenVMS still
supports the SYSGEN parameter CPU_POWER_MGMT, the iLO interface takes precedence
over this parameter.) Before installing OpenVMS Integrity servers, check that power
management is set in the state that you prefer. For more information, see the HP OpenVMSSystem Management Utilities Reference Manual.
•OpenVMS Integrity servers support virtual keyboard, video, and mouse (vKVM) with
Integrity servers (rx2660, rx3600, and rx6600 Integrity servers and the BL860c and BL870c
About this document15
Server Blade products). HP iLO management processors make it simpler, faster and less
costly to manage your Integrity servers remotely. The iLO Advanced KVM Card on the
Integrity servers combines a physical graphics/USB card with additional logic to permit the
Lights Out Advanced features of Virtual Media and Integrated Remote Console. Licenses
to use iLO/vKVM are provided with the Server Blade products. For other server products,
licenses might have to be purchased separately.
Document Organization
This manual is organized as follows:
•Chapter 1 (page 21) defines key terms and provides information about hardware and
software components. Review this chapter before performing any installation or upgrade.
•Chapter 3 (page 45) explains how to install the OpenVMS Alpha or OpenVMS Integrity
servers operating system. It also includes instructions for installing the OpenVMS Guest
operating system.
•Chapter 4 (page 83) describes how to prepare your system for an upgrade.
•Chapter 5 (page 95) supplements Chapter 4 (page 83) with additional tasks you must
perform before upgrading an OpenVMS Cluster system.
•Chapter 6 (page 103) describes how to upgrade the operating system.
•Chapter 7 (page 125) describes the tasks you must perform after installing or upgrading the
operating system.
•Appendix A (page 167) contains instructions on booting, halting, and shutting down
OpenVMS Alpha systems. It also includes instructions on configuring boot options.
•Appendix B (page 187) provides an overview of the utilities available with HP Integrity
servers, and explains how to configure the system console, how to configure boot options,
and how to boot the OpenVMS operating system.
•Appendix C (page 227) explains how to set up and perform network booting for installations
and upgrades using the InfoServer utility, a software application available on certain
OpenVMS Alpha and OpenVMS Integrity server systems.
•Appendix D (page 245) explains how to set up and perform provisioning (installations and
upgrades) of OpenVMS on one or more Integrity servers in a network using HP SIM. In
addition, this appendix explains how to use vMedia to install or upgrade OpenVMS on
Integrity servers in the network.
•Appendix E (page 289) explains how to boot the Fibre Channel storage device.
•Appendix F (page 301) explains how to back up and restore the system disk.
•Appendix G (page 309) discusses the OpenVMS internationalization data kit (VMSI18N) and
how to install it.
•Appendix H (page 311) explains how to prepare your OpenVMS system and your PC to run
the OpenVMS Management Station server and client software.
•Appendix I (page 321) explains how to remove the OpenVMS operating system from your
disk.
•Appendix J (page 323) explains alternate methods of initializing an OpenVMS Alpha or
OpenVMS Integrityservers system disk and includes information about diagnostic partitions
on OpenVMS Integrity servers system disks.
•The Glossary (page 325) defines key terms used in this manual.
16
Typographical Conventions
The following conventions are used in this manual:
MeaningConvention
Ctrl/X
PF1X
Enter
…
.
.
.
( )
[ ]
|
A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while
you press another key or a pointing device button.
A sequence such as PF1X indicates that you must first press and release the key labeled
PF1 and then press and release another key (x) or a pointing device button.
In examples, a key name in bold indicates that you press that key.
A horizontal ellipsis in examples indicates one of the following possibilities:− Additional
optional arguments in a statement have been omitted.− The preceding item or items can
be repeated one or more times.− Additional parameters, values, or other information can
be entered.
A vertical ellipsis indicates the omission of items from a code example or command
format; theitems are omitted because they are not important to the topic being discussed.
In command format descriptions, parentheses indicate that you must enclose choices in
parentheses if you specify more than one. In installationor upgrade examples, parentheses
indicate the possible answers to a prompt, such as: Is this correct? (Y/N) [Y]
In command format descriptions, brackets indicate optional choices. You can choose one
or more items or no items. Do not type the brackets on the command line. However, you
must include the brackets in the syntax for OpenVMS directory specifications and for a
substring specification in an assignment statement. In installation or upgrade examples,
brackets indicate the default answer to a prompt if you press Enter without entering a
value, as in: Is this correct? (Y/N) [Y]
In commandformat descriptions,vertical bars separate choices within brackets or braces.
Within brackets, the choices are optional; within braces, at least one choice is required.
Do not type the vertical bars on the command line.
{ }
bold type
italic type
UPPERCASE TYPE
Example
–
numbers
Related Information
Before installing, upgrading, or using the OpenVMS operating system on your computer, be
sure you have access to the following documents. Some of the documents listed here are from
In command format descriptions, braces indicate required choices; you must choose at
least one of the items listed. Do not type the braces on the command line.
Bold type represents the name of an argument, an attribute, or a reason. In command
and scriptexamples, bold indicates user input. Bold type also representsthe introduction
of a new term.
Italic type indicates important information, complete titles of manuals, or variables.
Variables include information that varies in system output (Internal error number), in
command lines (/PRODUCER=name), and in command parameters in text (where dd
represents the predefined code for the device type).
Uppercase type indicates a command, the name of a routine, the name of a file, or the
abbreviation for a system privilege.
This typefaceindicates code examples, command examples, and interactive screen displays.
In text, this type also identifies website addresses, UNIX command and pathnames,
PC-based commands and folders, and certain elements of the C programming language.
A hyphen at the end of a command format description, command line, or code line
indicates that the command or statement continues on the following line.
All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal
radixes—binary, octal, or hexadecimal—are explicitly indicated.
Typographical Conventions17
an earlier OpenVMS version documentation set. They have not been revised, they remain valid
for OpenVMS Version 8.4.
•Cover Letter for HP OpenVMS Version 8.4 and any other cover letters included with your kit.
•HP OpenVMS Version 8.4 New Features and Documentation Overview, which describes
enhancements and new features included in this release of the OpenVMS Integrity servers
operating system and provides an overview of the documentation that supports OpenVMS.
•HP OpenVMS License Management Utility Manual, which explains how to use the License
Management Facility (LMF), the license management tool for the OpenVMS operating
system. The manual describes licensing requirements and the tasks required to manage
licenses.
•HP OpenVMS Version 8.4 Release Notes, which provides important supplementary information
about the OpenVMS 8.4 release.
•HP OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations, if you plan
to install your system in an OpenVMS Cluster environment.
•The most recent version of the DECwindows Motif for OpenVMS Installation Guide and ManagingDECwindows Motif for OpenVMS Systems (if you plan to install and customize DECwindows
Motif for OpenVMS software).
•HP Open Source Security for OpenVMS, Volume 1: Common Data Security Architecture, which
provides information about CDSA software.
•HP Open Source Security for OpenVMS, Volume 2: HP SSL for OpenVMS, which provides
information about HP SSL software.
•HP Open Source Security for OpenVMS, Volume 3: Kerberos, which provides information about
Kerberos software.
•HP Availability Manager Installation Instructions, which provides information about Availability
Manager software and is available at the following website:
•For documentation related to the Performance Data Collector (TDC), see the following
website:
http://www.hp.com/products/openvms/tdc/
•The following networking software documents (if you plan to install and configure
DECnet-Plus for OpenVMS,DECnet Phase IV for OpenVMS, orTCP/IP Services for OpenVMS
software):
—HP TCP/IP Services for OpenVMS Installation and Configuration
—DECnet-Plus for OpenVMS Installation and Configuration
Documentation for these networking products is included on the OpenVMS Version 8.4
Online Documentation CD. Hardcopy documentation must be purchased separately.
•For documentation related to Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP),
, see the HP Instant Capacity User’s Guide on the following website:
•HP SIM documentation is available in the Information Library on the following website:
http://www.hp.com/go/hpsim
•HP gWLM documentation is available in the Information Library on the following website
(select the Information Library link and then the Manuals, Release Notes, Manpages link
and see the Version A.40 manuals):
http://www.docs.hp.com/en/vse.html
Information about gWLM and documentation for installing the gWLM agent on OpenVMS
Integrity server systems, including release notes, is available at the following website:
•The hardware manuals that are supplied with your Alpha or Integrity servers computer.
These manuals provide detailed information about your system hardware, including the
operation of the system unit, the drives, and the monitor.
During the course of installing, upgrading, or using the OpenVMS operating system on your
computer, you could refer to the following documents as well:
•HP OpenVMS License Management Utility Manual, which contains detailed information about
registering your software licenses.
•HP OpenVMS System Manager's Manual and the HP OpenVMS System Management UtilitiesReference Manual, which contain information about system management operations and
utilities that you might need to use when you install, upgrade, customize, and maintain
your OpenVMS system. The HP OpenVMS System Management Utilities Reference Manual:M-Z provides complete information about using the PCSI utility PRODUCT command to
add or remove files, install other software, and related operations.
•HP Volume Shadowing for OpenVMS, which you might need if you are installing or upgrading
the OpenVMS operating system on a shadowed system disk.
•HP OpenVMS Management Station Installation Guide, which provides information about getting
started, setting up, and using OpenVMS Management Station.
For additional information about HP OpenVMS products and services, see the following website:
http://www.hp.com/go/openvms
For information about managing nPartitions on midrange or Superdome servers, see the nPartitionAdministrator's Guide (previously titled HP System Partitions Guide: Administration for nPartitions).
For the latest hardware documentation for HP Integrity servers, see the following website:
http://docs.hp.com/en/hw.html
For the latest hardware documentation for Alpha computers, see the following website:
http://www.hp.com/go/alphadocs
Publishing History
The document printing date and part number indicate the document’s current edition. The
printing date will change when a new edition is printed. Minor changes may be made at reprint
without changing the printing date. The document part number will change when extensive
changes are made. Document updates may be issued between editions to correct errors or
document product changes. To ensure that you receive the updated or new editions, you should
subscribe to the appropriate product support service. See your HP sales representative for details.
You can find the latest version of this document on line at:
Please send comments to the following email address:
openvmsdoc@hp.com
How to Order Additional Documentation
For more information about how to order additional documentation, see the OpenVMS
documentation website:
http://www.hp.com/go/openvms/doc/order
20
1 Getting Started
This chapter defines key terms and describes preliminary procedures you must perform before
installing or upgrading your OpenVMS system.
NOTE:Throughout thisbook, examples are takenfrom OpenVMS Integrity servers' installations
or upgrades except where stated otherwise. OpenVMS DCL commands are in uppercase, while
HP Integrity servers console commands are in lowercase.
1.1 Key Terms
Table 1-1 lists a few key terms you need to know before you install or upgrade the system.
Table 1-1 Definitions of Terms
DefinitionTerm
HP Integrity Virtual
Machines (Integrity
VM)
HSx device
InfoServer
Integrity VM is a soft partitioning andvirtualization technology that provides operating system
isolation, with sub-CPU allocation granularity and shared I/O. Integrity VM can be installed
on an Integrity server or a hardware partition (nPartition) running HP-UX. OpenVMS can be
one of the guest operating systems supported.
A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS
Cluster system environment share disks.The disk on which you install or upgrade theoperating
system can be connected to one of these systems (for example, an HSV or HSG).
A general-purpose disk storage server. For OpenVMS Alpha systems, the InfoServer may be
an independent hardware device or, beginning with OpenVMS Version 8.3, it may be a utility
(software application) on an OpenVMS system. On OpenVMS Integrity server systems, the
InfoServer is only available as a software application on an OpenVMS system.
The InfoServer hardware can serve CDs only (it does not support DVDs); thus, this hardware
device cannot serve the OpenVMS Integrity servers operating environment (OE) DVD. The
InfoServer utility can serve both DVDs and CDs (for OpenVMS Integrity servers and OpenVMS
Alpha systems, respectively). The systems connected to the same LAN can use the InfoServer
utility to boot the OpenVMS operating system from a virtual drive (instead of the local drive).
For more information about the InfoServer utility, see the HP OpenVMS Version 8.4 New Featuresand Documentation Overview.
local drive
operating system
media
provisioning
source drive
system disk
target drive
A drive on your computer system, such as a CD, DVD, or disk drive (hard drive), that is
connected directly to the computer. If you have a standalone computer, it is likely that all
drives connected to the computer system are local drives.
The OpenVMS Alpha operating system CD or the OpenVMS for Integrity servers Operating
Environment DVD (OE DVD) included with an OpenVMS distribution kit, which contains
the OpenVMS operating system and the installation and other procedures described in this
manual.
Using HPSystems Insight Manager (HP SIM), the process of installingor upgradingOpenVMS
on one or more Integrity servers automatically. HP SIM initiates the process and the installation
or upgrade automatically continues in the background.
The drive that holds the operating system media during an upgrade or installation. This can
be a local drive or an InfoServer virtual drive. The drive contains the OpenVMS Alphaoperating
system CD or the OpenVMS for Integrity servers Operating Environment DVD, or a copy of
it.
The disk from which OpenVMS is typically booted. During an installation or upgrade, this is
the target disk because it receives files from the source drive. After installation or upgrade,
the target drive is booted and becomes the system disk.
The drive that holds the target system disk during the upgrade or installation. Note: the target
drive must be a hard drive, not a CD or DVD.
1.1 Key Terms21
Table 1-1 Definitions of Terms (continued)
DefinitionTerm
Virtual KVM
(vKVM)
virtual media
(vMedia)
Virtual keyboard, video, and mouse feature included with Integrated Lights Out (iLO) 2
Management Processor (MP) on Integrityservers (rx2660, rx3600, and rx6600 Integrity servers
and the BL860c and BL870c Server Blade products). The feature allows you to connect a virtual
serial line from your PC to Integrity servers, enabling your PC, keyboard, andmouse to function
as if directly connected to the server. Your window displays the contents of the Integrity server's
VGA.
A virtual-disk capability included with Integrated Lights Out (iLO) 2 Management Processor
(MP) on Integrity servers. vMedia provides virtual devices that mimic physical hardware
devices. For example, it can provide a virtual CD/DVD drive that emulates the DVD drive on
a PCand connects over thenetwork toyour Integrity servers as if it were physically connected.
You can use vMedia to install OpenVMS on Integrity servers that do not include a built-in
DVD drive or that are physically located elsewhere. vMedia can provide the network service
for HP SIM provisioning, or it can be used independently of HP SIM.
1.2 Getting to Know Your Integrity servers
The OpenVMS operating system is now supported on a wide variety of HP Integrity servers,
including the following:
•Entry-class servers, which include members of the rx16nn, rx26nn, rx36nn, rx46nn, and
rx66nn series and the BladeSystems Integrity BL860c and BL870c Server Blade products
•Midrange servers, which include members of the rx76nn and rx86nn series
•High-end servers (Superdome)
For an up-to-date list of servers supported by the current release of OpenVMS, see the HPOpenVMS Version 8.4 Software Product Description (SPD 82.35.xx).
The hardware, firmware, and software supported might vary significantly from system to system.
Integrity servers are available in many different configurations. The hardware, utilities, and
hardware configuration procedures might differ significantly across models, and even across
versions of the same model. This manual provides basic information about the firmware,
hardware, and utilities offered on Integrity servers. This information is not meant to replace the
hardware documentation. For the most up-to-date and relevant information for your particular
model, see the hardware documentation for your Integrity servers. The hardware documentation
includes model-specific illustrations to guide you. The latest version of documentation for your
server can be found online at:
http://docs.hp.com/en/hw.html
http://www.hp.com/support/itaniumservers
For the latest information about firmware, software requirements, and special considerations
for your Integrity servers, see the HP OpenVMS Version 8.4 Release Notes.
1.2.1 Entering Commands at Integrity servers Console Interfaces
When entering commands for the Integrity servers, if you press Delete on a VTxxx terminal (or
press the key you have mapped to send the DEL/RUBOUT character code in your terminal
emulator), the last character typed might not be deleted, as would be expected on an OpenVMS
Alpha system. The firmware on Integrity servers where that unexpected behavior occurs uses
Ctrl/H to delete the last character typed. On such Integrity servers, you can remap your terminal
to use Ctrl/H instead of DEL/RUBOUT, as described in Section B.1.3 (page 190).
1.2.2 Integrity server Tools
Integrity servers include multiple interfaces for working with various aspects of the server or
server complex. The Management Processor (MP) is available on most Integrity servers. Many
entry-class Integrity servers now come with the Integrated Lights Out (iLO) MP (Integrity iLO
2 MP), which provides a complete remote console experience, including a web-based graphical
22Getting Started
user interface and the functionality provided by vKVM and vMedia. MP and Integrity iLO
provide a service interface that allows access to all hardware and, in a complex, all nPartitions.
The MP is always available, even when the main power source is turned off (MP can operate on
standby power). On cell-based servers (such as rx7620, rx8620, and Superdome), MP is available
whether or not nPartitions are configured or booted in the server complex. You can navigate
from MP to and from the operating system (if it is booted).
The Extensible Firmware Interface (EFI) provides support for operating system loaders and
allows you to configure the firmware and control the booting environment. EFI is accessible only
when the operating system is not booted. On cell-based servers, each nPartition has a separate
EFI console interface. EFI provides support for managing nPartitions. The EFI interface is available
from an nPartition console only when the nPartition is in an active state but has not booted an
operating system.
You can move from the EFI interface to MP and back again. Similarly, you can move from MP
to the operating system and back.
OpenVMS Integrityservers now support a power managementinterface from the Integrity Lights
Out (iLO) console and from the Insight Power Manager (IPM) software. The power management
interface is available only on systems that support the iLO power management interface. For
more information about iLO power management interface available for your Integrity servers,
see the iLO MP Operations Guide. IPM provides centralized monitoring and control of server
power consumption and thermal output. (Although OpenVMS still supports the SYSGEN
parameter CPU_POWER_MGMT, the iLO interface takes precedence over this parameter.) Before
installing OpenVMS Integrity servers, check that power management is set in the state that you
prefer. For more information, see the HP OpenVMS System Management Utilities Reference Manual.
1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures
HP Virtual Connect (VC) is a set of interconnect modules and embedded software available for
HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server
connections. Where most server interconnect choices come with compromises such as too many
cables or too much to manage, VC reduces the number of network cables and simplifies
management while adding the unique ability to wire everything once, then add, replace or
recover servers in minutes instead of hours or days.
VC is enabled with a choice of Ethernet and Fibre Channel modules designed for the HP
BladeSystem. The built-in HP Virtual Connect manager defines a server connection profile for
each server bay—even before a server is installed. This profile establishes the Media Access
Control (MAC) addresses for all Network Interface Controllers (NICs), the World Wide Names
(WWNs) for all Host Bus Adapters (HBAs), and the SAN boot parameters. The profile then holds
them constant so that even if the server is changed, the configuration and connection profile stay
constant. When a new server takes its place, the same profile is assigned.
For more information about VC, select the Virtual Connect networking link at the following
website:
http://www.hp.com/go/bladesystem/virtualconnect
In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the
following location:
A cell-basedserver—such as the HP rx7620, rx8720, or Superdome server—is a hardware complex
that can run one or more operating systems and that supports dividing hardware resources into
nPartitions. Thus, it enables you to configure a complex into one large system or into several
smaller systems.
1.2 Getting to Know Your Integrity servers23
All processors (cores) and memory are contained in cells, each of which can be assigned for
exclusive use by an nPartition. An nPartition defines a subset of the server hardware resources
that is used as an independent system environment. An nPartition has its own EFI system boot
interface and each nPartition boots and reboots independently. Each nPartition provides both
hardware and software isolation so that hardware or software faults in one nPartition do not
affect other nPartitions within the same server complex.
By usingHP software-based nPartition management tools, you can configure nPartition definitions
for a server without physically modifying the server hardware configuration. The main
administration tools for nPartitions are the Partition Manager, which provides a graphical
interface, and the nPartition Commands, which provides a command-line interface. Versions of
these interfaces are provided on HP-UX, Linux, and Microsoft Windows systems. The nPartition
Commands tool is also available on Linux systems. MP and EFI can also perform nPartition
administrative tasks. Slightly different tool sets and capabilities are available on different server
models. For more information, see your hardware documentation. In addition, see the nPartitionAdministrator's Guide (previously titled HP System Partitions Guide: Administration for nPartitions).
1.2.5 Getting Started: Steps After You Unpack Your Integrity servers
When you unpack your Integrity servers, the main steps for getting OpenVMS up and running
are those listed in Table 1-2. As indicated in the third column, some of the instructions are
provided in this manual. However, for the most up-to-date information specific to your Integrity
servers model and version, always refer to the hardware documentation provided for your
Integrity servers.
Table 1-2 Getting OpenVMS Started on Integrity servers
1
your server, connect to the MP serial port.
2
Services for OpenVMS.
3
4
5
From the EFI Shell interface or EFI Boot Manager menu, select
the device for the OpenVMS console.
For systems with iLO console and Insight Power Manager, check
that power management is set to the state that you prefer.
Power on your Integrity servers, insert the OpenVMS Integrity
servers distribution media (DVD) into the drive, cycle power,
and then use the EFI boot menu to boot from the DVD.
Support for the latest HP Integrity servers supporting Intel and
Itanium. For Integrity servers that do not include a built-in
CD/DVD drive, youcan usean external USB CD/DVD drive (you
must supply this drive and the required cable; they are not
included with the Integrity servers). OpenVMS supports the
InfoServer utility, provisioning, and virtual media (vMedia)
devices to allow you to boot, install, or upgrade OpenVMS over
the network.
DocumentationActionStep
Section B.2 (page 191)Connect your console cable to the serial port; if MP is present on
Hardware manualOptionally, configure MP to accept connections over TCP/IP
Section B.2 (page 191); if you ordered
your server preinstalled, console
selections are already made but you
might need to change them
HP OpenVMS System Management
Utilities Reference Manual
For howto poweron and recycle power,
see the hardware documentation; for
instructions on booting the DVD, see
Section 3.2.2 (page 48)
For information on the Infoserver
utility, see Appendix C (page 227)
For information on provisioning and
vMedia, see Appendix D (page 245)
After the initial boot, you need not use EFI to configure boot options. You can configure EFI boot
options while OpenVMS is running by using the OpenVMS Integrity servers Boot Manager
(SYS$MANAGER:BOOT_OPTIONS.COM), as explained in Section B.5.2 (page 205). This utility
is easier to use than EFI and allows you to configure the most pertinent options for your system.
In addition, the OpenVMS installation (and upgrade) procedure can assist you in establishing
and validating boot options for your system disk.
24Getting Started
1.3 Examining Hardware and Software Components
Before you begin an installation or upgrade, be sure you have all the required hardware and
software components, as described in the following sections.
1.3.1 Hardware Components
For hardware components, verify the following::
•Be sure the hardware is installed and verified for proper operation. For detailed information,
see the hardware manuals you received with your computer.
For initial installations on Integrity servers, your console terminal requires a standard
PC-to-PC file transfer cable (also known as a null modem cable; 9-pin female connectors at
each end) to connect a PC, laptop, or similar device that includes terminal emulation software;
alternatively, on most systems you can use a VGA monitor and USB keyboard (and USB
mouse). For information about setting up your system console, see Section B.2 (page 191).
•Be sure you know how to turn on and operate the components of your system, including
the system unit, console, monitor, drives, terminals, and printers. If necessary, read the
hardware manuals that came with these components.
•Make sure you record the installation procedure. You need a transcript if a problem occurs
during installation. If you are using terminal emulation software, set the software to log the
session. Otherwise, set up your system to record the installation procedure on either a
hardcopy terminal or a printer attached to the console terminal. (See your hardware manuals
for more details about connecting those components to your system.)
1.3.2 Software Components
For software components, verify the following:
•Be sure you have all the items listed on the bill of materials contained in the distribution kit.
If your distribution kit is incomplete, notify HP Customer Support and request priority
shipment of any missing items.
•Before installing the OpenVMS operating system software, review all cover letters and
release notes.
1.3.3 OpenVMS Alpha Operating System CD
Included in your OpenVMS Alpha kit is the OpenVMS Alpha operating system CD, which you
use to install or upgrade the operating system, or to perform operations such as backing up the
system disk. The CD is labeled similar to the following:
HP OpenVMS Alpha Version 8.4 Operating SystemCD label
ALPHA084Volume label
The CD label is the printed label on the CD. The volume label is the machine-readable name that
the OpenVMS Alpha operating system and InfoServer systems (or utilities) use to access the CD.
1.3.4 OpenVMS for Integrity servers Operating Environment DVD
Included in your OpenVMS Integrity servers kit is the OpenVMS for Integrity servers OE DVD,
which you use to install the operating system or to perform operations such as backing up the
system disk. The DVD is labeled similar to the following:
HP OpenVMS Version 8.4 for Integrity servers Operating EnvironmentDVD label
I64084Volume label
1.3 Examining Hardware and Software Components25
The DVD label is the printed label on the OE DVD. The volume label is the machine-readable
name that the OpenVMS Integrity servers operating system uses to access and identify the DVD.
1.3.5 Firmware on Alpha Systems
OpenVMS Alpha performs a firmware check each time the system is booted. When you boot the
OpenVMS Alpha operating system CD, the system automatically checks the version of console
firmware that is running on your computer. The system also provides information about how
to update the firmware.
If you do not have the required version of console firmware, the system displays a message similar
to the following:
%SYSBOOT-F-FIRMREV, Firmware rev.nnn is below the absolute minimum ofnnn.
Please update your firmware to the recommended revision nnn,
Alpha Systems Firmware Update Vn.n.
If you do not have the recommended version of console firmware, the system displays a message
similar to the following:
%SYSBOOT-W-FIRMREV, Firmware rev.nnn is below the recommended minimum ofnn.
Please update your firmware to the recommended revision,
which can be found on the firmware CD labeled:
Alpha Systems Firmware Update Vn.n.
The latest firmware CD is included with your OpenVMS Alpha media kit. It includes system
firmware for current and recent Alpha systems and some I/O adapters. Firmware for older
hardware might not be included on the current CD but can be found on previous CDs or online
at:
http://h18002.www1.hp.com/alphaserver/firmware/
HP recommends updating to the latest released firmware for all systems and I/O adapters.
Firmware is released more often than the OpenVMS Alpha operating system. The firmware
version recommendations included in OpenVMS Alpha Version 8.4 might be superseded before
the next version of the OpenVMS Alpha operating system is released.
1.3.6 Firmware on Integrity server Systems
HP Integrity servers include several firmware components (varying with system type), any of
which might need updating. For the minimum versions recommended, see the HP OpenVMSVersion 8.4 Release Notes. HP recommends that you sign up for Subscriber's Choice so that you
can automatically receive email notices regarding the latest firmware updates. Make sure you
register all your products to receive the appropriate firmware update notices. You can sign up
for Subscriber's Choice at the following website:
http://itrc.hp.com
To update entry-class Integrity servers firmware, follow the instructions provided in this section;
for cell-based servers (midrange and high-end), contact HP Customer Support.
To update your firmware, perform the following steps:
1.Determine the current firmware versions on your Integrity servers (see Section 1.3.6.1
(page 27)).
NOTE:To receive notification of new firmware releases for the Integrity servers you own,
you can subscribe (free of charge) for drivers and software alerts, as instructed in
Section 1.3.6.1 (page 27).
2.Create a firmware update CD on any system equipped with a CD or CD/DVD-recordable
drive (see Section 1.3.6.2 (page 27)).
3.Update the firmware on your Integrity servers (see Section 1.3.6.3 (page 28)).
26Getting Started
1.3.6.1 Checking Firmware Version
To determine the firmware version in place on your Integrity servers, you can use the Extensible
Firmware Interface (EFI)info fw command at the EFI Shell prompt, as in the following example.
(For cell-based servers, check the firmware at the nPartition console.)
Shell> info fw
You can also use the EFI Boot Manager to obtain firmware information. With MP, you can use
the MP sysrev command.
NOTE:The info fw command at the EFI> Shell prompt cannot be used while OpenVMS is
running. You can use the MP interface to check firmware on your system while OpenVMS is
running.
NOTE:EFI Shell commands are not case sensitive. However, in this manual, EFI and other
Integrity servers interface commands are displayed in lowercase to help distinguish them from
OpenVMS DCL commands.
For more information about the latest firmware for your Integrity servers, check the HP OpenVMSVersion 8.4 Release Notes. In addition, see the information and resources provided on the HP
Support website by following these steps:
1.Go to the following website:
http://www.hp.com/support/itaniumservers
2.Select the appropriate server in the provided list.
The HP Support page that appears provides a list of tasks and services to choose. To
automatically receive drivers and support alerts from HP (free of charge), select “Signup:
drivers and support alerts” from the list of services (you might need to select “See more...”
to access the signup link), and fill out the forms as instructed.
For more information about firmware for your Integrity servers, select “Download drivers
and software” from the list of tasks, and continue with the next step.
3.On the “Download drivers and software” page, select “Cross operating system (BIOS,
Firmware, Diagnostics, etc.)”.
4.On the resulting page, locate the appropriate firmware (look for the latest update; previous
versions might also be listed), and select the link for the firmware in the “Description”
column.
5.Select the “Release Notes” tab and read the information about the latest version of firmware
available and the instructions on determining the version of firmware in place on your
Integrity servers. Compare your installed version with firmware versions listed in the release
notes.
1.3.6.2 Creating a Firmware Update CD
To create a firmware update CD for your entry-class Integrity servers, you need a CD-recordable
drive and software, plus a blank CD-R or CD-RW disk. (For updating firmware on a cell-based
server, you must contact HP Customer Support.)
NOTE:The following instructions are for recording a DVD on an OpenVMS system. You can
record the DVD on any system or PC, such as a Microsoft Windows computer, a Linux system,
or an HP-UX system.
1.Follow steps 1 through 3 from the preceding section.
2.Locate the appropriate ISO-image firmware file. (Look for the latest update; previous versions
might also be listed along with the latest.) Select the link for that file and read the instructions
for the file included in the release notes, and then download the ISO-image firmware
1.3 Examining Hardware and Software Components27
(zip-compressed) file to your system. (To access the release notes, see step 5 in the preceding
section.)
3.Unzip the firmware file into the corresponding .ISO file. The .ISO file is a block copy of the
firmware disk for the Integrity servers system. On OpenVMS systems, you can obtain the
INFO-ZIP utility from an OpenVMS Freeware CD and use the UnZip utility provided with
INFO-ZIP. OpenVMS Freeware CDs are packaged with the OpenVMS for Integrity servers
OE DVD, and the files on the Freeware CDs are available online at the following website:
www.hp.com/go/openvms/freeware
The following example shows the command for unzipping an .ISO image of the latest
firmware for an rx2600 system (the file name changes with each update of the firmware
available on the website):
4.Record the data on the CD, specifying the .ISO file as the source for the CD. For instructions
on doing this, enter the following command:
$ @SYS$MANAGER:CDRECORD HELP
NOTE:OpenVMS software includes the CD recording tool CDRECORD. For online help,
enter the @SYS$MANAGER:CDRECORD HELP command at the OpenVMS DCL prompt
as shown previously. For CDRECORD source files, check the OpenVMS Open Source Tools
CD supplied with your OpenVMS Integrity servers OE DVD. For more information about
the software, see the following website:
1.3.6.3 Updating Your Firmware from the Firmware Update CD
You update the firmware of an entry-class Integrity servers from the firmware update CD created
in the preceding section. For instructions, see the release notes provided for the firmware you
downloaded.
IMPORTANT:To update Integrity servers firmware on cell-based servers, contact HP Customer
Support.
1.3.7 Device-Naming Conventions
When you perform specific operations, you are asked to specify a device name for the source
drive and one for the target drive. When specifying those device names, note the following
naming conventions:
•When the source drive is a local CD or DVD drive, the device name is similar to the following:
DQA0 (IDE drive) or DNA0 (USB drive)
For a device name, such as DQA0:, note the following conventions:
—DQ is the device code.
—A is the device controller designation.
—0 is the unit number of the device.
•When the target drive is a local disk, the device name is similar to the following:
DKA0:
28Getting Started
•When the source drive is a virtual DVD drive served by the InfoServer, the device name is
typically the following:
DAD1:
•On OpenVMS systems configured in certain OpenVMS Cluster or HSx environments, the
device naming convention is similar to the following:
DUA20.14.0.2.0
The values you specify identify components such as the boot device, controller, unit number
of the boot device, HSx controller node number, and channel numbers. Because these values
vary depending on your specific hardware configuration, see the owner, operator, and
technical service manuals that came with your computer for detailed information.
1.4 Using the Operating System Menu
The following sections describe how to use the operating system menu to install, upgrade, and
modify your system disk, and perform other related tasks.
NOTE:The OpenVMS Alpha CD and OpenVMS Integrity servers DVD menu options are very
similar. This section provides examples from the OpenVMS Integrity servers menu system.
The OpenVMS operating system main menu displaysautomatically when you boot the OpenVMS
operating system from the operating system media (for instructions on how to boot from the
operating system media, see Section 3.2 (page 45)). From the menu, you can choose options to
perform any of the following tasks:
•Install or upgrade the operating system from the operating system media.
•Display a list of products that can be installed from the operating system media.
•Install or upgrade layered products from the operating system media.
•Show which products are installed on your system.
•Reconfigure layered products installed on your system.
•Remove products.
•Find, install, and remove patches, and display and remove recovery data.
•Enter the DCL environment from which you can perform preinstallation or maintenance
tasks, such as mounting or showing devices and backing up or restoring files on the system
disk.
•Shut down the system.
The following is a sample display of the OpenVMS main menu:
.
.
.
***************************************************************
You can install or upgrade the OpenVMS I64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS I64 distribution media (CD/DVD).
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS I64 Version 8.4
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete recovery data
1.4 Using the Operating System Menu29
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?)
Review the following sections to understand how the menu works. Then you can choose
appropriate menu options when you are asked to do so before, during, and after an installation
or upgrade.
1.4.1 Using the Install, Upgrade, or Reconfigure OpenVMS Option (1)
Select option 1 on the operating system main menu to install, upgrade, or reconfigure your
OpenVMS software. Selecting option 1 implements a PCSI utility concept called a platform. The
OpenVMS platform contains:
•The OpenVMS operating system
•Kerberos, Common Data Security Architecture (CDSA), HPBinarychecker, Secure Sockets
Layer (SSL), Performance Data Collector (TDC) (base), and Availability Manager (base),
all of which are installed automatically with OpenVMS, and for OpenVMS Integrity servers
only, WBEM Services for OpenVMS, and WBEM Providers for OpenVMS.
•The optional DECwindows Motif for OpenVMS, DECnet-Plus, DECnet Phase IV, and
TCP/IP Services for OpenVMS products
NOTE:For use of Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP), (supported
on cell-based Integrity servers), and for support of such products as gWLM and HP Systems
Insight Manager (HP SIM), you must install TCP/IP Services for OpenVMS. SSL for OpenVMS
is required and is installed automatically.
Including the optional products in the OpenVMS platform allows you to install or upgrade these
products along with the OpenVMS operating system.
When you choose to upgrade the system disk, and the OpenVMS software on the disk is the
same version, you are given options to reinstall or to reconfigure the OpenVMS system or
reconfigure the OpenVMS platform.
Before installing or upgrading OpenVMS, see the information in the following chapters, as
appropriate:
•Chapter 2: “Preparing to Install in an OpenVMS Cluster Environment” (page 41)
•Chapter 3: “Installing the OpenVMS Operating System” (page 45)
•Chapter 4: “Before Upgrading the OpenVMS Operating System” (page 83)
•Chapter 5: “Preparing to Upgrade in an OpenVMS Cluster Environment” (page 95)
•Chapter 6: “Upgrading the OpenVMS Operating System” (page 103)
NOTE:Before installing or upgrading OpenVMS on a target drive in an OpenVMS Cluster,
make sure the target system disk is not mounted elsewhere in the cluster. The target system disk
must be dismounted clusterwide (except on the system from which the installation or upgrade
is being performed) and must remain so during the installation or upgrade.
When you select option 1 on the operating system main menu, the system asks whether you
want to preserve or initialize the system disk. The display is similar to the following:
There are two choices for Installation/Upgrade:
INITIALIZE - Removes all software and data files that were
previously on the target disk and installs OpenVMS I64.
PRESERVE -- Installs or upgrades OpenVMS I64 on the target disk
and retains all other contents of the target disk.
* Note: You cannot use PRESERVE to install OpenVMS I64 on a disk on
30Getting Started
Loading...
+ 316 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.