ioscan.1m (2010 09)

i
ioscan(1M) ioscan(1M)
lunpath hardware path will map to a legacy hardware path.
cluster_dsf
Display the mapping between the cluster, legacy and persistent device
special files. Either a cluster, legacy or persistent special file can be
specified as an argument. If none is specified, all valid mappings for
character device special files are displayed. If the cluster special files are
not available, the command simply returns with a return value of 0. The
-F option can be used to generate a compact listing of fields separated by
colons (:). Fields include: cluster special file, persistent special file ,
legacy special file(s) .
resourcepath
Display the mapping between the hardware path, physical location and
resourcepath. The -H option can be used to restrict listings. The
-F
option can be used to generate a compact listing of fields separated by
colons (:). Fields include: Hardware path , Physical location , Resour-
cepath .
-M driver Specify the software driver to bind at the hardware path given by the
-H option.
Must be used with the
-H
option.
-n List device file names in the output. Only special files in the
/dev directory and its
subdirectories are listed. Must be used with either the
-f or the -F option.
-N Display the agile view (see intro (7)) of the system hardware. For mass storage dev-
ice entries that would normally include the driver class, the legacy hardware path,
and the device description, ioscan prints a class of lunpath, the lunpath hardware
path, and the name of the LUN that it maps to, when used with this option. In
addition, the output will include entries for the mass storage devices at their LUN
hardware paths, with the expected driver class and description. Thus, each mass
storage device will have at least two entries in the ioscan output: one for the
LUN hardware path and one for each lunpath hardware path. If used with the -n
option, ioscan only prints persistent special files.
-P property Display the property of nodes in the agile view. This option can be combined with
the -C, -d, -I and -H options, but the parameters passed must belong to the agile
view. The valid properties are:
bus_type , cdio, is_block , is_char , is_pseudo , b_major, c_major , minor , class ,
driver , hw_path , id_bytes , instance , module_name , sw_state , hw_type , description ,
health , error_recovery, is_inst_replaceable, wwid, uniq_name , alias_path ,
physical_location, and ms_scan_time .
More details about the above properties can be found in the Fields section below,
except for error_recovery, is_inst_replaceable, wwid, uniq_name, alias_path ,
physical_location, and ms_scan_time which are explained here:
error_recovery
This property indicates support for the PCI error recovery feature. The pro-
perty is only created for the Local Bus Adapters (LBA) nodes. The
error_recovery property can be set to one of the following values:
supported
The platform and all interface card driver instances under the given LBA
node support the PCI error recovery capability.
unsupported
Either the platform or one of the interface card driver instances under
the given LBA node do not support the PCI error recovery capability.
N/A The N/A is to be displayed for nodes that are not LBA nodes.
The availability of this feature is dependent on the platform and operating
system environment, as described in the PCI Error Recovery Support Matrix
at
http://www.hp.com/go/hpux-core-docs.
is_inst_replaceable
This property indicates the capability of the driver to support online instance
4 Hewlett-Packard Company − 4 − HP-UX 11i Version 3: September 2010