Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Ignite-UX Administration Guide: for HP-UX 11i > Chapter 7 Managing I/O for Installation and Recovery

Controlling the I/O Configuration Process


Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

It is possible to control the I/O configuration process associated with installation and recovery by using variables in the configuration file. These variables allow you to select disks that may be replaced with other disks, hide disks from the I/O configuration process, and control DSF naming.

By controlling the I/O configuration process, you can make configuration files that are general enough to use with clients having different hardware paths, protect disks from modification, and increase the performance of the I/O inventory process.

This section introduces the variables and value types associated with I/O configuration for use in configuration files. Further details can be found in instl_adm(4).

Table 7-3 I/O Configuration Variables

I/O Configuration VariableDescription
allow_disk_remap(boolean) Setting this to true allows Ignite to substitute a disk that was specified in the configuration files but does not exist on the system with a disk that does exist and was not specified to be used, hidden, or blocked. Default for this value is false for a noninteractive installation, and true for an interactive installation. This is useful when creating configuration files for use with multiple clients.
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 kernel is booted from a dedicated hard disk you wish to protect from being modified.
_hp_hide_other_disks(string) This may be set to one or more space-separated hardware paths of disks that should be “hidden” from being configured or otherwise modified during the installation. This is useful for hiding multiple disks.
hw_instance_number(string) Setting this keyword forces a specific instance number assignment for the specified hardware device. This is useful for producing client configurations consistent with others regardless of variations in hardware configurations.
inventory_block_path(string) This keyword is used to control Ignite inventory functionality by instructing Ignite to not collect inventory information for the devices specified. This is useful when you want devices hidden and not available for selection during installation.
inventory_block_protocols(string) This keyword is used to control Ignite inventory functionality by instructing Ignite to not collect inventory information for the devices of the protocol type specified. This is useful when you want to increase the performance of the I/O inventory process by ignoring all devices of a certain protocol. These devices will not be available for selection during installation.


Below are listed the value types for use with the I/O configuration variables.

Table 7-4 I/O Configuration Value Types

I/O Configuration Value TypeDescription
Hardware PathFor keywords that take a hardware path as an index parameter or value, the hardware path may be a series of more than one decimal or hexadecimal numbers separated by the period ( . ) or the forward slash ( / ) characters. A complex string or string variable may also be used where a hardware path is expected.
Physical LocationA physical location may be a series of alphanumeric values separated by the colon ( : ) character.
World-Wide Name / WWIDThe format of this value varies depending on the protocol and device. This value is often a standard IEEE value in hexadecimal format, however this value may have some other format. This value may not contain white space.
I/O ProtocolThe valid protocol values are:
  • fibre_channel

  • parallel_scsi

  • sas

  • usb


Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.