instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
disk["WWID=’wwid’ PHYS_LOC=’phys_loc’ HW_PATH=’hw_path’"]
In this example, Ignite-UX would first look for a disk with a
WWID of wwid, and if it could not
be found, then it would look for a disk with a
PHYS_LOC of phys_loc , and if that could not be
found, then it would look for a disk with a
HW_PATH of hw_path and return that if found. If
all attributes are exhausted, then Ignite-UX will find a replacement disk if
allow_disk_remap
is set to true.
I/O Protocol (protocol ):
An I/O protocol type. Not all HP-UX releases support all protocol types listed here. Some pro-
tocol types listed here may not be supported by any HP-UX release and are included to indi-
cate what the protocol value would be if the protocol is ever supported in the future. Protocols
not supported by an HP-UX release will be ignored. These protocol type values may be used to
construct a protocol list. That list order may be used by some parameters to indicate a specific
prioritization of I/O adapters and devices for install or recovery processing. The valid protocol
values are:
fibre_channel
I/O protocol type Fibre Channel (FC). The priority order of FC devices connected via the
same I/O adapter is based on hardware path (lunpath hardware path for HP-UX 11.31
and later).
parallel_scsi
I/O protocol type Parallel Small Computer System Interface (SCSI). The priority order of
Parallel SCSI devices connected via the same I/O adapter is based on SCSI bus priority
order (e.g. SCSI address 7 to 0 followed by 15 to 8).
sas I/O protocol type Serial Attached SCSI (SAS). The order of SAS devices connected via the
same I/O adapter is based on physical location. Note that hardware path values should
not be used for device selection or recovery device matching since these values are not
consistent for the same device from install to install.
usb I/O protocol type Universal Serial Bus (USB). The order of USB devices is not yet
defined. There is currently no support for USB devices as a target for install or recovery.
This section contains variables related to advanced features used to control the behavior of I/O
configuration during installation and recovery.
allow_disk_remap =
boolean
Setting this to
true allows Ignite-UX to substitute a disk that was specified in the
configuration 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 generated
for one client to be more easily used for a different system that has disks at different 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 interactive
install. During an interactive install, you are shown which disks are being substituted 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 hardware
device. This keyword may be used when specific device special file names are desired to pro-
duce a client consistent with others regardless of variations in hardware configurations. The
HP-UX 11i Version 3: March 2012 − 13 − Hewlett-Packard Company 13