HP-UX HB v13.00 Ch-06 - Ignite-UX

HP-UX Handbook – Rev 13.00 Page 13 (of 58)
Chapter 06 Ignite-UX
October 29, 2013
bootptab entry for an Ignite-UX client:
sysname:\
hn:\
vm=rfc1048:\
ht=ether:\
ha=080009352575:\
ip=15.1.51.82:\
sm=255.255.248.0:\
bf=/opt/ignite/boot/boot_lif
Session options:
 <Confirm New Clients> controls the appearance of a dialog screen each time a
new client is booted from the Ignite-UX server.
 <Ask for customer information during client installation>: select
this to see the form for <Customer Name, " System Serial #, and Order
Number> when installing clients.
 <Show the welcome screen for the install server>: select this to
automatically display the Ignite-UX server Welcome screen. This is a useful
default if many new operators run Ignite-UX.
 <Halt the client after installation>: select this to cause the client
system to halt (rather than reboot) after installation.
 <Automatically move completed clients to history>: select this button to
automatically add completed clients to the end of the history log,
/var/opt/ignite/clients/history/history.log. It will also move their
config and manifest files to history for future reference. The client icon will be
removed from the client-server screen. The client must be complete (fully
installed) for this to take place.
Configuring the Ignite-UX Server for Itanium clients
Itanium systems lack the ability to boot directly from the Ignite-UX server unless using the
dbprofile configuration at EFI. On PA-RISC systems the target LAN address of the Ignite-UX
server can be specified in the boot command “boot lan.<IP> install”. This is not possible on
Itanium, where the “lanboot” command on the EFI shell will send a DHCP/BOOTP broadcast
into the subnet, choosing the server which answers first. There are two mutually exclusive
options available to configure the Ignite-UX server for Itanium clients:
 In HP-UX 11.23, the bootpd server has been modified so that it is possible to
configure bootpd to respond to anonymous Itanium clients.