HP OpenVMS Systems Documentation

Content starts here 1.2 Getting to Know Your Integrity servers
HP OpenVMS Version 8.4 Upgrade and Installation Manual > Chapter 1 Getting Started

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 HP OpenVMS 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:



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.

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


In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the following location:


1.2.4 Cell-Based Server Terminology

A cell-based server—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 (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 using HP 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 nPartition Administrator'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




Connect your console cable to the serial port; if MP is present on your server, connect to the MP serial port.Section B.2


Optionally, configure MP to accept connections over TCP/IP Services for OpenVMS.Hardware manual


From the EFI Shell interface or EFI Boot Manager menu, select the device for the OpenVMS console.Section B.2; if you ordered your server preinstalled, console selections are already made but you might need to change them


For systems with iLO console and Insight Power Manager, check that power management is set to the state that you prefer.

HP OpenVMS System Management Utilities Reference Manual


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, 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). OpenVMS supports the InfoServer utility, provisioning, and virtual media (vMedia) devices to allow you to boot, install, or upgrade OpenVMS over the network.

For how to power on and recycle power, see the hardware documentation; for instructions on booting the DVD, see Section 3.2.2

For information on the Infoserver utility, see Appendix C

For information on provisioning and vMedia, see Appendix D


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