User's Guide

1000Mb). For more information run "instl_dbg -D <clientdir> -d".
ERROR: The root volume (/) size plus the boot volume (/stand) size plus
primary swap size plus dump volume(s) size (1024000Kb + 24576Kb +
17780736Kb + 0Kb) is larger than the root disk (0/0/2/1.15.0)capacity
(17776640Kb) by 1052672Kb. These volumes must fit contiguously on the
root disk. For more information run "instl_dbg -D <clientdir> -d".
In this case there were two disks in the root volume group. Ignite-UX was able to move all of the
logical volumes except root, boot, and primary swap to the second disk. But because the size
value for primary swap was so large, Ignite-UX was unable to fit root, boot, and primary swap onto
the disk _hp_root_disk, and the installation failed.
Assuming the value for _hp_min_swap (if you’ve included the per-release config file
66
into the
cfg clause) is not too large, the size would be better given as:
size = _hp_min_swap | remaining | _hp_pri_swap
This would allow the size of primary swap to be at least _hp_min_swap, but can take all the
remaining space on the disk up to the value of _hp_pri_swap (which we know is larger than the
size of the disk.)
Doing this would allow the disk configuration to successfully create a system.
Example Four (installation file system configuration)
The example in this section is intended for use in an installation file system, not in configuration
files. The best use of this configuration is in an installation file system contained in LIF and used to
boot a system using tape|CD|DVD so it does not use DHCP to gain an IP address. This section
does not discuss other configuration items you might set like _hp_lanadmin_args.
This example is intended for use with HP9000 systems. For information on how to achieve these
same results with HP Integrity systems (or to create media that can be used on both hardware
architectures) see "Building an Installation DVD" in the Ignite-UX Administration Guide, Edition 18
or later. Additionally, this section contains information about the placement of a LIF inside an El-
Torito boot image for use with Itanium®-based systems.
Part A (custom configuration in installation file system)
This part of the example deals with simply providing an IP address and network information that
can be applied to an LIF (and hence to the installation file system within the LIF.) This method
requires you to build a different LIF for every system and place it onto media separately.
The following configuration is needed to contact the Ignite-UX server:
server="10.0.0.2"
netmask[]="255.255.255.0"
route_gateway[0]="10.0.1.1"
route_destination[0]="default"
disable_dhcp=true
This line gives the system its IP address:
66
Since this example is about 11.23 the per-release config file would be /opt/ignite/data/Rel_B.11.23/config.
139