[storm] iSCSI MIB: Functional enhancements proposal

"Black, David" <david.black@emc.com> Sat, 15 September 2012 01:06 UTC

Return-Path: <david.black@emc.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38BE21F85AA for <storm@ietfa.amsl.com>; Fri, 14 Sep 2012 18:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mtKRygrYTggH for <storm@ietfa.amsl.com>; Fri, 14 Sep 2012 18:06:28 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id DCC3321F85A8 for <storm@ietf.org>; Fri, 14 Sep 2012 18:06:27 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8F16Q95001689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <storm@ietf.org>; Fri, 14 Sep 2012 21:06:27 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <storm@ietf.org>; Fri, 14 Sep 2012 21:06:16 -0400
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q8F16FmX032116 for <storm@ietf.org>; Fri, 14 Sep 2012 21:06:15 -0400
Received: from mxhub40.corp.emc.com (128.222.70.107) by mxhub25.corp.emc.com (10.254.110.181) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 14 Sep 2012 21:06:15 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Fri, 14 Sep 2012 21:06:15 -0400
From: "Black, David" <david.black@emc.com>
To: "storm@ietf.org" <storm@ietf.org>
Date: Fri, 14 Sep 2012 21:06:13 -0400
Thread-Topic: iSCSI MIB: Functional enhancements proposal
Thread-Index: Ac2S3k0VAOHDeEHlQP66E4/tbPSxkA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DCD1567@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Subject: [storm] iSCSI MIB: Functional enhancements proposal
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Sep 2012 01:06:28 -0000

The iSCSI MIB has been waiting for a WG decision about what to incorporate from
the list of functional enhancements suggested by the MIB Doctor review.

With <WG chair hat off>, based on consulting with the MIB draft editors, I offer
the following initial proposal for the WG's consideration ... in the hope of
getting to a decision.

--- Make the following functional enhancements:

[1] Add NOP counters at iSCSI session scope for heartbeat tracking
[2] Add a port number to the iscsiTgtLoginFailure and iscsiIntrLoginFailure notifications,
	and to the last failure info in iscsiInitiatorAttributesEntry.
[3] Add a description string to the iSCSI portal:

iscsiPortalDescr OBJECT-TYPE
    SYNTAX        SnmpAdminString
    MAX-ACCESS    read-only
    STATUS        current
    DESCRIPTION
        "A UTF-8 string, determined by the implementation to
        describe the iSCSI portal.  When only a single instance
        is present, this object may be set to the zero-length
        string; with multiple iSCSI portals, it may be used in
        an implementation-dependent manner to describe the 
        respective portal, and could include information such as
        HBA model, description and version or software driver and
        version."

[4] Support "Target Unmapped" session failure reporting in the iscsiInstSessionFailure notification:

Editors: FailureType is an OID pointing to a stat in iscsiInstSsnErrorStatsTable, so we would need to add this:

    iscsiInstSsnTgtUnmappedErrors       Counter32

[5] Add a port number to iscsiPortalAttributesEntry

[6] Add a timeout counter to iscsiInitiatorLogoutStatsEntry to distinguish implicit
	logouts caused by timeouts from implicit logouts caused by other reasons.

--- Do not make any other functional enhancements, including the following

[A] Summary notifications for large numbers of targets or initiators.  (At most
	a single summary with a count would be appropriate for each notification type).
[B] RowPointer or other connection to transport state as part of
	iscsiInstanceSsnErrorStatsEntry (can be found indirectly in current structure).
[C] Support for reporting more than two digest algorithms (only one is standardized).
[D] Additional list of authentication methods for negotiation (already available based
	on reporting of authorized entities).
[E] Additional support for mutual authentication (check the MIBs at both ends instead).
[F] Support for digest provisioning at the iSCSI node level (use iSCSI portal instead).
[G] Additional session reporting, including digest, error recovery level, session type
	and additional counters for missing PDUs, data in PDUs, data out PDUs, async PDUs.
[H] Report initial remote IP address and port for connections in addition to actual
	IP address and port - this would be for situations in which a redirection has
	occurred.
[I] Report list of discovered targets (out of scope for this MIB).

--------------------

Of the above list, I'd be particularly interested in comments on [A], [G] and [H] -
if these were added to the MIB, would they be likely to be implemented and used?

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953             FAX: +1 (508) 293-7786
david.black@emc.com        Mobile: +1 (978) 394-7754
----------------------------------------------------