Section 1: Installation of Ignite-UX Server Software




	NOTE: Ignite-UX is a replacement for the Net-Install product. If your server contains the Net-Install bundle (HPUX-Install product), Ignite-UX will require that the NetInstall bundle be removed (using `swremove`), or that you touch the file `/tmp/okay_to_remove_net_install` before loading Ignite-UX, in which case loading Ignite-UX will automatically remove the NetInstall software.

Ignite-UX Server System Requirements:

HP-UX Version:

It is recommended that the Ignite-UX server be running at least HP-UX 10.20. It is supported on any HP-UX 10.x version of the operating system. Only 10.10 and later versions of HP-UX are supported as a DHCP server which Ignite-UX takes advantage of.

Disk Space:

Ignite-UX will be loaded under the directory /opt/ignite. The data files Ignite-UX creates will be placed under /var/opt/ignite. Ignite-UX installation will require ~75 MB of disk space. You will probably need additional space available under /var/opt/ignite for archive and software depot storage.

NFS Server:

The Ignite-UX server requires NFS to be configured and working. The Ignite-UX installation will add lines to the /etc/exports file, and run exportfs.

tftp:

Ignite-UX will transfer some of its files using tftp. The minimum directories needed by tftp are set up in the /etc/inetd.conf file. Others may need to be added if you place configuration scripts in non-standard locations.

Load the Ignite-UX software

You should load one or more Ignite-UX release versions. They are organized as bundles corresponding to the release that youwish to load on your target systems. For example, if youwish to load HP-UX 10.20 onto systems you should load theIgnite-UX-10-20 bundle. You can multiple releases if desiredTo load this software use the swinstall command.

For example to load Ignite-UX to load HP-UX 10.20 execute thefollowing command:

swinstall -s /dev/rmt/0m Ignite-UX-10-20

This assumes you are load Ignite-UX from a tape drive that isreferenced by the device file at /dev/rmt/0m.

Edit Default Search Path

In your login scripts, add /opt/ignite/bin to your default search path:

# export PATH=${PATH}:/opt/ignite/bin

Initial Ignite-UX Server Configuration

The majority of the Ignite-UX server configuration is performed by the product installation post-process procedures, but there are a few site-specific configuration steps you will need to perform. These are centered around the specification of available IP addresses and hostnames.

You can note that the Ignite-UX installation has added 2 services to your /etc/inetd.conf file; tftp, and instl_boots.

Step 1) Run the Ignite-UX user interface

Enter the following:

# /opt/ignite/bin/ignite




	NOTE: You will get a warning screen stating no clients exists. In this situation, this is normal since you really do not have any clients waiting.

If you get the following error message:

ERROR: This machine is not an NFS server (no nfsd running). The -n option will not be processed.

you did not follow the installation instructions properly. The Ignite-UX server must be an NFS server. Exit Ignite-UX, and make the Ignite-UX server an NFS server before continuing. You can do this by using "sam", or by editing /etc/rc.config.d/nfsconf and setting NFS_SERVER=1 and rebooting. If you do not get the above error, you can note that Ignite-UX has modified your /etc/exports file to include the /var/opt/ignite/clients directory.

This directory is exported to allow remote "root" users to write to the client's directory. This is required for proper Ignite-UX operations. You may need to export additional directories; for example, if you use NFS to transfer an archive, it must be NFS accessible.

Step 2) Perform Ignite-UX Server Configuration

Step 2.1) Select "Options->Server Configuration"

This will show the Server Configuration Menu with two tabs: "Server Options" and "Session Options". Under the "Server Options" tab, do the following:

Modify (if needed) the Server Options to match the following:

Default Configuration:Set to the OS revision you wish to be the default.

Default Printer: <select a default printer to be used by IUX>

 Client Timeout: 40 [this is the number of minutes delay due to network, or client failures before the IUX server will inform the administrator of a problem]

 Run client installation UI on: server "Server= run the GUI for all installations on the server" or " target = run the TUI on the target system" or none+ don't run a UI"..

Step 2.2) Select "Add booting IP Address"

During the install process, the clients need to do a network boot from the Ignite-UX server. In order to do this, the clients need to be given a temporary IP address.

Under "Booting Clients", provide an initial range of available IP addresses. The following example will allow Ignite-UX to perform 20 simultaneous installations. This IP address is only used when booting over the network during the initial transfer of the kernel to the client. You may only need 1 or 2 addresses depending on how many systems do network boots at the same time. (See instl_bootd(1M)). If you need to changes these addresses later, you will need to edit the /etc/opt/ignite/instl_boottab file directly.

15.2.73.1 15.2.73.20

Step 2.2.2) Permanent IP addresses are distributed via DHCP Services.

DHCP Address ranges to use for remainder of installation.

Unless you are familiar with DHCP services, for this exercise, do not modify the DHCP Class ID, or the DHCP Addresses are temporary field.

Provide a range of available "permanent" IP address. These can only be supplied once here in Ignite-UX. After the initial definition, further modification will need to be performed using SAM "Networking and Communications->Bootable Devices" area.

Step 2.3) Configure Ignite-UX Session Options

Under "Options->Server Configurations->Sessions Options" you can see various options for your server.

Confirm new clients
If this is selected, the option will put a dialog popup window on your server whenever a new client is requesting to be installed by your server.
Ask for customer information during client installation
If selected this will allow you to enter the customer name, serial number, and order number for each client. This information will appear on the system manifest report.
Show the welcome screen for the install server
. If selected, a welcome screen with information on getting started and Ignite-UX concepts will appear every time the ignite program is started.
Halt the client after installation
If selected this will cause the client to halt after the installation completes.
Automatically move completed clients to history
If selected, the server will move information related to the install of each client to the history area. Any further information about the client would need to be obtained from the install history.

You may wish to de-select the "Ask for customer information" checkbox, as this installation information is more geared to HP and HP distributor-partner manufacturing.

Step 3) Starting the Installation Process

There is nothing that needs to be done to the target system to allow it to use Ignite-UX.

If the target system is currently running any version of HP-UX 9.x, 10.x, or later, the target system can be remotely controlled by the Ignite-UX server. The Ignite-UX bootsys command can be used to perform a target system shutdown, and re-set the target networking parameters after the OS installation.

If the target system is not currently running HP-UX, then a manual network boot will need to be performed on the target. Reboot the target, press ESC to interrupt the boot process, and then perform the network boot from the Ignite-UX server:

> boot lan.15.2.72.150 install

where the above IP address is the IP address of the Ignite-UX server.

Note that this process and command may be slightly different on your target system, depending on the age of your hardware. You'll need to be familiar with your system boot commands.