scsimgr.1m (2011 03)
s
scsimgr(1M) scsimgr(1M)
NAME
scsimgr - SCSI management and diagnostic utility
SYNOPSIS
/usr/sbin/scsimgr
[-fpv] command [-d driver][identifier][keyword]... [argument ]...
/usr/sbin/scsimgr
[-h][-d driver][command]
DESCRIPTION
scsimgr performs management and diagnostic operations on the SCSI objects and subsystems.
SCSI objects are identified by either their hardware path, hardware path alias, character Device Special
File (DSF), or their class and instance number. These are typically visible in the output of
ioscan.
Some SCSI objects may be identified by their object type and instance number. SCSI objects are typically
a single LUN (logical unit number), LUN path, target path, target port, enclosure, HBA controller, or a
group of these. The SCSI object is specified as an identifier in the command line.
A SCSI subsystem is typically the SCSI services module, a SCSI class driver, or a SCSI interface (also
known as I/F) driver.
scsimgr provides generic management and diagnostic capabilities for the SCSI subsystem as well as
specific management and diagnostic capabilities for SCSI class drivers or SCSI interface drivers through
plug-ins provided by these drivers.
Refer to the respective manpages of the
scsimgr driver plug-ins for detailed description of commands
and other functions specific to that driver. The manpages of driver plug-ins are in section 7, and are of
the form: scsimgr_driver where driver is the name of the driver. For example scsimgr_esdisk(7) is the
manpage of the
scsimgr plug-in for the esdisk driver.
A SCSI subsystem may maintain a set of attributes. An attribute is a data value associated with either
the SCSI subsystem, a set of SCSI objects, or a single instance of a SCSI object. It has a name, a data
type, and may have one or more value instances: current (run-time value), saved (value in a persistent
store), and default.
An attribute can be read-only or read-write. Read-only attributes are global or per-object instance infor-
mation that can be queried individually through their name. Saved and default values are irrelevant for
such attributes.
Read-write (or settable) attributes are tunables. Users or user applications can change their current or
saved values. The saved value is used to set the current value of the attribute at system boot or other re-
initialization points. When no saved value exists, the default value is used to set the current value.
Attributes can be generic or driver specific. Generic attributes do not depend on a class or an interface
driver. They are described in this manpage. Driver specific attributes are maintained by a class or an
interface driver. They are described in the respective manpages of the driver plug-ins for
scsimgr.
To ease management, adapt to various resource conditions, and increase the interoperability and reliabil-
ity of the SCSI stack, settable attributes can be defined at various scopes or levels:
• Global: A value of an attribute set at this scope, affects the default behavior for the SCSI stack, a class
driver or an interface driver. For instance, the default I/O timeout can be set to 60sec for all SCSI
devices.
• Device Set or DDR (Device Data Repository): This scope includes a set of devices bound to a driver,
and defined by parameters such as device type, vendor identifier, product identifier or product revi-
sion. An attribute set at this scope affects the default behavior for the set of devices bound to the
specified driver and meeting the specified criteria. For instance, the default I/O time out can be set to
60sec for disk devices from HP and bound to driver esdisk, and to 120sec for all tape devices bound
to driver estape.
• Per a specific instance of an object: A value of an attribute set at this scope overwrites the default
behavior for a specific instance of an object. For instance, I/O time out can be set to 50sec for
disk0.
When the change to the current value of an attribute takes effect depends on the attribute and the level
or scope where the change is performed. In general, change of an attribute at a global or intermediate
level (such as, device type and vendor id) will immediately affect the current values of all existing objects
covered by the scope.
For example, if the default I/O timeout is changed for all HP disk devices, this will immediately affect I/O
timeout for all HP disk devices whether they are currently open or not. However, the change will not
HP-UX 11i Version 3: March 2011 − 1 − Hewlett-Packard Company 1