However, if you can remember part of the WWID, you can use the Ignite user interface Disk Selection dialog box Filter text box to limit displayed devices to those with WWIDs containing the text you can remember.
Agile addressing means the hardware path actually used by the system to access a device is independent of the path used to select the device. Selecting a disk via one hardware path might result in the system choosing some other, better hardware path. For example, this can happen when selecting a disk for boot, and when volume managers determine the appropriate set of paths to use for device access.
NOTE: For HP-UX 11i v3, the one hardware path used for selection has no special significance in most Ignite-UX user interfaces. Ignite-UX will allow HP-UX system software to select the best path when a particular path is needed. For example, boot paths will be selected by system software when the boot device is selected.
A more user-friendly approach is to identify I/O devices with a device identifier. A device identifier is a human-readable device ID defined by the user. It can be written to the device and read back. Data centers may want to create some standard policy for device IDs (e.g. LAB2CAB23LUN15).
In the current implementation, the device ID can be set, checked, and read at installation. The device identifier is stored on the device, so it remains available if the disk is moved to a different system or connected to multiple systems. Not all devices support the use of a device identifier.
See the scsimgr(1M) command for more information on how to set and read a device identifier.
When identifying I/O hardware for Ignite-UX configuration files, see Table 5 (page 81) for the format of I/O variables.
NOTE: Your data center may use separate processes or groups to administer systems and storage. It is important to record WWID, Device ID, and other details of LUNs assigned to your systems. Access control or protection zones may be used to control the systems permitted to use a LUN; it is important to record which systems have access to LUNs.
For more details on agile view HP-UX, see the white paper Overview: The Next Generation Mass Storage Stack available at http://www.hp.com/go/hpux-core-docs.
Practical Considerations
Ignite-UX uses hardware paths to help you identify I/O devices such as disks, CD/DVD drives and tape drives during installation and recovery. The format of the hardware path used to identify I/O devices will depend on the version of HP-UX you are using and other factors. Also, depending on your configuration, multiple paths might be displayed for a single device.
For HP-UX 11i v3, Ignite-UX will allow HP-UX system software to select the best path when a particular path is needed. For example, boot paths will be selected by system software when the boot device is selected.
Note that horizontal scrolling might be required to read the entire hardware path and associated data in Ignite-UX GUI screens.
IMPORTANT: Due to application dependencies, HP-UX software deployment tools such as Ignite-UX expect legacy DSFs to be present and the legacy naming model to be enabled. Therefore, HP recommends only partial migration be performed, as detailed in the HP-UX 11i v3 Persistent DSF Migration Guide, available at http://www.hp.com/go/hpux-core-docs.
System Installation Configuration
When using Ignite to install HP-UX on a client, a root disk must be identified. Ignite-UX selects a default disk, but it may be changed using the Root Disk... button on the Basic tab on the client installation configuration interface shown below.
