Create a copy of the example config file:
cp /opt/ignite/data/examples/core11.cfg \ /var/opt/ignite/data/Rel_B.11.00/core_700_archive_cfg
The destination file name is arbitrary. You can store configuration
files anywhere on the system you chose. Ignite-UX manages the names
and locations via the INDEX file (see Step 3 below). This file must be accessible
via tftp.
Modify the core_700_archive_cfg section to set up the OS archive for NFS transfer.
Key changes are:
In the sw_source clause, change the following:
nfs_source =
"15.2.72.150:/var/opt/ignite/archives/Rel_B.11.00"
(This points to directory where the archive lives and must
be NFS exported.)
In the init sw_sel clause, change the following:
description = "Archive HP-UX 11.00 CDE"
(This will now appear in the Environments section of the Ignite-UX user-interface
as a menu choice).
archive_path = "hpfcnjm2.gz"
(This points to the actual file in combination with the nfs_source line).
Add impacts lines in the init sw_sel clause by executing:
/opt/ignite/lbin/archive_impact -t -g archive_file
and including the results in the file, replacing the example impacts lines. By default, this assumes that we created
a tar archive that was gzipd.
Here is the complete sw_sel clause (some extra clauses in the example have
been deleted for simplicity):
init sw_sel "golden image" {
description = "Archive HP-UX 11.00 CDE"
sw_source = "core archive"
sw_category = "HPUXEnvironments"
archive_type = gzip tar
# For NFS, the path to the archive is relative to the mount
# point specified in the sw_source:
archive_path = "hpfcnjm2.gz"
# ftp/remsh sources can use a full path:
# archive_path = "/pub/IUXarchives/B.11.00_700_CDE.gz"
impacts = "/" 23Kb
impacts = "/.dt" 35Kb
impacts = "/TT_DB" 18Kb
impacts = "/etc" 1375Kb
impacts = "/export" 1Kb
impacts = "/opt" 74079Kb
impacts = "/sbin" 13449Kb
impacts = "/stand" 1Kb
impacts = "/tmp" 1Kb
impacts = "/usr" 225459Kb
impacts = "/var" 5736Kb
} = TRUE
Add the new configuration file to Ignite-UX:
Edit the /var/opt/ignite/INDEX file to install a new "configuration" to Ignite-UX.
For this example, add a new "cfg" clause as follows:
cfg "HP-UX B.11.00 archive" {
description "some description of this archive..."
"/opt/ignite/data/Rel_B.11.00/config"
"/var/opt/ignite/data/Rel_B.11.00/core_700_archive_cfg"
"/var/opt/ignite/config.local" }The line of most interest is the one containing the core_700_archive_cfg, which is the config file we added in Step 2.2. The "config" and "config.local" are
standard configurations.
/var/opt/ignite/config.local should be last. The last config file has the highest
priority and can override values in prior config files.
The file /opt/ignite/data/Rel_B.11.00/config supplies the disk and file-system layout defaults, plus
other control information required by Ignite-UX. It must be first
in every cfg clause.
Each cfg clause appears as an available configuration to Ignite-UX. Therefore,
the string HP-UX B.11.00 archive will now appear as a valid configuration.
Ensure NFS file system is exported correctly.
In the above sw_source clause, we specified the location of the OS archive
to be a file on an NFS server. You need to ensure target systems have
access to this directory.
Make sure the NFS configuration is correct. To view the current
status and ensure the directory containing the archive is correctly
exported, enter:
exportfs -v
Ignite-UX will automatically try to export /var/opt/ignite/clients for its use. In our example, /var/opt/ignite/archives/Rel_B.11.00 must also be exported because that is where we placed
the OS archive.
Here's our /etc/exports file:
/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives/Rel_B.11.00 -ro,anon=2
If these are not correct, use SAM to set them up correctly.
Printable version
