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

Client boot and deployment server control - You will need to consider how new client systems will be

recognized and set up for CMS-controlled Ignite-UX installation support. CMS software can take a boot-first

or configure-first approach, or support both. Client systems use NFS to mount a client-specific directory if

networking is enabled and an Ignite-UX server is specified. When the Ignite-UX install environment starts up,

one of the first things that happens is a client system inventory. That inventory data are written to the server

via NFS.

Networking configuration - You must also decide if static or dynamic IP addresses will be used for your

solution. Ignite-UX software supports both. Depending on the approach, you will want to include config file

content in IINSTALLFS to correctly set up client networking when Ignite-UX starts. During initial installation

configuration, the Ignite-LUX package places content in the IINSTALLFS file to handle a dynamic IP

address approach.

Note: Hewlett-Packard strongly recommends installing all HP-UX OS content on one LUN (with the obvious

exception of mirroring). Existing HP-UX Dynamic Root Disk (DRD) capabilities rely on this type of system

configuration. Additional future HP-UX OS image management features are likely to rely on the same type

of single LUN OS content configuration.

Client-Specific Server Content

Ignite-UX uses several files to control clients and provide client information. When possible, all client control

and monitoring should be done using Ignite-LUX commands rather than direct file access.

Ignite-UX saves client-specific content in the directory

/var/opt/ignite/clients/<MAC_address>

To aid usability, Ignite-UX creates a symbolic link for the client hostname at

/var/opt/ignite/clients/<hostname>

Ignite-LUX servers have the following client-specific files that may be used for CMS integration:

CINDEX (client-specific config clauses)

client_name (client hostname)

client_status (client installation status)

config (config file used to control installation)

config.sys (config file content used to perform installation)

env.vars (environment variables set in config content)

host.info (client system characteristics)

install.log (detailed IINSTALL log)

io.info (client system I/O inventory)

server.instr (instructions for client system from server)

Other files should not be used. For example, the directory might include an hw.info file, which you might

find easier to parse than io.info. But, hw.info is being replaced with io.info and might not be

created in a future Ignite-UX release.