Once your Ignite server is up and running, you can set general options by accessing the Server Configuration dialog box from Options→Server Configuration.
3.4.1 Configuring Server Options
General server settings are available on the Server Options tab.
Figure 3-7 Ignite-UX Server Configuration Tabs
The following options are available:
• Default Configuration – Click the button next to Default Configuration to select
from the list of available configurations. The selected configuration is the default that will be used when installing clients. You can override this default setting on a per-client basis with Ignite-UX.
• Default Printer – Click the button next to Default Printer, then select one of the
available (configured) printers. This is the printer used for printing amanifestor installation history. The printer IP address is verified by Ignite-UX before a job is sent.
• Client Timeout(minutes) – Click the button next to Client Timeout (minutes):,
then select the number of minutes or off. Status information is written into the client’s install.log file during the installation, and this log is actively monitored by Ignite-UX on the server. Setting this value configures Ignite-UX to display a warning message if the install.log file has not been updated in the selected number of minutes. HP recommends you use the default value.
Setting Client Timeout to off disables this notification and does not affect the outcome of the installation.
• Run client installation UI on – Use the Run client installation UI on: menu to
designate where you want to run the client UI for this installation. If you have an Ignite-UX server configured, you can run the client installation interface from the target system using a terminal user interface (TUI), or from the server using whatever UI is set up there (the Ignite-UX GUI or TUI). If the client installation is to be noninteractive (no user intervention), select none.
The default is for the UI to be displayed on the Ignite-UX server.
• Use ssh to gather client data – For all clients, ssh will be used instead of remsh,
rlogin, and rcp.
• The Configure Booting IP Addresses... button gives you access to the Configure Booting IP Addresses dialog previously described in“Register the PA-RISC Clients with the Server” (page 48).
• Add DHCP Addresses... –
The assignment of DHCP IP addresses for booting is only used foranonymous clients. SeeChapter 4 (page 61)for more information.
The IP addresses you provide here are used during boot and installation. These addresses are in use for most of the Ignite-UX download to a client. One address is required for each simultaneous download. For more information see“Network Booting and IP Addresses” (page 28).
Figure 3-8 Add DHCP Addresses Dialog Box
This provision of DHCP capability is for the boot and installation only. You will have to coordinate with the administrator of regular DHCP services, which distributes networking IP addresses, to make sure you use a set of available IP addresses that will not cause a conflict with regular DHCP services. SeeAppendix B (page 317)for information on configuring regular DHCP services on your Ignite-UX server. Unless you are familiar with DHCP services, do not modify the DHCP Class ID field or the DHCP Addresses are temporary check box.
Provide a range of available IP addresses in the DHCP Addresses fields from lowest number to highest:
10.2.73.21 10.2.73.40
Other ways to set these IP address values are: when prompted by Ignite when it's first run are instl_adm, and SMH or SAM.
For more information about setting up DHCP functions, addresses, and class IDs, see“Ignite-UX Server and Boot Helper Setup for DHCP” (page 63),
setup_server(1M), and instl_adm(4).
3.4.2 Configuring Session Options
Ignite-UX allows you to choose how client installation sessions behave. For example, you can decide whether or not to display the Welcome dialog each time you start Ignite-UX, and whether clients are halted on completion of the installation. The following options are accessible from the Server Configuration dialog box (Options→Server Configuration) Session Options tab.
Figure 3-9 Session Options Tab
The options you can configure on this tab are explained as follows:
• Confirm new clients – Controls whether a confirmation dialog box appears each
time a new client is booted from the Ignite-UX server.
• Ask for customer information during client installation – Controls whether an
and order number. This information is stored in the manifest.seed file in the /var/opt/ignite/local/manifestdirectory. It is used when you are viewing and printing a manifest (see“Viewing and Printing a Manifest ” (page 213)) with print_manifest(1M). The information entered has no effect on the outcome of an installation.
• Show the welcome screen for the install server – Controls whether the WELCOME
TO IGNITE UX dialog box appears. The default behavior is to display this dialog box.
• Halt the client after installation – Controls whether the client system is halted
(rather than rebooted, the default) after installation.
• Automatically move completed clients to history – Controls whether completed
clients are automatically added to the end of the history log, /var/opt/ignite/ clients/history/history.log. As part of this action, client configuration and manifest files are automatically moved to the history directory on the Ignite-UX server for future reference. The client icon is removed from the GUI workspace. The client must be COMPLETE (fully installed) for this to take place.
• Show all the information for network recovery image creation – Controls the
amount of information that appears during networkrecovery imagecreation and installation. The default behavior is to hide this information.
• Show all the information for tape recovery image creation – Controls the amount
of information that appears during tape recovery image creation and installation. The default behavior is to hide this information.