These solutions use a single Ignite server that supports network boot, installation, and recovery. The Ignite server and the client systems must be on the same subnet, and no other boot or installation servers can be on that subnet.
Questions you will have to answer when configuring a simple network are:
• Are my clients PA-RISC or Itanium-based? • Do I want to network boot all my clients?
• Do I want my clients to have their MAC addresses registered with the server to always boot to the same assigned IP address (registered clients), or do I want an available IP address assigned to them when they boot (anonymous clients) ? • Do I want the booting IP address to be the same IP address used for networking
after installation is complete?
• Do I haveDHCPrunning on my subnet?
Decision trees for Ignite-UX server configuration follow. Do not treat them as strictly yes-or-no exercises. Your environment may require choosing multiple methods from the decision trees, and although you may be able to use an option, you might reject it because it is not the best answer for your environment. Also, keep in mind that these decision trees cover booting, so only the initial IP address is affected. For more information, see“Network Booting and IP Addresses” (page 28).
A decision tree for network booting PA-RISC systems is shown inFigure 2-1. A decision tree for network booting Itanium-based systems is shown inFigure 2-2 (page 40). The decision trees assume the network boot clients are on the same subnet as the Ignite-UX server, and that you will always use the install option to theboot console handler (BCH)bootcommand for PA-RISC systems. Further, the decision tree for network booting Itanium-based systems assumes there is only one DHCP server on your subnet configured to answer boot requests, and that it is running HP-UX.
If you want to boot a system without using the network and your Ignite-UX server, see the decision tree shown inFigure 9-2 “Decision Tree for Booting From Media and Installing HP-UX From the Server ”.
NOTE: A lot of clients can only be booted using their built-in LAN interfaces. Other LAN interfaces might not be supported for boot. For more information about LAN interface boot support, consult the hardware documentation for the system or the add-in LAN card.
Use the following decision tree when configuring an Ignite-UX server for PA-RISC clients:
Figure 2-1 Decision Tree When Configuring a Server for Booting PA-RISC Systems YES NO NO Network booting support ? YES Registered clients ? PA-RISC Configure instl_boottab for registered clients
Configure instl_boottab for anonymous clients
See the decision tree for booting stand alone
systems
Configure instl_boottab for registered clients - To network boot registered PA-RISC
clients, the server uses the instl_bootd daemon to answer boot requests, and has clients’ IP addresses and LAN addresses registered in /etc/opt/ignite/
instl_boottab. The process of configuring an Ignite-UX server for registered PA-RISC clients is described in“Configuring the Ignite-UX Server for PA-RISC Clients” (page 45). See the Ignite-UX Quick Start Guide available athttp://www.docs.hp.com/en/
oshpux11iv3.html#Ignite-UXif you are new to HP-UX.
Configure instl_boottab for anonymous clients - Network booting anonymous
PA-RISC clients is similar to booting registered PA-RISC clients; the difference is that some IPs in the /etc/opt/ignite/instl_boottab file are not associated with any clients’ MAC addresses, and so may be assigned to clients as requests come in. See
“Configuring an Ignite Server to Boot Anonymous PA-RISC Clients” (page 61)for more information.
See the decision tree for booting stand alone systems - This decision tree can be found
inFigure 9-2.
Use the decision tree below when configuring an Ignite-UX server for Itanium-based clients.
Figure 2-2 Decision Tree When Configuring a Server for Booting Itanium-Based Systems YES NO NO NO Network booting support ? YES YES YES Registered clients ? DHCP running ? DHCP running ? NO Itanium-based Configure individual entries in bootptab Consider replacing bootptab with instl_bootd Configure a DHCP device
group for anonymous clients See the decision tree for booting stand alone
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 50)for details. See the Ignite-UX Quick Start Guide available athttp://www.docs.hp.com/en/
oshpux11iv3.html#Ignite-UXif you are new to HP-UX.
Configure a DHCP device group foranonymous clients - Configuring an Ignite-UX
see“Configuring an Ignite Server to Boot Anonymous Itanium-Based Clients” (page 62). This option is only available for Ignite servers running HP-UX 11i v2 and later.
Consider replacing bootpd with instl_bootd- The instl_bootd daemon can
support anonymous Itanium-based clients and provide enough information for them to boot. The instl_bootd daemon can also be configured forregistered clients. You might consider running instl_bootd if you have PA-RISC and Itanium-based clients on one subnet, since this would allow you to manage client IP addresses in one place: /etc/opt/ignite/instl_boottab. The drawback to this arrangement is that an Ignite-UX server configured this way cannot provide DHCP services. This method is not recommended for an environment that consists mainly of Itanium-based systems - use DHCP or bootpd in that case. See“Replacing bootpd with instl_bootd” (page 67)
for more information.
See the decision tree for bootingstand alonesystems - This decision tree can be found
inFigure 9-2.