— two-step media recovery” (page 217) and the Ignite-UX Installation Booting white paper available at http://www.hp.com/go/ignite-ux-docs 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.

◦

◦

◦

Ignite-UX servers must have at least 2 GB of free disk space available in /opt/ignite to support installation of all HP-UX releases (B.11.11, B.11.23, and B.11.31).

To save space, you can support only those HP-UX releases you plan to install or recover.

Ignite-UX servers might require significant space in /var/opt/ignite to support clients’ systems, store software depots, and save recovery archives. Default HP-UX file system sizes are unlikely to be sufficient for an Ignite-UX server. You must consider the number of client systems you intend to support and the maximum number of recovery archives to be saved for each client.

The size of a recovery archive depends on the content being saved. A recovery archive will normally include at least a full set of HP-UX operating system software.

File system space is needed to hold depots required for installation. You must consider how many different OS releases the server might need to support. Note that you might also want to support different OE versions of each HP-UX revision on your Ignite server, such as the HP-UX 11i v2 September 2004 OE release and the 11i v2 September 2006 OE release, or the 11i v3 Base OE (BOE) and the 11i v3 Virtual Server OE (VSE-OE) of a particular release. Space will also be needed to store additional application and patch depots.

◦If you use golden images, file system space is needed to hold them. Consider the size and number of images you will require.

◦See the HP-UX Installation and Update Guide available from http://www.hp.com/ go/hpux-core-docs-11iv3 for a detailed description of the disk space required for all Operating Environments for your version of HP-UX.

Other considerations

An Ignite-UX server might also require software, utilities, and configuration:

•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.

tftp dgram udp wait root /usr/lbin/tftpd\ tftpd /opt/ignite /var/opt/ignite

If you are using HP Serviceguard clusters or systems with multiple IP addresses on a LAN interface, use the -soption 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_[tapenet]_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:

Ignite-UX server requirements 23