Figure 6 Decision Tree When Configuring a Server for Booting Itanium-Based Systems
Configure individual entries in bootptab — To network boot registered Itanium-based clients, the server uses the bootpd daemon to answer boot requests, and has clients’ IP addresses and LAN addresses registered in /etc/bootptab. One drawback to this option is that you must configure an entry for every system that needs to boot. The advantage of this method is that it works on all versions of HP-UX. See “Configuring the Ignite-UX server for Itanium-based clients” (page 35) for details. See the Ignite-UX Quick Start Guide available at http://www.hp.com/go/ignite-ux-docs if you are new to HP-UX.
Configure a DHCP device group for anonymous clients - Configuring an Ignite-UX server to boot anonymous Itanium-based clients requires sophisticated considerations; see “Configuring an Ignite server to boot anonymous Itanium-based clients” (page 44). This option is only available for Ignite servers running HP-UX 11i v2 and later.
See the decision tree for booting stand alone systems - This decision tree can be found in Figure 34.
Alternate boot with network server installation
A simple way to avoid boot issues in complex network configurations is to avoid network boot. Network installation may be started via non-network boot. The Ignite install environment may be
Alternate boot with network server installation | 27 |