[storm] iSCSI MIB: Matching connections to the TCP/TCP-ESTATS MIBs

Mark Bakke <Mark_Bakke@DELL.com> Fri, 13 July 2012 22:54 UTC

Return-Path: <Mark_Bakke@DELL.com>
X-Original-To: storm@ietfa.amsl.com
Delivered-To: storm@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 62CA511E80CB for <storm@ietfa.amsl.com>; Fri, 13 Jul 2012 15:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.097
X-Spam-Status: No, score=-106.097 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Eo0nX8bxGgJC for <storm@ietfa.amsl.com>; Fri, 13 Jul 2012 15:54:13 -0700 (PDT)
Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com []) by ietfa.amsl.com (Postfix) with ESMTP id 506B911E8116 for <storm@ietf.org>; Fri, 13 Jul 2012 15:54:12 -0700 (PDT)
X-Loopcount0: from
X-IronPort-AV: E=Sophos; i="4.77,583,1336366800"; d="scan'208,217"; a="537322445"
Received: from mail.compellent.com ([]) by aussmtpmrkps320.us.dell.com with ESMTP; 13 Jul 2012 17:54:50 -0500
From: Mark Bakke <Mark_Bakke@DELL.com>
To: "Storm (storm@ietf.org)" <storm@ietf.org>
Date: Fri, 13 Jul 2012 17:54:48 -0500
Thread-Topic: iSCSI MIB: Matching connections to the TCP/TCP-ESTATS MIBs
Thread-Index: Ac1fgTiIrOMUDrA1QV2yDNd7eQgXvA==
Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA03F19A9137@shandy.Beer.Town>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_975552A94CBC0F4DA60ED7B36C949CBA03F19A9137shandyBeerTow_"
MIME-Version: 1.0
Cc: "mrm@vmware.com" <mrm@vmware.com>, "prakashvn@hcl.com" <prakashvn@hcl.com>
Subject: [storm] iSCSI MIB: Matching connections to the TCP/TCP-ESTATS MIBs
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: Fri, 13 Jul 2012 22:54:15 -0000

Fellow iSCSI MIB enthusiasts,

During our latest review, one suggestion was to provide better troubleshooting connectivity with the TCP MIB module.  I have a few questions for the list, below.

>From MIB Doctor Review:

  |  |
  |  +--iscsiTgtLoginFailure(1) [iscsiTgtLoginFailures,iscsiTgtLastFailureType,iscsiTgtLastIntrFailureName,iscsiTgtLastIntrFailureAddrType,iscsiTgtLastIntrFailureAddr]

Consider adding port number.

  |  +--iscsiIntrLoginFailure(2) [iscsiIntrLoginFailures,iscsiIntrLastFailureType,iscsiIntrLastTgtFailureName,iscsiIntrLastTgtFailureAddrType,iscsiIntrLastTgtFailureAddr]

Can't determine if the failure is due to failure of the underlying transport or not.
When transport is TCP there should be some way to get to the TCP-MIB/TCP-ESTATS-MIB diagnostics.
See notes on iscsiInstanceSsnErrorStatsTable.

Consider adding port number.

[Mark]  Although we can navigate to the TCP-MIB for connections that are alive (these provide local and remote IP addresses and port numbers, for the LastFailures for initiator and target entries, adding the port number as suggested would allow these to be potentially matched with these MIBs.

The question to the list is:

1.       Will this provide better troubleshooting capabilities for failed connections?

2.       Will implementations be likely to provide and use these fields?