HP-UX System Administrator's Guide: Overview HP-UX 11i v3 (B3921-90011, September 2010)

ioscan ioscan performs many functions. Primarily it scans a server’s hardware,
binding new hardware with appropriate drivers. With regard to device
special files, ioscan can display the mapping between legacy device
special files and persistent device special files. See ioscan(1M) for details
on ioscan’s many functions and options.
scsimgr scsimgr, like ioscan, has many functions other than working with
device special files. But, you can use scsimgr to validate the change of
a LUN associated with a legacy device special file (replace a legacy
device special file). If you have replaced a disk drive and are using legacy
device special files, refer to the scsimgr(1M) manpage for assistance with
remapping the device special file to the new device. The scsimgr
command to do this is replace_leg_dsf.
For More Information on the Next Generation Mass Storage Stack
The following resources contain much more information on the components of the Next
Generation Mass Storage Stack:
• Technical White Paper: The Next Generation Mass Storage Stack HP-UX 11i v3
• The following manpages:
— scsimgr(1M)
— io_redirect_dsf(1M)
— insf(1M), lssf(1M), mksf(1M), rmsf(1M)
— iobind(1M), iofind(1M), ioscan(1M)
— intro(7)
Superdome 2 Resource Paths
On Superdome 2 systems, the Onboard Administrator (OA), used to configure nPartitions and
Virtual Partitions (vPars), uses a special form of addressing to reference the components of the
system. Known as resource paths, these addresses reference system components using operating
system agnostic path elements called entities.
The Superdome 2 OA works whether or not any operating systems are installed or booted; it
therefore needs its own mechanism for identifying system components. Resource paths provide
that mechanism.
Resource paths are associated with easily identifiable system components (for example, enclosures,
blades, I/O bays, and I/O slots), and are therefore a more “human friendly” way of representing
addresses.
Once booted, HP-UX uses its own hardware addressing mechanism (described in the previous
sections of this chapter). These hardware addresses, in either legacy or agile form, allow HP-UX
to locate its resources; but, they are much less suitable for human interpretation.
On Superdome 2 systems, where nPartitions and Virtual Partitions are created using the Onboard
Administrator, there are occasions when you need to map a hardware address (for example, as
reported by the ioscan command) to the corresponding resource path or physical location
needed to properly partition your system. The ioscan command, when used with the “-m
resourcepath” option provides this mapping. For examples of how this works see the HP
Superdome 2 Partitioning Administrator Guide, and the resourcepath(5) and ioscan(1M)manpages.
Managing HP-UX Swap Space
Swap space is where HP-UX stores unneeded pages of memory from running processes, a process
called virtual memory paging (or simply paging) because the chunks of data moved in and out
of physical RAM are called pages. This enables HP-UX to use much more memory than physically
exists on a server.
Storage on HP-UX 59