Ignite-UX Installation Booting

10
Booting a vPars system
When you boot HP Integrity servers running vPars you are using EFI to perform the boot. This is
different from the way vPars works on HP9000 systems. Please consult the other areas in this white
paper for information on how HP Integrity systems boot. Please consult the vPars release notes for
the version you are running to see if there are any limitations on what boot methods are allowed.
Booting from a tape
Some HP Integrity servers released after June, 2006 have support for native tape boot. Some
systems available before that time received firmware updates that enable tape boot. However, not
all systems will receive firmware updates to enable tape boot. Also, only some SCSI HBAs will be
supported for tape boot. Fibre Channel and SAS HBAs do not support native tape boot
on all
systems. Refer to table "Tape Drive Capabilities by Protocol" to see where they are supported.
For HP Integrity systems that do not support tape boot, or those that do with tape drives connected
to HBAs that do not support tape boot, Ignite-UX will still continue to support tape recovery support
via a method called Tape Recovery with No Tape Boot Support, Dual-Media Recovery, or Two-Step
Media Recovery. This method requires that a tape drive be connected to the client, that you boot
the client from the HP-UX installation media, and that you choose options to continue installation or
recovery from tape. For more information, refer to the “Tape Recovery with No Tape Boot Support
- Two-Step Media Recovery” section of the Ignite-UX Administration Guide at:
http://www.docs.hp.com/en/IUX/infolib.html
The information presented in this section is different from other sections in this white paper. Because
native tape boot is new functionality on HP Integrity servers and there are combinations that allow
and prohibit native tape boot, you need to review the following four tables:
• The first table will show if the system will support tape boot.
• The second will show what add-on SCSI HBAs a tape drive must be connected to in order
to allow tape boot.
• The third shows tape drive capability according to protocol.
• The fourth will show the version of Ignite-UX required to support bootable recovery tapes.
On systems supporting native tape boot, the parallel SCSI interfaces on the core I/O are also
supported for tape boot.
Important:
HP does not support native tape boot on interfaces shared with internal
or external disks. This restriction applies to both built-in parallel SCSI
interfaces
4
4
If the parallel SCSI interfaces on the core I/O of your system are used for the internal disks and also have an external connector, you cannot
use these interfaces for native tape boot, as no disks can be present on a parallel SCSI interface used for native tape boot.
and add-on cards.