
NOTE: To boot your OpenVMS I64 operating system, you can use a VGA graphics device (except on an rx2600 Integrity server or other servers that lack the firmware capabilities), a serial device, or a network interface for the console. For information about setting up the console on your Integrity server, see Section A.2 (page 152).
When using a VGA console and installing from vMedia or a USB DVD drive with the keyboard plugged into a USB hub, if the keyboard does not respond, simply unplug the hub and plug it back in.
NOTE: HP Integrity servers maintain a system event log (SEL) within system console storage, and OpenVMS I64 automatically transfers the contents of the SEL into the OpenVMS error log. During a successful boot operation while using a console, you might see a message indicating that the BMC SEL is full. You can safely continue when the BMC SEL is full by following the prompts; OpenVMS processes the contents of the SEL.
HP recommends that the latest system firmware be loaded and used. For more information about updating the system firmware, see Section 1.3.4 (page 29). For midrange and
A.6.1 Overview of Booting on a Cell-Based Server
This section gives an overview of booting the nPartition hardware and booting OpenVMS on an nPartition.
A.6.1.1 Booting the nPartition Hardware
Each nPartition runs its own firmware and has its own system boot environment. You can boot an nPartition independently of any other nPartitions in the same server complex.
The nPartition boot process includes two phases: the cell boot phase and the nPartition boot phase. Note that these phases occur only as part of the hardware boot process, not as part of the operating system boot.
•Cell boot
•nPartition boot
You can view progress of these phases by using the Virtual Front Panel (VFP) to check the nPartition boot state. Access VFP from the MP main menu.
For information about how to boot the nPartition hardware, see your hardware documentation.
A.6 Booting Operations 173