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

Example 3-2 Hardware Path Format Summary
The three formats described previously are different ways of referring to the same LUN, so a
single LUN could have all of the following addresses:
0/2/1/0.1.4.0.0.2.7
0/2/1/0.1.5.0.0.2.7
0/4/1/0.1.4.0.0.2.7
0/4/1/0.1.5.0.0.2.7
0/2/1/0.0x50001fe1500170ac.0x4017000000000000
0/2/1/0.0x50001fe1500170ad.0x4017000000000000
0/4/1/0.0x50001fe1500170ac.0x4017000000000000
0/4/1/0.0x50001fe1500170ad.0x4017000000000000
64000/0xfa00/0x22
In the previous example the LUN has four physical hardware paths. The first four lines represent
them using the legacy hardware path format, the next four lines represent them using the SCSI-3
hardware path format, and the final line represents the single virtual hardware path (used for
all four physical paths).
HP-UX 11i version 3 commands will accept any of these three formats to specify a hardware
path to a LUN.
Commands Associated with Device Special Files
Here is a list of key commands used for managing device special files:
insf
Used during boot to create both legacy and persistent device special
files for new devices. insf can also be used manually, while the system
is running, to create such device special files (for example, if ioscan
caused new hardware to be discovered insf could be run to create
device special files for that new hardware without having to wait for a
reboot of the system)
3
. See insf(1M) for details.
With the -L option, insf enables the legacy naming model.
mksf
Used to create a single device special file, usually with non-default
characteristics. For details on specifying the parameters for your device
special file, see mksf(1M).
If you wish to create a single device special file, perhaps with specific
parameters, use mksf instead of insf. For details on specifying the
parameters for your device special file, see mksf(1M).
lssf lssf lists information about specified device special files (in a friendly,
human readable form). For example, lssf can list stale device special files.
You can specify legacy or persistent device special files. For details and
examples of lssf output, see lssf(1M).
rmsf rmsf removes specified device special files. For information about the
many rmsf options for specifying which device special files to remove
(and from where to remove them), see the rmsf(1M) manpage.
With the -L option, rmsf disables the legacy naming model, removing
all legacy I/O nodes and their device special files from the system.
io_redirect_dsf io_redirect_dsf reassigns an existing device special file from one
device to another. Because this takes advantage of one of the primary
benefits of persistent device special files, it will not work with legacy
device special files. See io_redirect_dsf(1M) for details.
3. In some cases, new hardware is automatically discovered and associated persistent device special files are created,
even before ioscan is run. However, if you have new hardware with no associated device special files, insf can
create them for you.
58 Major Components of HP-UX