ioscan.1m (2010 09)

i
ioscan(1M) ioscan(1M)
In the agile view, EFI device paths are associated with the nodes which have class
as lunpath.
-f Generate a full listing, displaying the module’s class, instance number, hardware
path, driver, software state, hardware type, and a brief description.
-F Produce a compact listing of fields (see Fields below), separated by colons (
:). This
option overrides the
-f option.
-H hw_path Restrict the scan and output listing to those devices connected at the specified
hardware path. The hardware path must be a bus path. Scanning below the bus
level will not probe the hardware and may produce incorrect results.
For example, specifying the path at the target level will always change the state of
the device attached to it as
NO_HW
. The state of the device may be restored by
retrying
ioscan from a bus node above the
NO_HW node.
When used with
-M, this option specifies the full hardware path at which to bind
the software modules.
-I instance Restrict the output listing to the specified instance , when used with either
-d or
-C. When used with -M
, specifies the desired instance number for binding. Must
be used with either the
-d,
-C,or-M option.
-k Scan kernel I/O system data structures instead of the actual hardware and list the
results. No binding or unbinding of drivers is performed. The
-d, -C, -I
, and -H
options can be used to restrict listings. Cannot be used with -u. This option does
not require superuser privileges.
-l List locally connected devices.
-m keyword Display mapping information according to the keyword specified. ioscan retrieves
the information from the kernel I/O data structures without scanning the hardware.
Keywords can be any one of the following:
lun Display the LUN to lunpath mapping. The -d, -C, -I
, and -H options
can be used to restrict listings. Arguments passed must be from the agile
view. The
-F option can be used to generate a compact listing of fields
separated by colons (:). Fields include: class , instance number, LUN
hardware path , driver , software state , hardware type , block major
number, character major number, health , a brief description ,
lunpath(s) . Device special files corresponding to LUN will be shown on
separate line(s).
dsf Display the mapping between the legacy and persistent special files.
Either a legacy or persistent special file can be specified as an argument.
If none is specified, all valid mappings for character special files are
displayed. The -F option can be used to generates a compact listing of
fields separated by colons (:). Fields include: persistent special file ,
legacy special file(s) . Multiple legacy special files mapping to the per-
sistent special file are separated by a white space.
hwpath Display the mapping between the legacy hardware path, lunpath
hardware path, and LUN hardware path. The -H option can be used to
restrict listings. The argument specified with -H can either be a legacy
hardware path, lunpath hardware path, or LUN hardware path. The
hardware path specified will also be displayed along with the correspond-
ing other two representations, if present.
The
-F option can be used to generate a compact listing of fields
separated by colons (:), which is useful for producing custom listings
with awk. Fields include: LUN hardware path , lunpath hardware
path , legacy hardware path(s) . If there are multiple legacy hardware
path s mapped to a lunpath hardware path , they will be separated by a
white space in the last field. For example, if a lunpath hardware path
has two mappings to a legacy hardware path, the two legacy hardware
paths are separated by a white space in the last field. If there are multi-
ple mappings, they are displayed in separate lines. For example, if one
lun hardware path maps to two lunpath hardware paths, then each
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3