The -poption creates intermediate directories. It is best to store it in a directory of type /var/opt/ignite/archives/Rel_rel. This directory must be NFS-exported if you are using NFS to transfer the archive to the client.

4.If you do not have enough disk space, or you want the archive created on a remote server, you may use the following options:

#/tmp/make_sys_image -ddirectory_to_place_archive -sdestination_system_IP_address

5.On the golden system, run:

#/tmp/make_sys_image [options]

By default, this creates a gzip-compressed tar archive in /var/tmp with the name hostname.gz (where hostname is the name of the client). All specific host information, device files, log files, and network information are removed.

IMPORTANT: If an error similar to the following appears:ERROR: Cannot remsh server system_name (check server .rhosts file), you must add the name of the client to the /.rhosts file on your Ignite-UX server as in the following example entry:

system_name root

The make_sys_image command can build an archive with the tar, cpio, or pax format, compressed with a selectable compression method. HP recommends using tar (default) for the archive format and gzip (default) for compression. To use the pax format with 11i v2,

you must have the PAX-Enh™ product installed. The pax format is not available for 11i

IMPORTANT: When using the pax command you should consider the size of your files. Files included by the pax command with tar and cpio formats must be less than 8 on 11i v2 and v3, and less than 2 for v1. Using the pax format will allow large files in an archive – up to 2 TB for 11i v2 and up to 16 TB for v3.

Configuring the Ignite-UX Server to Recognize the Golden Image

To create an Ignite-UX configuration file for the golden image, use the example config file /opt/ ignite/data/examples/B.11.11.golden_image.cfg. Other example config files are available to match the version of HP-UX your golden systems is running: B.11.23.golden_image.cfg and B.11.31.golden_image.cfg.

1.Create a copy of the example configuration file:

# cp /opt/ignite/data/examples/B.11.11.golden_image.cfg \ /var/opt/ignite/data/Rel_B.11.11/core_archive.cfg

Because the configuration file must be accessible by tftp or NFS, depending on how you've set up your server, make sure you store it in a directory of type /var/opt/ignite/data/Rel_rel.

Ignite-UX manages the names and locations of configurations using the /var/opt/ignite/ data/INDEX file (see step 3).

2.Modify the core_archive.cfg file to set up the golden image for NFS transfer. (See the complete sw_sel and sw_source examples following these instructions. Use values appropriate for your systems.) Key changes are:

a.In the sw_source clause, change the following line so it has the path to your archive, including the IP address of your Ignite-UX server. This directory will have to be NFS exported later.

nfs_source = "10.2.72.150:/var/opt/ignite/archives/Rel_B.11.11"

b.Remove the init sw_sel clauses you will not be using for this golden image.

154 Golden Images