B-1InfoServer Booting: Differences Between Alpha and I64 Systems..............................................189
B-2Procedure for Enabling InfoServer Network Booting.................................................................190
13
14
List of Examples
3-1Component Options and Suboptions............................................................................................68
B-1Setting Up the Boot Server and Client.........................................................................................198
15
16
Preface
About this document
This document explains how to install, or upgrade to, Version 8.3-1H1 of the OpenVMS for
Integrity servers (OpenVMS I64) 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 I64
operating system, and for the startup, shutdown, and backup operations required on 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 Integrity server, see the release notes provided with
the software, and use this manual for any information not covered in those release notes.
New and Changed Information in this Edition
The following information is new or revised for OpenVMS Version 8.3–1H1:
•Support for the latest HP Integrity servers supporting Intel® Itanium® Dual-Core processors,
including the HP Integrity BL860c Server Blade
Some of these servers do not include a built-in CD/DVD drive. You can use an external USB
CD/DVD drive (you must supply this drive and the required cable; they are not included
with the Integrity servers). However, OpenVMS Version 8.3–1H1 supports provisioning
and virtual media (vMedia) devices to allow you to boot, install, or upgrade OpenVMS over
the network. For an up-to-date list of servers supported by this release of OpenVMS, see
the HP OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.3-1H1 Software ProductDescription (SPD 82.35.xx).
•Management support, including provisioning, providers, and WBEM infrastructure
OpenVMS on HP Integrity rx3600 and rx6600 servers and on HP Integrity BL860c Server
Blades can be managed from HP Systems Insight Manager (HP SIM) Version 5.2 or later.
HP SIM (an HP implementation of WBEM) provides simplified, centralized management
of multiple servers and platforms through a web-based, unified interface. HP SIM is
supported on OpenVMS from Microsoft Windows® ProLiant servers. The Windows server
requires an OpenVMS plug-in for HP SIM (the plug-in is available from the web; for more
information, see Section C.1.5.1 (page 214)). To be managed by HP SIM, your Integrity server
requires HP WBEM (Web-Based Enterprise Management) Services for OpenVMS and the
HP WBEM Providers forOpenVMS. TheseWBEM products areinstalled automaticallywith
OpenVMS but you must configure them manually. (Configuration instructions for these
products are provided in Section 7.8.5 (page 127) and Section 7.8.6 (page 131), respectively.)
The WBEM products enable HP SIM to retrieve information about the OpenVMS operating
system on your Integrity server and to manage the operating system. For network
functionality, the WBEM products also require HP TCP/IP Services for OpenVMS and HP
SSL.
With provisioning support, you can use HP SIM to install or upgrade OpenVMS quickly
and easily on one or more servers in the network, much in the same way as HP-UX supports
About this document17
provisioning. Such support facilitates installing or upgrading OpenVMS on Integrity servers
that do not include a CD/DVD drive.
Provisioning is supported with HP SIM Version 5.1 or later. You use HP SIM to initiate the
provisioning, after which the installation or upgrade process occurs automatically in the
background. To provide provisioning over the network, you can use HP SIM in two ways:
—In conjunction withthe InfoServersoftware utility (and TCP/IP Services for OpenVMS),
you create a service for a bootable image of OpenVMS (a container file) stored at a
location on the network accessible to the InfoServer. In this use of HP SIM, you can
provision multiple servers (up to 8) simultaneously.
—In conjunction with vMedia, you create an ISO image of the OpenVMS Operating
Environment (OE) DVD, store the image on the server where HP SIM is running, and
use HP SIM to connect vMedia to that image. Using vMedia, you can provision one
server at a time. Currently, provisioning does not support booting from a shadowed
system disk.
For more information about HP SIM, see the Information Library on the following website:
http://www.hp.com/go/hpsim
For information about configuring WBEM Services for OpenVMS and WBEM Providers for
OpenVMS, see Section 7.8.5 (page 127) and Section 7.8.6 (page 131). For information about
setting up and performing provisioning, see Appendix C (page 203).
•Support for virtual media (vMedia)
The vMedia device is the first in a series of virtual-disk capabilities included in the current
generation of management-processor (MP, Integrity iLO 2) hardware. vMedia consists of
two primary components: firmware in MP hardware that emulates a USB DVD and Java™
code that runs on a remote PC and performs I/O to the PC’s local CD/DVD drive. vMedia
can provide you with a virtual CD/DVD drive that connects over the network to your
Integrity server, just as if they are physically connected. You can use vMedia for initial
system installation on a system without a built-in DVD, or remote installation on a system
physically located elsewhere. It also allows you to install layered products, either remotely
or on systems without a built-in DVD. For information about setting up and performing
vMedia provisioning, see Appendix C (page 203).
•Support for 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 cablesor too much to manage, VC reduces the number of network cablesand 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 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
•Support for a VGA console and USB keyboard as console devices for booting
With VGA support, you can now connect a monitor, keyboard, and mouse directly to
connectors provided for that purpose on your Integrity server panel. You no longer need
to use a serial console, including PC/terminal emulator or character-cell terminal as a console.
On systems that do not include an embedded graphics device, you might be able to select
a graphics option card in a PCI slot to be the graphics console. Check your Integrity server
hardware documentation for details. OpenVMS also supports multiple VGA devices on the
same Integrity server. XDELTA boot and conversational (interactive) boot are not supported
over a VGA console. VGA console support for OpenVMS is available for most Integrity
servers. For more information, see Section A.2 (page 152).
•Support of new time zones
Eight new time zones have been added to this release:
—America/Atikokan
—America/Blanc-Sablon
—America/North_Dakota/New_Salem
—Europe/Guernsey
—Europe/Isle_of_Man
—Europe/Jersey
—Europe/Podgorica
—Europe/Volgograd
For information about setting the local time zone for your computer, seeSection 3.3.3
(page 53). The new time zones are not shown in the examples provided in this manual.
•
Document Organization
This manual is organized as follows:
•Chapter 1 (page 25) defines key terms and provides information about hardware and
software components. Review this chapter before performing any installation or upgrade.
•Chapter 3 (page 49) explains how to install the OpenVMS I64 operating system.
•Chapter 4 (page 77) describes how to prepare your system for an upgrade.
•Chapter 5 (page 87) supplements Chapter 4 (page 77) with additional tasks you must
perform before upgrading an OpenVMS Cluster system.
•Chapter 6 (page 95) describes how to upgrade the operating system.
•Chapter 7 (page 113) describes the tasks you must perform after installing or upgrading the
operating system.
•Appendix A (page 149) 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 B (page 189) 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 I64 systems.
•Appendix C (page 203) 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 an
Integrity server in the network.
•Appendix D (page 241) explains how to boot the Fibre Channel storage device.
•Appendix E (page 247) explains how to back up and restore the system disk.
Document Organization19
•Appendix F (page 255) discusses the OpenVMS internationalization data kit (VMSI18N) and
how to install it.
•Appendix G (page 257) explains how to prepare your OpenVMS system and your PC to run
the OpenVMS Management Station server and client software.
•Appendix H (page 267) explains how to remove the OpenVMS operating system from your
disk.
•Appendix I (page 269) explains alternate methods of initializing an OpenVMS I64 system
disk and includes information about diagnostic partitions on OpenVMS I64 system disks.
•The Glossary (page 271) defines key terms used in this manual.
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 topicbeing 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 choiceswithin bracketsor 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.
20
{ }
bold type
italic type
UPPERCASE TYPE
Example
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.
MeaningConvention
–
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
an earlier OpenVMS version documentation set. They have not been revised, they remain valid
for OpenVMS Version 8.3-1H1.
•Cover Letter for HP OpenVMS Version 8.3-1H1 for Integrity Servers and any other cover letters
included with your kit.
•HP OpenVMS Version 8.3-1H1 for Integrity Servers New Features and Release Notes, which
describes enhancements and new features included in this release of the OpenVMS I64
operating system and provides important supplementary information about the OpenVMS
I64 operating system.
•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.3 Release Notes, which provides important supplementary information
about the OpenVMS I64 system that might still be valid for the OpenVMS 8.3-1H1 release.
•HP OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations, if you plan
to install your system in an OpenVMS Cluster environment.
•The mostrecent version of the DECwindowsMotif 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:
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.
•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,or TCP/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.3
Online Documentation CD. Hardcopy documentation must be purchased separately.
Related Information21
•For documentation related to Instant Capacity (iCAP), Temporary Instant Capacity (TiCAP),
and Pay per use (PPU), see the HP Instant Capacity User’s Guide and HP Pay per use User’sGuide 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.01.01 manuals):
http://www.hp.com/go/gwlm
Information about gWLM and documentation for installing the gWLM agent on OpenVMS
I64 systems, including release notes, is available at the following website:
•The hardware manuals that are supplied with your Integrity server 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, whichcontains 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
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:
22
http://www.docs.hp.com.
Manufacturing Part
Number
Systems
HP Encourages Your Comments
HP welcomes your comments on this manual.
Please send comments to either of the following addresses:
Internet: openvmsdoc@hp.com
Postal Mail:
Hewlett-Packard Company
OpenVMS Documentation Group
ZKO3-4/Y02
110 Spit Brook Road
Nashua, NH 03062-2698
How to Order Additional Documentation
Visit the following World Wide Web address for information about how to order additional
documentation:
This chapter defines key terms and describes preliminary procedures you must perform before
installing or upgrading your OpenVMS system.
NOTE:Throughout this book, examples are taken from OpenVMS I64 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
HSx device
InfoServer
A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS
Cluster system environment share disks. The disk on which you install orupgrade the operating
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 I64 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 cannotserve the OpenVMS I64 operating environment (OE) DVD. TheInfoServer utility
can serve both DVDs and CDs (for OpenVMS I64 andOpenVMS 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.3 New Features and Documentation Overview.
local drive
operating system
media
provisioning
source drive
system disk
target drive
virtual media
(vMedia)
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 processof installingor upgrading OpenVMS
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 Alpha operating
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.
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 PC and connects over the network to your Integrity server 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.1 Key Terms25
1.2 Getting to Know Your Integrity Server
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 Server Blade
•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 HP
OpenVMS Alpha Version 8.3 and HP OpenVMS I64 Version 8.3-1H1 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 server. 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 server, see the HP OpenVMS Version 8.3-1H1 for Integrity Servers New Featuresand Release Notes.
1.2.1 Entering Commands at Integrity Server Console Interfaces
When entering commands for the Integrity server, 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. 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 A.1.3 (page 152).
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
user interface and the functionality provided by 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.
26Getting Started
You can move from the EFI interface to MP and back again. Similarly, you can move from MP
to the operating system and back.
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.
All processors 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 configurenPartition 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 nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administrationfor nPartitions).
1.2.5 Getting Started: Main Steps After You Unpack Your Integrity Server
When you unpack your Integrity server, 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
1.2 Getting to Know Your Integrity Server27
server model and version, alwaysrefer to the hardware documentation provided for your Integrity
server.
Table 1-2 Getting OpenVMS Started on Integrity Servers
DocumentationActionStep
1
your server, connect to the MP serial port.
2
Services for OpenVMS.
3
4
From the EFI Shell interface or EFI Boot Manager menu, select
the device for the OpenVMS console.
Power on your Integrity server, insert the OpenVMS I64
distribution media (DVD) into the drive, cycle power, and then
use the EFI boot menu to boot from the DVD.
Section A.2 (page 152)Connect your console cable to the serial port; if MP is present on
Hardware manualOptionally, configure MP to accept connections over TCP/IP
Section A.2 (page 152); if you ordered
your server preinstalled, console
selections are already made but you
might need to change them
For howto poweron and recycle power,
see the hardware documentation; for
instructions on booting the DVD, see
Section 3.2.1 (page 50)
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 I64 Boot Manager
(SYS$MANAGER:BOOT_OPTIONS.COM), as explained in Section A.5.2 (page 165). 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.
1.3 Examining Software and Hardware 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, you can use a VGA monitor and USB keyboard (and USB mouse). For
information about setting up your system console, see Section A.2 (page 152).
•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.)
28Getting Started
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 for Integrity Servers Operating Environment DVD
Included in your OpenVMS I64 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.3-1H1 for Integrity Servers Operating EnvironmentDVD label
I640831H1Volume label
The DVD label is the printed label on the OE DVD. The volume label is the machine-readable
name that the OpenVMS I64 operating system uses to access and identify the DVD.
1.3.4 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.3-1H1 for Integrity Servers New Features and 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 server 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 server (see Section 1.3.4.1
(page 29)).
NOTE:To receive notification of new firmware releases for the Integrity server you own,
you can subscribe (free of charge) for drivers and software alerts, as instructed in
Section 1.3.4.1 (page 29).
2.Create a firmware update CD on any system equipped with a CD or CD/DVD-recordable
drive (see Section 1.3.4.2 (page 30)).
3.Update the firmware on your Integrity server (see Section 1.3.4.3 (page 31)).
1.3.4.1 Checking Firmware Version
To determine the firmware version in place on your Integrity server, 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.
1.3 Examining Software and Hardware Components29
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 server interface commands are displayed in lowercase to help distinguish them from
OpenVMS DCL commands.
For more information about the latest firmware for your Integrity server, check the HP OpenVMSVersion 8.3-1H1 for Integrity Servers New Features and 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 server, 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 server. Compare your installed version with firmware versions listed in the release
notes.
1.3.4.2 Creating a Firmware Update CD
To create a firmware update CD for your entry-class Integrity server, 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
(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 server 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
30Getting Started
Loading...
+ 261 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.