In its current implementation,
beginning with C.7.0.x, Ignite-UX is aware
of multiple paths to I/O devices. Ignite-UX now supports agile view on HP-UX 11i v3.
One of the features of HP-UX 11i v3 and later
is the ability to tolerate I/O path changes. For HP-UX 11i v2 and
earlier releases of HP-UX, Ignite-UX is aware that multiple device
special files (DSFs) and hardware paths may refer to the same device
logical unit (LUN).
Previous to HP-UX 11i v3, I/O addressing looks
like Figure 5-1, where a DSF is
specific to one hardware path, which in turn points to an I/O device’s
LUN.
Any of the legacy DSFs can be used to access the
I/O device. Care must be taken to prevent the simultaneous use of
multiple DSFs for conflicting purposes. For example, two DSFs for
the same LUN might be used for different volume or disk groups. Ignite-UX
will detect such an invalid configuration created with the Ignite
user interface and prevent installation. A final validation is also
done during sanity checking, which takes place after starting an installation.
Printable version
