[RFCs/IDs] [Plain Text] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 03 04 05 06 07 08 09 RFC 4455
Internet Draft M. Hallak-Stamler
Sanrad Intelligent Storage
draft-ietf-ips-scsi-mib-04.txt M. Bakke
Cisco Systems
K. McCloghrie
Cisco Systems
Y. Lederman
Siliquent Technologies
M. Krueger
Hewlett-Packard
Expires: April 2003 October 2002
Definition of Managed Objects for SCSI Entities
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet- Drafts as
reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract
This memo defines a Management Information Base (MIB) for Small
Computer System Interface (SCSI) entities, independently of the
interconnect subsystem layer.
Table of Contents
1. The SNMP Management Framework.....................................3
2. Conventions.......................................................3
3. Overview..........................................................4
3.1 Introduction....................................................4
3.2 SCSI Terminology................................................6
Hallak-Stamler et al. [Page 1]
SCSI MIB October 2002
3.2.1 SCSI application layer......................................6
3.2.2 SCSI Device.................................................6
3.2.3 SCSI Port...................................................6
3.2.4 SCSI Initiator Device.......................................6
3.2.5 SCSI Initiator Port.........................................7
3.2.6 SCSI Target Device..........................................7
3.2.7 SCSI Target Port............................................7
3.2.8 Logical Units...............................................7
3.2.9 Logical Unit Number.........................................7
3.2.10 Interconnect subsystem.....................................7
3.2.11 Device Server..............................................7
3.2.12 Task Manager...............................................7
3.3 SCSI MIB implementations........................................8
3.4 Bridging and Virtualization....................................10
3.5 SCSI Commands MIB..............................................10
4. Structure of the MIB..............................................10
4.1 The SCSI Device Group..........................................10
4.2 The Initiator Group............................................11
4.3 The Target Group...............................................11
4.4 The Discovery Group............................................11
4.5 The LUN Map Group..............................................11
4.6 The Target Statistic Group.....................................11
4.7 The Target High Speed Statistic Group..........................11
4.8 The LUN Map Statistics Group...................................12
4.9 The LUN Map Statistics High Speed Group........................12
4.10 The Initiator Statistic Group.................................12
4.11 The Initiator High Speed Statistic Group......................12
4.12 The Discovery Statistics Group................................12
4.13 The Discovery Statistics High Speed Group.....................12
4.14 The Device Statistics Group...................................13
5. Relationships in this MIB.........................................13
6. Relationship to Other MIBs........................................14
6.1 Host Resource MIB..............................................14
6.2 iSCSI MIB......................................................14
7. Miscellaneous Details.............................................14
7.1 Names and Identifiers..........................................15
7.2 Logical Unit Number............................................15
7.3 State of logical units.........................................15
7.4 Notifications..................................................15
7.5 SCSI Domains...................................................15
7.6 Counters: 32 bits and 64 bits..................................15
8. Abbreviations.....................................................16
9. Object Definitions................................................16
10. Acknowledgments..................................................65
11.Objects Population Example: Target and Initiator on a pSCSI bus...65
12. References.......................................................70
12.1 Normative References..........................................70
12.2 Informative References........................................71
13. Security Considerations..........................................71
14. Authors' Addresses...............................................72
15. Full Copyright Statement........................................73
Hallak-Stamler et al Expires April 2003 [Page 2]
SCSI MIB October 2002
1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 and
described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and
RFC 1215 [20]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [4], STD 58, RFC 2579 [5] and STD 58, RFC
2580 [6].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1
and described in STD 15, RFC 1157 [7]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[21] and RFC 1906 [8]. The third version of the message
protocol is called SNMPv3 and described in RFC 1906 [8], RFC
2572 [9] and RFC 2574[10].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [7]. A second set of protocol
operations and associated PDU formats is described in RFC 1905
[11].
o A set of fundamental applications described in RFC 2573 [12]
and the view-based access control mechanism described in RFC
2575[13].
A more detailed introduction to the current SNMP Management
Framework can be found in RFC 2570 [22].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine-readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of
machine-readable information is not considered to change the
semantics of the MIB.
2. Conventions
Hallak-Stamler et al Expires April 2003 [Page 3]
SCSI MIB October 2002
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
they appear in this document, are to be interpreted as described in
RFC 2119 [23].
3. Overview
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects to configure
and monitor Small Computer System Interface entities (SCSI
entities), i.e. SCSI Devices, SCSI Targets and Initiators and SCSI
Ports.
SCSI is a client-server protocol in which application clients within
an initiator device (client) issue service requests to logical units
contained in a target (server).
This MIB is based on documents defined by the ANSI T10 Technical
Committee, specifically the SCSI Architecture Model - 2 document
[14].
3.1 Introduction
In the late 1970s a firm called Shugart Associates started to have
some considerable success with a peripheral interface definition in
what became the PC marketplace, and this interface was adopted
and extended by an open standards committee to form the Small
Computer Systems Interface (SCSI). SCSI defines an 8 bit wide multi-
drop "bus" structure which could interconnect a total of eight
peripherals and computer systems.
It's important to realize that all SCSI initially standardized was
the "physical connection" i.e. the connectors, cables and interface
signals. Thus even though a peripheral could be connected to
multiple systems, the information that flowed across the interface
was different in each case. This was addressed some five years later
by the definition of a Common Command Set, and with this definition
in place it was possible for the first time to develop a peripheral
with both a common interface and common operating firmware for
connection to multiple systems.
The physical interface of SCSI continued to be developed throughout
the 1980s with the addition of fast (up to 10 megabytes/s) and wide
(16 bits) variants, but the distance supported remained a maximum of
25 meters (from one end of the bus to another), and indeed some of
the faster variants supported much less than that distance. The
command set development continued, with special commands for tapes,
printers, and even processors being added to the original disk-
oriented set. So successful was SCSI in the 1980s that the majority
of the available Operating Systems incorporated support for the SCSI
command set as standard.
Hallak-Stamler et al Expires April 2003 [Page 4]
SCSI MIB October 2002
However at the end of the 1980s the distance, speed and number of
devices supported by SCSI were starting to become significant
impediments to systems design, and while the "information explosion"
had not yet started in earnest, it was already being anticipated. At
the same time, the serial interface technologies developed for Local
Area Networks such as Ethernet, and the fibre optics technologies
that were first deployed in telecommunications applications, were
starting to appear sufficiently rugged & low-cost for use in
peripheral interface applications. Thus a standards project was
begun in 1988 to develop a new serial, fibre-optic interface to
carry the SCSI command sets and other peripheral protocols. This
interface eventually became known as Fibre Channel (FC), and it is
based on an architecture centered around an abstractly defined
"fabric", which may be a switch or a loop connection. MIBs for
various FC equipments are already in existence.
In order to support the new interfaces, it was necessary to
completely reorganize the SCSI standards and definitions. The
command sets were separated from the physical interface definitions,
and a SCSI Architectural Model (SAM) was created to define the
interaction between the various standards. It is a key to
understanding SAM to realize that it was first created approximately
10 years AFTER the first SCSI products were shipped!!
The most recent development in this saga occurred in 2000 when an
IETF Working Group was formed to address, amongst other things, a
definition for transporting the SCSI command sets directly over a
TCP/IP infrastructure. This effort is known as iSCSI [24], and an
iSCSI MIB is already under development [25].
Most of the projects are in T10, except Fibre Channel that is
defined by T11 and IEEE defines 1394.
The SCSI MIB represents the SCSI protocol layer common to all SCSI
command sets and transports. It does not represent the command sets
and transports themselves. These should appear in other MIBs
specific to the transport or command set. The following drawing
shows the relationships between the various actual and possible
SCSI-related MIBs.
Hallak-Stamler et al Expires April 2003 [Page 5]
SCSI MIB October 2002
+---------------------------------+
SCSI Command | Higher-level MIBs, specific to |
Sets | command sets, disk, tape, etc. |
+---------------------------------+
SCSI | SCSI MIB |
+-------+---------+-------+-------+
SCSI | iSCSI | FCP | SPI | Other |
Transport | MIB | MIB | MIB | MIBs |
Protocols | | | | |
+-------+---------+-------+-------+
SCSI | TCP | Fibre | Other |
Interconnect | MIB | Channel | Interconnect |
| | MIBs | MIBs |
+-------+---------+-------+-------+
An iSCSI MIB [25], and a Fibre Channel interconnect MIB [26] are
currently being developed. No development is currently planned for
standard command-set-specific or device-specific MIBs.
Standard Fibre Channel interconnect MIBs [26] are also under
development.
No development is currently planned for standard command-set-
specific or device-specific MIBs.
The TCP MIB [27] is already a proposed standard RFC 2012.
3.2 SCSI Terminology
The following sections explain some of the SCSI terminology, which
is used later in defining the MIB. For the authoritative
definitions of these terms, see SAM-2 [14].
3.2.1 SCSI application layer
The protocols and procedures that implement or invoke SCSI commands
and task management functions by using services provided by a SCSI
protocol layer.
3.2.2 SCSI Device
A SCSI device is an entity that contains one or more SCSI ports that
are connected to a service delivery subsystem and supports a SCSI
application protocol.
3.2.3 SCSI Port
A SCSI port is a device-resident entity that connects the
application client, device server or task manager to the service
delivery subsystem through which requests and responses are routed.
A SCSI port is synonymous with port and either a SCSI initiator port
or a SCSI target port.
3.2.4 SCSI Initiator Device
A SCSI initiator device contains application clients and SCSI
initiator ports that originate device service and task management
Hallak-Stamler et al Expires April 2003 [Page 6]
SCSI MIB October 2002
requests to be processed by a target SCSI device. When used this
term refers to SCSI initiator devices or SCSI target/initiator
devices that are using the SCSI target/initiator port as a SCSI
initiator port.
3.2.5 SCSI Initiator Port
A SCSI initiator port acts as the connection between application
clients and the service delivery subsystem through which requests
and responses are routed. In all cases when this term is used it
refers to an initiator port or a SCSI target/initiator port
operating as a SCSI initiator port.
3.2.6 SCSI Target Device
A SCSI target device contains logical units and SCSI target ports
that receive device service and task management requests for
processing. When used this term refers to SCSI target devices or
SCSI target/initiator devices that are using the SCSI
target/initiator port as a SCSI target port.
3.2.7 SCSI Target Port
A SCSI target port contains a task router and acts as the connection
between device servers and task managers and the service delivery
subsystem through which requests and responses are routed. When this
term is used it refers to a SCSI target port or a SCSI
target/initiator port operating as a SCSI target port.
3.2.8 Logical Units
A logical unit is an entity residing in the target that implements a
device model and processes SCSI commands sent by an application
client.
3.2.9 Logical Unit Number
A Logical Unit Number or LUN is a 64-bit identifier for a logical
unit.
3.2.10 Interconnect subsystem
An interconnect subsystem is one or more physical interconnects that
appear as a single path for the transfer of information between SCSI
devices.
3.2.11 Device Server
A device server is an object within the logical unit that processes
SCSI tasks according to the rules for task management.
3.2.12 Task Manager
A task manager is a server within the target that processes task
management functions.
3.2.13 SCSI Instance
A "SCSI instance" is a distinct SCSI entity within a managed system.
While most implementations will have just one SCSI instance, the MIB
allows for multiple (virtual) instances, such that a large system
can be "partitioned" into multiple, distinct virtual systems.
Hallak-Stamler et al Expires April 2003 [Page 7]
SCSI MIB October 2002
For example, in a host, it allows multiple vendors' implementations
of the MIB to co-exist under a single SNMP agent through each
vendor's implementation being a different SCSI instance. It also
allows a single SNMP agent to represent multiple subsystems each of
which have their own SCSI instance.
3.3 SCSI MIB implementations
The SCSI MIB is a basic building block to use in the various SCSI
management scenarios. The SCSI MIB is intended to be implemented in
every SCSI entity in a managed system. A SCSI entity can be a SCSI
Initiator device, SCSI Target device or SCSI Initiator and Target
device. Since SCSI (storage) networking devices may contain more
than one SCSI entity, it is possible that more than one SCSI
instance will reside in a single device.
In small-scale environments a single NMS may have SNMP access to
both initiators and targets. However if the SCSI targets, or
virtualized targets, are being provided as a service, it is more
likely that the provider of the service owns and manages the
targets, and that the consumer of the service owns and manages the
initiators. In this case, the service provider NMS and the consumer
NMS may have only allowed SNMP access to the targets and the
initiators respectively.
The figures in this chapter describe the location of the SCSI MIB
implementations in the various SCSI management scenarios. The
locations of the SCSI SNMP agent implementing the SCSI MIB, are
denoted with '*.
+----------+ +---------+
|SCSI | SCSI Transport |SCSI |
|Initiator +---------------------------------------+Target |
|Device | |Device |
| * | | * |
+----------+ +---------+
| |
| |
| |
| |
| |
| SNMP +----------+ SNMP |
+------------------|SCSI |-------------------+
|Management|
| (NMS) |
+----------+
Figure 1: Single SCSI Initiator device and Single SCSI Target device
Hallak-Stamler et al Expires April 2003 [Page 8]
SCSI MIB October 2002
Figure 1 describes a simple SCSI management scenario of a SCSI
Initiator device, a SCSI Target device and a Management station. In
this scenario there are two SNMP agents, each containing its SCSI
instance and its respective objects. As the SCSI Target and SCSI
Initiator device are interconnected, their Target and Initiator port
objects will be complementary.
+-----------+
| +--------+-+ SCSI Transport +---------+
| | SCSI |---------------------------------------+ SCSI |
|* | Initiator+---------------------------------------+ Target |
+--| Device | SCSI Transport | Device |
| | * | | * |
| +----------+ +---------+
| | |
| | |
| | |
| | |
| | |
|SNMP | SNMP +----------+ SNMP |
+-------+------------------|SCSI |-------------------+
|Management|
| (NMS) |
+----------+
Figure 2: Multiple Hosts and a Single Target device
Figure 2 adds another SCSI Initiator device, to the SCSI network,
which connects to the same SCSI target device.The additional
Initiator also has an SNMP agent implementing the SCSI MIB. In this
case, the SCSI Target device's MIB will show that two SCSI Initiator
devices are attached to it.
+-----------+ +-----------+
| +----------+ +---------------+ +-+-------+ |
| |SCSI |--------------| Virtualization| | SCSI | |
|* |Initiator +--------------| Device +-------+ Target | |
+--|Device | SCSI | | | Device | * |
| | * | | * | | * |---+
| +----------+ Transport +------------+--+ +---------+ |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | SNMP +-----------+ | SNMP | |
+-------+------------------+ SCSI + +-+------------+-------+
| Management|
| (NMS) |
+-----------+
Hallak-Stamler et al Expires April 2003 [Page 9]
SCSI MIB October 2002
Figure 3: Multiple Hosts, Virtualization device and multiple Targets
Figure 3 adds an in-band virtualization device which encapsulates,
and possibly modifies, the SCSI Target devices representation to the
SCSI Initiator devices. It is common practice for an in-band
virtualization device, to include both SCSI Target and Initiator
device functionality. Therefore, its SCSI MIB implementation
includes both the SCSI Target and Initiator device objects. It
should be noted that the Virtualization device may implement
additional proprietary MIB's, as the SCSI MIB does not distinguish
between physical and virtual SCSI entities.
3.4 Bridging and Virtualization
Storage virtualization is a concept that abstracts storage resources
in such a way that, storage entities are provided as pool of logical
entities.
Usually the virtualization process is transparent to the storage
users (i.e. Hosts). Virtualization normally affects the SCSI
entities represented to SCSI Initiators. However, the SCSI MIB
enables the representation of SCSI entities and their respective
status, including error and performance-monitoring statistics. It
should be possible to perform a limited number of configuration
modification and diagnostic actions.
The SCSI entities embodied in the bridging and virtualization
devices can be represented by the SCSI MIB. However, Bridging and
Virtualization devices configuration is beyond the above-described
scope and therefore should be provided through other MIBs.
3.5 SCSI Commands MIB
The management of SCSI commands is beyond the scope of this MIB.
Future SCSI Command MIB can link to this MIB, through the use of
OIDs or INDEX values of appropriate tables.
4. Structure of the MIB
This MIB contains fourteen conformance groups:
4.1 The SCSI Device Group
The scsiDeviceGroup group contains the objects general to each SCSI
instance: instance, device and port objects. It contains also the
objects referring to the transport(s) used by those SCSI instances.
This group is mandatory for all SCSI managed system.
Hallak-Stamler et al Expires April 2003 [Page 10]
SCSI MIB October 2002
4.2 The Initiator Group
The scsiInitiatorGroup contains all the managed information related
to a local initiator device and port. In addition, it contains the
managed objects referring to the monitored attached targets. Any
managed system acting, as an initiator or target/initiator port must
support this group.
4.3 The Target Group
The scsiTargetGroup contains all the managed objects related to a
local target device, a local target port, monitored attached
initiator ports, logical units and logical unit identifiers.
Managed systems acting, as a target or target/initiator device and
port must support this group.
4.4 The Discovery Group
The scsiDiscoveryGroup group is a collection of managed objects
referring to remote target devices, remote target ports, remote
logical units and remote logical unit identifiers discovered by or
configured to a managed system acting as an initiator device.
Managed systems acting as an initiator device and port and
supporting remote target devices or ports configuration or discovery
should implement this group.
4.5 The LUN Map Group
The scsiLunMapGroup group is a collection of managed objects
allowing mapping between target devices, logical units and logical
unit numbers in one side to remote authorized initiator devices or
ports in another side.
Managed systems supporting this mapping should implement the
scsiLunMapGroup.
4.6 The Target Statistic Group
The scsiTargetStatsGroup group is a collection of managed objects
representing various statistics referring to a target device or
port.
Managed systems acting as a target device and port supporting
statistics should implement this group.
4.7 The Target High Speed Statistic Group
The scsiTargetHSStatsGroup group is a collection of managed objects
representing various statistics referring to a target device or
port. It provides support for systems, which can quickly generate
countable information because they run at high speed.
Managed systems acting, as a target device and port and running at
high speed supporting should implement this group.
Hallak-Stamler et al Expires April 2003 [Page 11]
SCSI MIB October 2002
4.8 The LUN Map Statistics Group
The scsiLunMapStatsGroup group is a collection of managed objects
representing various statistics referring to remote authorized
initiator devices or ports.
Managed systems acting as a target device and port and able to
gather statistics on remote initiator devices or ports should
implement this group.
4.9 The LUN Map Statistics High Speed Group
The scsiLunMapHSStatsGroup group is a collection of managed objects
representing various statistics referring to remote authorized
initiator devices or ports. It provides support for systems, which
can quickly generate countable information because they run at high
speed.
Managed systems acting, as a target device and port, able to gather
statistics on remote initiator devices or ports and running at high
speed should implement this group.
4.10 The Initiator Statistic Group
The scsiInitiatorStatsGroup group is a collection of managed objects
representing various statistics referring to a initiator device or
port.
Managed systems acting as a initiator device and port supporting
statistics should implement this group.
4.11 The Initiator High Speed Statistic Group
The scsiInitiatorHSStatsGroup group is a collection of managed
objects representing various statistics referring to an initiator
device or port. It provides support for systems, which can quickly
generate countable information because they run at high speed.
Managed systems acting, as an initiator device and port and running
at high speed supporting should implement this group.
4.12 The Discovery Statistics Group
The scsiDiscoveryStatsGroup group is a collection of managed objects
representing various statistics referring to remote discovered or
configured target devices or ports.
Managed systems acting as an initiator device and port and able to
gather statistics on remote target devices or ports should implement
this group.
4.13 The Discovery Statistics High Speed Group
The scsiDiscoveryHSStatsGroup group is a collection of managed
objects representing various statistics referring to remote
discovered or configured target devices or ports. It provides
Hallak-Stamler et al Expires April 2003 [Page 12]
SCSI MIB October 2002
support for systems, which can quickly generate countable
information because they run at high speed.
Managed systems acting, as an initiator device and port, able to
gather statistics on remote target devices or ports and running at
high speed should implement this group.
4.14 The Device Statistics Group
The scsiDeviceStatGroup group is a collection of managed objects
representing various statistics referring to a SCSI device.
Managed systems able to gather device statistics should implement
this group.
5. Relationships in this MIB
This chapter outlines the functionality and the depenency between
the SNMP tables providing the required management functionality for
SCSI initiator and target devices. For specific usage of these
tables, the reader should refer to the description of the tables and
their respective table entries and attributes.
Following is a list of required SCSI initiator related features, and
the respective tables facilitating this functionality:
- List all the SCSI initiator ports, which should be managed through
this MIB. The table SCSI Initiator Port maintains all the SCSI
initiator ports for the SCSI initiator devices in the MIB.
- Provide a list of all SCSI target ports or SCSI target devices to
which a SCSI initiator port can attach. This should prevent a SCSI
initiator device or port to attach to SCSI target devices, which
should be either invisible or inaccessible to it. The entries in
this list can be either created manually or by automatic discovery
mechanisms (e.g. SLP, iSNS).
The ScsiDscTgtTable provides this information. The entries in this
table point to SCSI initiator port, and indicate that the SCSI
initiator port can only attach to SCSI target ports or SCSI target
devices provided in the respective entries of the ScsiDscTgtTable.
- The information, for the aforementioned SCSI target ports or SCSI
target devices, about the LUNs and their respective LUN Ids should
be provided.
The scsiDscLunTable and scsiDscLunIdTable maintain this information.
- The scsiAttTgtPortTable provides the information related to
monitoring all the currently exiting connections from a SCSI
initiator port to the SCSI target ports or SCSI target devices. This
table should be dynamically updated to reflect those connections.
Following is a list of required SCSI target related features, and
the respective tables facilitating this functionality:
Hallak-Stamler et al Expires April 2003 [Page 13]
SCSI MIB October 2002
- List all the SCSI target ports, which should be managed through
this MIB.
The table SCSITargetsPort maintains all the SCSI target ports for
the SCSI target devices in the MIB.
-Provide a list of valid SCSI initiator ports or SCSI initiator
devices authorized to attach to a SCSI target port. This list should
feature the concept of æaccess listsÆ, which are common in IP
routers and switches. The ScsiAuthorizedIntr table provide this
information.
- It should be possible to specify the list of LUNs exposed to each
SCSI initiator port or device, when it attached to the SCSI target.
SCSI target devices must be provide a default list of LUNÆs. This
list of LUNÆs can be either a unique list for each SCSI initiator
device, or be the default list.
For each entry in the ScsiAuthorizedIntr table a pointer, named
scsiAuthIntrLunMapIndex, indexing the ScsiLunMapTable facilitates
this feature.
- Provide means to monitor all the SCSI initiator devices currently
attached to this SCSI target. The scsiAttIntrPrtTable provides this
information. This table should be dynamically updated to reflect
those connections.
6. Relationship to Other MIBs
6.1 Host Resource MIB
The SCSI MIB extends objects defined in the host resource MIB to
SCSI specific entities but does not contain information on software
modules such as device drivers. If MIB objects are required for
installed packages of SCSI software, then the hrSWInstalledGroup of
the host resource MIB (RFC 2790 [18]) are the standard MIB objects
to use.
6.2 iSCSI MIB
The SCSI MIB defines managed objects for SCSI protocol layer. The
SCSI layer can run on the top of several transport layers; iSCSI is
one of them. The iSCSI MIB [25] is the MIB portion defining the
managed objects for the transport called iSCSI. In the same way, a
fibre channel or parallel SCSI MIB would define managed objects for
a transport called respectively fibre channel or parallel SCSI.
The relationship between the SCSI MIB and any valid transport MIB is
determined via the SCSI port managed table that has an object
pointing to the corresponding row, if any, of the relevant table in
a transport MIB.
7. Miscellaneous Details
Hallak-Stamler et al Expires April 2003 [Page 14]
SCSI MIB October 2002
7.1 Names and Identifiers
The names and the identifiers of the SCSI devices, ports and logical
units depend on the underlying transport protocols; their format and
length vary accordingly. Please refer to [17] in order to get more
details.
7.2 Logical Unit Number
The logical unit number is a 64-bit integer. This type does not
exist in SMI and therefore, this MIB contains a textual convention
defining LUN as an OCTET STRING.
7.3 State of logical units
The state of a logical unit determines whether the data is protected
or not. It is often referred as protected entity. Protected entities
are entities that are able to tolerate one or more entity failing
without any loss of data or loss of data availability.
For more information on the logical unit states see the SCSI
Controller Commands-2 (SCC-2) standard (NCITS.318-1998)
7.4 Notifications
Separate SNMP notifications may be enabled/disabled to notify of a
change in any of the SCSI device status variables. A notification
will be generated theoretically for each occurrence (see restriction
below) of the abnormal status (e.g., if the SCSI device's current
status is abnormal and another logical unit changes its status to
from available another notification will occur).
To avoid sending an excessive number of notifications due to
multiple errors counted, an SNMP agent implementing the SCSI MIB
should not send more than three SCSI notifications in any 10-second
period.
The 3-in-10 rule was chosen because one notification every three
seconds was deemed often enough, but if and when two or three
different notifications happen at the same time, it would not be
desirable to suppress them. Three notifications in ten seconds is a
happy medium, where a short burst of notifications is allowed,
without inundating the network and/or destination host with a large
number of notifications.
7.5 SCSI Domains
SAM-2 specifies that devices belong to a domain. However, it is not
usually possible to determine this from within a system, so domains
are not represented within this MIB.
7.6 Counters: 32 bits and 64 bits
Hallak-Stamler et al Expires April 2003 [Page 15]
SCSI MIB October 2002
Some counters, in (newer) high-performance systems, can increase at
a fast enough rate such that their representation as Counter32's,
can cause them to "wrap" in less than an hour. The SMIv2 provides
Counter64 as the syntax for such counters. However, (older) SNMPv1
implementations cannot support Counter64's. Thus, this MIB defines
such counters as both Counter32's and Counter64's.
The counters in this MIB which count data, are defined in terms of
megabytes (i.e., as the number of megabytes of data), such that
Counter64's are not required.
However, the counters in this MIB, which count commands, when in use
at 10GBit/second with 512 read/write operations, could wrap within
an hour. Therefore, each of these counters will be defined as both
a Counter32 and a Counter64, with the latter being conditionally
mandatory, depending on the system speed.
7.7 Local versus Remote Entities
This MIB qualifies often SCSI entities as local or remote. The local
entities are the ones for which the agent is reporting. The remote
entities are the ones, which the local entities are in communication
with via the SCSI protocol.
8. Abbreviations
This MIB will use the following abbreviations:
Inst = Instance
Dev = Device
Tgt = Target
Intr = Initiator
Att = Attached
Id = Identifier
Prt = Port
Trnspt = Transport
Dsc = Discovered
9. Object Definitions
SCSI-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, Integer32, Unsigned32, Counter32,
Counter64, Gauge32,
mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TimeStamp, TruthValue,
RowStatus, RowPointer, AutonomousType FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF
SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
Hallak-Stamler et al Expires April 2003 [Page 16]
SCSI MIB October 2002
scsiModule MODULE-IDENTITY
LAST-UPDATED "200202250000Z" -- 25 February 2002
ORGANIZATION "IETF"
CONTACT-INFO "
Michele Hallak-Stamler
Sanrad Intelligent Network
32 Habarzel Street
Tel Aviv, Israel
Phone: +972 3 7674809
E-mail: michele@sanrad.com
Yaron Lederman
Siliquent Technologies Ltd.
33 Bezalel Street
Ramat Gan, Israel
Phone: +972 3 7552320
E-mail: yaronl@siliquent.com
Mark Bakke
Postal: Cisco Systems, Inc
6450 Wedgwood Road, Suite 130
Maple Grove, MN
USA 55311
Phone: +1 763-398-1000
Fax: +1 763-398-1001
E-mail: mbakke@cisco.com
Marjorie Krueger
Postal: Hewlett-Packard
Networked Storage Architecture
Networked Storage Solutions Org.
8000 Foothills Blvd.
Roseville, CA 95747
Phone: +1 916-785-2656
Phone: +1 916-785-0391
E-mail: marjorie_krueger@hp.com
Keith McCloghrie
Cisco Systems, Inc.
Postal: 170 West Tasman Drive
San Jose, CA USA 95134
Phone: +1 408 526-5260
E-mail: kzm@cisco.com
"
DESCRIPTION
"The SCSI MIB"
-- Revision History
Hallak-Stamler et al Expires April 2003 [Page 17]
SCSI MIB October 2002
REVISION "200202250000Z"
DESCRIPTION " Initial version published as RFC nnnn."
::= { mib-2 xxx} -- must be changed in the future
--******************** Textual Conventions *************************
ScsiLUNOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" This Textual Convention represents either a SCSI Logical
Unit Number (LUN) or a zero-length string. Objects defined
with this syntax must specify the meaning of the zero-length
string. The format of a LUN is:
- a zero-length octet string or
- a string of two octets if the underlying transport protocol
is SBP-3 or SPI-4 using data group transfers or
- a string of eight octets for all other cases."
SYNTAX OCTET STRING (SIZE (0 | 2 | 8))
ScsiIndexValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" An arbitrary integer value, greater than zero, for use as a
unique index value."
SYNTAX Unsigned32(1..4294967295)
ScsiPortIndexValueOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the
ScsiIndexValue convention. The latter defines a greater than
zero value used to identify an index. This extension permits
the additional value of zero and is applicable only to
indices of SCSI port. Usage of the zero is object-specific
and must therefore be defined as part of the description of
any object, which uses this syntax. Examples of the usage of
zero might include situations where index was unknown, or
when none or all indices need to be referenced."
SYNTAX Unsigned32(0..4294967295)
ScsiIndexValueOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention is an extension of the
ScsiIndexValue convention. The latter defines a greater than
zero value used to identify an index. This extension permits
the additional value of zero. Usage of the zero is object-
specific and must therefore be defined as part of the
description of any object, which uses this syntax. Examples
of the usage of zero might include situations where index was
unknown, or when none or all indices need to be referenced."
SYNTAX Unsigned32(0..4294967295)
Hallak-Stamler et al Expires April 2003 [Page 18]
SCSI MIB October 2002
ScsiIdentifier ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This Textual Convention represents a generic SCSI device or
port identifier.
The format depends on the transport used:
- SPI: only bits:0-3 for a port identifier (LSB is 0 and MSB
is 3). Other bits must be zero.
- SPI: identifier of a device is a zero-length octet string.
- FCP: 3 bytes for a port identifier
- FCP: identifier of a device is a zero-length octet string.
- SRP: 16 bytes for a port identifier.
- SRP: it is a zero-length octet string for a device
identifier.
- iSCSI: 256 bytes for a device identifier.
- iSCSI: 258 bytes for a target port identifier.
- iSCSI: 262 bytes for an initiator port identifier.
- SBP: it is a zero-length octet string for a device
identifier.
- SBP: 2 bytes for an initiator port identifier.
- SBP: 11 bytes for a target port identifier. "
REFERENCE
" T10 - Names, Addresses, Identifiers, Oh my! - George
Penokie - 01-084r6."
SYNTAX OCTET STRING (SIZE (0..262))
ScsiName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
" This Textual Convention represents a generic SCSI device or
port name.
The format depends on the transport used:
- SPI: it is a zero-length octet string for a device or port
name.
- FCP: 8 bytes for a port name.
- FCP: it is a zero-length octet string for a device name.
- SRP: 16 bytes for a port name.
- SRP: it is a zero-length octet string for a device name.
- iSCSI: 256 bytes for a device name.
- iSCSI: 258 bytes for a target port name.
- iSCSI: 262 bytes for an initiator port name.
- SBP: it is a zero-length octet string for a device name.
- SBP: 8 bytes for an initiator port name.
- SBP: 11 bytes for a target port name. "
REFERENCE
" T10 - Names, Addresses, Identifiers, Oh my! - George
Penokie - 01-084r6."
SYNTAX OCTET STRING (SIZE (0..262))
ScsiNameIdOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 19]
SCSI MIB October 2002
" This Textual Convention represents either the SCSI name of
a logical unit or a zero-length string. Objects defined with
this syntax must specify the meaning of the zero-length
string. The format of the name of a LU is:
- a zero-length octet string or
- a string of eight octets."
SYNTAX OCTET STRING (SIZE (0 | 8))
ScsiDeviceOrPort ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This type specifies whether a particular configuration is
applicable to a port or to a device."
SYNTAX INTEGER {
device(1),
port(2),
other(3)
}
ScsiIdCodeSet ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This Textual Convention specifies the code set for the
identifier contained in an Identification Descriptor returned
in a Logical Unit's Device Identification Page, and is
formatted as defined in T10 SPC-2 (see REFERENCE) table 177 -
Code Set"
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20, 18
July 2001 Chapter 8: section 8.4.4, page 210 Vital Product
Data Parameters [16]"
SYNTAX Unsigned32(0..15)
ScsiIdAssociation ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This Textual Convention specifies what the identifier is
associated with (e.g, with the addressed physical/logical
device or with a particular port) for the identifier contained
in an Identification Descriptor returned in a Logical Unit's
Device Identification Page, and is formatted as defined in T10
SPC-2 (see REFERENCE) table 178 û Association."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20, 18
July 2001 - Chapter 8: section 8.4.4, page 210 Vital Product
Data Parameters [16]"
SYNTAX Unsigned32(0..3)
ScsiIdType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This Textual Convention specifies the type for the
identifier contained in an Identification Descriptor returned
Hallak-Stamler et al Expires April 2003 [Page 20]
SCSI MIB October 2002
in a Logical Unit's Device Identification Page, and is
formatted as defined in T10 SPC-2 (see REFERENCE) table 179 û
Identifier Type."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20,
Chapter 8: section 8.4.4, page 210 Vital Product Data
Parameters [16]"
SYNTAX Unsigned32(0..15)
ScsiIdValue ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This Textual Convention represents an identifier. The
objects of type ScsiIdCodeSet, ScsIdAssociation, ScsiIdType,
define together the format.
The format is the same as contained in an Identification
Descriptor returned in a Logical Unit's Device Identification
Page, and is formatted as defined in T10 SPC-2 (see REFERENCE)
tables 180-188."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20, 18
July 2001 - Chapter 8: section 8.4.4, page 210 Vital Product
Data Parameters [16]"
SYNTAX OCTET STRING (SIZE (0..255))
HrSWInstalledIndexOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The index value for a software module's row in the Host
Resources MIB's hrSWInstalledTable. A zero value indicates
that no row in the hrSWInstalledTable is applicable."
REFERENCE
"hrSWInstalledTable is defined in the Host Resources MIB, RFC
2790."
SYNTAX Integer32 (0..2147483647)
--****************** Structure of the MIB *************************
scsiObjects OBJECT IDENTIFIER ::= { scsiModule 1 }
scsiNotifications OBJECT IDENTIFIER ::= { scsiModule 2 }
scsiConformance OBJECT IDENTIFIER ::= { scsiModule 3 }
scsiTransportTypes OBJECT IDENTIFIER ::= { scsiObjects 1 }
scsiGeneral OBJECT IDENTIFIER ::= { scsiObjects 2 }
scsiInitiator OBJECT IDENTIFIER ::= { scsiObjects 3 }
scsiTarget OBJECT IDENTIFIER ::= { scsiObjects 4 }
scsiLogicalUnit OBJECT IDENTIFIER ::= { scsiObjects 5 }
--****************** Transport Types *******************************
-- The following object identifiers allow determining the different
-- transports (service delivery subsystems) in use under the SCSI
-- layer.
Hallak-Stamler et al Expires April 2003 [Page 21]
SCSI MIB October 2002
scsiTransportOther OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies a transport that has no identity;
it might happen because the transport is unknown or might not
have been defined when this MIB was created."
::= { scsiTransportTypes 1 }
scsiTransportSPI OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies a parallel SCSI transport."
REFERENCE
" T10 - SCSI Parallel Interface - 4 (SPI-4) - #1365-D
Rev [10]"
::= { scsiTransportTypes 2 }
scsiTransportFCP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies a Fibre Channel Protocol for SCSI,
Second Version."
REFERENCE
" T10 - SCSI Fibre Channel Protocol - 2 (FCP-2)- #1144-D
Rev [07a]."
::= { scsiTransportTypes 3 }
scsiTransportSRP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies a protocol for transporting SCSI
over RDMA interfaces, e.g., InfiniBand (tm)."
REFERENCE
"T10 - SCSI RDMA Protocol (SRP) - #1415-D Rev [16]."
::= { scsiTransportTypes 4 }
scsiTransportISCSI OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies an ISCSI transport."
REFERENCE
"IETF IPS Working Group û draft-ietf-ips-iscsi-14.txt"
::= { scsiTransportTypes 5 }
scsiTransportSBP OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identity identifies the Serial Bus Protocol 3 (SBP-3)."
REFERENCE
"T10 - Serial Bus Protocol 3 (SBP-3)- #1467-D Rev [02a]."
::= { scsiTransportTypes 6 }
Hallak-Stamler et al Expires April 2003 [Page 22]
SCSI MIB October 2002
--****************** Instance Table *******************************
scsiInstanceTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiInstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of SCSI instances present on the system.
The SCSI Instance is the top-level entity, to which
everything else belongs. An SNMP agent could represent more
than one instance if it represents either a stack of devices,
or virtual partitions of a larger device, or a host running
multiple SCSI implementations from different vendors."
::= { scsiGeneral 1 }
scsiInstanceEntry OBJECT-TYPE
SYNTAX ScsiInstanceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing management information applicable
to a particular SCSI instance."
INDEX { scsiInstIndex }
::= { scsiInstanceTable 1 }
ScsiInstanceEntry::= SEQUENCE {
scsiInstIndex ScsiIndexValue,
scsiInstAlias SnmpAdminString,
scsiInstSoftwareIndex HrSWInstalledIndexOrZero,
scsiInstVendorVersion SnmpAdminString,
scsiInstScsiNotificationsEnable TruthValue
}
scsiInstIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object represents an arbitrary integer used to uniquely
identify a particular SCSI instance."
::= { scsiInstanceEntry 1 }
scsiInstAlias OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..79))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object represents an administrative string, configured
by the administrator. It can be a zero-length string."
::= { scsiInstanceEntry 2 }
scsiInstSoftwareIndex OBJECT-TYPE
SYNTAX HrSWInstalledIndexOrZero
MAX-ACCESS read-only
Hallak-Stamler et al Expires April 2003 [Page 23]
SCSI MIB October 2002
STATUS current
DESCRIPTION
"If this management instance corresponds to an installed
software module, then this object's value is the value of the
hrSWInstalledIndex of that module. If there is no
correspondence to an installed software module (or no module
which has a hrSWInstalledIndex value), then the value of this
object is zero."
REFERENCE
"hrSWInstalledIndex is defined in the Host Resources MIB, RFC
2790."
::= { scsiInstanceEntry 3 }
scsiInstVendorVersion OBJECT-TYPE
SYNTAX SnmpAdminString(SIZE(0..79))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents a text string set by the manufacturer
describing the version of this instance. The format of this
string is determined solely by the manufacturer, and is for
informational purposes only. It is unrelated to the SCSI
specification version numbers."
::= { scsiInstanceEntry 4 }
scsiInstScsiNotificationsEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object allows to enable/disable sending all the
notifications defined in this MIB."
DEFVAL { true }
::= { scsiInstanceEntry 5 }
--******************** Device Table *******************************
scsiDeviceTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiDeviceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of SCSI Devices contained in each instance this agent
is reporting."
::= { scsiGeneral 2 }
scsiDeviceEntry OBJECT-TYPE
SYNTAX ScsiDeviceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 24]
SCSI MIB October 2002
"An entry (row) containing management information applicable
to a particular SCSI Device included in this SCSI manageable
instance."
INDEX { scsiInstIndex, scsiDeviceIndex }
::= { scsiDeviceTable 1 }
ScsiDeviceEntry::= SEQUENCE {
scsiDeviceIndex ScsiIndexValue,
scsiDeviceAlias SnmpAdminString,
scsiDeviceRole BITS,
scsiDevicePortNumber Unsigned32,
scsiDeviceResets Counter32
}
scsiDeviceIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This object is an arbitrary integer used to uniquely
identify a particular device within a particular SCSI
instance."
::= { scsiDeviceEntry 1 }
scsiDeviceAlias OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..79))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object represents is an admistrative name for this
device. If no name is assigned, the value of this object is
the zero-length string."
::= { scsiDeviceEntry 2 }
scsiDeviceRole OBJECT-TYPE
SYNTAX BITS {
target(0),
initiator(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object determines whether this device is acting as an
initiator device, or as a target device or as both."
::= { scsiDeviceEntry 3 }
scsiDevicePortNumber OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of ports contained in this
device."
Hallak-Stamler et al Expires April 2003 [Page 25]
SCSI MIB October 2002
::= { scsiDeviceEntry 4 }
scsiDeviceResets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of times that this device
has reset."
::= { scsiDeviceEntry 5 }
--****************** Port Table ***********************************
scsiPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of SCSI Ports for each SCSI device in each instance."
::= { scsiGeneral 3 }
scsiPortEntry OBJECT-TYPE
SYNTAX ScsiPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing management information applicable
to a particular SCSI port of a particular SCSI device in a
particular SCSI instance."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex }
::= { scsiPortTable 1 }
ScsiPortEntry ::= SEQUENCE {
scsiPortIndex ScsiIndexValue,
scsiPortRole BITS,
scsiPortTrnsptPtr RowPointer,
scsiPortBusyStatuses Counter32
}
scsiPortIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer used to uniquely identify a particular
port of a given device within a particular SCSI instance."
::= { scsiPortEntry 1 }
scsiPortRole OBJECT-TYPE
SYNTAX BITS {
target(0),
initiator(1)
}
Hallak-Stamler et al Expires April 2003 [Page 26]
SCSI MIB October 2002
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether this port is acting as an
initiator port, or as a target port or as both."
::= { scsiPortEntry 2 }
scsiPortTrnsptPtr OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is a pointer to the corresponding row in the
scsiTrnsptTable. This row contains information on the transport
like transport type and port name."
::= { scsiPortEntry 3 }
scsiPortBusyStatuses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of port busy status sent
or received by this port. Note: Initiator ports only receive
busy status and target ports only send busy status."
::= { scsiPortEntry 4 }
--******************** Table of supported transports ***************
scsiTrnsptTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiTrnsptEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the device transport-specific information
for each transport connected to each device in
scsiDeviceTable."
::= { scsiGeneral 5 }
scsiTrnsptEntry OBJECT-TYPE
SYNTAX ScsiTrnsptEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing parameters applicable to a
transport used by a particular device of a particular SCSI
manageable instance."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiTrnsptIndex}
::= { scsiTrnsptTable 1 }
ScsiTrnsptEntry ::= SEQUENCE {
scsiTrnsptIndex ScsiIndexValue,
scsiTrnsptType AutonomousType,
Hallak-Stamler et al Expires April 2003 [Page 27]
SCSI MIB October 2002
scsiTrnsptPointer RowPointer,
scsiTrnsptDevName ScsiName
}
scsiTrnsptIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer used to uniquely identify a particular
transport within a given device within a particular SCSI
instance."
::= { scsiTrnsptEntry 1 }
scsiTrnsptType OBJECT-TYPE
SYNTAX AutonomousType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the transport type of this row of the
transport table. For example, if this object has the value
scsiTransportFCP, then the identified transport is FCP."
::= { scsiTrnsptEntry 2 }
scsiTrnsptPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents a pointer to a conceptual row in a
'transport' MIB allowing a manager to get useful information
for the transport described by this entry.
For example, if the transport of this device is iSCSI, this
object will point to the iSCSI Instance of the iSCSI MIB.
If there is no MIB for this transport, this object has the
value 0.0."
::= { scsiTrnsptEntry 3 }
scsiTrnsptDevName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the name of this device in one of
the format(s) appropriate for this type of transport."
::= { scsiTrnsptEntry 4 }
--******************** Initiator Device Table ******************
scsiIntrDevTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiIntrDevEntry
MAX-ACCESS not-accessible
STATUS current
Hallak-Stamler et al Expires April 2003 [Page 28]
SCSI MIB October 2002
DESCRIPTION
"This table contains information for each local initiator
device in each instance."
::= { scsiInitiator 1}
scsiIntrDevEntry OBJECT-TYPE
SYNTAX ScsiIntrDevEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing information applicable to an
initiator device within a particular SCSI instance."
INDEX { scsiInstIndex, scsiDeviceIndex }
::= { scsiIntrDevTable 1 }
ScsiIntrDevEntry ::= SEQUENCE {
scsiIntrDevTgtAccessMode INTEGER,
scsiIntrDevOutResets Counter32
}
scsiIntrDevTgtAccessMode OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
autoEnable(2),
manualEnable(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls whether a discovered target is
immediately authorized or not:
- autoEnable (2) means that when an initiator discovers a
target, it can use it immediately,
- manualEnable (3) means that the initiator must wait for an
operator to set scsiIntrDscTgtConfigured = true before it is
authorized."
::= { scsiIntrDevEntry 1 }
scsiIntrDevOutResets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the number of resets sent by this
initiator."
::= { scsiIntrDevEntry 2 }
-- The following section describes managed objects related to
-- initiator ports.
scsiIntrPrtTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiIntrPrtEntry
MAX-ACCESS not-accessible
Hallak-Stamler et al Expires April 2003 [Page 29]
SCSI MIB October 2002
STATUS current
DESCRIPTION
"This table contains all the initiator ports for each local
SCSI Initiator or Target/Initiator devices in each SCSI
instance."
::= { scsiInitiator 3 }
scsiIntrPrtEntry OBJECT-TYPE
SYNTAX ScsiIntrPrtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing information applicable to a
particular initiator port of a particular device within a
SCSI instance. "
INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex }
::= { scsiIntrPrtTable 1 }
ScsiIntrPrtEntry ::= SEQUENCE {
scsiIntrPrtName ScsiName,
scsiIntrPrtIdentifier ScsiIdentifier,
scsiIntrPrtOutCommands Counter32,
scsiIntrPrtWrittenMegaBytes Counter32,
scsiIntrPrtReadMegaBytes Counter32,
scsiIntrPrtHSOutCommands Counter64
}
scsiIntrPrtName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the name of the port assigned for
use by the SCSI protocol. The format will depend on the type
of transport this port is using."
::= { scsiIntrPrtEntry 1 }
scsiIntrPrtIdentifier OBJECT-TYPE
SYNTAX ScsiIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the identifier of the port in one of
the format(s) appropriate for the type of transport in use."
::= { scsiIntrPrtEntry 2 }
scsiIntrPrtOutCommands OBJECT-TYPE
SYNTAX Counter32
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 30]
SCSI MIB October 2002
"This object represents the number of commands sent by this
initiator port."
::= { scsiIntrPrtEntry 3 }
scsiIntrPrtWrittenMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the amount of data in Megabytes sent
by this initiator port."
::= { scsiIntrPrtEntry 4 }
scsiIntrPrtReadMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the amount of data in Megabytes
received by this initiator port."
::= { scsiIntrPrtEntry 5 }
scsiIntrPrtHSOutCommands OBJECT-TYPE
SYNTAX Counter64
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of commands sent by this
initiator device. This object provides support for systems
which can quickly generate lots of commands because they run
at high speed port."
::= { scsiIntrPrtEntry 6 }
--******************** Discovered Target group ******************
scsiRemoteTarget OBJECT IDENTIFIER ::= { scsiInitiator 4 }
-- Targets discovered or authorized to attach each of the initiator
-- ports of each initiator device of each instance.
scsiDscTgtTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiDscTgtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the remote (not in the local system)
target ports that are authorized to attach to each local
initiator port of this SCSI instance."
::= { scsiRemoteTarget 1 }
Hallak-Stamler et al Expires April 2003 [Page 31]
SCSI MIB October 2002
scsiDscTgtEntry OBJECT-TYPE
SYNTAX ScsiDscTgtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry (row) contains information about the target
device or port to which this initiator port (or all initiator
ports in the initiator entry indexed by scsiInstIndex,
scsiDeviceIndex) will attempt to attach. The entry is either
for all local ports (if scsiDscTgtIntrPortIndex is zero), or
only for the specific initiator port identified by
scsiDscTgtIntrPortIndex. Note that if an entry in this table
is deleted, any corresponding entries in the scsiDscLunsTable
must be deleted as well."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex,
scsiDscTgtIndex }
::= { scsiDscTgtTable 1 }
ScsiDscTgtEntry ::= SEQUENCE {
scsiDscTgtIntrPortIndex ScsiPortIndexValueOrZero,
scsiDscTgtIndex ScsiIndexValue,
scsiDscTgtDevOrPort ScsiDeviceOrPort,
scsiDscTgtName ScsiName,
scsiDscTgtConfigured TruthValue,
scsiDscTgtDiscovered TruthValue,
scsiDscTgtInCommands Counter32,
scsiDscTgtWrittenMegaBytes Counter32,
scsiDscTgtReadMegaBytes Counter32,
scsiDscTgtHSInCommands Counter64,
scsiDscTgtLastCreation TimeStamp,
scsiDscTgtRowStatus RowStatus
}
scsiDscTgtIntrPortIndex OBJECT-TYPE
SYNTAX ScsiPortIndexValueOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object relates to a particular local device within a
particular SCSI instance and specifies:
- the index of the local scsi initiator port,
- or zero, if this entry refers to the local device and
therefore refers to all the local initiator ports."
::= { scsiDscTgtEntry 1 }
scsiDscTgtIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary integer used to uniquely
identify a particular authorized target amongst those
Hallak-Stamler et al Expires April 2003 [Page 32]
SCSI MIB October 2002
authorized for one or more ports (of a particular device
within a particular SCSI instance) to attach to."
::= { scsiDscTgtEntry 2 }
scsiDscTgtDevOrPort OBJECT-TYPE
SYNTAX ScsiDeviceOrPort
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates whether this entry describes a
configured target device name (and applies to all ports on
the identified target) or an individual target port."
::= { scsiDscTgtEntry 3 }
scsiDscTgtName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object represents the name of this authorized or
discovered target device or port depending on the value of
scsiDscTgtDevOrPort."
::= { scsiDscTgtEntry 4 }
scsiDscTgtConfigured OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object means:
-true(1): this entry has been configured by an administrator
-false(2): this entry has been added from a discovery
mechanism (eg. SendTargets, SLP, iSNS).
An administrator can modify this value from false to true."
DEFVAL { true }
::= { scsiDscTgtEntry 5 }
scsiDscTgtDiscovered OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object means:
-true(1): this entry has been discovered by the SCSI instance
as result of an automatic discovery process.
-false(2): this entry has been added by manual configuration.
This entry is read-only because an administrator cannot
change it.
Note that it is an implementation decision to determine how
long to retain a row with configured=false, as and when the
target is no longer visible/accessible to the local
initiator."
Hallak-Stamler et al Expires April 2003 [Page 33]
SCSI MIB October 2002
::= { scsiDscTgtEntry 6 }
scsiDscTgtInCommands OBJECT-TYPE
SYNTAX Counter32
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of commands received by
this target port or device."
::= { scsiDscTgtEntry 7 }
scsiDscTgtWrittenMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the amount of megabytes of data sent
as the result of WRITE commands to this target port or
device."
::= { scsiDscTgtEntry 8 }
scsiDscTgtReadMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the amount of megabytes received as
the result of READ commands to this target port or device."
::= { scsiDscTgtEntry 9 }
scsiDscTgtHSInCommands OBJECT-TYPE
SYNTAX Counter64
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of commands received by
this target port or device. This object provides support for
systems which can quickly generate lots of commands because
they run at high speed."
::= { scsiDscTgtEntry 10 }
scsiDscTgtLastCreation OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the value of sysUpTime when this row
was created."
::= { scsiDscTgtEntry 11 }
Hallak-Stamler et al Expires April 2003 [Page 34]
SCSI MIB October 2002
scsiDscTgtRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows an administrator to configure dynamically
a new entry in this table via SNMP or eventually delete it.
An administrator is not allowed to delete an entry for which
the value of the object scsiIntrDscTgtDiscovered is equal to
true.
Note that when an entry in this table is deleted, then any
corresponding entries in the scsiDscLunsTable must also be
automatically deleted. "
::= { scsiDscTgtEntry 12 }
--********************** LUNs discovered **************************
scsiDscLunTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiDscLunEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the remote (not in the local system)
logical unit numbers (LUNS) discovered via each local
initiator port of each local device within a particular SCSI
instance."
::= { scsiRemoteTarget 2 }
scsiDscLunEntry OBJECT-TYPE
SYNTAX ScsiDscLunEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) represents a discovered LUN at a particular
SCSI target device (scsiDscTgtIndex), where the LUN was
discovered by a particular local initiator device within a
particular SCSI instance, possibly via a particular local
initiator port.
Note that when an entry in the scsiDscTgtTable is deleted,
then any corresponding entries in this table is automatically
deleted."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex,
scsiDscTgtIndex, scsiDscLunIndex }
::= { scsiDscLunTable 1 }
ScsiDscLunEntry ::= SEQUENCE {
scsiDscLunIndex ScsiIndexValue,
scsiDscLunLun ScsiLUNOrZero
}
scsiDscLunIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
Hallak-Stamler et al Expires April 2003 [Page 35]
SCSI MIB October 2002
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary integer used to uniquely
identify a particular LUN discovered by a particular scsi
initiator port or a particular SCSI initiator device within a
particular SCSI instance. Entries in the scsiDscLunIdTable
are associated with a LUN by having the value of this object
in their INDEX."
::= { scsiDscLunEntry 1 }
scsiDscLunLun OBJECT-TYPE
SYNTAX ScsiLUNOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the Logical Unit Number (LUN) of the
discovered logical unit.
A value of zero has no meaning in this case."
::= { scsiDscLunEntry 2 }
--******************** LU Identifiers discovered ******************
scsiDscLunIdTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiDscLunIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the known LU Identifiers of the
remote (not in the local system) logical units discovered via
each local initiator port or device of this SCSI instance."
::= { scsiRemoteTarget 3 }
scsiDscLunIdEntry OBJECT-TYPE
SYNTAX ScsiDscLunIdEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) represents the LU Identifier of a discovered
LUN at a particular SCSI target device (scsiDscTgtIndex),
where the LUN was discovered by a particular local initiator
device within a particular SCSI instance, possibly via a
particular local initiator port."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiDscTgtIntrPortIndex,
scsiDscTgtIndex, scsiDscLunIndex, scsiDscLunIdIndex }
::= { scsiDscLunIdTable 1 }
ScsiDscLunIdEntry ::= SEQUENCE {
scsiDscLunIdIndex ScsiIndexValue,
scsiDscLunIdCodeSet ScsiIdCodeSet,
scsiDscLunIdAssociation ScsiIdAssociation,
scsiDscLunIdType ScsiIdType,
scsiDscLunIdValue ScsiIdValue
Hallak-Stamler et al Expires April 2003 [Page 36]
SCSI MIB October 2002
}
scsiDscLunIdIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary integer used to uniquely
identify a particular LUN Identifier discovered by each scsi
initiator device or particular SCSI initiator port within a
particular SCSI instance."
::= { scsiDscLunIdEntry 1 }
scsiDscLunIdCodeSet OBJECT-TYPE
SYNTAX ScsiIdCodeSet
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the code set in use with this
identifier.
The value is represented in the same format as is contained
in the identifier's Identification Descriptor within the
Logical Unit's Device Identification Page."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2),Revision 20,
Chapter 8: section 8.4.4, page 210 Vital Product Data
Parameters [16]"
::= { scsiDscLunIdEntry 2 }
scsiDscLunIdAssociation OBJECT-TYPE
SYNTAX ScsiIdAssociation
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies what the identifier is associated with
(e.g, with the addressed physical/logical device or with a
particular port). The value is represented in the same
format as is contained in the identifier's Identification
Descriptor within the Logical Unit's Device Identification
Page."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20,
Chapter 8: section 8.4.4, page 210 Vital Product Data
Parameters [16]"
::= { scsiDscLunIdEntry 3 }
scsiDscLunIdType OBJECT-TYPE
SYNTAX ScsiIdType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the type of the identifier.
Hallak-Stamler et al Expires April 2003 [Page 37]
SCSI MIB October 2002
The value is represented in the same format as is contained
in the identifier's Identification Descriptor within the
Logical Unit's Device Identification Page."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), Revision 20,
Chapter 8: section 8.4.4, page 210 Vital Product Data
Parameters [16]"
::= { scsiDscLunIdEntry 4 }
scsiDscLunIdValue OBJECT-TYPE
SYNTAX ScsiIdValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the actual value of this identifier.
The format is defined by the objects scsiDscLunIdCodeSet,
scsiDscLunIdAssociation, scsiDscLunIdType.
The value is represented in the same format as is contained
in the identifier's Identification Descriptor within the
Logical Unit's Device Identification Page."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2),
Chapter 8: section 8.4.4, page 210 Vital Product Data
Parameters [16]"
::= { scsiDscLunIdEntry 5 }
--******* Table of Targets Attached to local Initiator Ports *******
scsiAttTgtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiAttTgtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the remote (not in the local system)
target ports that are currently attached to each local
initiator port of this SCSI instance."
::= { scsiRemoteTarget 6 }
scsiAttTgtPortEntry OBJECT-TYPE
SYNTAX ScsiAttTgtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) represents a remote target port
(scsiAttTgtPortIndex) currently attached to a particular
initiator port (scsiPortIndex) of a particular SCSI initiator
device within a particular SCSI instance."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex,
scsiAttTgtPortIndex }
::= { scsiAttTgtPortTable 1 }
ScsiAttTgtPortEntry ::= SEQUENCE {
scsiAttTgtPortIndex ScsiIndexValue,
Hallak-Stamler et al Expires April 2003 [Page 38]
SCSI MIB October 2002
scsiAttTgtPortDscTgtIdx ScsiIndexValueOrZero,
scsiAttTgtPortName ScsiName,
scsiAttTgtPortIdentifier ScsiIdentifier
}
scsiAttTgtPortIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer used to uniquely identify a particular
target currently attached to a particular SCSI initiator port
of a particular SCSI initiator device within a particular
SCSI instance."
::= { scsiAttTgtPortEntry 1 }
scsiAttTgtPortDscTgtIdx OBJECT-TYPE
SYNTAX ScsiIndexValueOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains the value of the scsiAttTgtPortIndex
index variable for the row in the scsiDscTgtTable
representing this currently attached target port. If the
currently attached target port is not represented in the
scsiDscTgtTable, then the value of this object is zero."
::= { scsiAttTgtPortEntry 2 }
scsiAttTgtPortName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object contains the name of the attached target port."
::= { scsiAttTgtPortEntry 3 }
scsiAttTgtPortIdentifier OBJECT-TYPE
SYNTAX ScsiIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object contains the identifier of the attached target
port."
::= { scsiAttTgtPortEntry 4 }
-- Management Objects regarding target type of scsi devices
--
scsiTgtDevTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiTgtDevEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 39]
SCSI MIB October 2002
"This table contains information about each local target
device."
::= { scsiTarget 1 }
scsiTgtDevEntry OBJECT-TYPE
SYNTAX ScsiTgtDevEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) containing information applicable to a
particular local target device within a particular SCSI
instance. "
INDEX { scsiInstIndex, scsiDeviceIndex }
::= { scsiTgtDevTable 1 }
ScsiTgtDevEntry ::= SEQUENCE {
scsiTgtDevNumberOfLUs Gauge32,
scsiTgtDeviceStatus INTEGER,
scsiTgtDevNonAccessibleLUs Gauge32
}
scsiTgtDevNumberOfLUs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the number of Logical Units accessible via
this local target device."
::= { scsiTgtDevEntry 1 }
scsiTgtDeviceStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
available(2),
broken(3),
readying(4),
abnormal(5),
nonAddrFailure(6),
nonAddrFailReadying(7),
nonAddrFailAbnormal(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the status of this SCSI device,
summarizing the state of both the addressable devices (i.e.,
the logical units) and the non-addressable devices within
this SCSI device:
- unknown(1): This value is used when the status cannot be
determined
- available(2): All addressable and non-addressable devices
within the SCSI device are fully operational (i.e., no
logical units have an abnormal status).
Hallak-Stamler et al Expires April 2003 [Page 40]
SCSI MIB October 2002
- broken(3): The SCSI device is not operational and cannot be
made operational without external intervention.
- readying(4): One or more logical units within the SCSI
device are being initialized and access to the SCSI device is
temporarily limited (i.e., one or more of the logical unit
have a readying status).
- abnormal(5): One or more addressable devices within the
SCSI device are indicating a status other than available;
nevertheless, the SCSI device is operational (i.e., one or
more of the logical units have an abnormal status).
- nonAddrFailure(6): One or more non-addressable devices
within the SCSI device have failed; nevertheless, the SCSI
device is operational (i.e., no logical units have an
abnormal or readying status).
- nonAddrFailReadying(7): One or more non-addressable devices
within the SCSI device have failed; nevertheless,one or more
logical units within the SCSI device are being initialized
and access to the SCSI device is temporarily limited.
- nonAddrFailAbnormal(8): One or more non-addressable devices
within the SCSI device have failed and one or more
addressable devices within the SCSI device are indicating a
status other than available however the SCSI device is
operational.
"
REFERENCE
"SCSI Controller Commands-2 (SCC-2) standard NCITS.318-1998
6.3.1.8 REPORT STATES service action"
::= { scsiTgtDevEntry 2}
scsiTgtDevNonAccessibleLUs OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the number of Logical Units existing but not
currently accessible via this local target device."
::= { scsiTgtDevEntry 3 }
--******************** Target Port Table ***************************
scsiTgtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiTgtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the local target ports of all the
local target devices."
::= { scsiTarget 2 }
scsiTgtPortEntry OBJECT-TYPE
SYNTAX ScsiTgtPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 41]
SCSI MIB October 2002
"An entry (row) containing information applicable to a
particular local target port of a particular local target
device within a particular SCSI instance. "
INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex}
::= { scsiTgtPortTable 1 }
ScsiTgtPortEntry ::= SEQUENCE {
scsiTgtPortName ScsiName,
scsiTgtPortIdentifier ScsiIdentifier,
scsiTgtPortInCommands Counter32,
scsiTgtPortWrittenMegaBytes Counter32,
scsiTgtPortReadMegaBytes Counter32,
scsiTgtPortHSInCommands Counter64
}
scsiTgtPortName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the name of the port assigned for
use in the SCSI protocol."
::= { scsiTgtPortEntry 1 }
scsiTgtPortIdentifier OBJECT-TYPE
SYNTAX ScsiIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the identifier of the port in one of
the format(s) appropriate for the type of transport."
::= { scsiTgtPortEntry 2 }
scsiTgtPortInCommands OBJECT-TYPE
SYNTAX Counter32
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the number of commands received by
this target port."
::= { scsiTgtPortEntry 3 }
scsiTgtPortWrittenMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the amount of data written in
Megabytes by this target port."
::= { scsiTgtPortEntry 4 }
Hallak-Stamler et al Expires April 2003 [Page 42]
SCSI MIB October 2002
scsiTgtPortReadMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the amount of data read in Megabytes
by this target port."
::= { scsiTgtPortEntry 5 }
scsiTgtPortHSInCommands OBJECT-TYPE
SYNTAX Counter64
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the number of commands received.
This object provides support for systems that can quickly
generate lots of commands because they run at high speed."
::= { scsiTgtPortEntry 6 }
scsiRemoteInitiators OBJECT IDENTIFIER ::= { scsiTarget 3 }
-- The scsiAuthorizedIntrTable contains the list of remote initiator
-- ports that are authorized to be attached specific target ports
-- and on which, an administrator would like to keep permanent
-- information and long term statistics even when not currently
-- attached.
scsiAuthorizedIntrTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiAuthorizedIntrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table includes all the authorized initiator devices or
ports that may attach a target device or port of the local
SCSI instance. Statistics are kept for each such
authorization; thus, the authorizations should be configured
in the manner, which will cause the desired set of statistics
to be collected and that will determine the correct LUN map."
::= { scsiRemoteInitiators 1 }
scsiAuthorizedIntrEntry OBJECT-TYPE
SYNTAX ScsiAuthorizedIntrEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) represents a remote initiator port or remote
initiator device that may attach to the local target port or
device within a particular SCSI instance."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiAuthIntrTgtPortIndex,
scsiAuthIntrIndex }
Hallak-Stamler et al Expires April 2003 [Page 43]
SCSI MIB October 2002
::= { scsiAuthorizedIntrTable 1 }
ScsiAuthorizedIntrEntry ::= SEQUENCE {
scsiAuthIntrTgtPortIndex ScsiPortIndexValueOrZero,
scsiAuthIntrIndex ScsiIndexValue,
scsiAuthIntrDevOrPort ScsiDeviceOrPort,
scsiAuthIntrName ScsiName,
scsiAuthIntrLunMapIndex ScsiIndexValueOrZero,
scsiAuthIntrAttachedTimes Counter32,
scsiAuthIntrOutCommands Counter32,
scsiAuthIntrReadMegaBytes Counter32,
scsiAuthIntrWrittenMegaBytes Counter32,
scsiAuthIntrHSOutCommands Counter64,
scsiAuthIntrLastCreation TimeStamp,
scsiAuthIntrRowStatus RowStatus
}
scsiAuthIntrTgtPortIndex OBJECT-TYPE
SYNTAX ScsiPortIndexValueOrZero
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object contains either the index of the port, or zero
to indicate any port, on the particular local target device."
::= { scsiAuthorizedIntrEntry 1 }
scsiAuthIntrIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object is an arbitrary integer used to uniquely
identify a SCSI initiator which is authorized to attach to a
particular local target device or port of a particular SCSI
instance."
::= { scsiAuthorizedIntrEntry 2 }
scsiAuthIntrDevOrPort OBJECT-TYPE
SYNTAX ScsiDeviceOrPort
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies if this entry refers to a remote
initiator port or a device.
A value of device(1) means that the authorized remote
initiator is a device and includes all its ports.
A value of port(2) means that the authorized remote initiator
is a port."
::= { scsiAuthorizedIntrEntry 3 }
scsiAuthIntrName OBJECT-TYPE
SYNTAX ScsiName
Hallak-Stamler et al Expires April 2003 [Page 44]
SCSI MIB October 2002
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object represents the name of the remote initiator
device or port authorized by this row."
::= { scsiAuthorizedIntrEntry 4 }
scsiAuthIntrLunMapIndex OBJECT-TYPE
SYNTAX ScsiIndexValueOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object identifies the set of entries in the
scsiLunMapTable for which scsiLunMapIndex has the same value
as the value of this object. The identified set of entries
constitute the LUN map to be used for accessing logical units
when the remote initiator port or device corresponding to
this entry is attached to any local target port or device
corresponding to this entry.
Note that this object has a value of zero if this entry
should use the default LUN map."
::= { scsiAuthorizedIntrEntry 5 }
scsiAuthIntrAttachedTimes OBJECT-TYPE
SYNTAX Counter32
UNITS "Times"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the number of times that this remote
initiator has transitioned from unattached to attached to
this local target device or port."
::= { scsiAuthorizedIntrEntry 6 }
scsiAuthIntrOutCommands OBJECT-TYPE
SYNTAX Counter32
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the number of commands that the remote
initiator corresponding to this entry has sent to the local
target device or port corresponding to this entry."
::= { scsiAuthorizedIntrEntry 7 }
scsiAuthIntrReadMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the amount of data in Megabytes that
the remote initiator corresponding to this entry has read
Hallak-Stamler et al Expires April 2003 [Page 45]
SCSI MIB October 2002
from the local target device or port corresponding to this
entry."
::= { scsiAuthorizedIntrEntry 8 }
scsiAuthIntrWrittenMegaBytes OBJECT-TYPE
SYNTAX Counter32
UNITS "Megabytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the amount of data in Megabytes that
the remote initiator corresponding to this entry has written
from the local target device or port corresponding to this
entry."
::= { scsiAuthorizedIntrEntry 9}
scsiAuthIntrHSOutCommands OBJECT-TYPE
SYNTAX Counter64
UNITS "commands"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents the number of commands sent by the
remote initiator corresponding to this entry to the local
target device or port corresponding to this entry. This
object provides support for systems which can quickly
generate lots of commands because they run at high speed."
::= { scsiAuthorizedIntrEntry 10 }
scsiAuthIntrLastCreation OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the value of sysUpTime when this row
was last created."
::= { scsiAuthorizedIntrEntry 11 }
scsiAuthIntrRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object allows an administrator to create or delete this
entry."
::= { scsiAuthorizedIntrEntry 12 }
--****** Table of Initiators Attached to local Target Ports ********
scsiAttIntrPrtTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiAttIntrPrtEntry
MAX-ACCESS not-accessible
STATUS current
Hallak-Stamler et al Expires April 2003 [Page 46]
SCSI MIB October 2002
DESCRIPTION
"This table includes all the remote initiator ports that are
currently attached to a local target port of all local
devices within all SCSI instances."
::= { scsiRemoteInitiators 2 }
scsiAttIntrPrtEntry OBJECT-TYPE
SYNTAX ScsiAttIntrPrtEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) represents a remote initiator currently
attached to a particular local target port of a particular
target device of a particular SCSI instance."
INDEX { scsiInstIndex, scsiDeviceIndex, scsiPortIndex,
scsiAttIntrPrtIdx }
::= { scsiAttIntrPrtTable 1 }
ScsiAttIntrPrtEntry ::= SEQUENCE {
scsiAttIntrPrtIdx ScsiIndexValue,
scsiAttIntrPrtAuthIntrIdx ScsiIndexValueOrZero,
scsiAttIntrPrtName ScsiName,
scsiAttIntrPrtId ScsiIdentifier
}
scsiAttIntrPrtIdx OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This object represents an arbitrary integer used to
uniquely identify a particular attached remote initiator port
to a particular target port within a particular SCSI target
device within a particular SCSI instance."
::= { scsiAttIntrPrtEntry 1 }
scsiAttIntrPrtAuthIntrIdx OBJECT-TYPE
SYNTAX ScsiIndexValueOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the corresponding index in the
scsiAuthorizedIntrTable for this current attached remote
initiator or zero if this remote attached initiator is not
configured in that table."
::= { scsiAttIntrPrtEntry 2 }
scsiAttIntrPrtName OBJECT-TYPE
SYNTAX ScsiName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
Hallak-Stamler et al Expires April 2003 [Page 47]
SCSI MIB October 2002
" This object represents the name of the remote initiator
attached to this local target port."
::= { scsiAttIntrPrtEntry 3 }
scsiAttIntrPrtId OBJECT-TYPE
SYNTAX ScsiIdentifier
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the identifier of the remote
initiator attached to this local target port."
::= { scsiAttIntrPrtEntry 4 }
--****************** Managed Objects regarding logical units *******
scsiLuTable OBJECT-TYPE
SYNTAX SEQUENCE OF ScsiLuEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This table contains all the logical units exposed by local
target devices.
It includes attributes for the WWN, scsiLuVendorId,
scsiLuProductId and scsiLuRevisionId. The WWN and the group
of scsiLuVendorId, scsiLuProductId, scsiLuRevisionId are
represented each in a block. The scsiLuIdTable may include
each of those two blocks according to the LUIdType. Not every
LU must have a those attributes (e.g. WWN), but each LU can
have only one single value for any of those attributes.
Therefore in the case that one or more entries in the
scsiLuIdTable provide either the WWN or the group of
scsiLuVendorId, scsiLuProductId, scsiLuRevisionId, the values
of those MUST be identical to those provided in the
scsiLUTable "
::= { scsiLogicalUnit 1 }
scsiLuEntry OBJECT-TYPE
SYNTAX ScsiLuEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (row) contains information applicable to a
particular logical unit of a particular local target device
within a particular SCSI instance. "
INDEX { scsiInstIndex, scsiDeviceIndex, scsiLuIndex}
::= { scsiLuTable 1 }
ScsiLuEntry ::= SEQUENCE {
scsiLuIndex ScsiIndexValue,
scsiLuDefaultLun ScsiLUNOrZero,
scsiLuWwnName ScsiNameIdOrZero,
scsiLuVendorId SnmpAdminString,
scsiLuProductId SnmpAdminString,
Hallak-Stamler et al Expires April 2003 [Page 48]
SCSI MIB October 2002
scsiLuRevisionId SnmpAdminString,
scsiLuPeripheralType Unsigned32,
scsiLuStatus INTEGER,
scsiLuState BITS,
scsiLuInCommands Counter32,
scsiLuReadMegaBytes Counter32,
scsiLuWrittenMegaBytes Counter32,
scsiLuInResets Counter32,
scsiLuOutQueueFullStatus Counter32,
scsiLuHSInCommands Counter64
}
scsiLuIndex OBJECT-TYPE
SYNTAX ScsiIndexValue
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
" This object represents an arbitrary integer used to
uniquely identify a particular logical unit within a
particular SCSI target device within a particular SCSI
instance."
::= { scsiLuEntry 1 }
scsiLuDefaultLun OBJECT-TYPE
SYNTAX ScsiLUNOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the default Logical Unit Number
(LUN) for this logical unit; it is the LUN that will appear
to an initiator that was not configured to see another LUN.
Note that this object will have a zero-length string if this
Logical Unit does not have a default LUN."
::= { scsiLuEntry 2 }
scsiLuWwnName OBJECT-TYPE
SYNTAX ScsiNameIdOrZero
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the World-Wide Name of this LU.
A value of zero means that there is no WWN for this LU."
::= { scsiLuEntry 3 }
scsiLuVendorId OBJECT-TYPE
SYNTAX SnmpAdminString(SIZE(0..79))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents a string identifying the vendor of
this LU according to the value in SCSI device page."
::= { scsiLuEntry 4 }
Hallak-Stamler et al Expires April 2003 [Page 49]
SCSI MIB October 2002
scsiLuProductId OBJECT-TYPE
SYNTAX SnmpAdminString(SIZE(0..79))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents a string identifying the product for
this LU according to the value in SCSI device page."
::= { scsiLuEntry 5 }
scsiLuRevisionId OBJECT-TYPE
SYNTAX SnmpAdminString(SIZE(0..79))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object represents a string defining the product
revision of this LU according to the value in SCSI device
page."
::= { scsiLuEntry 6 }
scsiLuPeripheralType OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object is the value returned to SCSI query VPD page 83.
It can be: direct-access device, sequential-access device,
printer, communication device and so on.
The values that can be returned here are defined in SCSI
Primary Commands -2."
REFERENCE
" ANSI - SCSI Primary Commands - 2 (SPC-2), T10 Project 1236-
D, Revision 20, 18 July 2001 [16]"
::= { scsiLuEntry 7 }
scsiLuStatus OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
available(2),
notAvailable(3),
broken(4),
readying(5),
abnormal(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
" This object represents the status of this logical unit:
- unknown(1): The status of this logical unit cannot be
determined.
- available(2): The logical unit is fully operational (i.e.,
accepts media access SCSI commands and has no state
information to report).
Hallak-Stamler et al Expires April 2003 [Page 50]
SCSI MIB October 2002
- notAvailable(3): The logical unit is capable of being
supported but not available (i.e., no logical unit is
currently present or the logical unit is present but not
configured for use).
- broken(4): The logical unit has failed and cannot respond
to SCSI commands.
- readying(5): The logical unit is being initialized and
access is temporarily limited.
- abnormal(6): The logical unit has state information
available that indicates it is operating with limits. The
scsiLuState indicates what those limits are.
"
REFERENCE
" SCSI Controller Commands-2 (SCC-2) standard NCITS.318-1998
6.3.1.8 REPORT STATES service action"
::= { scsiLuEntry 8 }
scsiLuState OBJECT-TYPE
SYNTAX BITS {
dataLost(0),
dynamicReconfigurationInProgress(1),
exposed(2),
fractionallyExposed(3),
partiallyExposed(4),
protectedRebuild(5),
protectionDisabled(6),
rebuild(7),