ignite.5 (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

ignite(5) ignite(5)

NAME

ignite - HP-UX conﬁguration, installation, and recovery manager

SYNOPSIS

/opt/ignite/bin/ignite

[-recovery][

-install][-S][XToolkit-Options]

[client1, client2, client3, ... ]

DESCRIPTION

Introduction

The Ignite-UX product supports HP-UX install and recovery. The Ignite-UX product supports a very rich

set of functionality and customization beyond the scope of what can be presented here. It is important to

consult product documentation to better understand Ignite-UX (see http://www.hp.com/go/ignite-ux).

The current version of Ignite-UX is the "C" version. The various HP-UX releases that the "C" version is

capable of installing and recovering include:

C.7.3-C.7.? 11.31, 11.23, and 11.11

C.7.0-C.7.2 11.31, 11.23, 11.11, and 11.00

C.6.9-C.6.10 11.23, 11.11, and 11.00

The Ignite-UX product enables users to:

• Control multiple simultaneous install sessions from a single server.

• Perform a single standalone installation of a target client from a terminal user interface running

on the target machine.

• Initiate non-interactive installations from the client or from the server.

• Install multiple applications at the same time as the base operating system.

• Load software from non-Software Distributor (SD) sources (

tar, cpio, or pax) as well as from

SD sources in one session.

• Customize a client so that it is "ready to go" as soon as the install session completes.

• Specify user-supplied scripts to be executed at pre-deﬁned points both during the installation pro-

cess and after.

• Create a "golden system image" that may be unpacked directly to a target machine over the net-

work.

• Save customized conﬁgurations and quickly apply those conﬁgurations to multiple target clients.

• Capture a snapshot of the currently loaded software along with a complete hardware inventory.

• Create client-speciﬁc recovery archives that may be stored on the network and loaded by Ignite-

UX in the event of root disk failure or corruption.

• Create bootable system recovery tapes.

Hardware/Software Requirements

For performing installations, the following hardware is required to set up an Ignite-UX server. The

server requires either a graphics display or a display redirected to another X(1) windows system. The

redirection is accomplished by setting the

DISPLAY environment variable. For example, at the Korn

Shell or Posix Shell type:

export DISPLAY=<server>:0.0

Ignite-UX server requirements:

• An HP-UX system running HP-UX 11.11, 11.23 or 11.31.

• An X11 display server (workstation, X-terminal, PC running an X server, etc.). This may be the

same system as above.

• Sufﬁcient disk space to load Ignite-UX and any software depots and/or archives to be used during

the install.

• Access to the Ignite-UX tool set. The tool set may be loaded onto any of the above clients.

• DVD to load Ignite-UX and any software depots planned for distribution on the server.

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (10 pages)

PAGE 1
ignite(5) ignite(5) NAME ignite - HP-UX configuration, installation, and recovery manager SYNOPSIS /opt/ignite/bin/ignite [-recovery] [-install] [-S] [XToolkit-Options] [client1, client2, client3, ... ] DESCRIPTION Introduction The Ignite-UX product supports HP-UX install and recovery. The Ignite-UX product supports a very rich set of functionality and customization beyond the scope of what can be presented here.
PAGE 2
ignite(5) ignite(5) • Network access to any clients to be installed. Client and server must be on the same subnet if the initial boot of the client is planned to be over the network. Ignite-UX Server Setup: Overview 1. Install HP-UX. 2. Install the Ignite-UX software. 3. Set up the core HP-UX software. 4. Add additional applications (optional). 5. Run ignite to complete the configuration and to start the process. Note: All operations are executed as "privileged user" on the Ignite-UX server.
PAGE 3
ignite(5) ignite(5) For non-SD (archive) operating system software: Ignite-UX has the capability of loading a client from an archive image taken from a client that represents a standard configuration. This method gives significantly faster install times, but may not be as flexible as using an SD source. You will first need to generate the archive image of a client in the desired state. It is recommended that the /opt/ignite/data/scripts/make_sys_image script be used to accomplish this task.
PAGE 4
ignite(5) ignite(5) /opt/ignite/data/examples/noncore.cfg The comments in this example file describe where to copy the file and what to change in the file to make it reference your archive and work in your environment. 5. Run ignite to complete the configuration and start the process. On the server execute /opt/ignite/bin/ignite. This will start the Ignite-UX server program.
PAGE 5
ignite(5) ignite(5) where: n.n.n.n is the IP address of the Ignite-UX server. The client then begins to load the install kernel (ignite the client) from the network server. Note: To search for Ignite-UX servers, type the following at the client console (workstations only): Main Menu: Enter command > search lan install The list of servers that you can boot the client from is displayed with the corresponding IP addresses and is similar to: Searching for potential boot devices(s)...
PAGE 6
ignite(5) ignite(5) Cold Reset Exit 3) Select Add a Boot Option. EFI Boot Maintenance Manager ver 1.10 [14.60] Add a Boot Option. Removable Load File Load File Load File Exit 4) Select a Volume Media Boot[Acpi(HWP0002,0)/Pci(2|0)/Ata(Primary,.. [EFI Shell [Built-in]] [Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E1E4ED4)] [Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E1E4ED4)] Select the appropriate network interface so that this network boot loads the appropriate file.
PAGE 7
ignite(5) ignite(5) 11) Select the new boot option, LAN1 in this case, from the list, and then press Enter. The following is an example of a successful network boot using the new LAN1 boot option, which ignites the client: Loading.: LAN1 Running LoadFile() CLIENT IP: 10.1.52.128 GATEWAY IP: 10.1.48.1 Running LoadFile() MASK: 255.255.248. DHCP IP: 10.1.53.37 Starting: LAN1 @(#) HP-UX IA64 Network Bootstrap Program Revision 1.0 Downloading HPUX bootloader Starting HPUX bootloader Downloading file fpswa.
PAGE 8
ignite(5) ignite(5) After the client icon appears on the server screen, select it by clicking on the icon for that client. Use the Actions menu to select a task for the selected client. The first task would be to choose "Install Client". Then choose "New Install". During the installation, choose a configuration file for this installation. Clients will be installed per the description given in the configuration file. If you want to reuse this configuration, save the file.
PAGE 9
ignite(5) ignite(5) • If the client cannot boot over the network or is on a different subnet than the Ignite-UX server, see make_boot_tape(1M). • After the client is booted, select your recovery archive from the list of configuration choices displayed for installation on your client. • Ignite-UX detects from the configuration file for the archive that this is a recovery situation and uses the archive for recovery rather than for install.
PAGE 10
ignite(5) ignite(5) DIAGNOSTICS Logging All major events are logged to the server log file located at /var/opt/ignite/logs/server. FILES /opt/ignite/bin Contains Ignite-UX commands. /opt/ignite/lbin Contains Ignite-UX commands used by other commands. /var/opt/ignite/depots Contains the software depots used by Ignite-UX. /var/opt/ignite/logs Contains log files for each command. /var/opt/ignite/clients Contains the per-client directories. /var/opt/ignite/server Contains the file ignite.