HP-UX 11i v3 Persistent DSF Migration Guide

Backward Compatibility
Legacy DSF support is maintained in HP-UX 11i v3 to retain backward compatibility. HP-UX commands and
utilities have been enhanced to manage subsystems in both legacy and agile views. By default those commands
behave the same way in HP-UX 11i v3 as on prior HP-UX releases. For instance, the output of most commands
is the same in HP-UX 11i v2 and in HP-UX 11i v3 (for options supported on both releases). See the Backward
Compatibility Exceptions section for the list of exceptions.
Note that some commands display either agile view or legacy view depending on which view was used during
their configuration. For these commands, if the agile view was used to configure some devices, the commands
will display these devices in the agile view. For example, the LVM commands may display persistent DSFs,
legacy DSFs, or a mix of both, depending on which DSFs were used when the LVM configuration was created.
Fully Backward Compatible Commands and Utilities
Most commands are fully backward compatible, meaning that in the legacy view, they behave the same way
as they did on releases prior to HP-UX 11i v3. Here are examples of such commands:
o ioscan(1M) - Specify the –N option as necessary to manage the agile view. Without the –N option,
output appears the same as in HP-UX 11i v2 if using options supported on both releases (for example,
ioscan –kfn will still show legacy hardware paths and legacy DSFs).
o rmsf(1M), insf(1M), lssf(1M), mksf(1M) – Accept legacy and persistent DSFs and
hardware paths as input.
o savecrash(1M) - Accepts both legacy and persistent DSFs as input.
o swapon(1M) - Accepts both legacy and persistent DSFs as input.
o swapinfo(1M) - Displays either persistent or legacy DSF, depending on what was configured.
o STM - Provides a menu option to display in legacy or agile view.
o System Management Homepage (SMH) - Provides a toggle to allow users to display in legacy or agile
view.
o LVM commands - Accept both legacy and persistent DSFs as input. New options have been introduced
to allow a choice between legacy DSFs and persistent DSFs. For example, the –N option has been
added to the
vgscan command to perform /etc/lvmtab recovery using persistent DSFs. Without the
–N option,
vgscan behaves as in HP-UX 11i v2, using legacy DSFs. See the LVM documentation
mentioned in Read before Migrating to HP-UX 11i v3
.
Backward Compatibility Exceptions
The following commands and utilities behave differently in HP-UX 11i v3 than in previous HP-UX releases:
o The crashconf command accepts persistent DSFs as input. For backward compatibility, it accepts
legacy DSFs, but it converts them to persistent DSFs, and its output is displayed in the agile view only
(persistent DSFs are displayed with option –v and lunpath hardware paths are displayed with the
option
–l). For more information, see crashconf(1M).
o The setboot command accepts persistent DSFs as input as well as lunpath hardware paths, or legacy
hardware paths, but it selects and stores in stable storage the lunpath hardware path to the device, and
subsequently it only displays output in the agile view (persistent DSFs and lunpath hardware paths),
regardless of whether a legacy hardware path was passed as input. For more information, see
setboot(1M).
o Ignite-UX operates in the agile view. It displays lunpath hardware paths for the location of the target
install media in the root disk selection screen. The mapping of lunpath hardware paths to legacy
8