Table 5 I/O Configuration variables (continued)

I/O Configuration Variable

Description

_hp_hide_other_disks

(string) This may be set to one or more space-separated hardware paths of disks that

 

must 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 6 I/O Configuration value types

I/O Configuration Value Type

Description

Hardware Path

For 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 Location

A physical location may be a series of alphanumeric values separated by the colon (

 

: ) character.

World-Wide Name / WWID

The 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 Protocol

The valid protocol values are:

 

•

fibre_channel

 

•

parallel_scsi

 

•

sas

 

•

usb

 

 

 

Agile view questions and answers

What are the requirements for the use of persistent DSFs? Must I use them exclusively or can I mix them with legacy DSFs?

Ignite-UX will use persistent DSFs for installation and recovery on systems running HP-UX 11i v3. Internally, VxVM volume management software controlling installation and recovery uses persistent or legacy DSFs as appropriate for the VxVM version used. See “Important characteristics of the agile view” (page 78) for more information.

Can the user switch from persistent to legacy DSFs and back if desired?

Switching between persistent and legacy DSFs is specific to the volume manager. See your volume manager documentation for more details.

Does the Ignite–UX interface enforce a particular use model with respect to persistent and legacy DSFs?

No, but persistent DSFs will be used for HP-UX 11i v3 installation and recovery.

If a persistent DSF is specified, is the equivalent legacy DSF added as well? And vice versa?

82 Managing I/O for installation and recovery