Ignite-UX Administration Guide for HP-UX 11i (B3921-90080, November 2013)

Starting with HP-UX 11i v3 OE Update March 2013 release, Ignite-UX supports the size of Swap,
Dump, and unused logical volumes up to 1 TB instead of the previous limit of 128 GB on 11i v2
and 11i v3. During a cold installation or recovery, larger amounts of swap, dump, or swap volumes
can be utilized in disk or volume groups by defining multiple swap, dump, or swap volumes. The
limit for unused volumes on 11i v1 is 1 TB; however, the limit for swap and dump has not been
increased.
Identifying Devices for Other Tasks
There are a number of other Ignite tasks that require the identification of I/O devices:
When building installation media, you must use the ioscan command to find the tape, CD,
or DVD drive. Note that some of the CD/DVD writing SW included with Ignite-UX but not
developed by HP only works with legacy device special files.
When performing a system recovery on Itanium-based systems, you must find the tape device’s
hardware path to create an EFI boot option. (This should be done at the time the tape is
created.)
During two-step media recovery, you must select the hardware path of the tape drive to recover
from.
When in expert recovery mode, you must have the hardware path of the disk you are attempting
to recover.
When identifying disks in configuration files to define them or combine them in a single volume
group, you must supply the hardware paths of the disks.
Important Characteristics of the Agile View
The following points will help you move from the legacy view to the agile view:
When using the new persistent DSFs, be sure to use the new directory structure:
Table 3 Mass Storage DSF Directories
Legacy DSF DirectoryPersistent DSF Directory
/dev/dsk/dev/disk
/dev/rdsk/dev/rdisk
/dev/rmt/dev/rtape
Both legacy and persistent DSFs can be created during installation and recovery of HP-UX 11i
v3 depending on your volume manager. When Ignite-UX creates file system content for HP-UX
11i v3, persistent DSFs are used for LVM volumes and VxVM 5.0 layout, and legacy DSFs
are used for VxVM 4.1.
NOTE: The VxVM components in the Ignite-UX install environment and the installation depot
must be version 5.0 or higher in order to use persistent DSFs.
Keep in mind that persistent DSFs endure with recovery if Ignite recovers to the same hardware
or can map to replacement hardware, but are not guaranteed to remain the same between
installations. See Figure 25 for an overview regarding consistency of I/O addressing.
If hardware is replaced and recovery is not needed, you might want to run io_redirect_dsf
to correct the system configuration. For more information, see io_redirect_dsf(1M).
Practical Considerations 79