instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
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 dev-
ice, 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 process. This confusion
may be avoided by using the device’s hardware path instead of the interface name (for exam-
ple,
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 inventory 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. Because Ignite-UX does not control kernel boot
inventory, some inventory information for blocked devices may be collected. All blocked dev-
ices will be hidden and not available for selection during install. To take effect, this variable
must be set in the
*INSTALLFS file using instl_adm.
inventory_block_protocols={"protocol"[,"protocol" ]... }
This keyword is used to control Ignite-UX inventory functionality. Ignite-UX will not collect
inventory information for devices connected to I/O adapters of listed I/O protocol types. Res-
tricting the Ignite-UX inventory 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. Because Ignite-UX does not control kernel boot inventory, some inventory infor-
mation for blocked devices may be collected. All blocked devices will be hidden and not avail-
able for selection during install. To take effect, this variable must be set in the
*INSTALLFS
file using instl_adm.
io_info = io.info_entry
io_info += io.info_entry
This keyword is used to record details about hardware configuration for use during recovery.
Each value corresponds to a complete io.info entry and together they form a complete saved
io.info configuration file. These values are intended for Ignite-UX internal use and should not
be modified.
File System Configuration
The default disk and file system configuration may be specified as a
partitioned_disk or a
volume_group.Inapartitioned_disk configuration, each disk may have a maximum of two par-
titions. One partition is a file system and the other is swap space. This configuration is also referred to as
the "whole disk" layout. The volume_group configuration allows one or more disks to be configured
into a Logical Volume Manager (LVM) volume group or VxVM disk group. That volume group may then
be split into one or more logical volumes. Each logical volume may be used for either file system, swap or
dump space. An LVM volume group may also be split into one or more physical volume groups, with at
least one disk in each physical volume group.
The general syntax of the disk and file system configuration is:
partitioned_disk
{
physical_volume disk[hw_path|index|dev_spec]
{
physical_volume-attributes...
}
fs_partition
{
14 Hewlett-Packard Company − 14 − HP-UX 11i Version 3: March 2012