Getting to Know Your Integrity Server
» Table of Contents |  | | » Glossary | | | » Index | | |
| | |
| ||
| ||
The OpenVMS operating system is now supported on a wide variety of HP Integrity servers, including the following:
Entry-class servers (for example, the rx1600 or rx4600 series)
Midrange servers (for example, the rx7620 and rx8620)
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.3 for Alpha and Integrity Servers 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://docs.hp.com
http://www.hp.com/support/itaniumservers
For the latest information about firmware and software requirements and for considerations for your Integrity server, see also the HP OpenVMS Version 8.3 Release Notes.
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 is not deleted, as would be expected on an OpenVMS Alpha system. Integrity server facilities use Ctrl/H to delete the last character typed. For information about how to remap a terminal to use Ctrl/H instead of DEL/RUBOUT, see “Using the Delete or Backspace Key with Integrity Server Utilities”.
Integrity servers include multiple interfaces for working with various aspects of the server or server complex. The Management Processor (MP), which is also known on entry-class Integrity servers as Integrated Lights-Out (iLO), is available on most systems. It provides a service interface that allows access to all hardware and, in a complex, all nPartitions. 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.
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 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 and Microsoft® Windows® systems. nPartition Commands 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 HP System Partitions Guide: Administration for nPartitions.
When you unpack your Integrity server, the main steps for getting OpenVMS up and running are those listed in Table 1-2 “Getting OpenVMS Started on Integrity Servers”. 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 server model and version, always resort to the hardware documentation provided for your Integrity server.
Table 1-2 Getting OpenVMS Started on Integrity Servers
Step | Action | Documentation |
|---|---|---|
1 | Connect your console cable to the serial port; if MP is present on your server, connect to the MP serial port | “Selecting Your OpenVMS Console for the Integrity Server System” |
2 | Optionally, configure MP to accept connections over TCP/IP Services for OpenVMS | Hardware manual |
3 | Set the EFI console input, output, and error devices | “Selecting Your OpenVMS Console for the Integrity Server System”; if you ordered your server preinstalled, console selections are already made but you might need to change them |
4 | 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 | For how to power on and recycle power, see the hardware documentation; for instructions on booting the DVD, see “Booting the OpenVMS I64 OE DVD” |
After this, 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 “Setting Boot Options for Your System Disk”. 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.