Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
This section contains variables related to advanced features used to control the behavior of I/O configura-
tion during installation and recovery.
allow_disk_remap = boolean
Setting this to true allows Ignite-UX to substitute a disk that was specified in the con-
figuration files but that does not exist on the system with a disk that does exist and that
was not specified to be used, hidden or blocked. This allows for a configuration file gen-
erated for one client to be more easily used for a different system that has disks at differ-
ent hardware paths. This should be used with caution since the remapping algorithm may
end up using disks you did not originally wish to use. The remapping algorithm attempts
to find substitute disks with the same SCSI ID, and gives priority to finding a substitute
for the root disk. If a substitute disk cannot be found, the volume group is either created
without that disk or the file system is not created.
The default for this value is false for a non-interactive install, and true for an inter-
active install. During an interactive install, you are shown which disks are being substi-
tuted and may make changes, or cancel the install.
hide_boot_disk = boolean
Setting this to true prevents the installation process from allowing the boot disk to be
configured and/or "cleaned". This is useful only when the Ignite-UX kernel is booted
from a dedicated hard disk that you wish to protect from being modified.
_hp_hide_other_disks
String variable that may be set to one or more space-separated hardware paths or device
specifier attributes of disks that should be "hidden" from being configured or otherwise
modified during the installation. It allows for more disks to be hidden than that provided
by the hide_boot_disk keyword.
hw_instance_num = hw_path class_string [driver] instance_num
hw_instance_num += hw_path class_string [driver] instance_num
Setting this keyword forces a specific instance number assignment for the specified hard-
ware device. This keyword may be used when specific device special file names are
desired to produce a client consistent with others regardless of variations in hardware
configurations. The following examples assign the instance number 10 to the external
bus (SCSI bus) 2/0/1, and instance number 1 to the LAN device 2/0/2. Note that legacy
disk device special file names contain the instance number of the parent "ext_bus" device.
hw_instance_num = 2/0/1 "ext_bus" "c720" 10
hw_instance_num += 2/0/2 "lan" "btlan" 1
It may be very confusing when a configuration file defines the instance number for a
LAN device, and also specifies networking information by using the interface name,
which has the instance number in the string (for example, ip_addr[lan0]). In this case,
the original/default instance numbers are used because the instance number assignment
specified with hw_instance_num does not take place until late in the installation pro-
cess. This confusion may be avoided by using the device’s hardware path instead of the
interface name (for example, ip_addr[2/0/2]).
inventory_block_path = hw_path
inventory_block_path += hw_path
This keyword is used to control Ignite-UX inventory functionality. The hardware paths
must refer to an I/O adapter or a device. Ignite-UX will not collect inventory information
for devices listed or for devices connected to adapters listed. All adapters used for
devices must be listed when devices are connected using multiple paths. Ignite-UX will
inventory devices connected to any adapters not listed. Restricting the Ignite-UX inven-
tory process reduces the time required to collect I/O configuration information but will
result in some I/O information not being available for install and recovery processing.
Blocking inventory at the device level may not provide a significant performance benefit.
15