HP-UX Reference (11i v3 07/02) - 1M System Administration Commands N-Z (vol 4)

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, character Device Special File (DSF), or their
class and instance number. These are typically visible in the output of ioscan(1M). SCSI objects are typi-
cally a single LUN (logical unit number), LUN path, target path, 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 informa-
tion 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 reliability
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 60ms for all SCSI dev-
ices.
Per device type, vendor identifier, product identifier or specific product revision of devices bound to a
driver. A value of 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 60ms for disk devices from HP and bound to driver
esdisk, and to 120ms 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 50ms for disk0.
When the change to the current value of an attribute takes effect depends on the level or scope where the
change is performed. Change of an attribute at a global or intermediate levels (such as, device type and
vendor id) will not affect existing objects until an event requiring re-initialization of the object occurs.
For instance, change of global default I/O time out will not affect I/O transfer for LUNs already opened. If
a LUN is closed and re-opened, the new default I/O time out will be used. When change of an attribute at a
per-object instance level takes effect depends on the attribute and the driver owning it. For more informa-
tion, refer to the manpage of the driver plug-in for scsimgr.
HP-UX 11i Version 3: February 2007 1 Hewlett-Packard Company 309