Ignite-UX Server Requirements

Computer: An HP 9000 (PA-RISC) system running HP-UX 11i v1, HP-UX 11i v2, or HP-UX 11i v3; or an Itanium®-based system running HP-UX 11i v2 or HP-UX 11i v3 is required.

Memory: Client installation and recovery performance is typically limited by network throughput. Normally, no special consideration for system memory is needed.

DVD drive: A DVD device is recommended to simplify copying HP-UX release depots directly from installation media to the Ignite-UX server.

Tape device: As part of your overall disaster recovery plan, you should consider how the Ignite-UX server itself would be recovered. A tape drive allows the Ignite-UX server to use tape media to save the server’s own recovery archive. Note that depots, saved client recovery archives, and other client-specific content typically should not be included in the recovery archive saved to tape. This client content should be saved using backup software. Not all systems support tape boot and so require two-step media recovery. See “Tape Recovery With No Tape Boot Support — Two-Step Media Recovery” and the Ignite-UX Installation Booting white paper available at http://docs.hp.com/en/IUX/infolib.html for more information.

Network interface: One or more network adapters to support network boot and installation is required. A network adapter directly connected to each supported subnet is preferred. Note that multiple simultaneous network installations and recovery operations can create significant network traffic.

Disk space: An Ignite-UX server might need considerable disk space.

Use of TFTP: Ignite-UX transfers some files using TFTP. A list of the minimum directories needed for file transfer is kept in the /etc/inetd.conf file. You might need to add directories to the list if you place configuration scripts in nonstandard locations.

For example, the Ignite server must have the following entry in its /etc/inetd.conf file.

If you are using HP Serviceguard clusters or systems with multiple IP addresses on a LAN interface, use the -s option with tftp and install the patch PHNE_28762 11.11.

Use of ssh: With Ignite-UX version C.6.8 and later, bootsys can use ssh, and ignite can use ssh for make_[tape|net]_recovery. With Ignite-UX version C.7.1 and later, the ignite command can use ssh when calling bootsys. To use ssh, it must be available on the Ignite server and on the client, and you must have an existing public/private key pair.

Optional use of an X11 display server: An X11 display server allows you to use the GUI to configure and start Ignite. Your Ignite-UX server can use an X server to display the Ignite GUI, or you can redirect the display to another X terminal by entering the following command:

export DISPLAY=system_name:0.0

Software: Get Ignite-UX and any software depots you plan to distribute to clients from the product media (CD or DVD). Ignite-UX can also be downloaded from the web; see “Getting the Ignite-UX Software ” for more information.

Client access to server: There are multiple methods of having clients contact the Ignite server, each suited to a different environment. See Chapter 2 for more details.