Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

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

YES YESYES

Is HP-UX

running ?

Itanium-based

and dbprofile

support ?

Local server

or boot

helper ?

Using the Client Console

Use bootsys -c

Use dbprofile

Boot from

local server

boot helper

See the decision tree

for stand alone systems

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”

(page 98) 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 ” (page 99), or “Booting Itanium-Based Clients using the Network”

(page 100), 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” (page 102).

See the decision tree for booting stand alone systems - This decision tree can be found below in

figure Figure 34.

Boot Using Media

Use the following decision tree if you do not have support for network boot. The methods described

in Figure 34 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” (page 17) for more information on the network booting process.

Making Boot Decisions When Using the Client Console 97