Re: [Ips] no DHCP-assigned InitiatorName
Michael Howard <michael.howard@scalent.com> Wed, 24 September 2008 21:59 UTC
Return-Path: <ips-bounces@ietf.org>
X-Original-To: ips-archive@optimus.ietf.org
Delivered-To: ietfarch-ips-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 271C53A6B74; Wed, 24 Sep 2008 14:59:34 -0700 (PDT)
X-Original-To: ips@core3.amsl.com
Delivered-To: ips@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17BBD3A690E for <ips@core3.amsl.com>; Wed, 24 Sep 2008 14:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.352
X-Spam-Level:
X-Spam-Status: No, score=0.352 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZhvvFz1QIhr for <ips@core3.amsl.com>; Wed, 24 Sep 2008 14:59:30 -0700 (PDT)
Received: from mymail.scalent.com (69-233-57-200.ded.pacbell.net [69.233.57.200]) by core3.amsl.com (Postfix) with ESMTP id BDB993A6B20 for <ips@ietf.org>; Wed, 24 Sep 2008 14:59:30 -0700 (PDT)
Received: from [192.168.15.15] ([74.65.146.114]) by mymail.scalent.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Sep 2008 14:59:16 -0700
Message-ID: <48DAB828.4010609@scalent.com>
Date: Wed, 24 Sep 2008 14:59:04 -0700
From: Michael Howard <michael.howard@scalent.com>
User-Agent: Thunderbird 2.0.0.16 (Windows/20080708)
MIME-Version: 1.0
To: G_Chawla@Dell.com
References: <48D6F3EB.1080400@scalent.com><OF51EB8C4B.4A802DE0-ON852574CC.003C9899-852574CC.003D1E7C@il.ibm.com><48D79AA6.9040104@scalent.com><OF2B1DCFAA.18C9A07A-ON852574CC.004985AD-852574CC.004A10C4@il.ibm.com><48D7BC9D.7060306@scalent.com><OFBBCF89D4.CCDF2FC8-ON852574CC.005E8F41-852574CC.005F3669@il.ibm.com><48D7DF92.9030605@scalent.com><46A00B48CC54E4468EF6911F877AC4CA019D6922@blrx3m10.blr.amer.dell.com> <48D7F1DE.5060000@scalent.com> <42D8A6CDC96A5A4D8D91DE26991A51AA02016F63@ausx3mpc108.aus.amer.dell.com>
In-Reply-To: <42D8A6CDC96A5A4D8D91DE26991A51AA02016F63@ausx3mpc108.aus.amer.dell.com>
X-OriginalArrivalTime: 24 Sep 2008 21:59:16.0487 (UTC) FILETIME=[C9B36170:01C91E90]
Cc: ips@ietf.org, Shyam_Iyer@Dell.com
Subject: Re: [Ips] no DHCP-assigned InitiatorName
X-BeenThere: ips@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IP Storage <ips.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ips>
List-Post: <mailto:ips@ietf.org>
List-Help: <mailto:ips-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ips>, <mailto:ips-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ips-bounces@ietf.org
Errors-To: ips-bounces@ietf.org
Gaurav and Shyam, Q: Do you have contacts with the EqualLogic team who may be interested in working on a resolution for this iSCSI/DHCP issue? Q: Do you have any contacts at Broadcom? Thanks, Michael G_Chawla@Dell.com wrote: > My 2 cents based on my understanding of iSNS. > > - iSNS clients (initiators and targets) need to have an IQN address > before they register with the iSNS server. > - Most pre-OS iSCSI initiators available today are not iSNS clients i.e. > they don't register with and/or query iSNS server. > > Given this, it seems better to have a DHCP based standardized mechanism > for acquiring the initiator IQN. Based on initial email from Michael, > most pre-OS iSCSI Initiators available today have the capability to be a > DHCP client. > > Thanks, > Gaurav Chawla > Technology Strategist, Network Storage Architecture | Office of the CTO, > Dell, Inc. > Phone: 512.724.4064 (work) > > > -----Original Message----- > From: ips-bounces@ietf.org [mailto:ips-bounces@ietf.org] On Behalf Of > Michael Howard > Sent: Monday, September 22, 2008 2:29 PM > To: Iyer, Shyam > Cc: SIVANT@il.ibm.com; psarkar@almaden.ibm.com; ips@ietf.org; > Julian_Satran@il.ibm.com > Subject: Re: [Ips] no DHCP-assigned InitiatorName > > Shyam_Iyer@Dell.com wrote: >> My 2cents on the issue. Please correct me if I am wrong. > > Thank you for participating in this discussion. > >> Shouldn't it be possible to configure the isns server with a set of >> possibly regex rules for the control path. If this not possible today, >> then it could possibly be the root to take towards standardizing. > > I am not familiar enough with iSNS to comment. > > I have been exposed to about about a dozen commercial environments with > some level of iSCSI use/experimentation. I am not aware that any of them > > were running iSNS servers. > >> This can solve the problem of provisioning for dynamic boot > environments >> with minimum changes to legacy iqn implementations, many of which > would >> need to relearn to the new iqn mechanism that might end up as a result >> of this discussion. > > Frankly, my concern is that Broadcom/IBM already have a non-standard > DHCP Vendor Option work-around for this problem. > > Adding a new/standardized InitiatorName DHCP option would not break > existing initiator implementations. Vendors would integrate support for > this new InitiatorName option into their code/firmware releases over > time. > >> Instead of changing numerous configurations we could >> simply change the isns server control mechanism. > > I need to do some homework regarding iSNS. > >> Comments? > > iSCSI is still a very small part of the market. > > I advocate addressing this deficiency sooner rather than later. > > > Michael > _______________________________________________ > Ips mailing list > Ips@ietf.org > https://www.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list Ips@ietf.org https://www.ietf.org/mailman/listinfo/ips
- [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Julian Satran
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Julian Satran
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Black_David
- [Ips] no DHCP-assigned InitiatorName: Procedural … Black_David
- Re: [Ips] no DHCP-assigned InitiatorName: Procedu… Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Julian Satran
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName Shyam_Iyer
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard
- Re: [Ips] no DHCP-assigned InitiatorName G_Chawla
- Re: [Ips] no DHCP-assigned InitiatorName Shyam_Iyer
- Re: [Ips] no DHCP-assigned InitiatorName G_Chawla
- Re: [Ips] no DHCP-assigned InitiatorName Sivan Tal
- Re: [Ips] no DHCP-assigned InitiatorName Michael Howard