draft-ietf-ips-iscsi-mib-11.txt   rfc4544.txt 
Internet Draft Mark Bakke Network Working Group M. Bakke
<draft-ietf-ips-iscsi-mib-11.txt> Cisco Systems Request for Comments: 4544 Cisco Systems
Expires April 2006 Category: Standards Track M. Krueger
James Muchow Hewlett-Packard
Qlogic Corp. T. McSweeney
IBM
Marjorie Krueger J. Muchow
Hewlett-Packard Qlogic Corp.
May 2006
Tom McSweeney
IBM
October 2005
Definitions of Managed Objects for iSCSI
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
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 Definitions of Managed Objects
and may be updated, replaced, or obsoleted by other documents at any for Internet Small Computer System Interface (iSCSI)
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 Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.html.
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP-based internets.
In particular it defines objects for managing a client using the In particular, it defines objects for managing a client using the
iSCSI (SCSI over TCP) protocol. Internet Small Computer System Interface (iSCSI) protocol (SCSI over
TCP).
Table of Contents Table of Contents
1. Introduction........................................ 2 1. Introduction ....................................................3
2. Specification of Requirements....................... 3 2. Specification of Requirements ...................................3
3. The Internet-Standard Management Framework.......... 3 3. The Internet-Standard Management Framework ......................3
4. Relationship to Other MIB modules................... 3 4. Relationship to Other MIB Modules ...............................3
5. Relationship to SNMP Contexts....................... 4 5. Relationship to SNMP Contexts ...................................4
6. Discussion.......................................... 4 6. Discussion ......................................................4
6.1. iSCSI MIB Object Model.............................. 5 6.1. iSCSI MIB Object Model .....................................5
6.2. iSCSI MIB Table Structure........................... 6 6.2. iSCSI MIB Table Structure ..................................6
6.3. iscsiInstance....................................... 7 6.3. iscsiInstance ..............................................7
6.4. iscsiPortal......................................... 7 6.4. iscsiPortal ................................................7
6.5. iscsiTargetPortal................................... 8 6.5. iscsiTargetPortal ..........................................9
6.6. iscsiInitiatorPortal................................ 9 6.6. iscsiInitiatorPortal .......................................9
6.7. iscsiNode........................................... 10 6.7. iscsiNode .................................................10
6.8. iscsiTarget......................................... 10 6.8. iscsiTarget ...............................................10
6.9. iscsiTgtAuthorization............................... 10 6.9. iscsiTgtAuthorization .....................................11
6.10. iscsiInitiator...................................... 11 6.10. iscsiInitiator ...........................................11
6.11. iscsiIntrAuthorization.............................. 11 6.11. iscsiIntrAuthorization ...................................11
6.12. iscsiSession........................................ 11 6.12. iscsiSession .............................................11
6.13. iscsiConnection..................................... 12 6.13. iscsiConnection ..........................................12
6.14. IP Addresses and TCP Port Numbers................... 12 6.14. IP Addresses and TCP Port Numbers ........................12
6.15. Descriptors: Using OIDs in Place of Enumerated Types 12 6.15. Descriptors: Using OIDs in Place of Enumerated Types .....13
6.16. Notifications....................................... 13 6.16. Notifications ............................................13
7. MIB Definitions..................................... 14 7. MIB Definitions ................................................14
8. Security Considerations............................. 79 8. Security Considerations ........................................79
9. IANA Considerations................................. 80 9. IANA Considerations ............................................80
10. Normative References................................ 80 10. Normative References ..........................................80
11. Informative References.............................. 81 11. Informative References ........................................81
12. Acknowledgements.................................... 81 12. Acknowledgements ..............................................81
Authors' Addresses.................................. 81
IPR Notice.......................................... 82
Full Copyright Notice............................... 83
1. Introduction 1. Introduction
This document defines a MIB module for iSCSI [RFC3720], used to This document defines a MIB module for iSCSI [RFC3720], used to
manage devices which implement the iSCSI protocol. manage devices that implement the iSCSI protocol.
2. Specification of Requirements 2. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
skipping to change at page 3, line 26 skipping to change at page 3, line 31
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
4. Relationship to Other MIB modules 4. Relationship to Other MIB Modules
The iSCSI MIB module is normally layered between the SCSI MIB module The iSCSI MIB module is normally layered between the SCSI MIB module
[SCSIMIB] (work in progress) and the TCP MIB module [RFC2012], and [RFC4455] and the TCP MIB module [RFC4022], and makes use of the IP
makes use of the IPS Identity Authentication MIB module [AUTHMIB] Storage (IPS) Identity Authentication MIB module [RFC4545]. Here is
(work in progress). Here is how these modules are related: how these modules are related:
SCSI MIB Within systems where a SCSI layer is present, each SCSI MIB Within systems where a SCSI layer is present, each
iscsiNode, whether it has an initiator role, target role, iscsiNode, whether it has an initiator role, target role,
or both, is related to one SCSI device within the SCSI MIB or both, is related to one SCSI device within the SCSI MIB
module. In this case, the iscsiNodeTransportType attribute module. In this case, the iscsiNodeTransportType attribute
points to the SCSI transport object within the SCSI MIB points to the SCSI transport object within the SCSI MIB
module, which in turn contains an attribute that points module, which in turn contains an attribute that points
back to the iscsiNode. In this way, a management station back to the iscsiNode. In this way, a management station
can navigate between the two MIB modules. In systems where can navigate between the two MIB modules. In systems where
a SCSI layer is not present, such as within an iSCSI proxy a SCSI layer is not present, such as within an iSCSI proxy
skipping to change at page 4, line 17 skipping to change at page 4, line 23
points to an identity within the IPS Identity points to an identity within the IPS Identity
Authentication MIB module that will be allowed to access Authentication MIB module that will be allowed to access
the target. iSCSI nodes that serve in an initiator role the target. iSCSI nodes that serve in an initiator role
can also have a list of authorized targets. Each of the can also have a list of authorized targets. Each of the
entries in this list points to an identity within the Auth entries in this list points to an identity within the Auth
MIB module to which the initiator should attempt to MIB module to which the initiator should attempt to
establish sessions. The Auth MIB module includes establish sessions. The Auth MIB module includes
information used to identify initiators and targets by information used to identify initiators and targets by
their iSCSI name, IP address, and/or credentials. their iSCSI name, IP address, and/or credentials.
This MIB module imports objects from RFCs 2578 [RFC2578], This MIB module imports objects from RFCs 2578 [RFC2578], 2579
2579 [RFC2579], 2580 [RFC2580], and 3411 [RFC3411]. It [RFC2579], 2580 [RFC2580], and 3411 [RFC3411]. It also imports
also imports textual conventions from the INET-ADDRESS-MIB textual conventions from the INET-ADDRESS-MIB [RFC4001].
[RFC4001].
5. Relationship to SNMP Contexts 5. Relationship to SNMP Contexts
Each non-scalar object in the iSCSI MIB module is indexed first by an Each non-scalar object in the iSCSI MIB module is indexed first by an
iSCSI Instance. Each instance is a collection of nodes, portals, iSCSI Instance. Each instance is a collection of nodes, portals,
sessions, etc., that can define a physical or virtual partitioning of sessions, etc., that can define a physical or virtual partitioning of
an iSCSI-capable device. The use of an instance works well with an iSCSI-capable device. The use of an instance works well with
partitionable or hierarchical storage devices and fits in logically partitionable or hierarchical storage devices and fits in logically
with other management schemes. Instances do not replace SNMP with other management schemes. Instances do not replace SNMP
contexts, however they do provide a very simple way to assign a contexts, however they do provide a very simple way to assign a
virtual or physical partion of a device to one or more SNMP contexts, virtual or physical partition of a device to one or more SNMP
without having to do so for each individual node, portal, and session contexts, without having to do so for each individual node, portal,
row. and session row.
6. Discussion 6. Discussion
This MIB module structure supplies configuration, fault, and This MIB module structure supplies configuration, fault, and
statistics information for iSCSI devices [RFC3720]. It is structured statistics information for iSCSI devices [RFC3720]. It is structured
around the well-known iSCSI objects, such as targets, initiators, around the well-known iSCSI objects, such as targets, initiators,
sessions, connections, and the like. sessions, connections, and the like.
This MIB module may also be used to configure access to iSCSI This MIB module may also be used to configure access to iSCSI
targets, by creating iSCSI Portals and authorization list entries. targets, by creating iSCSI Portals and authorization list entries.
It is worthwhile to note that this is an iSCSI MIB module and as such It is worthwhile to note that this is an iSCSI MIB module and as such
reflects only iSCSI objects. This module does not contain information reflects only iSCSI objects. This module does not contain
about the SCSI-layer attributes of a device. If a SCSI layer is information about the SCSI-layer attributes of a device. If a SCSI
present, the SCSI MIB module, currently under development, may be layer is present, the SCSI MIB module, currently under development,
used to manage SCSI information for a device. may be used to manage SCSI information for a device.
The iSCSI MIB module consists of several "objects", each of which is The iSCSI MIB module consists of several "objects", each of which is
represented by one or more tables. This section contains a brief represented by one or more tables. This section contains a brief
description of the "object" hierarchy and a description of each description of the "object" hierarchy and a description of each
object, followed by a discussion of the actual table structure within object, followed by a discussion of the actual table structure within
the objects. the objects.
6.1. iSCSI MIB Object Model 6.1. iSCSI MIB Object Model
The top-level object in this structure is the iSCSI instance, which The top-level object in this structure is the iSCSI instance, which
skipping to change at page 5, line 45 skipping to change at page 5, line 51
-- Initiator-specific iSCSI node information. -- Initiator-specific iSCSI node information.
iscsiIntrAuth iscsiIntrAuth
-- A list of target identities to which this initiator -- A list of target identities to which this initiator
-- is configured to establish sessions. -- is configured to establish sessions.
iscsiSession iscsiSession
-- An active iSCSI session between an initiator and target. -- An active iSCSI session between an initiator and target.
-- The session's direction may be Inbound (outside -- The session's direction may be Inbound (outside
-- initiator to our target) or Outbound (our initiator to -- initiator to our target) or Outbound (our initiator to
-- an outside target). -- an outside target).
iscsiConnection iscsiConnection
-- An active TCP connection within an iSCSI session -- An active TCP connection within an iSCSI session.
An iSCSI Node can be an initiator, a target, or both. The iSCSI An iSCSI node can be an initiator, a target, or both. The iSCSI
Node's portals may be used to initiate connections (initiator) or node's portals may be used to initiate connections (initiator) or
listen for connections (target), depending on wither the iSCSI Node listen for connections (target), depending on whether the iSCSI node
is acting as an initiator or target. The iSCSI MIB module assumes is acting as an initiator or target. The iSCSI MIB module assumes
that any target may be accessed via any portal that can take on a that any target may be accessed via any portal that can take on a
target role, although other access controls not reflected in the target role, although other access controls not reflected in the
module might limit this. module might limit this.
6.2. iSCSI MIB Table Structure 6.2. iSCSI MIB Table Structure
Each iSCSI object exports one or more tables: an attributes table, Each iSCSI object exports one or more tables: an attributes table,
and zero or more statistics tables which augment the attributes and zero or more statistics tables, which augment the attributes
table. Since iSCSI is an evolving standard, it is much cleaner to table. Since iSCSI is an evolving standard, it is much cleaner to
provide statistics and attributes as separate tables, allowing provide statistics and attributes as separate tables, allowing
attributes and statistics to be added independently. In a few cases, attributes and statistics to be added independently. In a few cases,
there are multiple categories of statistics that will likely grow; in there are multiple categories of statistics that will likely grow; in
this case, an object will contain multiple statistics tables. this case, an object will contain multiple statistics tables.
iscsiObjects iscsiObjects
iscsiDescriptors iscsiDescriptors
iscsiInstance iscsiInstance
iscsiInstanceAttributesTable iscsiInstanceAttributesTable
skipping to change at page 7, line 28 skipping to change at page 7, line 34
this table's index as their primary index. this table's index as their primary index.
Most implementations will include just one iSCSI instance row in this Most implementations will include just one iSCSI instance row in this
table. However, this table exists to allow for multiple virtual table. However, this table exists to allow for multiple virtual
instances. For example, many IP routing products now allow multiple instances. For example, many IP routing products now allow multiple
virtual routers. The iSCSI MIB module has the same premise; a large virtual routers. The iSCSI MIB module has the same premise; a large
system could be "partitioned" into multiple, distinct virtual system could be "partitioned" into multiple, distinct virtual
systems. systems.
This also allows a single SNMP agent to proxy for multiple This also allows a single SNMP agent to proxy for multiple
subsystems, perhaps a set of stackable devices, each of which have subsystems, perhaps a set of stackable devices, each of which has one
one or even more instances. or even more instances.
The instance attributes include the iSCSI vendor and version, as well The instance attributes include the iSCSI vendor and version, as well
as information on the last target or initiator at the other end of a as information on the last target or initiator at the other end of a
session that caused a session failure. session that caused a session failure.
The iscsiInstanceSsnErrorStatsTable augments the attributes table, The iscsiInstanceSsnErrorStatsTable augments the attributes table and
and provides statistics on session failures due to digest, provides statistics on session failures due to digest, connection, or
connection, or iSCSI format errors. iSCSI format errors.
6.4. iscsiPortal 6.4. iscsiPortal
The iscsiPortalAttributesTable lists iSCSI portals that can either be The iscsiPortalAttributesTable lists iSCSI portals that can be used
used to listen for connections to targets, or initiate connections to to listen for connections to targets, to initiate connections to
other targets, or both. other targets, or to do both.
Each row in the table includes an IP address (either v4 or v6), and a Each row in the table includes an IP address (either v4 or v6), and a
transport protocol (currently only TCP is defined). Each portal may transport protocol (currently only TCP is defined). Each portal may
have additional attributes, depending on whether it is an initiator have additional attributes, depending on whether it is an initiator
portal, a target portal, or both. Initiator portals also have portal portal, a target portal, or both. Initiator portals also have portal
tags; these are placed in corresponding rows in the tags; these are placed in corresponding rows in the
iscsiIntrPortalAttributesTable. Target portals have both portal tags iscsiIntrPortalAttributesTable. Target portals have both portal tags
and ports (e.g. TCP listen ports if the transport protocol is TCP); and ports (e.g., TCP listen ports if the transport protocol is TCP);
these are placed in rows in the iscsiTgtPortalAttributesTable. these are placed in rows in the iscsiTgtPortalAttributesTable.
Portal rows, along with their initiator and target portal Portal rows, along with their initiator and target portal
counterparts, may be created and destroyed through this MIB module by counterparts, may be created and destroyed through this MIB module by
a management station. Rows in the initiator and target portal tables a management station. Rows in the initiator and target portal tables
are created and destroyed automatically by the agent, whenever a row are created and destroyed automatically by the agent, whenever a row
is created or destroyed in the iscsiPortalAttributesTable, or if the is created or destroyed in the iscsiPortalAttributesTable, or if the
value of iscsiPortalRoles changes. Attributes in these tables may value of iscsiPortalRoles changes. Attributes in these tables may
then be modified by the management station if the agent then be modified by the management station if the agent
implementation allows. implementation allows.
skipping to change at page 8, line 27 skipping to change at page 8, line 35
tables. Creating a row with the targetTypePortal bit set in tables. Creating a row with the targetTypePortal bit set in
iscsiPortalRoles will cause the implementation to start listening for iscsiPortalRoles will cause the implementation to start listening for
iSCSI connections on the portal. Creating a row with the iSCSI connections on the portal. Creating a row with the
initiatorTypePortal bit set in iscsiPortalRoles will not necessarily initiatorTypePortal bit set in iscsiPortalRoles will not necessarily
cause connections to be established; it is left to the implementation cause connections to be established; it is left to the implementation
whether and when to make use of the portal. Both bits may be set if whether and when to make use of the portal. Both bits may be set if
the portal is to be used by both initiator and target nodes. the portal is to be used by both initiator and target nodes.
When deleting a row in the iscsiPortalAttibutesTable, all connections When deleting a row in the iscsiPortalAttibutesTable, all connections
associated with that row are terminated. The implementation may associated with that row are terminated. The implementation may
either terminate the connection immediately, or request a clean either terminate the connection immediately or request a clean
shutdown as specified in [RFC3720]. An outbound connection (when an shutdown as specified in [RFC3720]. An outbound connection (when an
iscsiInitiatorPortal is deleted) matches the portal if its iscsiInitiatorPortal is deleted) matches the portal if its
iscsiCxnLocalAddr matches the iscsiPortalAddr. An inbound connection iscsiCxnLocalAddr matches the iscsiPortalAddr. An inbound connection
(when an iscsiTargetPortal is deleted) matches the portal if both its (when an iscsiTargetPortal is deleted) matches the portal if its
iscsiCxnLocalAddr matches the iscsiPortalAddr, and the iscsiCxnLocalAddr matches the iscsiPortalAddr, and its
iscsiCxnLocalPort matches the iscsiTargetPortalPort. iscsiCxnLocalPort matches the iscsiTargetPortalPort.
Individual objects within a row in this table may not be modified Individual objects within a row in this table may not be modified
while the row is active. For instance, changing the IP address of a while the row is active. For instance, changing the IP address of a
portal requires that the rows associated with the old IP address be portal requires that the rows associated with the old IP address be
deleted, and new rows be created (in either order). deleted, and new rows be created (in either order).
6.5. iscsiTargetPortal 6.5. iscsiTargetPortal
The iscsiTgtPortalAttributesTable contains target-specific attributes The iscsiTgtPortalAttributesTable contains target-specific attributes
for iSCSI Portals. Rows in this table use the same indices as their for iSCSI portals. Rows in this table use the same indices as their
corresponding rows in the iscsiPortalAttributesTable, with the corresponding rows in the iscsiPortalAttributesTable, with the
addition of iscsiNodeIndex. addition of iscsiNodeIndex.
Rows in this table are created when the targetTypePortal bit is set Rows in this table are created when the targetTypePortal bit is set
in the iscsiPortalRoles attribute of the corresponding in the iscsiPortalRoles attribute of the corresponding
iscsiPortalAttributesEntry; they are destroyed when this bit is iscsiPortalAttributesEntry; they are destroyed when this bit is
cleared. cleared.
This table contains the TCP (or other protocol) port on which the This table contains the TCP (or other protocol) port on which the
socket is listening for incoming connections. It also includes a socket is listening for incoming connections. It also includes a
skipping to change at page 9, line 27 skipping to change at page 9, line 39
iscsiNodeIndex of zero. iscsiNodeIndex of zero.
Other implementations do not use the same tag and/or port for all Other implementations do not use the same tag and/or port for all
nodes; these implementations will create a row in this table for each nodes; these implementations will create a row in this table for each
(portal, node) tuple, using iscsiNodeIndex to designate the node for (portal, node) tuple, using iscsiNodeIndex to designate the node for
this portal tag and port. this portal tag and port.
6.6. iscsiInitiatorPortal 6.6. iscsiInitiatorPortal
The iscsiIntrPortalAttributesTable contains initiator-specific The iscsiIntrPortalAttributesTable contains initiator-specific
objects for iSCSI Portals. Rows in this table use the same indices objects for iSCSI portals. Rows in this table use the same indices
as their corresponding entries in the iscsiPortalAttributesTable. A as their corresponding entries in the iscsiPortalAttributesTable. A
row in this table is created when the initiatorTypePortal bit is set row in this table is created when the initiatorTypePortal bit is set
in the iscsiPortalRoles attribute; it is destroyed when this bit is in the iscsiPortalRoles attribute; it is destroyed when this bit is
cleared. cleared.
Each row in this table contains a portal group aggregation tag, Each row in this table contains a portal group aggregation tag,
indicating which portals an initiator may use together within a indicating which portals an initiator may use together within a
multiple-connection session. multiple-connection session.
This table will be empty for iSCSI instances that contain only This table will be empty for iSCSI instances that contain only
skipping to change at page 10, line 10 skipping to change at page 10, line 20
Other implementations do not use the same tag and/or port for all Other implementations do not use the same tag and/or port for all
nodes; these implementations will create a row in this table for each nodes; these implementations will create a row in this table for each
(portal, node) tuple, using iscsiNodeIndex to designate the node for (portal, node) tuple, using iscsiNodeIndex to designate the node for
this portal tag and port. this portal tag and port.
6.7. iscsiNode 6.7. iscsiNode
The iscsiNodeAttributesTable contains a list of iSCSI nodes, each of The iscsiNodeAttributesTable contains a list of iSCSI nodes, each of
which may have an initiator role, a target role, or both. which may have an initiator role, a target role, or both.
This table contains the node's attributes which are common to both This table contains the node's attributes that are common to both
roles, such as its iSCSI Name and alias string. Attributes specific roles, such as its iSCSI name and alias string. Attributes specific
to initiators or targets are available in the iscsiTarget and to initiators or targets are available in the iscsiTarget and
iscsiInitiator objects. Each row in this table that can fulfill a iscsiInitiator objects. Each row in this table that can fulfill a
target role has a corresponding row in the iscsiTarget table; each target role has a corresponding row in the iscsiTarget table; each
entry that fulfills an initiator role has a row in the iscsiInitiator entry that fulfills an initiator role has a row in the iscsiInitiator
table. Nodes such as copy managers that can take on both roles have table. Nodes such as copy managers that can take on both roles have
a corresponding row in each table. a corresponding row in each table.
This table also contains the login negotiations preferences for this This table also contains the login negotiations preferences for this
node. These objects indicate the values this node will offer or node. These objects indicate the values this node will offer or
prefer in the operational negotiation phase of the login process. prefer in the operational negotiation phase of the login process.
For most implementations, each entry in the table also contains a For most implementations, each entry in the table also contains a
RowPointer to the transport table entry in the SCSI MIB module which RowPointer to the transport table entry in the SCSI MIB module that
this iSCSI node represents. For implementations without a standard this iSCSI node represents. For implementations without a standard
SCSI layer above iSCSI, such as an iSCSI proxy or gateway, this SCSI layer above iSCSI, such as an iSCSI proxy or gateway, this
RowPointer can point to a row in an implementation specific table RowPointer can point to a row in an implementation-specific table
that this iSCSI node represents. that this iSCSI node represents.
6.8. iscsiTarget 6.8. iscsiTarget
The iscsiTargetAttributesTable contains target-specific attributes The iscsiTargetAttributesTable contains target-specific attributes
for iSCSI nodes. Each entry in this table uses the same index values for iSCSI nodes. Each entry in this table uses the same index values
as its corresponding iscsiNode entry. as its corresponding iscsiNode entry.
This table contains attributes used to indicate the last failure that This table contains attributes used to indicate the last failure that
was (or should have been) sent as a notification. was (or should have been) sent as a notification.
skipping to change at page 11, line 42 skipping to change at page 12, line 6
The iscsiSessionAttributesTable contains a set of rows that list the The iscsiSessionAttributesTable contains a set of rows that list the
sessions known to be existing locally for each node in each iSCSI sessions known to be existing locally for each node in each iSCSI
instance. instance.
The session type for each session indicates whether the session is The session type for each session indicates whether the session is
used for normal SCSI commands or for discovery using the SendTargets used for normal SCSI commands or for discovery using the SendTargets
text command. Discovery sessions that do not belong to any text command. Discovery sessions that do not belong to any
particular node have a node index attribute of zero. particular node have a node index attribute of zero.
The session direction for each session indicates whether it is an The session direction for each session indicates whether it is an
Inbound Session or an Outbound Session. Inbound sessions are from Inbound session or an Outbound session. Inbound sessions are from
some other initiator to the target node under which the session some other initiator to the target node under which the session
appears. Outbound sessions are from the initiator node under which appears. Outbound sessions are from the initiator node under which
the session appears to a target outside this iSCSI instance. the session appears to a target outside this iSCSI instance.
Many attributes may be negotiated when starting an iSCSI session. Many attributes may be negotiated when starting an iSCSI session.
Most of these attributes are included in the session object. Most of these attributes are included in the session object.
Some attributes, such as the integrity and authentication schemes, Some attributes, such as the integrity and authentication schemes,
have some standard values which can be extended by vendors to include have some standard values that can be extended by vendors to include
their own schemes. These contain an object identifier, rather than their own schemes. These contain an object identifier, rather than
the expected enumerated type, to allow these values to be extended by the expected enumerated type, to allow these values to be extended by
other MIB modules, such as an enterprise MIB module. other MIB modules, such as an enterprise MIB module.
The iscsiSessionStatsTable includes statistics related to The iscsiSessionStatsTable includes statistics related to
performance; it counts iSCSI data bytes and PDUs. performance; it counts iSCSI data bytes and PDUs.
For implementations that support error recovery without terminating a For implementations that support error recovery without terminating a
session, the iscsiSessionCxnErrorStatsTable contains counters for the session, the iscsiSessionCxnErrorStatsTable contains counters for the
numbers of digest and connection errors that have occurred within the numbers of digest and connection errors that have occurred within the
session. session.
6.13. iscsiConnection 6.13. iscsiConnection
The iscsiConnectionAttributesTable contains a list of active The iscsiConnectionAttributesTable contains a list of active
connections within each session. It contains the IP addresses and connections within each session. It contains the IP addresses and
TCP (or other protocol) ports of both the local and remote side of TCP (or other protocol) ports of both the local and remote sides of
the connection. These may be used to locate other connection-related the connection. These may be used to locate other connection-related
information and statistics in the TCP MIB module [RFC2012]. information and statistics in the TCP MIB module [RFC4022].
The attributes table also contains a connection state. This state is The attributes table also contains a connection state. This state is
not meant to directly map to the state tables included within the not meant to directly map to the state tables included within the
iSCSI specification; they are meant to be simplified, higher-level iSCSI specification; they are meant to be simplified, higher-level
definitions of connection state that provide information more useful definitions of connection state that provide information more useful
to a user or network manager. to a user or network manager.
No statistics are kept for connections. No statistics are kept for connections.
6.14. IP Addresses and TCP Port Numbers 6.14. IP Addresses and TCP Port Numbers
The IP addresses in this module are represented by two attributes, The IP addresses in this module are represented by two attributes,
one of type InetAddressType, and the other of type InetAddress. one of type InetAddressType, and the other of type InetAddress.
These are taken from [RFC4001], which specifies how to support These are taken from [RFC4001], which specifies how to support
addresses that may be either IPv4 or IPv6. addresses that may be either IPv4 or IPv6.
The TCP port numbers that appear in a few of the structures are The TCP port numbers that appear in a few of the structures are
described as simply port numbers, with a protocol attribute described as simply port numbers, with a protocol attribute
indicating whether they are TCP ports, or something else. This will indicating whether they are TCP ports or something else. This will
allow the module to be compatible with iSCSI over transports other allow the module to be compatible with iSCSI over transports other
than TCP in the future. than TCP in the future.
6.15. Descriptors: Using OIDs in Place of Enumerated Types 6.15. Descriptors: Using OIDs in Place of Enumerated Types
The iSCSI MIB module has a few attributes, namely the digest method The iSCSI MIB module has a few attributes, namely, the digest method
attributes, where an enumerated type would work well, except that an attributes, where an enumerated type would work well, except that an
implementation may need to extend the attribute and add types of its implementation may need to extend the attribute and add types of its
own. To make this work, this MIB module defines a set of object own. To make this work, this MIB module defines a set of object
identities within the iscsiDescriptors subtree. Each of these object identities within the iscsiDescriptors subtree. Each of these object
identities is basically an enumerated type. identities is basically an enumerated type.
Attributes that make use of these object identities have a value Attributes that make use of these object identities have a value that
which is an OID instead of an enumerated type. These OIDs can either is an Object Identifier (OID) instead of an enumerated type. These
indicate the object identities defined in this module, or object OIDs can indicate either the object identities defined in this module
identities defined elsewhere, such as in an enterprise MIB module. or object identities defined elsewhere, such as in an enterprise MIB
Those implementations that add their own digest methods should also module. Those implementations that add their own digest methods
define a corresponding object identity for each of these methods should also define a corresponding object identity for each of these
within their own enterprise MIB module, and return its OID whenever methods within their own enterprise MIB module, and return its OID
one of these attributes is using that method. whenever one of these attributes is using that method.
6.16. Notifications 6.16. Notifications
Three notifications are provided. One is sent by an initiator Three notifications are provided. One is sent by an initiator
detecting a critical login failure; another is sent by a target detecting a critical login failure, another is sent by a target
detecting a critical login failure, and the third is sent upon a detecting a critical login failure, and the third is sent upon a
session being terminated due to an abnormal connection or digest session being terminated due to an abnormal connection or digest
failure. Critical failures are defined as those that may expose failure. Critical failures are defined as those that may expose
security-related problems that may require immediate action, such as security-related problems that may require immediate action, such as
failures due to authentication, authorization, or negotiation failures due to authentication, authorization, or negotiation
problems. Attributes in the initiator, target, and instance objects problems. Attributes in the initiator, target, and instance objects
provide the information necessary to send in the notification, such provide the information necessary to send in the notification, such
as the initiator or target name and IP address at the other end that as the initiator or target name and IP address at the other end that
may have caused the failure. may have caused the failure.
To avoid sending an excessive number of notifications due to multiple To avoid sending an excessive number of notifications due to multiple
errors counted, an SNMP agent implementing the iSCSI MIB module errors counted, an SNMP agent implementing the iSCSI MIB module
SHOULD NOT send more than three iSCSI notifications in any 10-second SHOULD NOT send more than three iSCSI notifications in any 10-second
period. period.
The 3-in-10 rule was chosen because one notification every three The 3-in-10 rule was chosen because one notification every three
seconds was deemed often enough, but should two or three different seconds was deemed often enough, but should two or three different
notifications happen at the same time, it would not be desirable to notifications happen at the same time, it would not be desirable to
suppress them. Three notifications in ten seconds is a happy medium, suppress them. Three notifications in 10 seconds is a happy medium,
where a short burst of notifications is allowed, without inundating where a short burst of notifications is allowed, without inundating
the network and/or notification host with a large number of the network and/or notification host with a large number of
notifications. notifications.
7. MIB Definitions 7. MIB Definitions
ISCSI-MIB DEFINITIONS ::= BEGIN ISCSI-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, NOTIFICATION-TYPE,
skipping to change at page 14, line 30 skipping to change at page 14, line 33
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
InetAddressType, InetAddress, InetPortNumber InetAddressType, InetAddress, InetPortNumber
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
; ;
iscsiMibModule MODULE-IDENTITY iscsiMibModule MODULE-IDENTITY
LAST-UPDATED "200510100000Z" -- October 10, 2005 LAST-UPDATED "200605220000Z" -- May 22, 2006
ORGANIZATION "IETF IPS Working Group" ORGANIZATION "IETF IPS Working Group"
CONTACT-INFO CONTACT-INFO
" "
Mark Bakke Mark Bakke
Postal: Cisco Systems, Inc Cisco Systems, Inc
7900 International Drive, Suite 400 7900 International Drive, Suite 400
Bloomington, MN Bloomington, MN
USA 55425 USA 55425
E-mail: mbakke@cisco.com E-mail: mbakke@cisco.com
Marjorie Krueger Marjorie Krueger
Postal: Hewlett-Packard Hewlett-Packard
Networked Storage Architecture Networked Storage Architecture
Networked Storage Solutions Org. Networked Storage Solutions Org.
8000 Foothills Blvd. 8000 Foothills Blvd.
Roseville, CA 95747 Roseville, CA 95747
E-mail: marjorie_krueger@hp.com E-mail: marjorie_krueger@hp.com
Tom McSweeney Tom McSweeney
Postal: IBM Corporation IBM Corporation
600 Park Offices Drive 600 Park Offices Drive
Research Triangle Park, NC Research Triangle Park, NC
USA 27709 USA 27709
E-mail: tommcs@us.ibm.com E-mail: tommcs@us.ibm.com
James Muchow James Muchow
Postal: Qlogic Corp. Qlogic Corp.
6321 Bury Dr. 6321 Bury Dr.
Eden Prairie, MN Eden Prairie, MN
USA 55346 USA 55346
E-Mail: james.muchow@qlogic.com" E-mail: james.muchow@qlogic.com"
DESCRIPTION DESCRIPTION
"The iSCSI Protocol MIB module. "The iSCSI Protocol MIB module.
Copyright (C) The Internet Society (2005). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC 4544; see the RFC itself for
full legal notices." full legal notices."
REVISION "200510100000Z" -- October 10, 2005 REVISION "200605220000Z" -- May 22, 2006
DESCRIPTION DESCRIPTION
"Initial version of the iSCSI Protocol MIB module" "Initial version of the iSCSI Protocol MIB module"
::= { mib-2 xx } -- xx to be assigned by IANA ::= { mib-2 142 }
iscsiNotifications OBJECT IDENTIFIER ::= { iscsiMibModule 0 } iscsiNotifications OBJECT IDENTIFIER ::= { iscsiMibModule 0 }
iscsiObjects OBJECT IDENTIFIER ::= { iscsiMibModule 1 } iscsiObjects OBJECT IDENTIFIER ::= { iscsiMibModule 1 }
iscsiConformance OBJECT IDENTIFIER ::= { iscsiMibModule 2 } iscsiConformance OBJECT IDENTIFIER ::= { iscsiMibModule 2 }
iscsiAdmin OBJECT IDENTIFIER ::= { iscsiMibModule 3 } iscsiAdmin OBJECT IDENTIFIER ::= { iscsiMibModule 3 }
-- Textual Conventions -- Textual Conventions
IscsiTransportProtocol ::= TEXTUAL-CONVENTION IscsiTransportProtocol ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
skipping to change at page 16, line 13 skipping to change at page 16, line 15
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
IscsiDigestMethod ::= TEXTUAL-CONVENTION IscsiDigestMethod ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type represents the methods possible "This data type represents the methods possible
for digest negotiation. for digest negotiation.
none - a placeholder for a secondary digest method none - a placeholder for a secondary digest method
that means only the primary method can be that means only the primary method can be
used. used.
other - a digest method other than those defined below; other - a digest method other than those defined below.
noDigest - does not support digests (will operate without noDigest - does not support digests (will operate without
a digest (NOTE: implementations must support a digest (Note: implementations must support
digests to be compliant with the RFC3720); digests to be compliant with the RFC3720).
CRC32c - require a CRC32C digest." CRC32c - require a CRC32C digest."
REFERENCE REFERENCE
"RFC 3720, Section 12.1, HeaderDigest and DataDigest" "RFC 3720, Section 12.1, HeaderDigest and DataDigest"
SYNTAX INTEGER { SYNTAX INTEGER {
none(1), none(1),
other(2), other(2),
noDigest(3), noDigest(3),
crc32c(4) crc32c(4)
} }
IscsiName ::= TEXTUAL-CONVENTION IscsiName ::= TEXTUAL-CONVENTION
DISPLAY-HINT "223t" DISPLAY-HINT "223t"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used for objects whose value is an "This data type is used for objects whose value is an
iSCSI Name with the properties described in RFC 3720 iSCSI name with the properties described in RFC 3720
section 3.2.6.1, and encoded as specified in RFC 3720 section 3.2.6.1, and encoded as specified in RFC 3720
section 3.2.6.2. A zero-length string indicates the section 3.2.6.2. A zero-length string indicates the
absense of an iSCSI name." absence of an iSCSI name."
REFERENCE REFERENCE
"RFC 3720, Section 3.2.6, iSCSI Names." "RFC 3720, Section 3.2.6, iSCSI Names."
SYNTAX OCTET STRING (SIZE(0 | 16..223)) SYNTAX OCTET STRING (SIZE(0 | 16..223))
--********************************************************************** --**********************************************************************
iscsiDescriptors OBJECT IDENTIFIER ::= { iscsiAdmin 1 } iscsiDescriptors OBJECT IDENTIFIER ::= { iscsiAdmin 1 }
iscsiHeaderIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 1 } iscsiHeaderIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 1 }
skipping to change at page 17, line 11 skipping to change at page 17, line 13
scheme (for either the header or data) is being scheme (for either the header or data) is being
used." used."
REFERENCE REFERENCE
"RFC 3720, Section 12.1, HeaderDigest and DataDigest" "RFC 3720, Section 12.1, HeaderDigest and DataDigest"
::= { iscsiHeaderIntegrityTypes 1 } ::= { iscsiHeaderIntegrityTypes 1 }
iscsiHdrIntegrityCrc32c OBJECT-IDENTITY iscsiHdrIntegrityCrc32c OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authoritative identifier when the integrity "The authoritative identifier when the integrity
scheme (for either the header or data) is CRC-32c." scheme (for either the header or data) is CRC32c."
REFERENCE REFERENCE
"RFC 3720, Section 12.1, HeaderDigest and DataDigest" "RFC 3720, Section 12.1, HeaderDigest and DataDigest"
::= { iscsiHeaderIntegrityTypes 2 } ::= { iscsiHeaderIntegrityTypes 2 }
iscsiDataIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 2 } iscsiDataIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 2 }
iscsiDataIntegrityNone OBJECT-IDENTITY iscsiDataIntegrityNone OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authoritative identifier when no integrity "The authoritative identifier when no integrity
scheme (for either the header or data) is being scheme (for either the header or data) is being
used." used."
REFERENCE REFERENCE
"RFC 3720, Section 12.1, HeaderDigest and DataDigest" "RFC 3720, Section 12.1, HeaderDigest and DataDigest"
::= { iscsiDataIntegrityTypes 1 } ::= { iscsiDataIntegrityTypes 1 }
iscsiDataIntegrityCrc32c OBJECT-IDENTITY iscsiDataIntegrityCrc32c OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authoritative identifier when the integrity "The authoritative identifier when the integrity
scheme (for either the header or data) is CRC-32c." scheme (for either the header or data) is CRC32c."
REFERENCE REFERENCE
"RFC 3720, Section 12.1, HeaderDigest and DataDigest" "RFC 3720, Section 12.1, HeaderDigest and DataDigest"
::= { iscsiDataIntegrityTypes 2 } ::= { iscsiDataIntegrityTypes 2 }
--********************************************************************** --**********************************************************************
iscsiInstance OBJECT IDENTIFIER ::= { iscsiObjects 1 } iscsiInstance OBJECT IDENTIFIER ::= { iscsiObjects 1 }
-- Instance Attributes Table -- Instance Attributes Table
skipping to change at page 18, line 35 skipping to change at page 18, line 36
iscsiInstLastSsnRmtNodeName IscsiName, iscsiInstLastSsnRmtNodeName IscsiName,
iscsiInstDiscontinuityTime TimeStamp iscsiInstDiscontinuityTime TimeStamp
} }
iscsiInstIndex OBJECT-TYPE iscsiInstIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a particular "An arbitrary integer used to uniquely identify a particular
ISCSI instance. This index value must not be modified or iSCSI instance. This index value must not be modified or
reused by an agent unless a reboot has occurred. An agent reused by an agent unless a reboot has occurred. An agent
should attempt to keep this value persistent across reboots." should attempt to keep this value persistent across reboots."
::= { iscsiInstanceAttributesEntry 1 } ::= { iscsiInstanceAttributesEntry 1 }
iscsiInstDescr OBJECT-TYPE iscsiInstDescr OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string, determined by the implementation to "A UTF-8 string, determined by the implementation to
skipping to change at page 19, line 50 skipping to change at page 20, line 4
iscsiInstVendorVersion OBJECT-TYPE iscsiInstVendorVersion OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string set by the manufacturer describing the "A UTF-8 string set by the manufacturer describing the
version of the implementation of this instance. The version of the implementation of this instance. The
format of this string is determined solely by the format of this string is determined solely by the
manufacturer, and is for informational purposes only. manufacturer, and is for informational purposes only.
It is unrelated to the iSCSI specification version numbers." It is unrelated to the iSCSI specification version numbers."
::= { iscsiInstanceAttributesEntry 6 } ::= { iscsiInstanceAttributesEntry 6 }
iscsiInstPortalNumber OBJECT-TYPE iscsiInstPortalNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "transport endpoints" UNITS "transport endpoints"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of rows in the iscsiPortalAttributesTable "The number of rows in the iscsiPortalAttributesTable
which are currently associated with this iSCSI instance." that are currently associated with this iSCSI instance."
::= { iscsiInstanceAttributesEntry 7 } ::= { iscsiInstanceAttributesEntry 7 }
iscsiInstNodeNumber OBJECT-TYPE iscsiInstNodeNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "iSCSI nodes" UNITS "iSCSI nodes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of rows in the iscsiNodeAttributesTable "The number of rows in the iscsiNodeAttributesTable
which are currently associated with this iSCSI instance." that are currently associated with this iSCSI instance."
::= { iscsiInstanceAttributesEntry 8 } ::= { iscsiInstanceAttributesEntry 8 }
iscsiInstSessionNumber OBJECT-TYPE iscsiInstSessionNumber OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of rows in the iscsiSessionAttributesTable "The number of rows in the iscsiSessionAttributesTable
which are currently associated with this iSCSI instance." that are currently associated with this iSCSI instance."
::= { iscsiInstanceAttributesEntry 9 } ::= { iscsiInstanceAttributesEntry 9 }
iscsiInstSsnFailures OBJECT-TYPE iscsiInstSsnFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of times a session belonging "This object counts the number of times a session belonging
to this instance has been failed. If this counter has to this instance has been failed. If this counter has
skipping to change at page 21, line 18 skipping to change at page 21, line 21
If the reason for failure is not found in the If the reason for failure is not found in the
iscsiInstSsnErrorStatsTable, the value { 0.0 } is iscsiInstSsnErrorStatsTable, the value { 0.0 } is
used instead." used instead."
::= { iscsiInstanceAttributesEntry 11 } ::= { iscsiInstanceAttributesEntry 11 }
iscsiInstLastSsnRmtNodeName OBJECT-TYPE iscsiInstLastSsnRmtNodeName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The iSCSI Name of the remote node from the failed "The iSCSI name of the remote node from the failed
session." session."
::= { iscsiInstanceAttributesEntry 12 } ::= { iscsiInstanceAttributesEntry 12 }
iscsiInstDiscontinuityTime OBJECT-TYPE iscsiInstDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of SysUpTime on the most recent occasion "The value of SysUpTime on the most recent occasion
at which any one or more of this instance's counters at which any one or more of this instance's counters
skipping to change at page 21, line 30 skipping to change at page 21, line 33
::= { iscsiInstanceAttributesEntry 12 } ::= { iscsiInstanceAttributesEntry 12 }
iscsiInstDiscontinuityTime OBJECT-TYPE iscsiInstDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of SysUpTime on the most recent occasion "The value of SysUpTime on the most recent occasion
at which any one or more of this instance's counters at which any one or more of this instance's counters
suffered a discontinuity. suffered a discontinuity.
If no such discontinuities have occurred since the last If no such discontinuities have occurred since the last
re-initialization of the local management subsystem re-initialization of the local management subsystem,
then this object contains a zero value." then this object contains a zero value."
::= { iscsiInstanceAttributesEntry 13 } ::= { iscsiInstanceAttributesEntry 13 }
-- Instance Session Failure Stats Table -- Instance Session Failure Stats Table
iscsiInstanceSsnErrorStatsTable OBJECT-TYPE iscsiInstanceSsnErrorStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiInstanceSsnErrorStatsEntry SYNTAX SEQUENCE OF IscsiInstanceSsnErrorStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 22, line 21 skipping to change at page 22, line 25
iscsiInstSsnCxnTimeoutErrors Counter32, iscsiInstSsnCxnTimeoutErrors Counter32,
iscsiInstSsnFormatErrors Counter32 iscsiInstSsnFormatErrors Counter32
} }
iscsiInstSsnDigestErrors OBJECT-TYPE iscsiInstSsnDigestErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of sessions which were failed due to receipt of "The count of sessions that were failed due to receipt of
a PDU containing header or data digest errors. If this a PDU containing header or data digest errors. If this
counter has suffered a discontinuity, the time of the last counter has suffered a discontinuity, the time of the last
discontinuity is indicated in iscsiInstDiscontinuityTime." discontinuity is indicated in iscsiInstDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 6.7, Digest Errors" "RFC 3720, Section 6.7, Digest Errors"
::= { iscsiInstanceSsnErrorStatsEntry 1 } ::= { iscsiInstanceSsnErrorStatsEntry 1 }
iscsiInstSsnCxnTimeoutErrors OBJECT-TYPE iscsiInstSsnCxnTimeoutErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of sessions which were failed due to a sequence "The count of sessions that were failed due to a sequence
exceeding a time limit. If this counter has suffered a exceeding a time limit. If this counter has suffered a
discontinuity, the time of the last discontinuity discontinuity, the time of the last discontinuity
is indicated in iscsiInstDiscontinuityTime." is indicated in iscsiInstDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 6.4, Connection Timeout Management" "RFC 3720, Section 6.4, Connection Timeout Management"
::= { iscsiInstanceSsnErrorStatsEntry 2 } ::= { iscsiInstanceSsnErrorStatsEntry 2 }
iscsiInstSsnFormatErrors OBJECT-TYPE iscsiInstSsnFormatErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "sessions" UNITS "sessions"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of sessions which were failed due to receipt of "The count of sessions that were failed due to receipt of
a PDU which contained a format error. If this counter has a PDU that contained a format error. If this counter has
suffered a discontinuity, the time of the last discontinuity suffered a discontinuity, the time of the last discontinuity
is indicated in iscsiInstDiscontinuityTime." is indicated in iscsiInstDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 6.6, Format Errors" "RFC 3720, Section 6.6, Format Errors"
::= { iscsiInstanceSsnErrorStatsEntry 3 } ::= { iscsiInstanceSsnErrorStatsEntry 3 }
--********************************************************************** --**********************************************************************
iscsiPortal OBJECT IDENTIFIER ::= { iscsiObjects 2 } iscsiPortal OBJECT IDENTIFIER ::= { iscsiObjects 2 }
-- Portal Attributes Table -- Portal Attributes Table
iscsiPortalAttributesTable OBJECT-TYPE iscsiPortalAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiPortalAttributesEntry SYNTAX SEQUENCE OF IscsiPortalAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of transport endpoints (using TCP or another transport "A list of transport endpoints (using TCP or another transport
protocol) used by this iSCSI instance. An iSCSI instance may protocol) used by this iSCSI instance. An iSCSI instance may
use a portal to listen for incoming connections to its targets, use a portal to listen for incoming connections to its targets,
to initiate connections to other targets, or both." to initiate connections to other targets, or both."
::= { iscsiPortal 1 } ::= { iscsiPortal 1 }
iscsiPortalAttributesEntry OBJECT-TYPE iscsiPortalAttributesEntry OBJECT-TYPE
SYNTAX IscsiPortalAttributesEntry SYNTAX IscsiPortalAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information applicable "An entry (row) containing management information applicable
skipping to change at page 24, line 43 skipping to change at page 24, line 47
iscsiPortalRoles OBJECT-TYPE iscsiPortalRoles OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
targetTypePortal(0), targetTypePortal(0),
initiatorTypePortal(1) initiatorTypePortal(1)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A portal can operate in one or both of two roles: "A portal can operate in one or both of two roles:
as a target portal and/or an initiator portal. If as a target portal and/or an initiator portal. If
the portal will operate in both roles, both bits the portal will operate in both roles, both bits
must be set. must be set.
This object will define a corresponding row that This object will define a corresponding row that
will exist or must be created in the will exist or must be created in the
iscsiTgtPortalAttributesTable, the iscsiTgtPortalAttributesTable, the
iscsiIntrPortalAttributesTable or both. If the iscsiIntrPortalAttributesTable or both. If the
targetTypePortal bit is set, one or more corresponding targetTypePortal bit is set, one or more corresponding
iscsiTgtPortalAttributesEntry rows will be found or iscsiTgtPortalAttributesEntry rows will be found or
created. If the initiatorTypePortal bit is set, created. If the initiatorTypePortal bit is set,
one or more corresponding iscsiIntrPortalAttributesEntry one or more corresponding iscsiIntrPortalAttributesEntry
rows will be found or created. If both bits are set, one rows will be found or created. If both bits are set, one
or more corresponding rows will be found or created in or more corresponding rows will be found or created in
of the above tables." one of the above tables."
::= { iscsiPortalAttributesEntry 3 } ::= { iscsiPortalAttributesEntry 3 }
iscsiPortalAddrType OBJECT-TYPE iscsiPortalAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Internet Network Address contained in the "The type of Internet Network Address contained in the
corresponding instance of the iscsiPortalAddr." corresponding instance of the iscsiPortalAddr."
DEFVAL { ipv4 } DEFVAL { ipv4 }
skipping to change at page 27, line 4 skipping to change at page 27, line 8
"An alternate data digest preference for this portal." "An alternate data digest preference for this portal."
DEFVAL { noDigest } DEFVAL { noDigest }
::= { iscsiPortalAttributesEntry 11 } ::= { iscsiPortalAttributesEntry 11 }
iscsiPortalRecvMarker OBJECT-TYPE iscsiPortalRecvMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether or not this portal will "This object indicates whether or not this portal will
request markers in it's incoming data stream." request markers in its incoming data stream."
REFERENCE REFERENCE
"RFC 3720, Appendix A." "RFC 3720, Appendix A."
DEFVAL { false } DEFVAL { false }
::= { iscsiPortalAttributesEntry 12 } ::= { iscsiPortalAttributesEntry 12 }
iscsiPortalStorageType OBJECT-TYPE iscsiPortalStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 27, line 46 skipping to change at page 27, line 50
connections to its targets." connections to its targets."
::= { iscsiTargetPortal 1 } ::= { iscsiTargetPortal 1 }
iscsiTgtPortalAttributesEntry OBJECT-TYPE iscsiTgtPortalAttributesEntry OBJECT-TYPE
SYNTAX IscsiTgtPortalAttributesEntry SYNTAX IscsiTgtPortalAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information applicable "An entry (row) containing management information applicable
to a particular portal instance that is used to listen for to a particular portal instance that is used to listen for
incoming connections to local targets. One or more rows in incoming connections to local targets. One or more rows in
this table is populated by the agent for each this table is populated by the agent for each
iscsiPortalAttributesEntry row that has the bit iscsiPortalAttributesEntry row that has the bit
targetTypePortal set in its iscsiPortalRoles column." targetTypePortal set in its iscsiPortalRoles column."
INDEX { iscsiInstIndex, iscsiPortalIndex, INDEX { iscsiInstIndex, iscsiPortalIndex,
iscsiTgtPortalNodeIndexOrZero } iscsiTgtPortalNodeIndexOrZero }
::= { iscsiTgtPortalAttributesTable 1 } ::= { iscsiTgtPortalAttributesTable 1 }
IscsiTgtPortalAttributesEntry ::= SEQUENCE { IscsiTgtPortalAttributesEntry ::= SEQUENCE {
iscsiTgtPortalNodeIndexOrZero Unsigned32, iscsiTgtPortalNodeIndexOrZero Unsigned32,
iscsiTgtPortalPort InetPortNumber, iscsiTgtPortalPort InetPortNumber,
iscsiTgtPortalTag Unsigned32 iscsiTgtPortalTag Unsigned32
} }
iscsiTgtPortalNodeIndexOrZero OBJECT-TYPE iscsiTgtPortalNodeIndexOrZero OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
skipping to change at page 28, line 47 skipping to change at page 28, line 50
portal listens for incoming iSCSI connections when the portal listens for incoming iSCSI connections when the
portal is used as a target portal. This object's storage portal is used as a target portal. This object's storage
type is specified in iscsiPortalStorageType." type is specified in iscsiPortalStorageType."
::= { iscsiTgtPortalAttributesEntry 2 } ::= { iscsiTgtPortalAttributesEntry 2 }
iscsiTgtPortalTag OBJECT-TYPE iscsiTgtPortalTag OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The portal's aggregation tag when portal is used as "The portal's aggregation tag when the portal is used as
a target portal. Multiple-connection sessions may a target portal. Multiple-connection sessions may
be aggregated over portals sharing an identical be aggregated over portals sharing an identical
aggregation tag. This object's storage type is aggregation tag. This object's storage type is
specified in iscsiPortalStorageType." specified in iscsiPortalStorageType."
REFERENCE REFERENCE
"RFC 3720, Section 3.4.1, iSCSI Architectural Modell" "RFC 3720, Section 3.4.1, iSCSI Architectural Model"
::= { iscsiTgtPortalAttributesEntry 3 } ::= { iscsiTgtPortalAttributesEntry 3 }
--********************************************************************** --**********************************************************************
iscsiInitiatorPortal OBJECT IDENTIFIER ::= { iscsiObjects 4 } iscsiInitiatorPortal OBJECT IDENTIFIER ::= { iscsiObjects 4 }
-- Initiator Portal Attributes Table -- Initiator Portal Attributes Table
iscsiIntrPortalAttributesTable OBJECT-TYPE iscsiIntrPortalAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiIntrPortalAttributesEntry SYNTAX SEQUENCE OF IscsiIntrPortalAttributesEntry
skipping to change at page 31, line 42 skipping to change at page 31, line 47
modified or reused by an agent unless a reboot has occurred. modified or reused by an agent unless a reboot has occurred.
An agent should attempt to keep this value persistent across An agent should attempt to keep this value persistent across
reboots." reboots."
::= { iscsiNodeAttributesEntry 1 } ::= { iscsiNodeAttributesEntry 1 }
iscsiNodeName OBJECT-TYPE iscsiNodeName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This node's iSCSI Name, which is independent of the location "This node's iSCSI name, which is independent of the location
of the node, and can be resolved into a set of addresses of the node, and can be resolved into a set of addresses
through various discovery services." through various discovery services."
::= { iscsiNodeAttributesEntry 2 } ::= { iscsiNodeAttributesEntry 2 }
iscsiNodeAlias OBJECT-TYPE iscsiNodeAlias OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A character string that is a human-readable name or "A character string that is a human-readable name or
description of the iSCSI node. If configured, this alias description of the iSCSI node. If configured, this alias
may be communicated to the initiator or target node at may be communicated to the initiator or target node at
the remote end of the connection during a Login Request the remote end of the connection during a Login Request
or Response message. This string is not used as an or Response message. This string is not used as an
skipping to change at page 32, line 27 skipping to change at page 32, line 32
iscsiNodeRoles OBJECT-TYPE iscsiNodeRoles OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
targetTypeNode(0), targetTypeNode(0),
initiatorTypeNode(1) initiatorTypeNode(1)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A node can operate in one or both of two roles: "A node can operate in one or both of two roles:
a target role and/or an initiator role. If the node a target role and/or an initiator role. If the node
will operate in both roles, both bits must be set. will operate in both roles, both bits must be set.
This object will also define the corresponding rows that This object will also define the corresponding rows that
will exist in the iscsiTargetAttributesTable, the will exist in the iscsiTargetAttributesTable, the
iscsiInitiatorAttributesTable or both. If the iscsiInitiatorAttributesTable or both. If the
targetTypeNode bit is set, there will be a corresponding targetTypeNode bit is set, there will be a corresponding
iscsiTargetAttributesEntry. If the initiatorTypeNode bit iscsiTargetAttributesEntry. If the initiatorTypeNode bit
is set, there will be a corresponding is set, there will be a corresponding
iscsiInitiatorAttributesEntry. If both bits are set, iscsiInitiatorAttributesEntry. If both bits are set,
there will be a corresponding iscsiTgtPortalAttributesEntry there will be a corresponding iscsiTgtPortalAttributesEntry
and iscsiPortalAttributesEntry." and iscsiPortalAttributesEntry."
::= { iscsiNodeAttributesEntry 4 } ::= { iscsiNodeAttributesEntry 4 }
iscsiNodeTransportType OBJECT-TYPE iscsiNodeTransportType OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to the corresponding row in the appropriate "A pointer to the corresponding row in the appropriate
table for this SCSI transport, thereby allowing management table for this SCSI transport, thereby allowing management
stations to locate the SCSI-level device that is represented stations to locate the SCSI-level device that is represented
by this iscsiNode. For example, it will usually point to the by this iscsiNode. For example, it will usually point to the
corresponding scsiTrnspt object in the SCSI MIB module. corresponding scsiTrnspt object in the SCSI MIB module.
If no corresponding row exists, the value 0.0 must be If no corresponding row exists, the value 0.0 must be
used to indicate this." used to indicate this."
REFERENCE REFERENCE
"SCSI-MIB" "SCSI-MIB"
::= { iscsiNodeAttributesEntry 5 } ::= { iscsiNodeAttributesEntry 5 }
iscsiNodeInitialR2T OBJECT-TYPE iscsiNodeInitialR2T OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
skipping to change at page 33, line 30 skipping to change at page 33, line 34
REFERENCE REFERENCE
"RFC 3720, Section 12.10, InitialR2T" "RFC 3720, Section 12.10, InitialR2T"
::= { iscsiNodeAttributesEntry 6 } ::= { iscsiNodeAttributesEntry 6 }
iscsiNodeImmediateData OBJECT-TYPE iscsiNodeImmediateData OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates ImmediateData preference for this "This object indicates ImmediateData preference for this
node node:
true = YES (but will accept NO), true = YES (but will accept NO),
false = NO " false = NO "
REFERENCE REFERENCE
"RFC 3720, Section 12.11, ImmediateData" "RFC 3720, Section 12.11, ImmediateData"
DEFVAL { true } DEFVAL { true }
::= { iscsiNodeAttributesEntry 7 } ::= { iscsiNodeAttributesEntry 7 }
iscsiNodeMaxOutstandingR2T OBJECT-TYPE iscsiNodeMaxOutstandingR2T OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "R2Ts" UNITS "R2Ts"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Maximum number of outstanding R2Ts allowed per ISCSI task." "Maximum number of outstanding requests-to-transmit (R2Ts)
allowed per iSCSI task."
REFERENCE REFERENCE
"RFC 3720, Section 12.17, MaxOutstandingR2T" "RFC 3720, Section 12.17, MaxOutstandingR2T"
DEFVAL { 1 } DEFVAL { 1 }
::= { iscsiNodeAttributesEntry 8 } ::= { iscsiNodeAttributesEntry 8 }
iscsiNodeFirstBurstLength OBJECT-TYPE iscsiNodeFirstBurstLength OBJECT-TYPE
SYNTAX Unsigned32 (512..16777215) SYNTAX Unsigned32 (512..16777215)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum length (bytes) supported for unsolicited data "The maximum length (bytes) supported for unsolicited data
skipping to change at page 34, line 20 skipping to change at page 34, line 27
"RFC 3720, Section 12.14, FirstBurstLength" "RFC 3720, Section 12.14, FirstBurstLength"
DEFVAL { 65536 } DEFVAL { 65536 }
::= { iscsiNodeAttributesEntry 9 } ::= { iscsiNodeAttributesEntry 9 }
iscsiNodeMaxBurstLength OBJECT-TYPE iscsiNodeMaxBurstLength OBJECT-TYPE
SYNTAX Unsigned32 (512..16777215) SYNTAX Unsigned32 (512..16777215)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of bytes which can be sent within "The maximum number of bytes that can be sent within
a single sequence of Data-In or Data-Out PDUs." a single sequence of Data-In or Data-Out PDUs."
REFERENCE REFERENCE
"RFC 3720, Section 12.13, MaxBurstLength" "RFC 3720, Section 12.13, MaxBurstLength"
DEFVAL { 262144 } DEFVAL { 262144 }
::= { iscsiNodeAttributesEntry 10 } ::= { iscsiNodeAttributesEntry 10 }
iscsiNodeMaxConnections OBJECT-TYPE iscsiNodeMaxConnections OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "connections" UNITS "connections"
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 35, line 29 skipping to change at page 35, line 36
"RFC 3720, Section 12.18, DataPDUInOrder" "RFC 3720, Section 12.18, DataPDUInOrder"
DEFVAL { true } DEFVAL { true }
::= { iscsiNodeAttributesEntry 13 } ::= { iscsiNodeAttributesEntry 13 }
iscsiNodeDefaultTime2Wait OBJECT-TYPE iscsiNodeDefaultTime2Wait OBJECT-TYPE
SYNTAX Unsigned32 (0..3600) SYNTAX Unsigned32 (0..3600)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DefaultTime2Wait preference of this node. This is the "The DefaultTime2Wait preference of this node. This is the
minimum time, in seconds, to wait before attempting an minimum time, in seconds, to wait before attempting an
explicit/implicit logout or active iSCSI task reassignment explicit/implicit logout or active iSCSI task reassignment
after an unexpected connection termination or a connection after an unexpected connection termination or a connection
reset." reset."
REFERENCE REFERENCE
"RFC 3720, Section 12.15, DefaultTime2Wait" "RFC 3720, Section 12.15, DefaultTime2Wait"
DEFVAL { 2 } DEFVAL { 2 }
::= { iscsiNodeAttributesEntry 14 } ::= { iscsiNodeAttributesEntry 14 }
iscsiNodeDefaultTime2Retain OBJECT-TYPE iscsiNodeDefaultTime2Retain OBJECT-TYPE
SYNTAX Unsigned32 (0..3600) SYNTAX Unsigned32 (0..3600)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DefaultTime2Retain preference of this node. This is "The DefaultTime2Retain preference of this node. This is
the maximum time, in seconds after an initial wait the maximum time, in seconds after an initial wait
(Time2Wait), before which an active iSCSI task reassignment (Time2Wait), before which an active iSCSI task reassignment
is still possible after an unexpected connection termination is still possible after an unexpected connection termination
or a connection reset." or a connection reset."
REFERENCE REFERENCE
"RFC 3720, Section 12.16, DefaultTime2Retain" "RFC 3720, Section 12.16, DefaultTime2Retain"
DEFVAL { 20 } DEFVAL { 20 }
::= { iscsiNodeAttributesEntry 15 } ::= { iscsiNodeAttributesEntry 15 }
iscsiNodeErrorRecoveryLevel OBJECT-TYPE iscsiNodeErrorRecoveryLevel OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ErrorRecoveryLevel preference of this node. "The ErrorRecoveryLevel preference of this node.
Currently, only 0-2 are valid. Currently, only 0-2 are valid.
skipping to change at page 36, line 15 skipping to change at page 36, line 20
DEFVAL { 20 } DEFVAL { 20 }
::= { iscsiNodeAttributesEntry 15 } ::= { iscsiNodeAttributesEntry 15 }
iscsiNodeErrorRecoveryLevel OBJECT-TYPE iscsiNodeErrorRecoveryLevel OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ErrorRecoveryLevel preference of this node. "The ErrorRecoveryLevel preference of this node.
Currently, only 0-2 are valid. Currently, only 0-2 are valid.
This object is designed to accommodate future error recover
This object is designed to accommodate future error recovery
levels. levels.
Higher error recovery levels imply support in addition to Higher error recovery levels imply support in addition to
support for the lower error level functions. In other words, support for the lower error level functions. In other words,
error level 2 implies support for levels 0-1, since those error level 2 implies support for levels 0-1, since those
functions are subsets of error level 2." functions are subsets of error level 2."
REFERENCE REFERENCE
"RFC 3720, Section 12.20, ErrorRecoveryLevel" "RFC 3720, Section 12.20, ErrorRecoveryLevel"
DEFVAL { 0 } DEFVAL { 0 }
::= { iscsiNodeAttributesEntry 16 } ::= { iscsiNodeAttributesEntry 16 }
iscsiNodeDiscontinuityTime OBJECT-TYPE iscsiNodeDiscontinuityTime OBJECT-TYPE
skipping to change at page 36, line 34 skipping to change at page 36, line 41
::= { iscsiNodeAttributesEntry 16 } ::= { iscsiNodeAttributesEntry 16 }
iscsiNodeDiscontinuityTime OBJECT-TYPE iscsiNodeDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of SysUpTime on the most recent occasion "The value of SysUpTime on the most recent occasion
at which any one or more of this node's counters at which any one or more of this node's counters
suffered a discontinuity. suffered a discontinuity.
If no such discontinuities have occurred since the last If no such discontinuities have occurred since the last
re-initialization of the local management subsystem re-initialization of the local management subsystem,
then this object contains a zero value." then this object contains a zero value."
::= { iscsiNodeAttributesEntry 17 } ::= { iscsiNodeAttributesEntry 17 }
iscsiNodeStorageType OBJECT-TYPE iscsiNodeStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for all read-write objects within this "The storage type for all read-write objects within this
row. Rows in this table are always created via an row. Rows in this table are always created via an
external process, and may have a storage type of readOnly external process, and may have a storage type of readOnly
or permanent. Conceptual rows having the value 'permanent' or permanent. Conceptual rows having the value 'permanent'
need not allow write access to any columnar objects in need not allow write access to any columnar objects in
the row. the row.
If this object has the value 'volatile', modifications If this object has the value 'volatile', modifications
to read-write objects in this row are not persistent to read-write objects in this row are not persistent
across reboots. If this object has the value across reboots. If this object has the value
'nonVolatile', modifications to objects in this row 'nonVolatile', modifications to objects in this row
are persistent. are persistent.
An implementation may choose to allow this object An implementation may choose to allow this object
to be set to either 'nonVolatile' or 'volatile', to be set to either 'nonVolatile' or 'volatile',
allowing the management application to choose this allowing the management application to choose this
behavior." behavior."
DEFVAL { volatile } DEFVAL { volatile }
::= { iscsiNodeAttributesEntry 18 } ::= { iscsiNodeAttributesEntry 18 }
--********************************************************************** --**********************************************************************
iscsiTarget OBJECT IDENTIFIER ::= { iscsiObjects 6 } iscsiTarget OBJECT IDENTIFIER ::= { iscsiObjects 6 }
-- Target Attributes Table -- Target Attributes Table
iscsiTargetAttributesTable OBJECT-TYPE iscsiTargetAttributesTable OBJECT-TYPE
skipping to change at page 38, line 35 skipping to change at page 38, line 44
iscsiTgtLastFailureType OBJECT-TYPE iscsiTgtLastFailureType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the most recent failure of a login attempt "The type of the most recent failure of a login attempt
to this target, represented as the OID of the counter to this target, represented as the OID of the counter
object in iscsiTargetLoginStatsTable for which the object in iscsiTargetLoginStatsTable for which the
relevant instance was incremented. A value of 0.0 relevant instance was incremented. A value of 0.0
indicates a type which is not represented by any of indicates a type that is not represented by any of
the counters in iscsiTargetLoginStatsTable." the counters in iscsiTargetLoginStatsTable."
::= { iscsiTargetAttributesEntry 3 } ::= { iscsiTargetAttributesEntry 3 }
iscsiTgtLastIntrFailureName OBJECT-TYPE iscsiTgtLastIntrFailureName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The iSCSI Name of the initiator that failed the last "The iSCSI name of the initiator that failed the last
login attempt." login attempt."
::= { iscsiTargetAttributesEntry 4 } ::= { iscsiTargetAttributesEntry 4 }
iscsiTgtLastIntrFailureAddrType OBJECT-TYPE iscsiTgtLastIntrFailureAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of Internet Network Address contained in the "The type of Internet Network Address contained in the
corresponding instance of the iscsiTgtLastIntrFailureAddr. corresponding instance of the iscsiTgtLastIntrFailureAddr.
skipping to change at page 39, line 28 skipping to change at page 39, line 37
attempt." attempt."
::= { iscsiTargetAttributesEntry 6 } ::= { iscsiTargetAttributesEntry 6 }
-- Target Login Stats Table -- Target Login Stats Table
iscsiTargetLoginStatsTable OBJECT-TYPE iscsiTargetLoginStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiTargetLoginStatsEntry SYNTAX SEQUENCE OF IscsiTargetLoginStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of counters which keep a record of the results "A table of counters that keep a record of the results
of initiators' login attempts to this target." of initiators' login attempts to this target."
::= { iscsiTarget 2 } ::= { iscsiTarget 2 }
iscsiTargetLoginStatsEntry OBJECT-TYPE iscsiTargetLoginStatsEntry OBJECT-TYPE
SYNTAX IscsiTargetLoginStatsEntry SYNTAX IscsiTargetLoginStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing counters for each result of "An entry (row) containing counters for each result of
a login attempt to this target." a login attempt to this target."
skipping to change at page 40, line 24 skipping to change at page 40, line 33
REFERENCE REFERENCE
"RFC 3720, Section 10.13.5, Status-Class and Status-Detail" "RFC 3720, Section 10.13.5, Status-Class and Status-Detail"
::= { iscsiTargetLoginStatsEntry 1 } ::= { iscsiTargetLoginStatsEntry 1 }
iscsiTgtLoginOtherFails OBJECT-TYPE iscsiTgtLoginOtherFails OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "failed logins" UNITS "failed logins"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of Login Response PDUs which were transmitted "The number of Login Response PDUs that were transmitted
by this target, and which were not counted by any other by this target and that were not counted by any other
object in the row. object in the row.
If this counter has suffered a discontinuity, the time of the If this counter has suffered a discontinuity, the time of the
last discontinuity is indicated in iscsiNodeDiscontinuityTime." last discontinuity is indicated in iscsiNodeDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 10.13.5, Status-Class and Status-Detail" "RFC 3720, Section 10.13.5, Status-Class and Status-Detail"
::= { iscsiTargetLoginStatsEntry 2 } ::= { iscsiTargetLoginStatsEntry 2 }
iscsiTgtLoginRedirects OBJECT-TYPE iscsiTgtLoginRedirects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "redirected logins" UNITS "redirected logins"
skipping to change at page 41, line 23 skipping to change at page 41, line 33
"RFC 3720, Section 10.13.5, Status-Class and Status-Detail" "RFC 3720, Section 10.13.5, Status-Class and Status-Detail"
::= { iscsiTargetLoginStatsEntry 4 } ::= { iscsiTargetLoginStatsEntry 4 }
iscsiTgtLoginAuthenticateFails OBJECT-TYPE iscsiTgtLoginAuthenticateFails OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "failed logins" UNITS "failed logins"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Login Response PDUs with status 0x0201, "The count of Login Response PDUs with status 0x0201,
Authentication Failed, transmitted by this target Authentication Failed, transmitted by this target.
If this counter is incremented, an iscsiTgtLoginFailure If this counter is incremented, an iscsiTgtLoginFailure
notification should be generated. notification should be generated.
If this counter has suffered a discontinuity, the time of the If this counter has suffered a discontinuity, the time of the
last discontinuity is indicated in iscsiNodeDiscontinuityTime." last discontinuity is indicated in iscsiNodeDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 10.13.5, Status-Class and Status-Detail" "RFC 3720, Section 10.13.5, Status-Class and Status-Detail"
::= { iscsiTargetLoginStatsEntry 5 } ::= { iscsiTargetLoginStatsEntry 5 }
iscsiTgtLoginNegotiateFails OBJECT-TYPE iscsiTgtLoginNegotiateFails OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "failed logins" UNITS "failed logins"
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 44, line 28 skipping to change at page 44, line 38
::= { iscsiTgtAuthAttributesEntry 2 } ::= { iscsiTgtAuthAttributesEntry 2 }
iscsiTgtAuthIdentity OBJECT-TYPE iscsiTgtAuthIdentity OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to the corresponding user entry in the IPS-AUTH "A pointer to the corresponding user entry in the IPS-AUTH
MIB module that will be allowed to access this iSCSI target." MIB module that will be allowed to access this iSCSI target."
REFERENCE REFERENCE
"IPS-AUTH MIB" "IPS-AUTH MIB, RFC 4545"
::= { iscsiTgtAuthAttributesEntry 3 } ::= { iscsiTgtAuthAttributesEntry 3 }
iscsiTgtAuthStorageType OBJECT-TYPE iscsiTgtAuthStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this row. Rows in this table that were "The storage type for this row. Rows in this table that were
created through an external process may have a storage type of created through an external process may have a storage type of
readOnly or permanent. readOnly or permanent.
skipping to change at page 46, line 18 skipping to change at page 46, line 28
iscsiIntrLastFailureType OBJECT-TYPE iscsiIntrLastFailureType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the most recent failure of a login attempt "The type of the most recent failure of a login attempt
from this initiator, represented as the OID of the counter from this initiator, represented as the OID of the counter
object in iscsiInitiatorLoginStatsTable for which the object in iscsiInitiatorLoginStatsTable for which the
relevant instance was incremented. A value of 0.0 relevant instance was incremented. A value of 0.0
indicates a type which is not represented by any of indicates a type that is not represented by any of
the counters in iscsiInitiatorLoginStatsTable." the counters in iscsiInitiatorLoginStatsTable."
::= { iscsiInitiatorAttributesEntry 3 } ::= { iscsiInitiatorAttributesEntry 3 }
iscsiIntrLastTgtFailureName OBJECT-TYPE iscsiIntrLastTgtFailureName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string giving the name of the target that failed "A UTF-8 string giving the name of the target that failed
the last login attempt." the last login attempt."
skipping to change at page 49, line 40 skipping to change at page 49, line 50
"RFC 3720, Section 6.10, Negotiation Failures" "RFC 3720, Section 6.10, Negotiation Failures"
::= { iscsiInitiatorLoginStatsEntry 6 } ::= { iscsiInitiatorLoginStatsEntry 6 }
-- Initiator Logout Stats Table -- Initiator Logout Stats Table
iscsiInitiatorLogoutStatsTable OBJECT-TYPE iscsiInitiatorLogoutStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiInitiatorLogoutStatsEntry SYNTAX SEQUENCE OF IscsiInitiatorLogoutStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When an initiator attempts send a Logout command, the target "When an initiator attempts to send a Logout command, the target
responds with a Logout Response that carries a status code. responds with a Logout Response that carries a status code.
This table contains a list of counters of Logout Response This table contains a list of counters of Logout Response
PDUs of each status code, that were received by each PDUs of each status code that was received by each
initiator belonging to this iSCSI instance present on this initiator belonging to this iSCSI instance present on this
system." system."
::= { iscsiInitiator 3 } ::= { iscsiInitiator 3 }
iscsiInitiatorLogoutStatsEntry OBJECT-TYPE iscsiInitiatorLogoutStatsEntry OBJECT-TYPE
SYNTAX IscsiInitiatorLogoutStatsEntry SYNTAX IscsiInitiatorLogoutStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing counters of Logout Response "An entry (row) containing counters of Logout Response
PDUs of each status code, that were generated by this PDUs of each status code that was generated by this
initiator." initiator."
AUGMENTS { iscsiInitiatorAttributesEntry } AUGMENTS { iscsiInitiatorAttributesEntry }
::= { iscsiInitiatorLogoutStatsTable 1 } ::= { iscsiInitiatorLogoutStatsTable 1 }
IscsiInitiatorLogoutStatsEntry ::= SEQUENCE { IscsiInitiatorLogoutStatsEntry ::= SEQUENCE {
iscsiIntrLogoutNormals Counter32, iscsiIntrLogoutNormals Counter32,
iscsiIntrLogoutOthers Counter32 iscsiIntrLogoutOthers Counter32
} }
iscsiIntrLogoutNormals OBJECT-TYPE iscsiIntrLogoutNormals OBJECT-TYPE
skipping to change at page 51, line 6 skipping to change at page 51, line 18
iscsiIntrAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 9 } iscsiIntrAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 9 }
-- Initiator Authorization Attributes Table -- Initiator Authorization Attributes Table
iscsiIntrAuthAttributesTable OBJECT-TYPE iscsiIntrAuthAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiIntrAuthAttributesEntry SYNTAX SEQUENCE OF IscsiIntrAuthAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of target identities which each initiator "A list of target identities that each initiator
on the local system may access." on the local system may access."
::= { iscsiIntrAuthorization 1 } ::= { iscsiIntrAuthorization 1 }
iscsiIntrAuthAttributesEntry OBJECT-TYPE iscsiIntrAuthAttributesEntry OBJECT-TYPE
SYNTAX IscsiIntrAuthAttributesEntry SYNTAX IscsiIntrAuthAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information applicable "An entry (row) containing management information applicable
to a particular initiator node's authorized target identity." to a particular initiator node's authorized target identity."
skipping to change at page 52, line 16 skipping to change at page 52, line 26
iscsiIntrAuthIdentity OBJECT-TYPE iscsiIntrAuthIdentity OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to the corresponding user entry in the IPS-AUTH "A pointer to the corresponding user entry in the IPS-AUTH
MIB module to which this initiator node should attempt to MIB module to which this initiator node should attempt to
establish an iSCSI session." establish an iSCSI session."
REFERENCE REFERENCE
"IPS-AUTH MIB" "IPS-AUTH MIB, RFC 4545"
::= { iscsiIntrAuthAttributesEntry 3 } ::= { iscsiIntrAuthAttributesEntry 3 }
iscsiIntrAuthStorageType OBJECT-TYPE iscsiIntrAuthStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this row. Rows in this table that were "The storage type for this row. Rows in this table that were
created through an external process may have a storage type of created through an external process may have a storage type of
readOnly or permanent. readOnly or permanent.
Conceptual rows having the value 'permanent' need not Conceptual rows having the value 'permanent' need not
allow write access to any columnar objects in the row." allow write access to any columnar objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { iscsiIntrAuthAttributesEntry 4 } ::= { iscsiIntrAuthAttributesEntry 4 }
--********************************************************************** --**********************************************************************
iscsiSession OBJECT IDENTIFIER ::= { iscsiObjects 10 } iscsiSession OBJECT IDENTIFIER ::= { iscsiObjects 10 }
-- Session Attributes Table -- Session Attributes Table
iscsiSessionAttributesTable OBJECT-TYPE iscsiSessionAttributesTable OBJECT-TYPE
skipping to change at page 53, line 7 skipping to change at page 53, line 18
::= { iscsiSession 1 } ::= { iscsiSession 1 }
iscsiSessionAttributesEntry OBJECT-TYPE iscsiSessionAttributesEntry OBJECT-TYPE
SYNTAX IscsiSessionAttributesEntry SYNTAX IscsiSessionAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information applicable "An entry (row) containing management information applicable
to a particular session. to a particular session.
If this session is a discovery session which is not attached If this session is a discovery session that is not attached
to any particular node, the iscsiSsnNodeIndex will be zero. to any particular node, the iscsiSsnNodeIndex will be zero.
Otherwise, the iscsiSsnNodeIndex will have the same value as Otherwise, the iscsiSsnNodeIndex will have the same value as
iscsiNodeIndex." iscsiNodeIndex."
INDEX { iscsiInstIndex, iscsiSsnNodeIndex, iscsiSsnIndex } INDEX { iscsiInstIndex, iscsiSsnNodeIndex, iscsiSsnIndex }
::= { iscsiSessionAttributesTable 1 } ::= { iscsiSessionAttributesTable 1 }
IscsiSessionAttributesEntry ::= SEQUENCE { IscsiSessionAttributesEntry ::= SEQUENCE {
iscsiSsnNodeIndex Unsigned32, iscsiSsnNodeIndex Unsigned32,
iscsiSsnIndex Unsigned32, iscsiSsnIndex Unsigned32,
iscsiSsnDirection INTEGER, iscsiSsnDirection INTEGER,
skipping to change at page 53, line 45 skipping to change at page 54, line 8
iscsiSsnDiscontinuityTime TimeStamp iscsiSsnDiscontinuityTime TimeStamp
} }
iscsiSsnNodeIndex OBJECT-TYPE iscsiSsnNodeIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular node within an iSCSI instance present particular node within an iSCSI instance present
on the local system. For normal, non-discovery on the local system. For normal, non-discovery
sessions, this value will map to the iscsiNodeIndex. sessions, this value will map to the iscsiNodeIndex.
For discovery sessions which do not have a node For discovery sessions that do not have a node
associated, the value 0 (zero) is used." associated, the value 0 (zero) is used."
::= { iscsiSessionAttributesEntry 1 } ::= { iscsiSessionAttributesEntry 1 }
iscsiSsnIndex OBJECT-TYPE iscsiSsnIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary integer used to uniquely identify a "An arbitrary integer used to uniquely identify a
particular session within an iSCSI instance present particular session within an iSCSI instance present
skipping to change at page 54, line 22 skipping to change at page 54, line 33
iSCSI sessions are destroyed during a reboot; rows iSCSI sessions are destroyed during a reboot; rows
in this table are not persistent across reboots." in this table are not persistent across reboots."
::= { iscsiSessionAttributesEntry 2 } ::= { iscsiSessionAttributesEntry 2 }
iscsiSsnDirection OBJECT-TYPE iscsiSsnDirection OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
inboundSession(1), inboundSession(1),
outboundSession(2) outboundSession(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Direction of iSCSI session: "Direction of iSCSI session:
InboundSession - session is established from an external inboundSession - session is established from an external
initiator to a target within this iSCSI initiator to a target within this iSCSI
instance. instance.
OutboundSession - session is established from an initiator outboundSession - session is established from an initiator
within this iSCSI instance to an external within this iSCSI instance to an external
target." target."
::= { iscsiSessionAttributesEntry 3 } ::= { iscsiSessionAttributesEntry 3 }
iscsiSsnInitiatorName OBJECT-TYPE iscsiSsnInitiatorName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If iscsiSsnDirection is Inbound, this object is a "If iscsiSsnDirection is Inbound, this object is a
skipping to change at page 57, line 4 skipping to change at page 57, line 15
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type of iSCSI session: "Type of iSCSI session:
normalSession - session is a normal iSCSI session normalSession - session is a normal iSCSI session
discoverySession - session is being used only for discovery." discoverySession - session is being used only for discovery."
REFERENCE REFERENCE
"RFC 3720, Section 12.21, SessionType" "RFC 3720, Section 12.21, SessionType"
::= { iscsiSessionAttributesEntry 12 } ::= { iscsiSessionAttributesEntry 12 }
iscsiSsnMaxOutstandingR2T OBJECT-TYPE iscsiSsnMaxOutstandingR2T OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "R2Ts" UNITS "R2Ts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of outstanding request-to-transmit "The maximum number of outstanding requests-to-transmit
(R2T)s per iSCSI task within this session." (R2Ts) per iSCSI task within this session."
REFERENCE REFERENCE
"RFC 3720, Section 12.17, MaxOutstandingR2T" "RFC 3720, Section 12.17, MaxOutstandingR2T"
::= { iscsiSessionAttributesEntry 13 } ::= { iscsiSessionAttributesEntry 13 }
iscsiSsnFirstBurstLength OBJECT-TYPE iscsiSsnFirstBurstLength OBJECT-TYPE
SYNTAX Unsigned32 (512..16777215) SYNTAX Unsigned32 (512..16777215)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 57, line 34 skipping to change at page 57, line 46
REFERENCE REFERENCE
"RFC 3720, Section 12.14, FirstBurstLength" "RFC 3720, Section 12.14, FirstBurstLength"
::= { iscsiSessionAttributesEntry 14 } ::= { iscsiSessionAttributesEntry 14 }
iscsiSsnMaxBurstLength OBJECT-TYPE iscsiSsnMaxBurstLength OBJECT-TYPE
SYNTAX Unsigned32 (512..16777215) SYNTAX Unsigned32 (512..16777215)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of bytes which can be sent within "The maximum number of bytes that can be sent within
a single sequence of Data-In or Data-Out PDUs." a single sequence of Data-In or Data-Out PDUs."
REFERENCE REFERENCE
"RFC 3720, Section 12.13, MaxBurstLength" "RFC 3720, Section 12.13, MaxBurstLength"
::= { iscsiSessionAttributesEntry 15 } ::= { iscsiSessionAttributesEntry 15 }
iscsiSsnConnectionNumber OBJECT-TYPE iscsiSsnConnectionNumber OBJECT-TYPE
SYNTAX Gauge32 (1..65535) SYNTAX Gauge32 (1..65535)
UNITS "connections" UNITS "connections"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of transport protocol connections that currently "The number of transport protocol connections that currently
belong to this session." belong to this session."
::= { iscsiSessionAttributesEntry 16 } ::= { iscsiSessionAttributesEntry 16 }
skipping to change at page 58, line 8 skipping to change at page 58, line 20
"The number of transport protocol connections that currently "The number of transport protocol connections that currently
belong to this session." belong to this session."
::= { iscsiSessionAttributesEntry 16 } ::= { iscsiSessionAttributesEntry 16 }
iscsiSsnAuthIdentity OBJECT-TYPE iscsiSsnAuthIdentity OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains a pointer to a row in the "This object contains a pointer to a row in the
IPS-AUTH MIB module which identifies the authentication IPS-AUTH MIB module that identifies the authentication
method being used on this session, as communicated method being used on this session, as communicated
during the login phase." during the login phase."
REFERENCE REFERENCE
"IPS-AUTH MIB" "IPS-AUTH MIB, RFC 4545"
::= { iscsiSessionAttributesEntry 17 } ::= { iscsiSessionAttributesEntry 17 }
iscsiSsnDataSequenceInOrder OBJECT-TYPE iscsiSsnDataSequenceInOrder OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"False indicates that iSCSI data PDU sequences may "False indicates that iSCSI data PDU sequences may
be transferred in any order. True indicates that be transferred in any order. True indicates that
data PDU sequences must be transferred using data PDU sequences must be transferred using
skipping to change at page 62, line 9 skipping to change at page 62, line 21
iscsiSsnCxnDigestErrors Counter32, iscsiSsnCxnDigestErrors Counter32,
iscsiSsnCxnTimeoutErrors Counter32 iscsiSsnCxnTimeoutErrors Counter32
} }
iscsiSsnCxnDigestErrors OBJECT-TYPE iscsiSsnCxnDigestErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "PDUs" UNITS "PDUs"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of PDUs which were received on the session and "The count of PDUs that were received on the session and
contained header or data digest errors. contained header or data digest errors.
If this counter has suffered a discontinuity, the time of the If this counter has suffered a discontinuity, the time of the
last discontinuity is indicated in iscsiSsnDiscontinuityTime." last discontinuity is indicated in iscsiSsnDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 6.7, Digest Errors" "RFC 3720, Section 6.7, Digest Errors"
::= { iscsiSessionCxnErrorStatsEntry 1 } ::= { iscsiSessionCxnErrorStatsEntry 1 }
iscsiSsnCxnTimeoutErrors OBJECT-TYPE iscsiSsnCxnTimeoutErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "connections" UNITS "connections"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of connections within this session "The count of connections within this session
which have been terminated due to timeout. that have been terminated due to timeout.
If this counter has suffered a discontinuity, the time of the If this counter has suffered a discontinuity, the time of the
last discontinuity is indicated in iscsiSsnDiscontinuityTime." last discontinuity is indicated in iscsiSsnDiscontinuityTime."
REFERENCE REFERENCE
"RFC 3720, Section 6.4, Connection Timeout Management" "RFC 3720, Section 6.4, Connection Timeout Management"
::= { iscsiSessionCxnErrorStatsEntry 2 } ::= { iscsiSessionCxnErrorStatsEntry 2 }
--********************************************************************** --**********************************************************************
iscsiConnection OBJECT IDENTIFIER ::= { iscsiObjects 11 } iscsiConnection OBJECT IDENTIFIER ::= { iscsiObjects 11 }
skipping to change at page 66, line 33 skipping to change at page 66, line 46
"This object identifies the iSCSI data "This object identifies the iSCSI data
digest scheme in use within this connection." digest scheme in use within this connection."
::= { iscsiConnectionAttributesEntry 13 } ::= { iscsiConnectionAttributesEntry 13 }
iscsiCxnRecvMarker OBJECT-TYPE iscsiCxnRecvMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether or not this connection "This object indicates whether or not this connection
is receiving markers in in its incoming data stream." is receiving markers in its incoming data stream."
REFERENCE REFERENCE
"RFC 3720, Appendix A." "RFC 3720, Appendix A."
::= { iscsiConnectionAttributesEntry 14 } ::= { iscsiConnectionAttributesEntry 14 }
iscsiCxnSendMarker OBJECT-TYPE iscsiCxnSendMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether or not this connection "This object indicates whether or not this connection
is inserting markers in in its outgoing data stream." is inserting markers in its outgoing data stream."
REFERENCE REFERENCE
"RFC 3720, Appendix A." "RFC 3720, Appendix A."
::= { iscsiConnectionAttributesEntry 15 } ::= { iscsiConnectionAttributesEntry 15 }
iscsiCxnVersionActive OBJECT-TYPE iscsiCxnVersionActive OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Active version number of the iSCSI specification negotiated "Active version number of the iSCSI specification negotiated
skipping to change at page 67, line 30 skipping to change at page 67, line 43
iscsiTgtLastIntrFailureAddrType, iscsiTgtLastIntrFailureAddrType,
iscsiTgtLastIntrFailureAddr iscsiTgtLastIntrFailureAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Sent when a login is failed by a target. "Sent when a login is failed by a target.
To avoid sending an excessive number of notifications due To avoid sending an excessive number of notifications due
to multiple errors counted, an SNMP agent implementing this to multiple errors counted, an SNMP agent implementing this
notification SHOULD NOT send more than 3 notifications of notification SHOULD NOT send more than 3 notifications of
this type in any 10 second time period." this type in any 10-second time period."
::= { iscsiNotifications 1 } ::= { iscsiNotifications 1 }
iscsiIntrLoginFailure NOTIFICATION-TYPE iscsiIntrLoginFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
iscsiIntrLoginFailures, iscsiIntrLoginFailures,
iscsiIntrLastFailureType, iscsiIntrLastFailureType,
iscsiIntrLastTgtFailureName, iscsiIntrLastTgtFailureName,
iscsiIntrLastTgtFailureAddrType, iscsiIntrLastTgtFailureAddrType,
iscsiIntrLastTgtFailureAddr iscsiIntrLastTgtFailureAddr
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Sent when a login is failed by a initiator. "Sent when a login is failed by an initiator.
To avoid sending an excessive number of notifications due To avoid sending an excessive number of notifications due
to multiple errors counted, an SNMP agent implementing this to multiple errors counted, an SNMP agent implementing this
notification SHOULD NOT send more than 3 notifications of notification SHOULD NOT send more than 3 notifications of
this type in any 10 second time period." this type in any 10-second time period."
::= { iscsiNotifications 2 } ::= { iscsiNotifications 2 }
iscsiInstSessionFailure NOTIFICATION-TYPE iscsiInstSessionFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
iscsiInstSsnFailures, iscsiInstSsnFailures,
iscsiInstLastSsnFailureType, iscsiInstLastSsnFailureType,
iscsiInstLastSsnRmtNodeName iscsiInstLastSsnRmtNodeName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Sent when an active session is failed by either the initiator "Sent when an active session is failed by either the initiator
or the target. or the target.
To avoid sending an excessive number of notifications due To avoid sending an excessive number of notifications due
to multiple errors counted, an SNMP agent implementing this to multiple errors counted, an SNMP agent implementing this
notification SHOULD NOT send more than 3 notifications of notification SHOULD NOT send more than 3 notifications of
this type in any 10 second time period." this type in any 10-second time period."
::= { iscsiNotifications 3 } ::= { iscsiNotifications 3 }
--********************************************************************** --**********************************************************************
-- Conformance Statements -- Conformance Statements
iscsiCompliances OBJECT IDENTIFIER ::= { iscsiConformance 1 } iscsiCompliances OBJECT IDENTIFIER ::= { iscsiConformance 1 }
iscsiGroups OBJECT IDENTIFIER ::= { iscsiConformance 2 } iscsiGroups OBJECT IDENTIFIER ::= { iscsiConformance 2 }
iscsiInstanceAttributesGroup OBJECT-GROUP iscsiInstanceAttributesGroup OBJECT-GROUP
skipping to change at page 71, line 23 skipping to change at page 71, line 36
::= { iscsiGroups 8 } ::= { iscsiGroups 8 }
iscsiTargetLogoutStatsGroup OBJECT-GROUP iscsiTargetLogoutStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiTgtLogoutNormals, iscsiTgtLogoutNormals,
iscsiTgtLogoutOthers iscsiTgtLogoutOthers
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
logout events between remote initiators to local targets." logout events between remote initiators and local targets."
::= { iscsiGroups 9 } ::= { iscsiGroups 9 }
iscsiTargetAuthGroup OBJECT-GROUP iscsiTargetAuthGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiTgtAuthRowStatus, iscsiTgtAuthRowStatus,
iscsiTgtAuthStorageType, iscsiTgtAuthStorageType,
iscsiTgtAuthIdentity iscsiTgtAuthIdentity
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 72, line 30 skipping to change at page 72, line 42
::= { iscsiGroups 12 } ::= { iscsiGroups 12 }
iscsiInitiatorLogoutStatsGroup OBJECT-GROUP iscsiInitiatorLogoutStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiIntrLogoutNormals, iscsiIntrLogoutNormals,
iscsiIntrLogoutOthers iscsiIntrLogoutOthers
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
logout events between local initiators to remote targets." logout events between local initiators and remote targets."
::= { iscsiGroups 13 } ::= { iscsiGroups 13 }
iscsiInitiatorAuthGroup OBJECT-GROUP iscsiInitiatorAuthGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiIntrAuthRowStatus, iscsiIntrAuthRowStatus,
iscsiIntrAuthStorageType, iscsiIntrAuthStorageType,
iscsiIntrAuthIdentity iscsiIntrAuthIdentity
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about all "A collection of objects providing information about all
remote targets that are initiators of the local system are remote targets that are initiators of the local system
authorized to access." that they are authorized to access."
::= { iscsiGroups 14 } ::= { iscsiGroups 14 }
iscsiSessionAttributesGroup OBJECT-GROUP iscsiSessionAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiSsnDirection, iscsiSsnDirection,
iscsiSsnInitiatorName, iscsiSsnInitiatorName,
iscsiSsnTargetName, iscsiSsnTargetName,
iscsiSsnTSIH, iscsiSsnTSIH,
iscsiSsnISID, iscsiSsnISID,
iscsiSsnInitiatorAlias, iscsiSsnInitiatorAlias,
skipping to change at page 74, line 51 skipping to change at page 75, line 16
"A collection of objects providing information about all "A collection of objects providing information about all
connections used by all sessions." connections used by all sessions."
::= { iscsiGroups 20 } ::= { iscsiGroups 20 }
iscsiTgtLgnNotificationsGroup NOTIFICATION-GROUP iscsiTgtLgnNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
iscsiTgtLoginFailure iscsiTgtLoginFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications which indicate a login "A collection of notifications that indicate a login
failure from a remote initiator to a local target." failure from a remote initiator to a local target."
::= { iscsiGroups 21 } ::= { iscsiGroups 21 }
iscsiIntrLgnNotificationsGroup NOTIFICATION-GROUP iscsiIntrLgnNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
iscsiIntrLoginFailure iscsiIntrLoginFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications which indicate a login "A collection of notifications that indicate a login
failure from a local initiator to a remote target." failure from a local initiator to a remote target."
::= { iscsiGroups 22 } ::= { iscsiGroups 22 }
iscsiSsnFlrNotificationsGroup NOTIFICATION-GROUP iscsiSsnFlrNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
iscsiInstSessionFailure iscsiInstSessionFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications which indicate session "A collection of notifications that indicate session
failures occurring after login." failures occurring after login."
::= { iscsiGroups 23 } ::= { iscsiGroups 23 }
--********************************************************************** --**********************************************************************
iscsiComplianceV1 MODULE-COMPLIANCE iscsiComplianceV1 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial version of compliance statement based on "Initial version of compliance statement based on
initial version of this MIB module. initial version of this MIB module.
skipping to change at page 79, line 15 skipping to change at page 79, line 15
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
iscsiPortalAttributesTable, iscsiTgtPortalAttributesTable, and iscsiPortalAttributesTable, iscsiTgtPortalAttributesTable, and
iscsiIntrPortalAttributes table can be used to add or remove IP iscsiIntrPortalAttributesTable can be used to add or remove IP
addresses to be used by iSCSI. addresses to be used by iSCSI.
iscsiTgtAuthAttributesTable entries can be added or removed, to iscsiTgtAuthAttributesTable entries can be added or removed, to
allow or disallow access to a target by an initiator. allow or disallow access to a target by an initiator.
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
skipping to change at page 80, line 11 skipping to change at page 80, line 11
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. IANA Considerations 9. IANA Considerations
9.1. OID Assignment The IANA has assigned a MIB OID number under the mib-2 branch for the
IANA is requested to make a MIB OID assignment under the mib-2 ISCSI-MIB.
branch.
10. Normative References 10. Normative References
[RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., and [RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M.,
E. Zeidner, "Internet Small Computer Systems Interface and E. Zeidner, "Internet Small Computer Systems
(iSCSI)", RFC 3720, March 2004. Interface (iSCSI)", RFC 3720, March 2004.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J. , [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
for Describing Simple Network Management Protocol (SNMP) Architecture for Describing Simple Network Management
Management Frameworks", STD 62, RFC 3411, December 2002. Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002.
[AUTHMIB] Bakke, M., and J. Muchow, "Definitions of Managed Objects [RFC4545] Bakke, M. and J. Muchow, "Definitions of Managed Objects
for User Identity Authorization", Work in Progress, draft- for IP Storage User Identity Authorization", RFC 4545,
ietf-ips-auth-mib-06.txt, January 2005. May 2006.
11. Informative References 11. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC2012] McCloghrie, K., "SNMPv2 Management Information Base for the [RFC4022] Raghunarayan, R., "Management Information Base for the
Transmission Control Protocol using SMIv2", RFC 2012, Transmission Control Protocol (TCP)", RFC 4022, March
November 1996. 2005.
[SCSIMIB] Hallak-Stamler, M., Bakke, M., McCloghrie, K., Lederman, Y., [RFC4455] Hallak-Stamler, M., Bakke, M., Lederman, Y., Krueger, M.,
and M. Krueger, "Definitions of Managed Objects for SCSI and K. McCloghrie, "Definition of Managed Objects for
Entities", Work in Progress, draft-ietf-ips-scsi-mib-06.txt, Small Computer System Interface (SCSI) Entities", RFC
August 2004. 4455, April 2006.
12. Acknowledgments 12. Acknowledgements
In addition to the authors, several people contributed to the In addition to the authors, several people contributed to the
development of this MIB module. Thanks especially to those who took development of this MIB module. Thanks especially to those who took
the time to participate in our weekly conference calls to build our the time to participate in our weekly conference calls to build our
requirements, object models, table structures, and attributes: John requirements, object models, table structures, and attributes: John
Hufferd, Tom McSweeney (IBM), Kevin Gibbons (Nishan Systems), Chad Hufferd, Tom McSweeney (IBM), Kevin Gibbons (Nishan Systems), Chad
Gregory (Intel), Jack Harwood (EMC), Hari Mudaliar (Adaptec), Ie Wei Gregory (Intel), Jack Harwood (EMC), Hari Mudaliar (Adaptec), Ie Wei
Njoo (Agilent), Lawrence Lamers (SAN Valley), Satish Mali (Stonefly Njoo (Agilent), Lawrence Lamers (SAN Valley), Satish Mali (Stonefly
Networks), and William Terrell (Troika). Networks), and William Terrell (Troika).
Special thanks to Tom McSweeney, Ie Wei Njoo, and Kevin Gibbons, who Special thanks to Tom McSweeney, Ie Wei Njoo, and Kevin Gibbons, who
wrote the descriptions for many of the tables and attributes in this wrote the descriptions for many of the tables and attributes in this
MIB module, to Ayman Ghanem for finding and suggesting changes for MIB module, to Ayman Ghanem for finding and suggesting changes for
many problems in this module, and to Keith McCloghrie for serving as many problems in this module, and to Keith McCloghrie for serving as
advisor to the team. advisor to the team.
Authors' Addresses Authors' Addresses
Mark Bakke Mark Bakke
Postal: Cisco Systems, Inc Cisco Systems, Inc
7900 International Drive, Suite 400 7900 International Drive, Suite 400
Bloomington, MN Bloomington, MN
USA 55425 USA 55425
E-mail: mbakke@cisco.com EMail: mbakke@cisco.com
Marjorie Krueger Marjorie Krueger
Postal: Hewlett-Packard Hewlett-Packard
Networked Storage Architecture Networked Storage Architecture
Networked Storage Solutions Org. Networked Storage Solutions Org.
8000 Foothills Blvd. 8000 Foothills Blvd.
Roseville, CA Roseville, CA
USA 95747 USA 95747
E-mail: marjorie_krueger@hp.com EMail: marjorie_krueger@hp.com
Tom McSweeney Tom McSweeney
Postal: IBM Corporation IBM Corporation
600 Park Offices Drive 600 Park Offices Drive
Research Triangle Park, NC Research Triangle Park, NC
USA 27709 USA 27709
E-mail: tommcs@us.ibm.com EMail: tommcs@us.ibm.com
James Muchow James Muchow
Postal: Qlogic Corp. Qlogic Corp.
6321 Bury Drive 6321 Bury Drive
Eden Prairie, MN Eden Prairie, MN
USA 55346 USA 55346
Email: james.muchow@qlogic.com EMail: james.muchow@qlogic.com
IPR Notice Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Notice
Copyright (C) The Internet Society (2005). This document is subject Acknowledgement
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an Funding for the RFC Editor function is provided by the IETF
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Administrative Support Activity (IASA).
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 165 change blocks. 
292 lines changed or deleted 291 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/