draft-ietf-storm-iscsimib-01.txt   draft-ietf-storm-iscsimib-02.txt 
INTERNET-DRAFT Mark Bakke INTERNET-DRAFT Mark Bakke
STORM Working Group Cisco Systems STORM Working Group Dell
Intended status: Proposed Standard Prakash Venkatesen Intended status: Proposed Standard Prakash Venkatesen
Expires: April 2012 HCL Technologies Expires: January 2013 HCL Technologies
Obsoletes: 4544 October 25, 2011 Obsoletes: 4544 July 13, 2012
Definitions of Managed Objects for Internet Small Computer System Definitions of Managed Objects for Internet Small Computer System
Interface (iSCSI) Interface (iSCSI)
draft-ietf-storm-iscsimib-01.txt draft-ietf-storm-iscsimib-02.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on April 25, 2012. This Internet-Draft will expire on January 13, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
skipping to change at page 3, line 9 skipping to change at page 3, line 9
6.10. iscsiInitiator..........................................11 6.10. iscsiInitiator..........................................11
6.11. iscsiIntrAuthorization..................................11 6.11. iscsiIntrAuthorization..................................11
6.12. iscsiSession............................................11 6.12. iscsiSession............................................11
6.13. iscsiConnection.........................................12 6.13. iscsiConnection.........................................12
6.14. IP Addresses and TCP Port Numbers.......................13 6.14. IP Addresses and TCP Port Numbers.......................13
6.15. Descriptors: Using OIDs in Place of Enumerated Types....13 6.15. Descriptors: Using OIDs in Place of Enumerated Types....13
6.16. Notifications...........................................13 6.16. Notifications...........................................13
7. MIB Definition................................................14 7. MIB Definition................................................14
8. Security Considerations.......................................82 8. Security Considerations.......................................82
9. IANA Considerations...........................................83 9. IANA Considerations...........................................83
10. References...................................................83 10. References...................................................84
10.1. Normative References....................................83 10.1. Normative References....................................84
10.2. Informative References..................................84 10.2. Informative References..................................85
11. Acknowledgments..............................................85 11. Acknowledgments..............................................85
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
skipping to change at page 3, line 36 skipping to change at page 3, line 36
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].
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 2. Introduction
-- RFC Editor:replace cccc in RFCcccc at all the places in which it is
-- used in this document, with the RFC number assigned to -- used in this document, with the RFC number assigned to
-- draft-ietf-storm-iscsi-cons-03 & remove this note. -- draft-ietf-storm-iscsi-cons-03 & remove this note.
This document defines a MIB module for iSCSI [RFCcccc], used to This document defines a MIB module for iSCSI [RFCcccc], used to
manage devices that implement the iSCSI protocol. It obsoletes RFC manage devices that implement the iSCSI protocol. It obsoletes RFC
4544 [RFC4544]. 4544 [RFC4544].
3. Relationship to Other MIB Modules 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
skipping to change at page 14, line 38 skipping to change at page 14, line 38
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 "201110210000Z" -- October 21, 2011 LAST-UPDATED "201207100000Z" -- July 10, 2012
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 Cisco Systems, Inc
Email: mbakke@cisco.com Email: mbakke@cisco.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) The IETF Trust (2011). This Copyright (c) 2011 IETF Trust and the persons identified as
version of this MIB module is part of RFC xxxx; authors of the code. All rights reserved.
see the RFC itself for full legal notices."
REVISION "201110210000Z" Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201207100000Z"
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 [RFCcccc] 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 xxxx."
-- RFC Editor: replace xxxx with actual RFC number & remove this note. -- RFC Editor: replace xxxx with actual RFC number & remove this note.
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 }
-- RFC Editor:replace cccc in RFC cccc at all the places in which it is
-- used in this document, with the RFC number assigned to
-- draft-ietf-storm-iscsi-cons-03 & remove this note.
-- 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.
REFERENCE Protocol numbers are assigned by IANA. A
"RFC791, RFC1700 current list of all assignments is available from
<http://www.iana.org/assignments/protocol-numbers/>."
The presently known, officially delegated numbers
can be found at:
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
skipping to change at page 20, line 43 skipping to change at page 20, line 50
is indicated in iscsiInstDiscontinuityTime." is indicated in iscsiInstDiscontinuityTime."
REFERENCE REFERENCE
"RFC cccc, Section 13.1, HeaderDigest and DataDigest" "RFC cccc, 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 iscsiInstSsnErrorStatsTable "The counter object in the iscsiInstanceSsnErrorStatsTable
that was incremented when the last session failure occurred. that was incremented when the last session failure occurred.
If the reason for failure is not found in the If the reason for failure is not found in the
iscsiInstSsnErrorStatsTable, the value { 0.0 } is iscsiInstanceSsnErrorStatsTable, the value { 0.0 } is
used instead." used instead."
::= { iscsiInstanceAttributesEntry 11 } ::= { iscsiInstanceAttributesEntry 11 }
iscsiInstLastSsnRmtNodeName OBJECT-TYPE iscsiInstLastSsnRmtNodeName OBJECT-TYPE
SYNTAX IscsiName SYNTAX IscsiName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The iSCSI name of the remote node from the failed "The iSCSI name of the remote node from the failed
session." session."
skipping to change at page 30, line 46 skipping to change at page 30, line 52
"A list of iSCSI nodes belonging to each iSCSI instance "A list of iSCSI nodes belonging to each iSCSI instance
present on the local system. An iSCSI node can act as present on the local system. An iSCSI node can act as
an initiator, a target, or both." an initiator, a target, or both."
::= { iscsiNode 1 } ::= { iscsiNode 1 }
iscsiNodeAttributesEntry OBJECT-TYPE iscsiNodeAttributesEntry OBJECT-TYPE
SYNTAX IscsiNodeAttributesEntry SYNTAX IscsiNodeAttributesEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (row) containing management information applicable "A conceptual row containing management information
to a particular iSCSI node." applicable to a particular iSCSI node."
INDEX { iscsiInstIndex, iscsiNodeIndex } INDEX { iscsiInstIndex, iscsiNodeIndex }
::= { iscsiNodeAttributesTable 1 } ::= { iscsiNodeAttributesTable 1 }
IscsiNodeAttributesEntry ::= SEQUENCE { IscsiNodeAttributesEntry ::= SEQUENCE {
iscsiNodeIndex Unsigned32, iscsiNodeIndex Unsigned32,
iscsiNodeName IscsiName, iscsiNodeName IscsiName,
iscsiNodeAlias SnmpAdminString, iscsiNodeAlias SnmpAdminString,
iscsiNodeRoles BITS, iscsiNodeRoles BITS,
iscsiNodeTransportType RowPointer, iscsiNodeTransportType RowPointer,
iscsiNodeInitialR2T TruthValue, iscsiNodeInitialR2T TruthValue,
skipping to change at page 32, line 51 skipping to change at page 33, line 8
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A pointer to the corresponding row in the appropriate "A pointer to the corresponding row in the appropriate
table for this SCSI transport, thereby allowing management table for this SCSI transport, thereby allowing management
stations to locate the SCSI-level device that is represented stations to locate the SCSI-level device that is represented
by this iscsiNode. For example, it will usually point to the by this iscsiNode. For example, it will usually point to the
corresponding scsiTrnspt object in the SCSI MIB module. corresponding scsiTrnspt object in the SCSI MIB module.
If no corresponding row exists, the value 0.0 must be If no corresponding row exists, the value 0.0 must be
used to indicate this." used to indicate this."
REFERENCE REFERENCE
"SCSI-MIB" "SCSI-MIB, RFC 4455 section 9, 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,
false = will try to negotiate NO, will accept YES " false = will try to negotiate NO, will accept YES "
REFERENCE REFERENCE
skipping to change at page 36, line 41 skipping to change at page 36, line 48
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). Conceptual external process (e.g. not created via this MIB module).
rows having the value 'permanent' need not allow write Conceptual rows having the value 'permanent' need not allow
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
to be set to either 'nonVolatile' or 'volatile', to be set to either 'nonVolatile' or 'volatile',
allowing the management application to choose this allowing the management application to choose this
skipping to change at page 44, line 20 skipping to change at page 44, line 25
::= { 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" "IPS-AUTH MIB, RFC 4545, 7.3, ipsAuthIdentAttributeEntry"
::= { 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.
skipping to change at page 52, line 26 skipping to change at page 52, line 33
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" "IPS-AUTH MIB, RFC 4545, 7.3, ipsAuthInstanceAttributeEntry"
::= { 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.
skipping to change at page 58, line 21 skipping to change at page 58, line 27
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" "IPS-AUTH MIB, RFC 4545, 7.3, ipsAuthInstanceAttributeEntry"
::= { 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 59, line 37 skipping to change at page 59, line 44
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 ssss, Section 7.1.1, iSCSIProtocolLevel"
-- RFC Editor: replace ssss in RFC ssss with the RFC number assigned to -- RFC Editor: replace ssss in RFC ssss with the RFC number assigned to
-- draft-ietf-storm-iscsi-sam-05 & remove this note.
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)
} }
skipping to change at page 61, line 46 skipping to change at page 61, line 52
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 that don't support Counter64. 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 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 that don't support Counter64. 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 }
-- Session Connection Error Stats Table -- Session Connection Error Stats Table
iscsiSessionCxnErrorStatsTable OBJECT-TYPE iscsiSessionCxnErrorStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IscsiSessionCxnErrorStatsEntry SYNTAX SEQUENCE OF IscsiSessionCxnErrorStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 62, line 49 skipping to change at page 63, line 6
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-
level is 1 or 2"
REFERENCE REFERENCE
"RFC cccc, Section 7.8, Digest Errors" "RFC cccc, 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-
level is 2"
REFERENCE REFERENCE
"RFC cccc, Section 7.5, Connection Timeout Management" "RFC cccc, 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
skipping to change at page 77, line 15 skipping to change at page 77, line 25
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."
::= { iscsiGroups 25 } ::= { iscsiGroups 25 }
--********************************************************************** --**********************************************************************
iscsiComplianceV1 MODULE-COMPLIANCE iscsiComplianceV1 MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION DESCRIPTION
"Initial version of compliance statement based on "Initial version of compliance statement.
initial version of this MIB module.
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." "[RFCcccc], 13.25 Obsoleted Keys."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
iscsiInstanceAttributesGroup, iscsiInstanceAttributesGroup,
skipping to change at page 79, line 45 skipping to change at page 80, line 4
OBJECT iscsiNodeErrorRecoveryLevel OBJECT iscsiNodeErrorRecoveryLevel
SYNTAX Unsigned32 (0..2) SYNTAX Unsigned32 (0..2)
DESCRIPTION DESCRIPTION
"Only values 0-2 are defined at present." "Only values 0-2 are defined at present."
::= { iscsiCompliances 1 } ::= { iscsiCompliances 1 }
iscsiComplianceV2 MODULE-COMPLIANCE iscsiComplianceV2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Initial version of compliance statement based on "Version 2 of compliance statement based on
initial version of this MIB module. this revised version of the MIB module.
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."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
iscsiInstanceAttributesGroup, iscsiInstanceAttributesGroup,
iscsiInstanceSsnErrorStatsGroup, iscsiInstanceSsnErrorStatsGroup,
iscsiPortalAttributesGroupV2, iscsiPortalAttributesGroupV2,
iscsiNodeAttributesGroup, iscsiNodeAttributesGroup,
iscsiSessionAttributesGroup, iscsiSessionAttributesGroup,
skipping to change at page 83, line 34 skipping to change at page 83, line 43
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 values recorded in the SMI Numbers 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
makes no additional requests of the IANA.
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., Perkins, D., and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)", "Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999. STD 58, RFC 2578, April 1999.
skipping to change at page 84, line 27 skipping to change at page 84, line 44
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 2006. May 2006.
[RFCcccc] Chadalapaka, M., Satran, J., and K. Meth, "iSCSI [RFCcccc] Chadalapaka, M., Satran, J., and K. Meth, "iSCSI
Protocol (Consolidated)", RFC cccc, mmyy Protocol (Consolidated)", RFC cccc, mmyy
-- RFC Editor:replace cccc with the RFC number assigned to
-- draft-ietf-storm-iscsi-cons-03 & remove this note. -- draft-ietf-storm-iscsi-cons-03 & remove this note.
-- RFC Editor:replace mmyy with the RFC month and year assigned to
-- draft-ietf-storm-iscsi-cons-03 & remove this note. -- draft-ietf-storm-iscsi-cons-03 & remove this note.
[RFCssss] Knight, F., Chadalapaka, M., "Internet Small [RFCssss] Knight, F., Chadalapaka, M., "Internet Small
Computer Systems Interface (iSCSI) Update", RFC ssss, Computer Systems Interface (iSCSI) Update", RFC ssss,
mmyy mmyy
-- RFC Editor: replace ssss with the RFC number assigned to -- RFC Editor: replace ssss with the RFC number assigned to
-- draft-ietf-storm-iscsi-sam-05 & remove this note.
-- RFC Editor: replace mmyy with the RFC month and year assigned to -- RFC Editor: replace mmyy with the RFC month and year assigned to
-- draft-ietf-storm-iscsi-sam-05 & remove this note.
10.2. Informative References 10.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4022] Raghunarayan, R., "Management Information Base for the [RFC4022] Raghunarayan, R., "Management Information Base for the
Transmission Control Protocol (TCP)", RFC 4022, March Transmission Control Protocol (TCP)", RFC 4022, March
2005. 2005.
skipping to change at page 85, line 28 skipping to change at page 85, line 44
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 David Black (EMC) and Tom Talpey (Microsoft) for their Thanks to Mike MacFaden (VMWare), David Black (EMC) and Tom Talpey
valuable inputs. (Microsoft) for their valuable inputs.
Authors' Address Authors' Address
Mark Bakke Mark Bakke
Cisco Systems, Inc Dell
7900 International Drive, Suite 400 7625 Smetana Lane
Bloomington, MN Eden Prairie, MN
USA 55425 USA 55344
EMail: mbakke@cisco.com E-mail: 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
EMail: prakashvn@hcl.com
E-mail: prakashvn@hcl.com
Authors of RFC 4544: Authors of RFC 4544:
Mark Bakke Mark Bakke
Cisco Systems, Inc Dell
7900 International Drive, Suite 400 7625 Smetana Lane
Bloomington, MN Eden Prairie, MN
USA 55425 USA 55344
EMail: mbakke@cisco.com E-mail: mark_bakke@dell.com
Marjorie Krueger Marjorie Krueger
Hewlett-Packard Hewlett-Packard
Networked Storage Architecture Networked Storage Architecture
Networked Storage Solutions Org. Networked Storage Solutions Org.
8000 Foothills Blvd. 8000 Foothills Blvd.
Roseville, CA Roseville, CA
USA 95747 USA 95747
EMail: marjorie_krueger@hp.com E-mail: marjorie_krueger@hp.com
Tom McSweeney Tom McSweeney
IBM Corporation IBM Corporation
600 Park Offices Drive 600 Park Offices Drive
Research Triangle Park, NC Research Triangle Park, NC
USA 27709 USA 27709
EMail: tommcs@us.ibm.com E-mail: tommcs@us.ibm.com
James Muchow James Muchow
Qlogic Corp. Qlogic Corp.
6321 Bury Drive 6321 Bury Drive
Eden Prairie, MN Eden Prairie, MN
USA 55346 USA 55346
EMail: james.muchow@qlogic.com E-mail: james.muchow@qlogic.com
 End of changes. 42 change blocks. 
60 lines changed or deleted 83 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/