draft-ietf-storm-iscsimib-04.txt   rfc7147.txt 
INTERNET-DRAFT Mark Bakke
STORM Working Group Dell
Intended status: Proposed Standard Prakash Venkatesen
Expires: October 2013 HCL Technologies
Obsoletes: 4544 April 2, 2013
Definitions of Managed Objects for Internet Small Computer System Internet Engineering Task Force (IETF) M. Bakke
Interface (iSCSI) Request for Comments: 7147 Dell
draft-ietf-storm-iscsimib-04.txt Obsoletes: 4544 P. Venkatesen
Category: Standards Track HCL Technologies
ISSN: 2070-1721 April 2014
Status of this Memo Definitions of Managed Objects
for the Internet Small Computer System Interface (iSCSI)
This Internet-Draft is submitted to IETF in full conformance with the Abstract
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document defines a portion of the Management Information Base
Task Force (IETF), its areas, and its working groups. Note that (MIB) for use with network management protocols. In particular, it
other groups may also distribute working documents as Internet- defines objects for managing a client using the Internet Small
Drafts. Computer System Interface (iSCSI) protocol (SCSI over TCP).
Internet-Drafts are draft documents valid for a maximum of six months This document obsoletes RFC 4544.
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at This is an Internet Standards Track document.
http://www.ietf.org/shadow.html
This Internet-Draft will expire on October 2, 2013. This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7147.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Abstract
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols. In particular, it
defines objects for managing a client using the Internet Small
Computer System Interface (iSCSI) protocol (SCSI over TCP).
This document obsoletes RFC4544.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework.....................3 1. The Internet-Standard Management Framework ......................4
2. Introduction...................................................3 2. Introduction ....................................................4
3. Relationship to Other MIB Modules..............................3 3. Relationship to Other MIB Modules ...............................4
4. Relationship to SNMP Contexts..................................4 4. Relationship to SNMP Contexts ...................................5
5. Differences from RFC 4544......................................5 5. Differences from RFC 4544 .......................................5
6. Discussion.....................................................5 6. Discussion ......................................................6
6.1. iSCSI MIB Object Model....................................6 6.1. iSCSI MIB Object Model .....................................7
6.2. iSCSI MIB Table Structure.................................7 6.2. iSCSI MIB Table Structure ..................................8
6.3. iscsiInstance.............................................8 6.3. iscsiInstance ..............................................9
6.4. iscsiPortal...............................................8 6.4. iscsiPortal ................................................9
6.5. iscsiTargetPortal.........................................9 6.5. iscsiTargetPortal .........................................10
6.6. iscsiInitiatorPortal.....................................10 6.6. iscsiInitiatorPortal ......................................11
6.7. iscsiNode................................................10 6.7. iscsiNode .................................................12
6.8. iscsiTarget..............................................11 6.8. iscsiTarget ...............................................12
6.9. iscsiTgtAuthorization....................................11 6.9. iscsiTgtAuthorization .....................................12
6.10. iscsiInitiator..........................................11 6.10. iscsiInitiator ...........................................13
6.11. iscsiIntrAuthorization..................................12 6.11. iscsiIntrAuthorization ...................................13
6.12. iscsiSession............................................12 6.12. iscsiSession .............................................13
6.13. iscsiConnection.........................................12 6.13. iscsiConnection ..........................................14
6.14. IP Addresses and TCP Port Numbers.......................13 6.14. IP Addresses and TCP Port Numbers ........................14
6.15. Descriptors: Using OIDs in Place of Enumerated Types....13 6.15. Descriptors: Using OIDs in Place of Enumerated Types .....15
6.16. Notifications...........................................13 6.16. Notifications ............................................15
7. MIB Definition................................................14 7. MIB Definition .................................................16
8. Security Considerations.......................................85 8. Security Considerations ........................................88
9. IANA Considerations...........................................86 9. IANA Considerations ............................................89
10. References...................................................87 10. References ....................................................89
10.1. Normative References....................................87 10.1. Normative References .....................................89
10.2. Informative References..................................88 10.2. Informative References ...................................91
11. Acknowledgments..............................................89 11. Acknowledgments ...............................................91
1. The Internet-Standard Management Framework 1. 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
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
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].
2. Introduction
This document defines a MIB module for iSCSI [RFC7143], used to
manage devices that implement the iSCSI protocol. It obsoletes RFC
4544 [RFC4544].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
2. Introduction 3. Relationship to Other MIB Modules
This document defines a MIB module for iSCSI [RFCcccc], used to
manage devices that implement the iSCSI protocol. It obsoletes RFC
4544 [RFC4544].
3. 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
[RFC4455] and the TCP MIB module [RFC4022], and makes use of the IP [RFC4455] and the TCP MIB module [RFC4022], and it makes use of the
Storage (IPS) Identity Authentication MIB module [RFC4545]. Here is IP Storage (IPS) Identity Authentication MIB module [RFC4545]. Here
how these modules are related: is 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
module. In this case, the iscsiNodeTransportType attribute MIB module. In this case, the iscsiNodeTransportType
points to the SCSI transport object within the SCSI MIB attribute points to the SCSI transport object within the
module, which in turn contains an attribute that points SCSI MIB module, which in turn contains an attribute that
back to the iscsiNode. In this way, a management station points back to the iscsiNode. In this way, a management
can navigate between the two MIB modules. In systems where station can navigate between the two MIB modules. In
a SCSI layer is not present, such as within an iSCSI proxy systems where a SCSI layer is not present, such as within
device, the iscsiNodeTransportType attribute points to the an iSCSI proxy device, the iscsiNodeTransportType
appropriate corresponding object within the appropriate attribute points to the appropriate corresponding object
MIB, or is left blank. within the appropriate MIB or is left blank.
TCP MIB Each iSCSI connection is related to one transport-level TCP MIB Each iSCSI connection is related to one transport-level
connection. Currently, iSCSI uses only TCP; the iSCSI connection. Currently, iSCSI uses only TCP; the iSCSI
connection is related to a TCP connection using its normal connection is related to a TCP connection using its
(protocol, source address, source port, destination normal (protocol, source address, source port,
address, destination port) 5-tuple. destination address, destination port) 5-tuple.
AUTH MIB Each iSCSI node that serves a target role can have a list AUTH MIB Each iSCSI node that serves a target role can have a list
of authorized initiators. Each of the entries in this list of authorized initiators. Each of the entries in this
points to an identity within the IPS Identity list 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
MIB module to which the initiator should attempt to IPS-AUTH MIB module to which the initiator should attempt
establish sessions. The Auth MIB module includes to establish sessions. The IPS-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], 2579 This MIB module imports objects from RFCs 2578 [RFC2578], 2579
[RFC2579], 2580 [RFC2580], and 3411 [RFC3411]. It also imports [RFC2579], 2580 [RFC2580], and 3411 [RFC3411]. It also imports
textual conventions from the INET-ADDRESS-MIB [RFC4001]. textual conventions from the INET-ADDRESS-MIB [RFC4001].
4. Relationship to SNMP Contexts 4. 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 partition of a device to one or more SNMP virtual or physical partition of a device to one or more SNMP
contexts, without having to do so for each individual node, portal, contexts, without having to do so for each individual node, portal,
and session row. and session row.
5. Differences from RFC 4544 5. Differences from RFC 4544
[RFCcccc] updates several RFCs, including [RFC3720]. This document [RFC7143] updates several RFCs, including [RFC3720]. This document
updates the iSCSI MIB correspondingly. The document uses updates the iSCSI MIB correspondingly. The document uses
iSCSIProtocolLevel as defined in [RFCssss]. It obsoletes [RFC4544]. iSCSIProtocolLevel as defined in [RFC7144]. It obsoletes [RFC4544].
Below is a brief description of the changes: Below is a brief description of the changes.
. Added iscsiInstXNodeArchitecture to InstanceAttributes - Added iscsiInstXNodeArchitecture to InstanceAttributes.
. Added iscsiSsnTaskReporting of type BITS to SessionAttributes - Added iscsiSsnTaskReporting of type BITS to SessionAttributes.
. Added iscsiSsnProtocolLevel to SessionAttributes - Added iscsiSsnProtocolLevel to SessionAttributes.
. Deprecated the marker objects - Deprecated the marker objects.
. Fixed the errata to [RFC4544] - Fixed the errata to [RFC4544].
. Added NOP counters at iSCSI session scope for heartbeat tracking
. Added port number to the iscsiTgtLoginFailure and
iscsiIntrLoginFailure notifications, and to the last failure info
in iscsiInitiatorAttributesEntry
. Added description string to the iSCSI portal
. Added iscsiInstSsnTgtUnmappedErrors to support "Target Unmapped"
session failure reporting in the iscsiInstSessionFailure
notification
. Added iscsiTgtLogoutCxnClosed and iscsiTgtLogoutCxnRemoved which
maintain the count of Logout Command PDUs received by the target
with reason codes 1 and 2 respectively
. Changed the conformance statements to match the above
6. Discussion - Added NOP counters at iSCSI session scope for heartbeat tracking.
- Added port number to the iscsiTgtLoginFailure and
iscsiIntrLoginFailure notifications, and to the last failure info
in iscsiInitiatorAttributesEntry.
- Added description string to the iSCSI portal.
- Added iscsiInstSsnTgtUnmappedErrors to support "Target Unmapped"
session failure reporting in the iscsiInstSessionFailure
notification.
- Added iscsiTgtLogoutCxnClosed and iscsiTgtLogoutCxnRemoved, which
maintain the count of Logout Command PDUs received by the target
with reason codes 1 and 2, respectively.
- Changed the conformance statements to match the above.
6. Discussion
This MIB module structure supplies configuration, fault, and This MIB module structure supplies configuration, fault, and
statistics information for iSCSI devices [RFCcccc]. It is structured statistics information for iSCSI devices [RFC7143]. 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 reflects only iSCSI objects. This module does not contain
information about the SCSI-layer attributes of a device. If a SCSI information about the SCSI-layer attributes of a device. If a SCSI
layer is present, the SCSI MIB module [RFC4455] layer is present, the SCSI MIB module [RFC4455] may be used to manage
may be used to manage SCSI information for a device. 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,
object, followed by a discussion of the actual table structure within followed by a discussion of the actual table structure within the
the objects. 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
"contains" all of the other objects. "contains" all of the other objects.
iscsiInstance iscsiInstance
-- A distinct iSCSI entity within the managed system. -- A distinct iSCSI entity within the managed system.
iscsiPortal iscsiPortal
-- An IP address used by this instance -- An IP address used by this instance.
iscsiTargetPortal iscsiTargetPortal
-- Contains portal information relevant when the portal -- Contains portal information relevant when the portal
-- is used to listen for connections to its targets. -- is used to listen for connections to its targets.
iscsiInitiatorPortal iscsiInitiatorPortal
-- Contains portal information relevant when the portal -- Contains portal information relevant when the portal
-- is used to initiate connections to other targets. -- is used to initiate connections to other targets.
iscsiNode iscsiNode
-- An iSCSI node can act as an initiator, a target, or both. -- An iSCSI node can act as an initiator, a target, or both.
-- Contains generic (non-role-specific) information. -- Contains generic (non-role-specific) information.
iscsiTarget iscsiTarget
-- Target-specific iSCSI node information. -- Target-specific iSCSI node information.
iscsiTgtAuth iscsiTgtAuth
-- A list of initiator identities that are allowed -- A list of initiator identities that are allowed
-- access to this target. -- access to this target.
iscsiInitiator iscsiInitiator
-- 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
-- The session's direction may be Inbound (outside -- target. The session's direction may be Inbound
-- initiator to our target) or Outbound (our initiator to -- (an outside initiator to the target represented by
-- an outside target). -- this node) or Outbound (the initiator represented by
iscsiConnection -- this node to an outside target).
-- An active TCP connection within an iSCSI session. iscsiConnection
-- 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 whether 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
iscsiInstanceSsnErrorStatsTable iscsiInstanceSsnErrorStatsTable
-- Counts abnormal session terminations -- Counts abnormal session terminations
iscsiPortal iscsiPortal
iscsiPortalAttributesTable iscsiPortalAttributesTable
iscsiTargetPortal iscsiTargetPortal
iscsiTgtPortalAttributesTable iscsiTgtPortalAttributesTable
iscsiInitiatorPortal iscsiInitiatorPortal
iscsiIntrPortalAttributesTable iscsiIntrPortalAttributesTable
iscsiNode iscsiNode
iscsiNodeAttributesTable iscsiNodeAttributesTable
iscsiTarget iscsiTarget
iscsiTargetAttributesTable iscsiTargetAttributesTable
iscsiTargetLoginStatsTable iscsiTargetLoginStatsTable
-- Counts successful and unsuccessful logins -- Counts successful and unsuccessful logins
iscsiTargetLogoutStatsTable iscsiTargetLogoutStatsTable
-- Counts normal and abnormal logouts -- Counts normal and abnormal logouts
iscsiTgtAuthorization iscsiTgtAuthorization
iscsiTgtAuthAttributesTable iscsiTgtAuthAttributesTable
iscsiInitiator iscsiInitiator
iscsiInitiatorAttributesTable iscsiInitiatorAttributesTable
iscsiInitiatorLoginStatsTable iscsiInitiatorLoginStatsTable
-- Counts successful and unsuccessful logins -- Counts successful and unsuccessful logins
iscsiInitiatorLogoutStatsTable iscsiInitiatorLogoutStatsTable
-- Counts normal and abnormal logouts -- Counts normal and abnormal logouts
iscsiIntrAuthorization iscsiIntrAuthorization
iscsiIntrAuthAttributesTable iscsiIntrAuthAttributesTable
iscsiSession iscsiSession
iscsiSessionAttributesTable iscsiSessionAttributesTable
iscsiSessionStatsTable iscsiSessionStatsTable
-- Performance-related counts (requests, responses, bytes) -- Performance-related counts (requests, responses, bytes)
iscsiSessionCxnErrorStatsTable iscsiSessionCxnErrorStatsTable
-- Counts digest errors, connection errors, etc. -- Counts digest errors, connection errors, etc.
iscsiConnection iscsiConnection
iscsiConnectionAttributesTable iscsiConnectionAttributesTable
Note that this module does not attempt to count everything that could Note that this module does not attempt to count everything that could
be counted; it is designed to include only those counters that would be counted; it is designed to include only those counters that would
be useful for identifying performance, security, and fault problems be useful for identifying performance, security, and fault problems
from a management station. from a management station.
6.3. iscsiInstance 6.3. iscsiInstance
The iscsiInstanceAttributesTable is the primary table of the iSCSI The iscsiInstanceAttributesTable is the primary table of the iSCSI
MIB module. Every table entry in this module is "owned" by exactly MIB module. Every table entry in this module is "owned" by exactly
one iSCSI instance; all other table entries in the module include one iSCSI instance; all other table entries in the module include
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
skipping to change at page 8, line 36 skipping to change at page 9, line 36
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 and The iscsiInstanceSsnErrorStatsTable augments the attributes table and
provides statistics on session failures due to digest, connection, or provides statistics on session failures due to digest, connection, or
iSCSI format errors. iSCSI format errors.
6.4. iscsiPortal 6.4. iscsiPortal
The iscsiPortalAttributesTable lists iSCSI portals that can be used The iscsiPortalAttributesTable lists iSCSI portals that can be used
to listen for connections to targets, to initiate connections to to listen for connections to targets, to initiate connections to
other targets, or to do 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 when a row is
is created or destroyed in the iscsiPortalAttributesTable, or if the created or destroyed in the iscsiPortalAttributesTable or when 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.
When created by a management station, the iscsiPortalRoles attribute When created by a management station, the iscsiPortalRoles attribute
is used to control row creation in the initiator and target portal is used to control row creation in the initiator and target portal
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 [RFCcccc]. An outbound connection (when an shutdown as specified in [RFC7143]. 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 its (when an iscsiTargetPortal is deleted) matches the portal if its
iscsiCxnLocalAddr matches the iscsiPortalAddr, and its iscsiCxnLocalAddr matches the iscsiPortalAddr and if 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 that 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
portal group aggregation tag; iSCSI target portals within this portal group aggregation tag; iSCSI target portals that are within
instance sharing the same tag can contain connections within the same this instance and share the same tag can contain connections within
session. the same session.
This table will be empty for iSCSI instances that contain only This table will be empty for iSCSI instances that contain only
initiators (such as iSCSI host driver implementations). initiators (such as iSCSI host driver implementations).
Many implementations use the same target portal tag and protocol port Many implementations use the same Target Portal Group Tag and
for all nodes accessed via a portal. These implementations will protocol port for all nodes accessed via a portal. These
create a single row in the iscsiTgtPortalAttributeTable, with an implementations will create a single row in the
iscsiNodeIndex of zero. iscsiTgtPortalAttributeTable, with an 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
skipping to change at page 10, line 44 skipping to change at page 12, line 5
Many implementations use the same initiator tag for all nodes Many implementations use the same initiator tag for all nodes
accessing targets via a given portal. These implementations will accessing targets via a given portal. These implementations will
create a single row in iscsiIntrPortalAttributeTable, with an create a single row in iscsiIntrPortalAttributeTable, with an
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.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 that 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
skipping to change at page 11, line 19 skipping to change at page 12, line 30
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 that 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.
This table is augmented by the iscsiTargetLoginStatsTable and the This table is augmented by the iscsiTargetLoginStatsTable and the
iscsiTargetLogoutStatsTable, which count the numbers of normal and iscsiTargetLogoutStatsTable, which count the numbers of normal and
abnormal logins and logouts to this target. abnormal logins and logouts to this target.
6.9. iscsiTgtAuthorization 6.9. iscsiTgtAuthorization
The iscsiTgtAuthAttributesTable contains an entry for each initiator The iscsiTgtAuthAttributesTable contains an entry for each initiator
identifier that will be allowed to access the target under which it identifier that will be allowed to access the target under which it
appears. Each entry contains a RowPointer to a user identity in the appears. Each entry contains a RowPointer to a user identity in the
IPS Authorization MIB module, which contains the name, address, and IPS Authorization MIB module, which contains the name, address, and
credential information necessary to authenticate the initiator. credential information necessary to authenticate the initiator.
6.10. iscsiInitiator 6.10. iscsiInitiator
The iscsiInitiatorAttributesTable contains a list of initiator- The iscsiInitiatorAttributesTable contains a list of initiator-
specific attributes for iSCSI nodes. Each entry in this table uses specific attributes for iSCSI nodes. Each entry in this table uses
the same index values as its corresponding iscsiNode entry. the same index values as its corresponding iscsiNode entry.
Most implementations will include a single entry in this table, Most implementations will include a single entry in this table,
regardless of the number of physical interfaces the initiator may regardless of the number of physical interfaces the initiator may
use. use.
This table is augmented by the iscsiInitiatorLoginStatsTable and the This table is augmented by the iscsiInitiatorLoginStatsTable and the
iscsiInitiatorLogoutStatsTable, which count the numbers of normal and iscsiInitiatorLogoutStatsTable, which count the numbers of normal and
abnormal logins and logouts from this initiator. abnormal logins and logouts from this initiator.
6.11. iscsiIntrAuthorization 6.11. iscsiIntrAuthorization
The iscsiIntrAuthAttributesTable contains an entry for each target The iscsiIntrAuthAttributesTable contains an entry for each target
identifier to which the initiator is configured to establish a identifier to which the initiator is configured to establish a
session. session.
Each entry contains a RowPointer to a user identity in the IPS Each entry contains a RowPointer to a user identity in the IPS
Authorization MIB module, which contains the name, address, and Authorization MIB module, which contains the name, address, and
credential information necessary to identify (for discovery purposes) credential information necessary to identify (for discovery purposes)
and authenticate the target. and authenticate the target.
6.12. iscsiSession 6.12. iscsiSession
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 exist 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
skipping to change at page 12, line 50 skipping to change at page 14, line 19
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 sides 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 [RFC4022]. 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 that Attributes that make use of these object identities have a value that
is an Object Identifier (OID) instead of an enumerated type. These is an Object Identifier (OID) instead of an enumerated type. These
OIDs can indicate either the object identities defined in this module OIDs can indicate either the object identities defined in this module
or object identities defined elsewhere, such as in an enterprise MIB or object identities defined elsewhere, such as in an enterprise MIB
module. Those implementations that add their own digest methods module. Those implementations that add their own digest methods
should also define a corresponding object identity for each of these should also define a corresponding object identity for each of these
methods within their own enterprise MIB module, and return its OID methods within their own enterprise MIB module, and return its OID
whenever 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
skipping to change at page 14, line 26 skipping to change at page 16, line 5
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 10 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 Definition 7. MIB Definition
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,
Unsigned32, Counter32, Counter64, Gauge32, Unsigned32, Counter32, Counter64, Gauge32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, TruthValue, RowPointer, TimeStamp, RowStatus, TEXTUAL-CONVENTION, TruthValue, RowPointer, TimeStamp, RowStatus,
skipping to change at page 14, line 51 skipping to change at page 16, line 30
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 "201210030000Z" -- October 3, 2012 LAST-UPDATED "201402180000Z" -- February 18, 2014
ORGANIZATION "IETF STORage Maintenance (STORM) Working Group" ORGANIZATION "IETF STORage Maintenance (STORM) Working Group"
CONTACT-INFO " CONTACT-INFO "
Working Group Email : storm@ietf.org Working Group Email: storm@ietf.org
Attn: Mark Bakke Attn: Mark Bakke
Cisco Systems, Inc Dell
Email: mbakke@cisco.com Email: mark_bakke@dell.com
Prakash Venkatesen Prakash Venkatesen
HCL Technologies HCL Technologies
Email: prakashvn@hcl.com" Email: prakashvn@hcl.com"
DESCRIPTION DESCRIPTION
"This module defines management information specific "This module defines management information specific
to the iSCSI protocol. to the iSCSI protocol.
Copyright (c) 2012 IETF Trust and the persons identified as Copyright (c) 2014 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)." (http://trustee.ietf.org/license-info)."
REVISION "201210030000Z" REVISION "201402180000Z"
DESCRIPTION DESCRIPTION
"Second version of the iSCSI Protocol MIB Module. "Second version of the iSCSI Protocol MIB Module.
[RFCcccc] makes several updates to [RFC3720]. This RFC 7143 makes several updates to [RFC3720]. This
version makes corresponding updates to the MIB module. version makes corresponding updates to the MIB module.
This MIB module published as RFC xxxx." This MIB module published as RFC 7147."
REVISION "200605220000Z" REVISION "200605220000Z"
DESCRIPTION DESCRIPTION
"Initial version of the iSCSI Protocol MIB module. "Initial version of the iSCSI Protocol MIB module.
This MIB module published as RFC 4544." This MIB module published as RFC 4544."
::= { mib-2 142 } ::= { 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"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used to define the transport "This data type is used to define the transport
protocols that will carry iSCSI PDUs. protocols that will carry iSCSI PDUs.
Protocol numbers are assigned by IANA. A Protocol numbers are assigned by IANA. A
current list of all assignments is available from current list of all assignments is available from
<http://www.iana.org/assignments/protocol-numbers/>." <http://www.iana.org/assignments/protocol-numbers/>."
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.
skipping to change at page 16, line 26 skipping to change at page 17, line 50
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 RFCcccc). digests to be compliant with RFC 7143).
CRC32c - require a CRC32C digest." CRC32c - require a CRC32C digest."
REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest"
REFERENCE
"RFC 7143, Section 13.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 cccc iSCSI name with the properties described in RFC 7143,
section 4.2.7.1, and encoded as specified in RFC cccc Section 4.2.7.1, and encoded as specified in RFC 7143,
section 4.2.7.2. A zero-length string indicates the Section 4.2.7.2. A zero-length string indicates the
absence of an iSCSI name." absence of an iSCSI name."
REFERENCE REFERENCE
"RFC cccc, Section 4.2.7, iSCSI Names." "RFC 7143, Section 4.2.7, 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 }
iscsiHdrIntegrityNone OBJECT-IDENTITY iscsiHdrIntegrityNone OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authoritative identifier when no integrity "The authoritative identifier when no integrity
scheme for the header is being used." scheme for the header is being used."
REFERENCE REFERENCE
skipping to change at page 17, line 14 skipping to change at page 18, line 39
iscsiDescriptors OBJECT IDENTIFIER ::= { iscsiAdmin 1 } iscsiDescriptors OBJECT IDENTIFIER ::= { iscsiAdmin 1 }
iscsiHeaderIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 1 } iscsiHeaderIntegrityTypes OBJECT IDENTIFIER ::= { iscsiDescriptors 1 }
iscsiHdrIntegrityNone OBJECT-IDENTITY iscsiHdrIntegrityNone OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The authoritative identifier when no integrity "The authoritative identifier when no integrity
scheme for the header is being used." scheme for the header is being used."
REFERENCE REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest" "RFC 7143, Section 13.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 the header is CRC32c." scheme for the header is CRC32c."
REFERENCE REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest" "RFC 7143, Section 13.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 the data is being used." scheme for the data is being used."
REFERENCE REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest" "RFC 7143, Section 13.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 the data is CRC32c." scheme for the data is CRC32c."
REFERENCE REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest" "RFC 7143, Section 13.1, HeaderDigest and DataDigest"
::= { iscsiDataIntegrityTypes 2 } ::= { iscsiDataIntegrityTypes 2 }
--********************************************************************** --**********************************************************************
iscsiInstance OBJECT IDENTIFIER ::= { iscsiObjects 1 } iscsiInstance OBJECT IDENTIFIER ::= { iscsiObjects 1 }
-- Instance Attributes Table -- Instance Attributes Table
iscsiInstanceAttributesTable OBJECT-TYPE iscsiInstanceAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiInstanceAttributesEntry SYNTAX SEQUENCE OF IscsiInstanceAttributesEntry
skipping to change at page 19, line 25 skipping to change at page 20, line 51
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum version number of the iSCSI specification "The minimum version number of the iSCSI specification
such that this iSCSI instance supports this minimum such that this iSCSI instance supports this minimum
value, the maximum value indicated by the corresponding value, the maximum value indicated by the corresponding
instance in iscsiInstVersionMax, and all versions in instance in iscsiInstVersionMax, and all versions in
between." between."
REFERENCE REFERENCE
"RFC cccc, Section 11.12, Login Request" "RFC 7143, Section 11.12, Login Request"
::= { iscsiInstanceAttributesEntry 3 } ::= { iscsiInstanceAttributesEntry 3 }
iscsiInstVersionMax OBJECT-TYPE iscsiInstVersionMax OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum version number of the iSCSI specification "The maximum version number of the iSCSI specification
such that this iSCSI instance supports this maximum such that this iSCSI instance supports this maximum
value, the minimum value indicated by the corresponding value, the minimum value indicated by the corresponding
instance in iscsiInstVersionMin, and all versions in instance in iscsiInstVersionMin, and all versions in
between." between."
REFERENCE REFERENCE
"RFC cccc, Section 11.12, Login Request" "RFC 7143, Section 11.12, Login Request"
::= { iscsiInstanceAttributesEntry 4 } ::= { iscsiInstanceAttributesEntry 4 }
iscsiInstVendorID OBJECT-TYPE iscsiInstVendorID OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string describing the manufacturer of the "A UTF-8 string describing the manufacturer of the
implementation of this instance." implementation of this instance."
::= { iscsiInstanceAttributesEntry 5 } ::= { iscsiInstanceAttributesEntry 5 }
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; the string 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
skipping to change at page 21, line 6 skipping to change at page 22, line 34
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 failed. If this counter has to this instance has failed. 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 cccc, Section 13.1, HeaderDigest and DataDigest" "RFC 7143, Section 13.1, HeaderDigest and DataDigest"
::= { iscsiInstanceAttributesEntry 10 } ::= { iscsiInstanceAttributesEntry 10 }
iscsiInstLastSsnFailureType OBJECT-TYPE iscsiInstLastSsnFailureType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The counter object in the iscsiInstanceSsnErrorStatsTable "The counter object in the iscsiInstanceSsnErrorStatsTable
that was incremented when the last session failure occurred. that was incremented when the last session failure occurred.
skipping to change at page 22, line 7 skipping to change at page 23, line 36
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 declaring the "A UTF-8 string set by the manufacturer declaring the
details of its iSCSI node architecture to the remote details of its iSCSI node architecture to the remote
endpoint. These details may include, but are not limited endpoint. These details may include, but are not limited
to, iSCSI vendor software, firmware, or hardware versions, to, iSCSI vendor software, firmware, or hardware versions,
the OS version, or hardware architecture. the OS version, or hardware architecture.
The format of this string is determined solely by the The format of this string is determined solely by the
manufacturer, and is for informational purposes only. manufacturer; the string is for informational purposes only.
It is unrelated to the iSCSI specification version numbers." It is unrelated to the iSCSI specification version numbers."
REFERENCE REFERENCE
"[RFCcccc], Section 13.26, X#NodeArchitecture" "RFC 7143, Section 13.26, X#NodeArchitecture"
::= { iscsiInstanceAttributesEntry 14 } ::= { iscsiInstanceAttributesEntry 14 }
-- 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
"Statistics regarding the occurrences of error types "Statistics regarding the occurrences of error types
skipping to change at page 22, line 52 skipping to change at page 24, line 32
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 that failed due to receipt of "The count of sessions that 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 cccc, Section 7.8, Digest Errors" "RFC 7143, Section 7.8, 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 that failed due to a sequence "The count of sessions that 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 cccc, Section 7.5, Connection Timeout Management" "RFC 7143, Section 7.5, 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 that failed due to receipt of "The count of sessions that failed due to receipt of
a PDU that 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 cccc, Section 7.7, Format Errors" "RFC 7143 Section 7.7, Format Errors"
::= { iscsiInstanceSsnErrorStatsEntry 3 } ::= { iscsiInstanceSsnErrorStatsEntry 3 }
iscsiInstSsnTgtUnmappedErrors OBJECT-TYPE iscsiInstSsnTgtUnmappedErrors 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 that failed due to the target "The count of sessions that failed due to the target
becoming unmapped. If this counter has becoming unmapped. If this counter has
skipping to change at page 25, line 16 skipping to change at page 26, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP. When adding a row to removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set. this table, all non-Index/RowStatus objects must be set.
When the value of this object is 'active', the values of When the value of this object is 'active', the values of
the other objects in this table cannot be changed. the other objects in this table cannot be changed.
Rows may be discarded using RowStatus. Rows may be discarded using RowStatus.
Note that creating a row in this table will typically Note that creating a row in this table will typically
cause the agent to create one or more rows in cause the agent to create one or more rows in the
iscsiTgtPortalAttributesTable and/or iscsiTgtPortalAttributesTable and/or the
iscsiIntrPortalAttributesTable." iscsiIntrPortalAttributesTable."
::= { iscsiPortalAttributesEntry 2 } ::= { iscsiPortalAttributesEntry 2 }
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
one of the above tables." one of the above tables."
::= { iscsiPortalAttributesEntry 3 } ::= { iscsiPortalAttributesEntry 3 }
iscsiPortalAddrType OBJECT-TYPE iscsiPortalAddrType OBJECT-TYPE
skipping to change at page 26, line 36 skipping to change at page 28, line 19
DEFVAL { 6 } -- TCP DEFVAL { 6 } -- TCP
::= { iscsiPortalAttributesEntry 6 } ::= { iscsiPortalAttributesEntry 6 }
iscsiPortalMaxRecvDataSegLength OBJECT-TYPE iscsiPortalMaxRecvDataSegLength OBJECT-TYPE
SYNTAX Unsigned32 (512..16777215) SYNTAX Unsigned32 (512..16777215)
UNITS "bytes" UNITS "bytes"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum PDU length this portal can receive. "The maximum PDU length this portal can receive.
This may be constrained by hardware characteristics This may be constrained by hardware characteristics,
and individual implementations may choose not to and individual implementations may choose not to
allow this object to be changed." allow this object to be changed."
REFERENCE REFERENCE
"RFC cccc, Section 13.12, MaxRecvDataSegmentLength" "RFC 7143, Section 13.12, MaxRecvDataSegmentLength"
DEFVAL { 8192 } DEFVAL { 8192 }
::= { iscsiPortalAttributesEntry 7 } ::= { iscsiPortalAttributesEntry 7 }
iscsiPortalPrimaryHdrDigest OBJECT-TYPE iscsiPortalPrimaryHdrDigest OBJECT-TYPE
SYNTAX IscsiDigestMethod SYNTAX IscsiDigestMethod
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The preferred header digest for this portal." "The preferred header digest for this portal."
DEFVAL { crc32c } DEFVAL { crc32c }
skipping to change at page 27, line 39 skipping to change at page 29, line 24
::= { iscsiPortalAttributesEntry 11 } ::= { iscsiPortalAttributesEntry 11 }
iscsiPortalRecvMarker OBJECT-TYPE iscsiPortalRecvMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This object indicates whether or not this portal will "This object indicates whether or not this portal will
request markers in its incoming data stream." request markers in its incoming data stream."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
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
"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 (e.g. not created via created through an external process (e.g., not created via
this MIB) may have a storage type of readOnly or permanent. this MIB) may have a storage type of 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 }
::= { iscsiPortalAttributesEntry 13 } ::= { iscsiPortalAttributesEntry 13 }
iscsiPortalDescr OBJECT-TYPE iscsiPortalDescr 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
describe the iSCSI portal. When only a single instance describe the iSCSI portal. When only a single instance
is present, this object may be set to the zero-length is present, this object may be set to the zero-length
string; with multiple iSCSI portals, it may be used in string; with multiple iSCSI portals, it may be used in
an implementation-dependent manner to describe the an implementation-dependent manner to describe the
respective portal, and could include information such as respective portal, and could include information such as
HBA model, description and version or software driver and Host Bus Adapter (HBA) model, description, and version, or
version." software driver and version."
::= { iscsiPortalAttributesEntry 14 } ::= { iscsiPortalAttributesEntry 14 }
--********************************************************************** --**********************************************************************
iscsiTargetPortal OBJECT IDENTIFIER ::= { iscsiObjects 3 } iscsiTargetPortal OBJECT IDENTIFIER ::= { iscsiObjects 3 }
-- Target Portal Attributes Table -- Target Portal Attributes Table
iscsiTgtPortalAttributesTable OBJECT-TYPE iscsiTgtPortalAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiTgtPortalAttributesEntry SYNTAX SEQUENCE OF IscsiTgtPortalAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 29, line 50 skipping to change at page 31, line 36
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 the 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 cccc, Section 4.4.1, iSCSI Architectural Model" "RFC 7143, Section 4.4.1, iSCSI Architecture 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
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 31, line 21 skipping to change at page 33, line 7
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 the portal is used as "The portal's aggregation tag when the portal is used as
an initiator portal. Multiple-connection sessions may an initiator 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 cccc, Section 4.4.1, iSCSI Architectural Model" "RFC 7143, Section 4.4.1, iSCSI Architecture Model"
::= { iscsiIntrPortalAttributesEntry 2 } ::= { iscsiIntrPortalAttributesEntry 2 }
--********************************************************************** --**********************************************************************
iscsiNode OBJECT IDENTIFIER ::= { iscsiObjects 5 } iscsiNode OBJECT IDENTIFIER ::= { iscsiObjects 5 }
-- Node Attributes Table -- Node Attributes Table
iscsiNodeAttributesTable OBJECT-TYPE iscsiNodeAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiNodeAttributesEntry SYNTAX SEQUENCE OF IscsiNodeAttributesEntry
skipping to change at page 33, line 4 skipping to change at page 34, line 41
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
identifier, but can be displayed by the system's user identifier, but it can be displayed by the system's user
interface in a list of initiators and/or targets to interface in a list of initiators and/or targets to
which it is connected. which it is connected.
If no alias exists, the value is a zero-length string." If no alias exists, the value is a zero-length string."
REFERENCE REFERENCE
"RFC cccc, Section 13.6, TargetAlias, 13.7, InitiatorAlias" "RFC 7143, Sections 13.6 (TargetAlias) and 13.7
(InitiatorAlias)"
::= { iscsiNodeAttributesEntry 3 } ::= { iscsiNodeAttributesEntry 3 }
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
skipping to change at page 33, line 49 skipping to change at page 35, line 39
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, RFC 4455 section 9, scsiTransportTypes" "SCSI-MIB, RFC 4455, Section 9, Object Definitions,
scsiTransportTypes"
::= { iscsiNodeAttributesEntry 5 } ::= { iscsiNodeAttributesEntry 5 }
iscsiNodeInitialR2T OBJECT-TYPE iscsiNodeInitialR2T OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the InitialR2T preference for this "This object indicates the InitialR2T preference for this
node: node:
true = YES, true = YES,
skipping to change at page 34, line 12 skipping to change at page 36, line 4
iscsiNodeInitialR2T OBJECT-TYPE iscsiNodeInitialR2T OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the InitialR2T preference for this "This object indicates the InitialR2T preference for this
node: node:
true = YES, true = YES,
false = will try to negotiate NO, will accept YES " false = will try to negotiate NO, will accept YES "
REFERENCE REFERENCE
"RFC cccc, Section 13.10, InitialR2T" "RFC 7143, Section 13.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 cccc, Section 13.11, ImmediateData" "RFC 7143, Section 13.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 requests-to-transmit (R2Ts) "Maximum number of outstanding requests-to-transmit (R2Ts)
allowed per iSCSI task." allowed per iSCSI task."
REFERENCE REFERENCE
"RFC cccc, Section 13.17, MaxOutstandingR2T" "RFC 7143, Section 13.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
to/from this node." to/from this node."
REFERENCE REFERENCE
"RFC cccc, Section 13.14, FirstBurstLength" "RFC 7143, Section 13.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 that 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 cccc, Section 13.13, MaxBurstLength" "RFC 7143, Section 13.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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of connections allowed in each "The maximum number of connections allowed in each
session to and/or from this node." session to and/or from this node."
REFERENCE REFERENCE
"RFC cccc, Section 13.2, MaxConnections" "RFC 7143, Section 13.2, MaxConnections"
DEFVAL { 1 } DEFVAL { 1 }
::= { iscsiNodeAttributesEntry 11 } ::= { iscsiNodeAttributesEntry 11 }
iscsiNodeDataSequenceInOrder OBJECT-TYPE iscsiNodeDataSequenceInOrder OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DataSequenceInOrder preference of this node. "The DataSequenceInOrder preference of this node.
False (=No) indicates that iSCSI data PDU sequences may False (=No) indicates that iSCSI data PDU sequences may
be transferred in any order. True (=Yes) indicates that be transferred in any order. True (=Yes) indicates that
data PDU sequences must be transferred using data PDU sequences must be transferred using
continuously increasing offsets, except during continuously increasing offsets, except during
error recovery." error recovery."
REFERENCE REFERENCE
"RFC cccc, Section 13.19, DataSequenceInOrder" "RFC 7143, Section 13.19, DataSequenceInOrder"
DEFVAL { true } DEFVAL { true }
::= { iscsiNodeAttributesEntry 12 } ::= { iscsiNodeAttributesEntry 12 }
iscsiNodeDataPDUInOrder OBJECT-TYPE iscsiNodeDataPDUInOrder OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DataPDUInOrder preference of this node. "The DataPDUInOrder preference of this node.
False (=No) indicates that iSCSI data PDUs within sequences False (=No) indicates that iSCSI data PDUs within sequences
skipping to change at page 36, line 10 skipping to change at page 38, line 4
iscsiNodeDataPDUInOrder OBJECT-TYPE iscsiNodeDataPDUInOrder OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The DataPDUInOrder preference of this node. "The DataPDUInOrder preference of this node.
False (=No) indicates that iSCSI data PDUs within sequences False (=No) indicates that iSCSI data PDUs within sequences
may be in any order. True (=Yes) indicates that data PDUs may be in any order. True (=Yes) indicates that data PDUs
within sequences must be at continuously increasing within sequences must be at continuously increasing
addresses, with no gaps or overlay between PDUs." addresses, with no gaps or overlay between PDUs."
REFERENCE REFERENCE
"RFC cccc, Section 13.18, DataPDUInOrder" "RFC 7143, Section 13.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 cccc, Section 13.15, DefaultTime2Wait" "RFC 7143, Section 13.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 cccc, Section 13.16, DefaultTime2Retain" "RFC 7143, Section 13.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.
This object is designed to accommodate future error recovery 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 cccc, Section 13.20, ErrorRecoveryLevel" "RFC 7143, Section 13.20, ErrorRecoveryLevel"
DEFVAL { 0 } DEFVAL { 0 }
::= { 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
skipping to change at page 37, line 40 skipping to change at page 39, line 35
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 (e.g. not created via this MIB module). external process (e.g., not created via this MIB module).
Conceptual rows having the value 'permanent' need not allow Conceptual rows having the value 'permanent' need not allow
Write access to any columnar objects in the row. Write access to any columnar objects in 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
skipping to change at page 39, line 4 skipping to change at page 40, line 48
iscsiTgtLoginFailures OBJECT-TYPE iscsiTgtLoginFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "failed login attempts" UNITS "failed login attempts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of times a login attempt to this "This object counts the number of times a login attempt to this
local target has failed. local target has failed.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiTargetAttributesEntry 1 } ::= { iscsiTargetAttributesEntry 1 }
iscsiTgtLastFailureTime OBJECT-TYPE iscsiTgtLastFailureTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp of the most recent failure of a login attempt "The timestamp of the most recent failure of a login attempt
to this target. A value of zero indicates that no such to this target. A value of zero indicates that no such
failures have occurred since the last system boot." failures have occurred since the last system boot."
::= { iscsiTargetAttributesEntry 2 } ::= { iscsiTargetAttributesEntry 2 }
skipping to change at page 39, line 29 skipping to change at page 41, line 24
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. If no such failures relevant instance was incremented. If no such failures
have occurred since the last system boot, this attribute have occurred since the last system boot, this attribute
will have the value 0.0. A value of 0.0 may also be used will have the value 0.0. A value of 0.0 may also be used
to indicate a type that is not represented by any of to indicate 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. If no such failures have occurred since login attempt. If no such failures have occurred since
the last system boot, this value is a zero-length string." the last system boot, this value is a zero-length string."
::= { 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.
The value 'dns' is not allowed. If no such failures have The value 'dns' is not allowed. If no such failures have
occurred since the last system boot, this value is zero." occurred since the last system boot, this value is zero."
::= { iscsiTargetAttributesEntry 5 } ::= { iscsiTargetAttributesEntry 5 }
iscsiTgtLastIntrFailureAddr OBJECT-TYPE iscsiTgtLastIntrFailureAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An Internet Network Address, of the type specified by "An Internet Network Address, of the type specified by
the object iscsiTgtLastIntrFailureAddrType, giving the the object iscsiTgtLastIntrFailureAddrType, giving the
host address of the initiator that failed the last login host address of the initiator that failed the last login
attempt. If no such failures have occurred since the last attempt. If no such failures have occurred since the last
system boot, this value is a zero-length string." system boot, this value is a zero-length string."
::= { iscsiTargetAttributesEntry 6 } ::= { iscsiTargetAttributesEntry 6 }
iscsiTgtLastIntrFailurePort OBJECT-TYPE iscsiTgtLastIntrFailurePort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport protocol port number used by the initiator "The transport protocol port number used by the initiator
that failed the last login attempt. If no such failures that failed the last login attempt. If no such failures
have occurred since the last system boot, this value is a have occurred since the last system boot, this value is a
zero-length string." zero-length string."
::= { iscsiTargetAttributesEntry 7 } ::= { iscsiTargetAttributesEntry 7 }
-- 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
skipping to change at page 41, line 21 skipping to change at page 43, line 19
UNITS "successful logins" UNITS "successful logins"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Login Response PDUs with status "The count of Login Response PDUs with status
0x0000, Accept Login, transmitted by this 0x0000, Accept Login, transmitted by this
target. target.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.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 that were transmitted "The number of Login Response PDUs that were transmitted
by this target and that 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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.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"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Login Response PDUs with status class 0x01, "The count of Login Response PDUs with status class 0x01,
Redirection, transmitted by this target. Redirection, transmitted by this target.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiTargetLoginStatsEntry 3 } ::= { iscsiTargetLoginStatsEntry 3 }
iscsiTgtLoginAuthorizeFails OBJECT-TYPE iscsiTgtLoginAuthorizeFails 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 0x0202, "The count of Login Response PDUs with status 0x0202,
Forbidden Target, transmitted by this target. Forbidden Target, transmitted by this target.
If this counter is incremented, an iscsiTgtLoginFailure If this counter is incremented, an iscsiTgtLoginFailure
skipping to change at page 42, line 18 skipping to change at page 44, line 17
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Login Response PDUs with status 0x0202, "The count of Login Response PDUs with status 0x0202,
Forbidden Target, transmitted by this target. Forbidden Target, 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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times a target has effectively refused a "The number of times a target has effectively refused a
login because the parameter negotiation failed. login because the parameter negotiation failed.
skipping to change at page 43, line 14 skipping to change at page 45, line 14
-- Target Logout Stats Table -- Target Logout Stats Table
iscsiTargetLogoutStatsTable OBJECT-TYPE iscsiTargetLogoutStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiTargetLogoutStatsEntry SYNTAX SEQUENCE OF IscsiTargetLogoutStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When a target receives a Logout command, it responds "When a target receives a Logout command, it responds
with a Logout Response that carries a status code. with a Logout Response that carries a status code.
This table contains counters for both normal and This table contains counters for both normal and
abnormal logout requests received by this target." abnormal Logout Requests received by this target."
::= { iscsiTarget 3 } ::= { iscsiTarget 3 }
iscsiTargetLogoutStatsEntry OBJECT-TYPE iscsiTargetLogoutStatsEntry OBJECT-TYPE
SYNTAX IscsiTargetLogoutStatsEntry SYNTAX IscsiTargetLogoutStatsEntry
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 that were received by this target." PDUs that were received by this target."
AUGMENTS { iscsiTargetAttributesEntry } AUGMENTS { iscsiTargetAttributesEntry }
skipping to change at page 43, line 46 skipping to change at page 45, line 45
SYNTAX Counter32 SYNTAX Counter32
UNITS "normal logouts" UNITS "normal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs received by this target, "The count of Logout Command PDUs received by this target,
with reason code 0 (closes the session). with reason code 0 (closes the session).
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiTargetLogoutStatsEntry 1 } ::= { iscsiTargetLogoutStatsEntry 1 }
iscsiTgtLogoutOthers OBJECT-TYPE iscsiTgtLogoutOthers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "abnormal logouts" UNITS "abnormal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs received by this target, "The count of Logout Command PDUs received by this target,
with any reason code other than 0. with any reason code other than 0.
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiTargetLogoutStatsEntry 2 } ::= { iscsiTargetLogoutStatsEntry 2 }
iscsiTgtLogoutCxnClosed OBJECT-TYPE iscsiTgtLogoutCxnClosed OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "abnormal logouts" UNITS "abnormal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs received by this target, "The count of Logout Command PDUs received by this target,
with reason code 1 (closes the connection). with reason code 1 (closes the connection).
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiTargetLogoutStatsEntry 3 } ::= { iscsiTargetLogoutStatsEntry 3 }
iscsiTgtLogoutCxnRemoved OBJECT-TYPE iscsiTgtLogoutCxnRemoved OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "abnormal logouts" UNITS "abnormal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs received by this target, "The count of Logout Command PDUs received by this target,
with reason code 2 (removes the connection). with reason code 2 (removes the connection).
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiTargetLogoutStatsEntry 4 } ::= { iscsiTargetLogoutStatsEntry 4 }
--********************************************************************** --**********************************************************************
iscsiTgtAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 7 } iscsiTgtAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 7 }
-- Target Authorization Attributes Table -- Target Authorization Attributes Table
iscsiTgtAuthAttributesTable OBJECT-TYPE iscsiTgtAuthAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiTgtAuthAttributesEntry SYNTAX SEQUENCE OF IscsiTgtAuthAttributesEntry
skipping to change at page 45, line 51 skipping to change at page 48, line 4
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This field allows entries to be dynamically added and "This field allows entries to be dynamically added and
removed from this table via SNMP. When adding a row to removed from this table via SNMP. When adding a row to
this table, all non-Index/RowStatus objects must be set. this table, all non-Index/RowStatus objects must be set.
When the value of this object is 'active', the values of When the value of this object is 'active', the values of
the other objects in this table cannot be changed. the other objects in this table cannot be changed.
Rows may be discarded using RowStatus." Rows may be discarded using RowStatus."
::= { 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, RFC 4545, 7.3, ipsAuthIdentAttributeEntry" "IPS-AUTH MIB, RFC 4545, Section 7.3, ipsAuthIdentity"
::= { 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 (e.g. not created via created through an external process (e.g., not created via
this MIB) may have a storage type of readOnly or permanent. this MIB) may have a storage type of 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 }
::= { iscsiTgtAuthAttributesEntry 4 } ::= { iscsiTgtAuthAttributesEntry 4 }
--********************************************************************** --**********************************************************************
iscsiInitiator OBJECT IDENTIFIER ::= { iscsiObjects 8 } iscsiInitiator OBJECT IDENTIFIER ::= { iscsiObjects 8 }
skipping to change at page 47, line 29 skipping to change at page 49, line 31
SYNTAX Counter32 SYNTAX Counter32
UNITS "failed logins" UNITS "failed logins"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of times a login attempt from "This object counts the number of times a login attempt from
this local initiator has failed. this local initiator has failed.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorAttributesEntry 1 } ::= { iscsiInitiatorAttributesEntry 1 }
iscsiIntrLastFailureTime OBJECT-TYPE iscsiIntrLastFailureTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The timestamp of the most recent failure of a login attempt "The timestamp of the most recent failure of a login attempt
from this initiator. A value of zero indicates that no such from this initiator. A value of zero indicates that no such
failures have occurred since the last system boot." failures have occurred since the last system boot."
::= { iscsiInitiatorAttributesEntry 2 } ::= { iscsiInitiatorAttributesEntry 2 }
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. If no such failures have relevant instance was incremented. If no such failures have
occurred since the last system boot, this attribute will occurred since the last system boot, this attribute will
have the value 0.0. A value of 0.0 may also be used to have the value 0.0. A value of 0.0 may also be used to
indicate a type that is not represented by any of indicate 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. If no such failures have occurred the last login attempt. If no such failures have occurred
since the last system boot, this value is a zero-length string." since the last system boot, this value is a zero-length string."
::= { iscsiInitiatorAttributesEntry 4 } ::= { iscsiInitiatorAttributesEntry 4 }
iscsiIntrLastTgtFailureAddrType OBJECT-TYPE iscsiIntrLastTgtFailureAddrType 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 iscsiIntrLastTgtFailureAddr. corresponding instance of the iscsiIntrLastTgtFailureAddr.
skipping to change at page 49, line 4 skipping to change at page 51, line 8
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The transport protocol port number used by the target "The transport protocol port number used by the target
that failed the last login attempt. that failed the last login attempt.
If no such failures have occurred since the last system boot, If no such failures have occurred since the last system boot,
this value is a zero-length string." this value is a zero-length string."
::= { iscsiInitiatorAttributesEntry 7 } ::= { iscsiInitiatorAttributesEntry 7 }
-- Initiator Login Stats Table -- Initiator Login Stats Table
iscsiInitiatorLoginStatsTable OBJECT-TYPE iscsiInitiatorLoginStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiInitiatorLoginStatsEntry SYNTAX SEQUENCE OF IscsiInitiatorLoginStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of counters which keep track of the results of "A table of counters that keep track of the results of
this initiator's login attempts." this initiator's login attempts."
::= { iscsiInitiator 2 } ::= { iscsiInitiator 2 }
iscsiInitiatorLoginStatsEntry OBJECT-TYPE iscsiInitiatorLoginStatsEntry OBJECT-TYPE
SYNTAX IscsiInitiatorLoginStatsEntry SYNTAX IscsiInitiatorLoginStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing counters of each result "An entry (row) containing counters of each result
of this initiator's login attempts." of this initiator's login attempts."
skipping to change at page 49, line 44 skipping to change at page 51, line 49
SYNTAX Counter32 SYNTAX Counter32
UNITS "successful logins" UNITS "successful logins"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Login Response PDUs with status "The count of Login Response PDUs with status
0x0000, Accept Login, received by this initiator. 0x0000, Accept Login, received by this initiator.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 1 } ::= { iscsiInitiatorLoginStatsEntry 1 }
iscsiIntrLoginOtherFailRsps OBJECT-TYPE iscsiIntrLoginOtherFailRsps 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 received by this "The count of Login Response PDUs received by this
initiator with any status code not counted in the initiator with any status code not counted in the
objects below. objects below.
If this counter has suffered a discontinuity, the time of the If this counter has suffered a discontinuity, the time of the
skipping to change at page 50, line 10 skipping to change at page 52, line 16
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 received by this "The count of Login Response PDUs received by this
initiator with any status code not counted in the initiator with any status code not counted in the
objects below. objects below.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 2 } ::= { iscsiInitiatorLoginStatsEntry 2 }
iscsiIntrLoginRedirectRsps OBJECT-TYPE iscsiIntrLoginRedirectRsps 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 class 0x01, "The count of Login Response PDUs with status class 0x01,
Redirection, received by this initiator. Redirection, received by this initiator.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 3 } ::= { iscsiInitiatorLoginStatsEntry 3 }
iscsiIntrLoginAuthFailRsps OBJECT-TYPE iscsiIntrLoginAuthFailRsps 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 class 0x201, "The count of Login Response PDUs with status class 0x201,
Authentication Failed, received by this initiator. Authentication Failed, received by this initiator.
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 4 } ::= { iscsiInitiatorLoginStatsEntry 4 }
iscsiIntrLoginAuthenticateFails OBJECT-TYPE iscsiIntrLoginAuthenticateFails 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 times the initiator has aborted a "The number of times the initiator has aborted a
login because the target could not be authenticated. login because the target could not be authenticated.
No response is generated. No response is generated.
If this counter is incremented, an iscsiIntrLoginFailure If this counter is incremented, an iscsiIntrLoginFailure
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 5 } ::= { iscsiInitiatorLoginStatsEntry 5 }
iscsiIntrLoginNegotiateFails OBJECT-TYPE iscsiIntrLoginNegotiateFails 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 times the initiator has aborted a "The number of times the initiator has aborted a
login because parameter negotiation with the target login because parameter negotiation with the target
failed. failed.
No response is generated. No response is generated.
If this counter is incremented, an iscsiIntrLoginFailure If this counter is incremented, an iscsiIntrLoginFailure
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 cccc, Section 7.12, Negotiation Failures" "RFC 7143, Section 7.12, Negotiation Failures"
::= { iscsiInitiatorLoginStatsEntry 6 } ::= { iscsiInitiatorLoginStatsEntry 6 }
iscsiIntrLoginAuthorizeFails OBJECT-TYPE iscsiIntrLoginAuthorizeFails 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 0x0202, "The count of Login Response PDUs with status 0x0202,
Forbidden Target, received by this initiator. Forbidden Target, received by this initiator.
If this counter is incremented, an iscsiIntrLoginFailure If this counter is incremented, an iscsiIntrLoginFailure
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 cccc, Section 11.13.5, Status-Class and Status-Detail" "RFC 7143, Section 11.13.5, Status-Class and Status-Detail"
::= { iscsiInitiatorLoginStatsEntry 7 } ::= { iscsiInitiatorLoginStatsEntry 7 }
-- 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 to send a Logout command, the target "When an initiator attempts to send a Logout command, the target
skipping to change at page 52, line 43 skipping to change at page 54, line 49
SYNTAX Counter32 SYNTAX Counter32
UNITS "normal logouts" UNITS "normal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs generated by this initiator "The count of Logout Command PDUs generated by this initiator
with reason code 0 (closes the session). with reason code 0 (closes the session).
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiInitiatorLogoutStatsEntry 1 } ::= { iscsiInitiatorLogoutStatsEntry 1 }
iscsiIntrLogoutOthers OBJECT-TYPE iscsiIntrLogoutOthers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "abnormal logouts" UNITS "abnormal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs generated by this initiator "The count of Logout Command PDUs generated by this initiator
with any status code other than 0. with any status code other than 0.
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."
skipping to change at page 53, line 8 skipping to change at page 55, line 15
SYNTAX Counter32 SYNTAX Counter32
UNITS "abnormal logouts" UNITS "abnormal logouts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The count of Logout Command PDUs generated by this initiator "The count of Logout Command PDUs generated by this initiator
with any status code other than 0. with any status code other than 0.
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 cccc, Section 11.14.1, Reason Code" "RFC 7143, Section 11.14.1, Reason Code"
::= { iscsiInitiatorLogoutStatsEntry 2 } ::= { iscsiInitiatorLogoutStatsEntry 2 }
--********************************************************************** --**********************************************************************
iscsiIntrAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 9 } iscsiIntrAuthorization OBJECT IDENTIFIER ::= { iscsiObjects 9 }
-- Initiator Authorization Attributes Table -- Initiator Authorization Attributes Table
iscsiIntrAuthAttributesTable OBJECT-TYPE iscsiIntrAuthAttributesTable OBJECT-TYPE
skipping to change at page 54, line 31 skipping to change at page 56, line 39
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, RFC 4545, 7.3, ipsAuthInstanceAttributeEntry" "IPS-AUTH MIB, RFC 4545, Section 7.3, ipsAuthIdentity"
::= { 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 (e.g. not created via created through an external process (e.g., not created via
this MIB) may have a storage type of readOnly or permanent. this MIB) may have a storage type of 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 }
skipping to change at page 57, line 37 skipping to change at page 59, line 48
contain a zero-length string." contain a zero-length string."
::= { iscsiSessionAttributesEntry 5 } ::= { iscsiSessionAttributesEntry 5 }
iscsiSsnTSIH OBJECT-TYPE iscsiSsnTSIH OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The target-defined identification handle for this session." "The target-defined identification handle for this session."
REFERENCE REFERENCE
"RFC cccc, Section 11.12.6, TSIH" "RFC 7143, Section 11.12.6, TSIH"
::= { iscsiSessionAttributesEntry 6 } ::= { iscsiSessionAttributesEntry 6 }
iscsiSsnISID OBJECT-TYPE iscsiSsnISID OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(6)) SYNTAX OCTET STRING (SIZE(6))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The initiator-defined portion of the iSCSI Session ID." "The initiator-defined portion of the iSCSI Session ID."
REFERENCE REFERENCE
"RFC cccc, Section 11.12.5, ISID" "RFC 7143, Section 11.12.5, ISID"
::= { iscsiSessionAttributesEntry 7 } ::= { iscsiSessionAttributesEntry 7 }
iscsiSsnInitiatorAlias OBJECT-TYPE iscsiSsnInitiatorAlias OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string that gives the alias communicated by the "A UTF-8 string that gives the alias communicated by the
initiator end of the session during the login phase. initiator end of the session during the login phase.
If no alias exists, the value is a zero-length string." If no alias exists, the value is a zero-length string."
REFERENCE REFERENCE
"RFC cccc, Section 13.7, InitiatorAlias" "RFC 7143, Section 13.7, InitiatorAlias"
::= { iscsiSessionAttributesEntry 8 } ::= { iscsiSessionAttributesEntry 8 }
iscsiSsnTargetAlias OBJECT-TYPE iscsiSsnTargetAlias OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A UTF-8 string that gives the alias communicated by the "A UTF-8 string that gives the alias communicated by the
target end of the session during the login phase. target end of the session during the login phase.
If no alias exists, the value is a zero-length string." If no alias exists, the value is a zero-length string."
REFERENCE REFERENCE
"RFC cccc, Section 13.6, TargetAlias" "RFC 7143, Section 13.6, TargetAlias"
::= { iscsiSessionAttributesEntry 9 } ::= { iscsiSessionAttributesEntry 9 }
iscsiSsnInitialR2T OBJECT-TYPE iscsiSsnInitialR2T OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If set to true, indicates that the initiator must wait "If set to true, indicates that the initiator must wait
for an R2T before sending to the target. If set to false, for an R2T before sending to the target. If set to false,
the initiator may send data immediately, within limits set the initiator may send data immediately, within limits set
by iscsiSsnFirstBurstLength and the expected data transfer by iscsiSsnFirstBurstLength and the expected data transfer
length of the request." length of the request."
REFERENCE REFERENCE
"RFC cccc, Section 13.10, InitialR2T" "RFC 7143, Section 13.10, InitialR2T"
::= { iscsiSessionAttributesEntry 10 } ::= { iscsiSessionAttributesEntry 10 }
iscsiSsnImmediateData OBJECT-TYPE iscsiSsnImmediateData OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the initiator and target have agreed to "Indicates whether the initiator and target have agreed to
support immediate data on this session." support immediate data on this session."
REFERENCE REFERENCE
"RFC cccc, Section 13.11, ImmediateData" "RFC 7143, Section 13.11, ImmediateData"
::= { iscsiSessionAttributesEntry 11 } ::= { iscsiSessionAttributesEntry 11 }
iscsiSsnType OBJECT-TYPE iscsiSsnType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
normalSession(1), normalSession(1),
discoverySession(2) discoverySession(2)
} }
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."
skipping to change at page 59, line 15 skipping to change at page 61, line 28
normalSession(1), normalSession(1),
discoverySession(2) discoverySession(2)
} }
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 cccc, Section 13.21, SessionType" "RFC 7143, Section 13.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 requests-to-transmit "The maximum number of outstanding requests-to-transmit
(R2Ts) per iSCSI task within this session." (R2Ts) per iSCSI task within this session."
REFERENCE REFERENCE
"RFC cccc, Section 13.17, MaxOutstandingR2T" "RFC 7143, Section 13.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
"The maximum length supported for unsolicited data sent "The maximum length supported for unsolicited data sent
within this session." within this session."
REFERENCE REFERENCE
"RFC cccc, Section 13.14, FirstBurstLength" "RFC 7143, Section 13.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 that 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 cccc, Section 13.13, MaxBurstLength" "RFC 7143, Section 13.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 60, line 24 skipping to change at page 62, line 39
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 that identifies the authentication IPS-AUTH MIB module that identifies the authentication
identity being used on this session, as communicated identity being used on this session, as communicated
during the login phase." during the login phase."
REFERENCE REFERENCE
"IPS-AUTH MIB, RFC 4545, 7.3, ipsAuthInstanceAttributeEntry" "IPS-AUTH MIB, RFC 4545, Section 7.3, ipsAuthIdentity"
::= { 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 60, line 37 skipping to change at page 63, line 4
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
continuously increasing offsets, except during continuously increasing offsets, except during
error recovery." error recovery."
REFERENCE REFERENCE
"RFC cccc, Section 13.19, DataSequenceInOrder" "RFC 7143, Section 13.19, DataSequenceInOrder"
::= { iscsiSessionAttributesEntry 18 } ::= { iscsiSessionAttributesEntry 18 }
iscsiSsnDataPDUInOrder OBJECT-TYPE iscsiSsnDataPDUInOrder 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 PDUs within sequences "False indicates that iSCSI data PDUs within sequences
may be in any order. True indicates that data PDUs may be in any order. True indicates that data PDUs
within sequences must be at continuously increasing within sequences must be at continuously increasing
addresses, with no gaps or overlay between PDUs. addresses, with no gaps or overlay between PDUs.
Default is true." Default is true."
REFERENCE REFERENCE
"RFC cccc, Section 13.18, DataPDUInOrder" "RFC 7143, Section 13.18, DataPDUInOrder"
::= { iscsiSessionAttributesEntry 19 } ::= { iscsiSessionAttributesEntry 19 }
iscsiSsnErrorRecoveryLevel OBJECT-TYPE iscsiSsnErrorRecoveryLevel OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The level of error recovery negotiated between "The level of error recovery negotiated between
the initiator and the target. Higher numbers the initiator and the target. Higher numbers
represent more detailed recovery schemes." represent more detailed recovery schemes."
REFERENCE REFERENCE
"RFC cccc, Section 13.20, ErrorRecoveryLevel" "RFC 7143, Section 13.20, ErrorRecoveryLevel"
::= { iscsiSessionAttributesEntry 20 } ::= { iscsiSessionAttributesEntry 20 }
iscsiSsnDiscontinuityTime OBJECT-TYPE iscsiSsnDiscontinuityTime 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 session's counters at which any one or more of this session's counters
suffered a discontinuity. suffered a discontinuity.
skipping to change at page 61, line 39 skipping to change at page 64, line 6
of SysUpTime." of SysUpTime."
::= { iscsiSessionAttributesEntry 21 } ::= { iscsiSessionAttributesEntry 21 }
iscsiSsnProtocolLevel OBJECT-TYPE iscsiSsnProtocolLevel OBJECT-TYPE
SYNTAX Unsigned32 (0..31) SYNTAX Unsigned32 (0..31)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The iSCSI protocol level negotiated for this session." "The iSCSI protocol level negotiated for this session."
REFERENCE REFERENCE
"RFC ssss, Section 7.1.1, iSCSIProtocolLevel" "RFC 7144, Section 7.1.1, iSCSIProtocolLevel"
DEFVAL { 1 } DEFVAL { 1 }
::= { iscsiSessionAttributesEntry 22 } ::= { iscsiSessionAttributesEntry 22 }
iscsiSsnTaskReporting OBJECT-TYPE iscsiSsnTaskReporting OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
taskReportingRfc3720(0), taskReportingRfc3720(0),
taskReportingResponseFence(1), taskReportingResponseFence(1),
taskReportingFastAbort(2) taskReportingFastAbort(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This key is used to negotiate the task completion reporting "This key is used to negotiate the task completion reporting
semantics from the SCSI target. semantics from the SCSI target.
Default value is taskReportingRfc3720." Default value is taskReportingRfc3720."
REFERENCE REFERENCE
"RFC cccc, Section 13.23, Task Reporting" "RFC 7143, Section 13.23, TaskReporting"
::= { iscsiSessionAttributesEntry 23 } ::= { iscsiSessionAttributesEntry 23 }
-- Session Stats Table -- Session Stats Table
iscsiSessionStatsTable OBJECT-TYPE iscsiSessionStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiSessionStatsEntry SYNTAX SEQUENCE OF IscsiSessionStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of general iSCSI traffic counters for each of the "A list of general iSCSI traffic counters for each of the
skipping to change at page 63, line 51 skipping to change at page 66, line 17
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."
::= { iscsiSessionStatsEntry 4 } ::= { iscsiSessionStatsEntry 4 }
iscsiSsnLCTxDataOctets OBJECT-TYPE iscsiSsnLCTxDataOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Low Capacity shadow object of iscsiSsnTxDataOctets "A Low-Capacity shadow object of iscsiSsnTxDataOctets
for those systems which are accessible via SNMPv1 only. for those systems that are accessible via SNMPv1 only.
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."
::= { iscsiSessionStatsEntry 5 } ::= { iscsiSessionStatsEntry 5 }
iscsiSsnLCRxDataOctets OBJECT-TYPE iscsiSsnLCRxDataOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A Low Capacity shadow object of iscsiSsnRxDataOctets "A Low-Capacity shadow object of iscsiSsnRxDataOctets
for those systems which are accessible via SNMPv1 only. for those systems which are accessible via SNMPv1 only.
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."
::= { iscsiSessionStatsEntry 6 } ::= { iscsiSessionStatsEntry 6 }
iscsiSsnNopReceivedPDUs OBJECT-TYPE iscsiSsnNopReceivedPDUs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "PDUs" UNITS "PDUs"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 65, line 29 skipping to change at page 67, line 45
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 that 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.
This counter is most likely provided when the error-recovery- This counter is most likely provided when the error-recovery
level is 1 or 2" level is 1 or 2"
REFERENCE REFERENCE
"RFC cccc, Section 7.8, Digest Errors" "RFC 7143, Section 7.8, 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
that 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.
This counter is most likely provided when the error-recovery- This counter is most likely provided when the error-recovery
level is 2" level is 2"
REFERENCE REFERENCE
"RFC cccc, Section 7.5, Connection Timeout Management" "RFC 7143, Section 7.5, Connection Timeout Management"
::= { iscsiSessionCxnErrorStatsEntry 2 } ::= { iscsiSessionCxnErrorStatsEntry 2 }
--********************************************************************** --**********************************************************************
iscsiConnection OBJECT IDENTIFIER ::= { iscsiObjects 11 } iscsiConnection OBJECT IDENTIFIER ::= { iscsiObjects 11 }
-- Connection Attributes Table -- Connection Attributes Table
iscsiConnectionAttributesTable OBJECT-TYPE iscsiConnectionAttributesTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiConnectionAttributesEntry SYNTAX SEQUENCE OF IscsiConnectionAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of connections belonging to each iSCSI instance "A list of connections belonging to each iSCSI instance
skipping to change at page 69, line 12 skipping to change at page 71, line 31
iscsiCxnMaxRecvDataSegLength OBJECT-TYPE iscsiCxnMaxRecvDataSegLength 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 data payload size supported for command "The maximum data payload size supported for command
or data PDUs able to be received on this connection." or data PDUs able to be received on this connection."
REFERENCE REFERENCE
"RFC cccc, Section 13.12, MaxRecvDataSegmentLength" "RFC 7143, Section 13.12, MaxRecvDataSegmentLength"
::= { iscsiConnectionAttributesEntry 10 } ::= { iscsiConnectionAttributesEntry 10 }
iscsiCxnMaxXmitDataSegLength OBJECT-TYPE iscsiCxnMaxXmitDataSegLength 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 data payload size supported for command "The maximum data payload size supported for command
or data PDUs to be sent on this connection." or data PDUs to be sent on this connection."
REFERENCE REFERENCE
"RFC cccc, Section 13.12, MaxRecvDataSegmentLength" "RFC 7143, Section 13.12, MaxRecvDataSegmentLength"
::= { iscsiConnectionAttributesEntry 11 } ::= { iscsiConnectionAttributesEntry 11 }
iscsiCxnHeaderIntegrity OBJECT-TYPE iscsiCxnHeaderIntegrity OBJECT-TYPE
SYNTAX IscsiDigestMethod SYNTAX IscsiDigestMethod
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the iSCSI header "This object identifies the iSCSI header
digest scheme in use within this connection." digest scheme in use within this connection."
::= { iscsiConnectionAttributesEntry 12 } ::= { iscsiConnectionAttributesEntry 12 }
skipping to change at page 70, line 4 skipping to change at page 72, line 24
::= { iscsiConnectionAttributesEntry 13 } ::= { iscsiConnectionAttributesEntry 13 }
iscsiCxnRecvMarker OBJECT-TYPE iscsiCxnRecvMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This object indicates whether or not this connection "This object indicates whether or not this connection
is receiving markers in its incoming data stream." is receiving markers in its incoming data stream."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
::= { iscsiConnectionAttributesEntry 14 } ::= { iscsiConnectionAttributesEntry 14 }
iscsiCxnSendMarker OBJECT-TYPE iscsiCxnSendMarker OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"This object indicates whether or not this connection "This object indicates whether or not this connection
is inserting markers in its outgoing data stream." is inserting markers in its outgoing data stream."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
::= { 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
on this connection." on this connection."
REFERENCE REFERENCE
"RFC cccc, Section 11.12, Login Request" "RFC 7143, Section 11.12, Login Request"
::= { iscsiConnectionAttributesEntry 16 } ::= { iscsiConnectionAttributesEntry 16 }
--********************************************************************** --**********************************************************************
-- Notifications -- Notifications
iscsiTgtLoginFailure NOTIFICATION-TYPE iscsiTgtLoginFailure NOTIFICATION-TYPE
OBJECTS { OBJECTS {
iscsiTgtLoginFailures, iscsiTgtLoginFailures,
iscsiTgtLastFailureType, iscsiTgtLastFailureType,
iscsiTgtLastIntrFailureName, iscsiTgtLastIntrFailureName,
iscsiTgtLastIntrFailureAddrType, iscsiTgtLastIntrFailureAddrType,
iscsiTgtLastIntrFailureAddr, iscsiTgtLastIntrFailureAddr,
iscsiTgtLastIntrFailurePort iscsiTgtLastIntrFailurePort
} }
STATUS current STATUS current
skipping to change at page 73, line 4 skipping to change at page 75, line 26
iscsiPortalSecondaryDataDigest, iscsiPortalSecondaryDataDigest,
iscsiPortalRecvMarker iscsiPortalRecvMarker
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
the transport protocol endpoints of the local targets. the transport protocol endpoints of the local targets.
This object group is deprecated because the marker key This object group is deprecated because the marker key
is obsolete." is obsolete."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
::= { iscsiGroups 3 } ::= { iscsiGroups 3 }
iscsiTgtPortalAttributesGroup OBJECT-GROUP iscsiTgtPortalAttributesGroup OBJECT-GROUP
OBJECTS { OBJECTS {
iscsiTgtPortalPort, iscsiTgtPortalPort,
iscsiTgtPortalTag iscsiTgtPortalTag
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information about "A collection of objects providing information about
skipping to change at page 78, line 17 skipping to change at page 80, line 44
iscsiCxnSendMarker, iscsiCxnSendMarker,
iscsiCxnVersionActive iscsiCxnVersionActive
} }
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"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.
This object group is deprecated because the marker key This object group is deprecated because the marker key
is obsolete." is obsolete."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
::= { iscsiGroups 20 } ::= { iscsiGroups 20 }
iscsiTgtLgnNotificationsGroup NOTIFICATION-GROUP iscsiTgtLgnNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
iscsiTgtLoginFailure iscsiTgtLoginFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications that 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."
skipping to change at page 80, line 28 skipping to change at page 83, line 10
iscsiComplianceV1 MODULE-COMPLIANCE iscsiComplianceV1 MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Initial version of compliance statement. "Initial version of compliance statement.
If an implementation can be both a target and an If an implementation can be both a target and an
initiator, all groups are mandatory. initiator, all groups are mandatory.
This module compliance is deprecated because the This module compliance is deprecated because the
marker keys are obsolete." marker keys are obsolete."
REFERENCE REFERENCE
"[RFCcccc], 13.25 Obsoleted Keys." "RFC 7143, Section 13.25, Obsoleted Keys."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
iscsiInstanceAttributesGroup, iscsiInstanceAttributesGroup,
iscsiInstanceSsnErrorStatsGroup, iscsiInstanceSsnErrorStatsGroup,
iscsiPortalAttributesGroup, iscsiPortalAttributesGroup,
iscsiNodeAttributesGroup, iscsiNodeAttributesGroup,
iscsiSessionAttributesGroup, iscsiSessionAttributesGroup,
iscsiSessionPDUStatsGroup, iscsiSessionPDUStatsGroup,
iscsiSessionCxnErrorStatsGroup, iscsiSessionCxnErrorStatsGroup,
iscsiConnectionAttributesGroup, iscsiConnectionAttributesGroup,
skipping to change at page 85, line 31 skipping to change at page 88, line 15
GROUP iscsiNewObjectsV2 GROUP iscsiNewObjectsV2
DESCRIPTION DESCRIPTION
"This group is mandatory for all iSCSI implementations "This group is mandatory for all iSCSI implementations
that support a value of the iSCSIProtocolLevel key of that support a value of the iSCSIProtocolLevel key of
2 or greater." 2 or greater."
::= { iscsiCompliances 2 } ::= { iscsiCompliances 2 }
END END
8. Security Considerations 8. Security Considerations
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
skipping to change at page 86, line 14 skipping to change at page 88, line 47
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
iscsiNodeAttributesTable, iscsiTargetAttributesTable, and iscsiNodeAttributesTable, iscsiTargetAttributesTable, and
iscsiTgtAuthorization can be used to glean information needed to iscsiTgtAuthorization can be used to glean information needed to
make connections to the iSCSI targets this module represents. make connections to the iSCSI targets this module represents.
However, it is the responsibility of the initiators and targets However, it is the responsibility of the initiators and targets
involved to authenticate each other to ensure that an involved to authenticate each other to ensure that an
inappropriately advertised or discovered initiator or target does inappropriately advertised or discovered initiator or target does
not compromise their security. These issues are discussed in not compromise their security. These issues are discussed in
[RFCcccc]. [RFC7143].
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM) authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM) MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH[RFC5592] [RFC5591] in combination with a secure transport such as SSH
or TLS/DTLS [RFC6353]. [RFC5592] or TLS/DTLS [RFC6353].
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
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER value recorded in the "SMI Network Management MGMT
Codes Internet-standard MIB" registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
iscsiMibModule { mib-2 142 } iscsiMibModule { mib-2 142 }
RFC Editor's Note (to be removed prior to publication): this draft IANA has updated the reference for the mib-2 142 identifier to refer
makes no additional requests of the IANA. IANA is required to update to this document.
the reference for the mib-2 142 to this document.
10. References 10. References
10.1. Normative References 10.1. Normative References
[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., and J. Schoenwaelder, [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Structure of Management Information Version 2 (SMIv2)", Schoenwaelder, Ed., "Structure of Management Information
STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Textual Conventions for SMIv2", STD 58, RFC 2579, April Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
1999. 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
"Conformance Statements for SMIv2", STD 58, RFC 2580, Schoenwaelder, Ed., "Conformance Statements for SMIv2",
April 1999. STD 58, RFC 2580, April 1999.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC3414] Blumenthal, U., and B. Wijnen, [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
"User-based Security Model (USM) for version 3 of the (USM) for version 3 of the Simple Network Management
Simple Network Management Protocol (SNMPv3)", RFC 3414, Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
December 2002.
[RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M., [RFC3720] Satran, J., Meth, K., Sapuntzakis, C., Chadalapaka, M.,
and E. Zeidner, "Internet Small Computer Systems and E. Zeidner, "Internet Small Computer Systems Interface
Interface (iSCSI)", RFC 3720, March 2004. (iSCSI)", RFC 3720, April 2004.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
"The Advanced Encryption Standard (AES) Cipher Advanced Encryption Standard (AES) Cipher Algorithm in the
Algorithm in the SNMP User-based Security Model", SNMP User-based Security Model", RFC 3826, June 2004.
RFC 3826, June 2004.
[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.
[RFC4545] Bakke, M. and J. Muchow, "Definitions of Managed Objects [RFC4545] Bakke, M. and J. Muchow, "Definitions of Managed Objects
for IP Storage User Identity Authorization", RFC 4545, for IP Storage User Identity Authorization", RFC 4545, May
May 2006. 2006.
[RFC5591] Harrington, D., and W. Hardaker, [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
"Transport Security Model for the Simple Network for the Simple Network Management Protocol (SNMP)", RFC
Management Protocol (SNMP)", June 2009. 5591, June 2009.
[RFC5592] Harrington, D., Saloway, J., and W. Hardaker, [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
"Secure Shell Transport Model for the Simple Network Shell Transport Model for the Simple Network Management
Management Protocol (SNMP)", June 2009. Protocol (SNMP)", RFC 5592, June 2009.
[RFC6353] W. Hardaker, "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
July 2011. RFC 6353, July 2011.
[RFCcccc] Chadalapaka, M., Satran, J., and K. Meth, "iSCSI [RFC7143] Chadalapaka, M., Satran, J., Meth, K., and D. Black,
Protocol (Consolidated)", RFC cccc, mmyy. "Internet Small Computer System Interface (iSCSI) Protocol
(Consolidated)", RFC 7143, April 2014.
[RFC7144] Knight, F. and M. Chadalapaka, "Internet Small Computer
System Interface (iSCSI) SCSI Features Update", RFC 7144,
April 2014.
[RFCssss] Knight, F., Chadalapaka, M., "Internet Small 10.2. Informative References
Computer Systems Interface (iSCSI) Update", RFC ssss,
mmyy.
10.2. Informative References [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC4022] Raghunarayan, R., Ed., "Management Information Base for
"Introduction and Applicability Statements for Internet- the Transmission Control Protocol (TCP)", RFC 4022, March
Standard Management Framework", RFC 3410, December 2002. 2005.
[RFC4022] Raghunarayan, R., "Management Information Base for the [RFC4455] Hallak-Stamler, M., Bakke, M., Lederman, Y., Krueger, M.,
Transmission Control Protocol (TCP)", RFC 4022, March and K. McCloghrie, "Definition of Managed Objects for
2005. Small Computer System Interface (SCSI) Entities", RFC
4455, April 2006.
[RFC4455] Hallak-Stamler, M., Bakke, M., Lederman, Y., Krueger, M., [RFC4544] Bakke, M., Krueger, M., McSweeney, T., and J. Muchow,
and K. McCloghrie, "Definition of Managed Objects for "Definitions of Managed Objects for Internet Small
Small Computer System Interface (SCSI) Entities", RFC Computer System Interface (iSCSI)", RFC 4544, May 2006.
4455, April 2006.
[RFC4544] Bakke, M., J. Muchow, M. Krueger and T. McSweeney, 11. Acknowledgments
"Definitions of Managed Objects for iSCSI", RFC 4544,
May 2006.
11. Acknowledgments The contents of this document were largely written as RFC 4544 by
Mark Bakke (Cisco), Marjorie Krueger (Hewlett-Packard), Tom McSweeney
(IBM), and James Muchow (QLogic). A special thank you to Marjorie,
Tom, and James for their hard work and especially to James for his
attention to detail on this work.
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.
Thanks to Mike MacFaden (VMWare), David Black (EMC) and Tom Talpey Thanks to Mike MacFaden (VMWare), David Black (EMC), and Tom Talpey
(Microsoft) for their valuable inputs. (Microsoft) for their valuable inputs.
Authors' Address Authors' Addresses
Mark Bakke Mark Bakke
Dell Dell
7625 Smetana Lane 7625 Smetana Lane
Eden Prairie, MN Eden Prairie, MN 55344
USA 55344 USA
E-mail: mark_bakke@dell.com EMail: mark_bakke@dell.com
Prakash Venkatesen Prakash Venkatesen
HCL Technologies Ltd. HCL Technologies Ltd.
50-53, Greams Road, 50-53, Greams Road,
Chennai - 600006 Chennai - 600006
India India
E-mail: prakashvn@hcl.com EMail: prakashvn@hcl.com
Authors of RFC 4544:
Mark Bakke
Dell
7625 Smetana Lane
Eden Prairie, MN
USA 55344
E-mail: mark_bakke@dell.com
Marjorie Krueger
Hewlett-Packard
Networked Storage Architecture
Networked Storage Solutions Org.
8000 Foothills Blvd.
Roseville, CA
USA 95747
E-mail: marjorie_krueger@hp.com
Tom McSweeney
IBM Corporation
600 Park Offices Drive
Research Triangle Park, NC
USA 27709
E-mail: tommcs@us.ibm.com
James Muchow
Qlogic Corp.
6321 Bury Drive
Eden Prairie, MN
USA 55346
E-mail: james.muchow@qlogic.com
 End of changes. 232 change blocks. 
440 lines changed or deleted 440 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/