Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

installed in an alternate location, it is likely symbolic links will need to be provided so commands run on the

Linux server operate correctly. For example:

# ln –s /opt/opsware/boot/tftpboot/opt/ignite/boot /opt/ignite/boot

When possible these links should be created before package installation. If links are set up before

installation you should unpack the package in the root directory:

For example:

# cd /

# tar xzf Ignite-UX-C-7-8.201.tar.gz

Or:

# cd /

# gunzip < Ignite-UX-C-7-8.201.tar.gz | tar xf -

When the Ignite-LUX product is installed using the SD swinstall command on an HP-UX Ignite-UX system,

package configuration is automatically done. The Ignite-LUX package includes a program that performs

necessary package configuration. This program must be manually run to complete package installation or

update:

# cd /

# /opt/ignite/bin/setup/configure

The first time the Ignite-LUX package is installed, the configure program will attempt to examine the network

configuration of your server and generate appropriate IINSTALLFS config content. After the configuration

is completed, you should validate these settings and modify them if necessary using the instl_adm

command:

# /opt/ignite/bin/instl_adm

When the package is reinstalled to update to a new version, IINSTALLFS config content is retained

without modification.

The package installs several files named *.new that allow the configuration process to retain Ignite-UX

server customizations. Some of these files are left on the server after configuration to act as a reference for

default file contents.

Warning: If the configuration is incomplete, the Ignite-LUX server will not function correctly to support HP-

UX install. Client systems might be unable to boot the Ignite-UX install environment, crash or hang during

attempted installation, or fail to correctly install in some other manner.