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

DHCP Usage Examples
You can configure a DHCP server to respond only to specific clients during an installation using
instl_adm to configure specific dhcp_class_ids. Your situation might fall into one of these
categories:
• The network has a DHCP server and the clients being installed will be requesting IP addresses
from it. See the section “Manage Clients That Will Use DHCP During and After Installation”
(page 233).
• The network has a DHCP server, but you would like to manage a small group of temporary
IP addresses for use in performing installations. When deployed, the clients will be reassigned
new addresses. In this case, see “Manage Clients with Temporary IP Addresses During
Installation” (page 233)
Ensure DHCP is configured and operating on your Ignite-UX server.
For more information, see instl_adm(1M) and bootpd(1M).
Manage Clients That Will Use DHCP During and After Installation
This example uses DHCP with your Ignite-UX server or boot helper to provide IP addresses during
installation and regular use. This section assumes no networking information is being provided
interactively or by the configuration used to install the system.
If you have an existing DHCP device group you wish to use for DHCP addresses, make the following
changes to the install file system, substituting YourClassId with the class ID you wish to use.
dhcp_class_id="YourClassId"
is_net_info_temporary=false
The use of dhcp_class_id is optional. Use it if you want a lease on a DHCP-allocated IP address
associated with a specific DHCP class id. If you do not wish to specify a DHCP class id, no changes
are required to the install file system since the is_net_info_temporary keyword is set to false
by default. If you previously customized the install file system, you should review and change the
configuration as appropriate.
You should not use the same DHCP device group as the device group created for installing
anonymous Itanium-based clients. Typically, the number of IP addresses available from that device
group is small and the IP addresses will be exhausted quickly, leaving you unable to install or
recover any systems over the network. If you don't have a suitable DHCP device group available,
consider configuring a new DHCP device group in consultation with your network administrator.
After a cold install, you will be prompted for networking information. You must indicate the system
will use DHCP. See set_parms(1M) for more information.
Manage Clients with Temporary IP Addresses During Installation
This example uses DHCP with your Ignite-UX server or boot helper to provide temporary IP addresses
for installation and recovery.
The following assumes you have created a DHCP device group suitable for booting anonymous
Itanium-based clients and that you have made changes to the device group allowing it to recognize
the IgniteDHCPDeviceGroup class id. See “Isolating Ignite-UX From Noncontrollable DHCP
Servers ” (page 45) for information on how to change the device group. Make the following
changes to the install file system.
dhcp_class_id="IgniteDHCPDeviceGroup"
is_net_info_temporary=true
When choosing to use the same DHCP device group as the one for booting anonymous
Itanium-based clients, the system being installed or recovered will continue to use the IP address
for a longer period. The number of IP addresses available for network booting in this device group
should be sized to allow for the maximum number of systems you expect to be concurrently installing
or recovering.
For information regarding the usage of is_net_info_temporary, see this important note.
DHCP Usage Examples 233