HP 9000 Manual page 76

Configuring an Ignite-UX Server
Setting Up an Ignite-UX Server
• Automatically move completed clients to history:
The server installation is complete at this point. If the client systems are
prepared and booted, you can skip to Chapter 5, "Installing from the
Ignite-UX Server," for the procedures for using the server with the client
systems.
1. Boot the Series 700 or Series 800 client system that supports network
Preparing the Clients
for Installation
If the client cannot find the server, check the following items:
• Client is on the same subnet as the server.
• Any instl_bootd errors in /var/adm/syslog/syslog.log.
• Your /var/adm/inetd.sec file to make sure that IP address
• If /etc/services comes from NIS, make sure that the NIS server
• The daemon rbootd is running.
The icons for all clients booted from the Ignite-UX server should now
appear on the Ignite-UX interface. If the server has not been set up
completely, or if the client could not obtain enough networking
parameters via DHCP, then the client may require interaction on the
client console.
76
Select this button to cause the client system to halt (rather than
reboot) after installation.
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 Server screen. The client
must be complete (fully installed) for this to take place.
boot by entering the appropriate command on the console for that
client.
Note that, if a client with a known IP address is already running
HP-UX, you can use the bootsys(1m) command from the Ignite-UX
server to install it with specific configuration, without further
interaction.
See the exact boot ROM commands for manual booting of your system
in "Booting Client Systems from the Network".
0.0.0.0 is not being disallowed.
has instl_boot* entries.
Chapter 4