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

installation and should not be modified. Modifications to the release-specific AUTO files might interfere with

CMS software operation and will be lost during package update.

The following directories should be set up for read-only access via TFTP:

/opt/ignite

/var/opt/ignite

By default, the Ignite-LUX package is configured to use NFS instead of TFTP whenever possible during the

installation process. However, UEFI PXE network boot relies on the use of TFTP. If client system HP UEFI

directed boot functionality is used, or you boot from a DVD and switch to the Ignite-UX server for

installation, bootp and TFTP are not required. You should consult HP UEFI documentation and the Ignite-UX

Administration Guide for further details.

Enabling HP-UX Installation

You must configure the NFS server to allow access to required Ignite-UX directories. Depending on how you

intend to use the Ignite-UX server and how you handle per-client access, you will need to customize the set

of directories exported.

/opt/ignite (read-only)

/var/opt/ignite/data (read-only)

/var/opt/ignite/config (read-only)

/var/opt/ignite/archives (read-only)

/var/opt/ignite/scripts (read-only)

/var/opt/ignite/clients (read/write)

/var/opt/ignite/recovery/archives/sys1 (read/write)

Important: Some Linux NFS servers limit maximum file size to 2GB or 4GB. Ignite-UX archive files

typically will be larger than 2GB and might be larger than 4GB. The Linux NFS server must be configured

to support large files. This might require a newer version of NFS; for example, version 3 or later.

Creating and Using Golden Images

The Ignite-LUX server may be used to support HP-UX installation of golden images and recovery archives

without requiring an HP-UX server.

The Ignite-UX Administration Guide provides details regarding creation and use of golden images.

However, there are some special considerations for an Ignite-LUX server.

The Ignite-LUX package includes the same make_sys_image command as included in the Ignite-UX

product. However, the make_sys_image command –s option relies on HP-UX-specific server functionality.