The itool wizard prompts you to specify whether the disks in the root volume/disk groups should be striped (as well as to specify the number of disks in the root volume/disk group on the same screen). However, in the Ignite-UX GUI you must use the Additional button on the Basic tab to display the item Stripe root VG disks?.

Even though instl_adm(4) discusses LVM, striping also applies to VxVM (VxVM licensing may restrict its use). Remember that the root, boot, and primary swap+dump cannot be striped, so this only applies to other volumes in the root volume/disk group.

_hp_addnl_fs_free_pct

The _hp_addnl_fs_free_pct integer variable is used to control the amount of additional free space allocated to volumes beyond the space required to load the software. If this variable is not set, it defaults to 10 (10%).

The _hp_addnl_fs_free_pct variable can be changed using Additional free space % during an installation because of the following configuration.

_hp_addnl_fs_free_pct = { 0,1,2,3,4,5,6,7,8,9,10 } init _hp_addnl_fs_free_pct = 10

_hp_addnl_fs_free_pct help_text "Additional free space %"

This variable is not present for recoveries.

The instl_adm(4) manpage states the following about how _hp_addnl_fs_free_pct affects the size calculations for volumes:

In addition to this minimum size, an additional percentage is added to the volumes to ensure sufficient room after the system is installed. This percentage is by default 10%, but can be controlled by the configuration file variable _hp_addnl_fs_free_pct. If the disk capacity is insufficient to accommodate this additional free space, this additional percentage value is continually reduced by 1/2 until a value is found that allows all the volumes to fit. If the volumes still do not fit with 0% additional space, then the installation is not allowed to proceed.

Therefore, the variable does nothing when there is no free disk space; however, if there is free disk space, volumes on the system may be expanded in an unexpected manner.

_hp_ignore_sw_impact

The _hp_ignore_sw_impact integer variable can be set to one if you want to disable all effects that the impacts statements declared in the software selections have on the volume size calculations. This may be helpful if you want to ensure that Ignite-UX does not automatically modify the file- system volume sizes.

Be careful when setting this variable to 1. Ignite-UX does not change the file system sizes based upon the impacts statements associated with software products that are being installed. The installer must correctly set file system sizes so the system does not fill file systems during installation.

So, when do you use this variable? To answer that you need to look at how impacts are created. Consider the following commands57:

57You do not call gen_impacts in this way, because the format that it accepts is not documented. This example is only to illustrate how impacts are generated.

95