Making Boot Decisions When Using the Client Console

Boot Using the Network

A decision tree for booting and installing HP-UX from the client console using the server is shown in Figure 9-1. If you want to boot a client without using an Ignite-UX server, see Figure 9-2 “Decision Tree for Booting From Media and Installing HP-UX From the Server ”.

Use the decision tree below when you want to install from the Ignite-UX server and control the installation from the client console.

Figure 9-1 Decision Tree for Booting and Installing HP-UX From the Server Using the Client Console

Use bootsys -c - If the client system is currently running HP-UX, you can use bootsys -c on the client console to boot from the Ignite-UX server. See “Using bootsys on the Client Console” and the bootsys(1M) manpage for more information.

Boot from local server or boot helper - You can boot your client from a server or boot helper system using the client console by interrupting the reboot process and invoking the boot from the firmware interface. Details vary depending whether your client is a PA-RISC or Itanium-based. See “Booting PA-RISC Clients from the Console ”, or “Booting Itanium-Based Clients using the Network”, depending on the hardware of your client.

Use dbprofile - All partitionable Itanium-based systems allow the definition of direct boot profiles. This EFI functionality is also found in other, non-partitionable systems. With these profiles, you can supply all the networking information needed to contact an Ignite-UX server and perform an install or recovery.

Some systems might require firmware updates to provide support for direct boot profiles. If your system does not provide the dbprofile command, check for any firmware updates that might enable it. You can also consult the system's hardware documentation to determine if dbprofile is supported.

For more information, see “Direct Boot Profiles for Itanium-Based Systems”.

See the decision tree for booting stand alone systems - This decision tree can be found below in figure Figure 9-2.

Boot Using Media

Use the following decision tree if you do not have support for network boot. The methods described in Figure 9-2 use media content to boot for install.

Once you have booted the system, you will be able to communicate with an Ignite-UX server to perform an installation or recovery. Note that if you do not have an active DHCP server to provide networking IP address requests, you will need to manually provide networking information before you can communicate with the server.

See “How Ignite Works” for more information on the network booting process.

Figure 9-2 Decision Tree for Booting From Media and Installing HP-UX From the Server

Boot from HP-UX OE install DVD, then switch to network server - This option requires the system to have a CD or DVD drive attached, or iLO vMedia support. The version of Ignite-UX on the OE media must match the Ignite-UX version on the server. For more information on iLO vMedia, see Appendix D and the HP Integrity iLO 2 MP Operations Guide available at http://www.docs.hp.com.

Create matching installation media on server - It is possible to create installation media for booting purposes. This type of installation media does not include a full archive. See Chapter 14: “Creating Your Own Installation Media”, for more information.

Boot from installation media then switch to network server - This option assumes you have created installation media for booting purposes. See Chapter 14: “Creating Your Own Installation Media”, for more information. This option requires the system to have a CD or DVD drive attached, or iLO vMedia support. For more information on iLO vMedia, see Appendix D and the HP Integrity iLO 2 MP Operations Guide available at http://www.docs.hp.com.

See the decision trees for network server installation - These decision trees are: Figure 2-1: “Decision Tree When Configuring a Server for Booting PA-RISC Systems”, and Figure 2-2, "Decision Tree When Configuring a Server for Booting Itanium-Based Systems.”