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

Introduction

The Ignite-LUX package enables network installation of HP-UX using a server that runs Linux.

The Ignite-LUX package includes portions of the Ignite-UX product that support installations initiated from a

client’s console. While this package does not include ignite’s functionality for server-controlled

installations via GUI, ignite functionality for Central Management Server (CMS) integration may be used

to perform client installations controlled by a Linux server. From the client’s perspective, there are virtually

no functional differences between an Ignite-UX server and an Ignite-LUX server.

This document details how to set up and manage Ignite-LUX content on a Linux server. Normally, the Ignite-

LUX software will be installed and configured as part of the CMS software installation process.

Assumptions

It is assumed the reader is familiar with managing Ignite-UX. General Ignite-UX documentation should be

consulted for creating config files and other details of Ignite-UX server management that are not covered in

this document.

The Linux server must support the NFS and TFTP network protocols so HP-UX clients are able to access Ignite

install environment and config file content.

The Ignite-LUX Package

A few Ignite-UX server commands are included in the Ignite-LUX package. These commands do not include

all the same options and functionality provided by their counterparts in the HP-UX server Ignite-UX product.

Generally, not all options are supported. In some cases, these commands support additional functionality

and options not supported by the HP-UX Ignite-UX server commands. Command usage messages provide

details regarding the options and features supported.

The Ignite-LUX package is released on the same schedule as the Ignite-UX product. Version numbers for both

packages match, so Ignite-UX config file content may be shared or moved between servers. This also allows

you to boot from one Ignite server and then switch to another Ignite server for installation. When CMS

software includes Ignite-LUX, the most recent release is normally included. Consult CMS software

documentation and support information about the processes for updating Ignite-LUX software.

Ignite-LUX is supported as part of your CMS software. Support requests should be sent through CMS support

processes. Support processes normally used for HP-UX Ignite-UX server support should not be used. Any

issue with HP-UX client software thatcan be reproduced on an HP-UX Ignite-UX server canbe processed

under your HP-UX Ignite-UX support contract.

The Ignite-LUX package provides support for installation of Integrity systems; boot or installation of PA-RISC

systems is not supported.

The Ignite-LUX package supports HP-UX installation but does not support installation of Linux, Solaris,

Windows®, or any other operating system. Your CMS software might support deployment of these

operating systems apart from the Ignite-LUX software.

The Ignite-LUX package may be installed on an HP-UX server to test its operation. However, this package is

not supported on HP-UX servers for production use; you should use the Ignite-UX product on HP-UX servers.

The CMS

Use of the package is officially supported only when used with HP-provided Central Management Server

(CMS) software, for example, HP Server Automation. CMS software might support servers running a