Return-Path: Received: from newbox.ece.cmu.edu (localhost [127.0.0.1]) by newbox.ece.cmu.edu (Cyrus v2.1.12) with LMTP; Tue, 15 Jul 2003 03:36:02 -0400 X-Sieve: CMU Sieve 2.2 Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by newbox.ece.cmu.edu (Postfix) with ESMTP id CCD4830BD for ; Tue, 15 Jul 2003 03:36:02 -0400 (EDT) Received: by bache.ece.cmu.edu (Postfix, from userid 953) id 6BA6282; Tue, 15 Jul 2003 03:36:02 -0400 (EDT) Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27]) by bache.ece.cmu.edu (Postfix) with ESMTP id A83FE8D; Tue, 15 Jul 2003 03:35:53 -0400 (EDT) Received: by sos.ece.cmu.edu (Postfix) id 16C8089DF; Tue, 15 Jul 2003 03:35:36 -0400 (EDT) Delivered-To: ips-outgoing@sos.ece.cmu.edu Received: from hazard.ece.cmu.edu (HAZARD.ECE.CMU.EDU [128.2.129.24]) by sos.ece.cmu.edu (Postfix) with ESMTP id E9A0789DD for ; Tue, 15 Jul 2003 03:35:35 -0400 (EDT) Received: by hazard.ece.cmu.edu (Postfix) id BF4EE16B; Tue, 15 Jul 2003 03:35:35 -0400 (EDT) Delivered-To: ips-outgoing@ece.cmu.edu Received: by hazard.ece.cmu.edu (Postfix, from userid 953) id 846A5175; Tue, 15 Jul 2003 03:35:35 -0400 (EDT) Received: from sos.ece.cmu.edu (SOS.ECE.CMU.EDU [128.2.129.27]) by hazard.ece.cmu.edu (Postfix) with ESMTP id 5B640136 for ; Tue, 15 Jul 2003 03:35:31 -0400 (EDT) Received: by sos.ece.cmu.edu (Postfix, from userid 363) id 3011D89E2; Tue, 15 Jul 2003 03:35:31 -0400 (EDT) X-Original-To: ips@sos.ece.cmu.edu Delivered-To: ips@sos.ece.cmu.edu Received: from osgood.ece.cmu.edu (OSGOOD.ECE.CMU.EDU [128.2.129.25]) by sos.ece.cmu.edu (Postfix) with ESMTP id 8875489DD for ; Tue, 15 Jul 2003 03:35:29 -0400 (EDT) Received: by osgood.ece.cmu.edu (Postfix) id 0A186AF; Tue, 15 Jul 2003 03:35:29 -0400 (EDT) Delivered-To: ips@ece.cmu.edu Received: by osgood.ece.cmu.edu (Postfix, from userid 953) id D0955A4; Tue, 15 Jul 2003 03:35:28 -0400 (EDT) Received: from SANSRV1.SAN-RAD.CO.IL (unknown [80.74.102.50]) by osgood.ece.cmu.edu (Postfix) with ESMTP id 54733B9 for ; Tue, 15 Jul 2003 03:35:20 -0400 (EDT) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C34AA3.DD748412" Subject: RE: question about iscsiTgtPortalAttributesTable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Tue, 15 Jul 2003 10:36:55 +0300 Message-ID: <838D8D2617300146B7F47E4D9AE7FF108BB64C@SANSRV1.SAN-RAD.CO.IL> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: question about iscsiTgtPortalAttributesTable Thread-Index: AcMq/dGwAJIWmwMMQ6ikmPQGyohnPwfperzw From: "Michele Hallak - Stamler" To: "KRUEGER,MARJORIE (HP-Roseville,ex1)" , "Venkat Movva" , Cc: , , Sender: owner-ips@ece.cmu.edu Precedence: bulk X-Spam-Status: No, hits=-5.0 required=5.0 tests=BAYES_10,HTML_60_70,HTML_FONT_COLOR_BLUE,HTML_FONT_FACE_ODD version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) This is a multi-part message in MIME format. ------_=_NextPart_001_01C34AA3.DD748412 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Is this issue closed? I'm waiting for the new draft in order to know how = to implement that function. Thanks, Michele -----Original Message----- From: KRUEGER,MARJORIE (HP-Roseville,ex1) = [mailto:marjorie.krueger@hp.com] Sent: Thursday, June 05, 2003 03:59 To: 'Venkat Movva'; mbakke@cisco.com Cc: 'black_david@emc.com'; 'Elizabeth.G.Rodriguez@123mail.net'; = Ips@Ece.Cmu.Edu (ips@ece.cmu.edu); Michele Hallak - Stamler Subject: RE: question about iscsiTgtPortalAttributesTable You are not assuming something wrong, this has been overlooked in the = current MIB draft. iSCSIPortal table is OK, but iSCSITargetPortal = should be indexed by iSCSINodeIndex and iscsiIntrPortalAttributesTable = should be deleted as there is no such thing as an initiator portal group = tag. Or alternatively, this table should just be genericly named = (iSCSIPortalGroupTable) and indexed by iscsiNodeIndex, and then an = initiator implementation can decide if they want to populate entries = with a conceptual portal group tag. =20 What is the status of this draft? Can we update this for the Vienna = IETF draft? =20 Regards, Marjorie Krueger Networked Storage Architecture Networked Storage Solutions Hewlett-Packard=20 -----Original Message----- From: Venkat Movva [mailto:vmovva@istor.com]=20 Sent: Wednesday, June 04, 2003 4:46 PM To: mbakke@cisco.com Cc: marjorie_krueger@hp.com Subject: question about iscsiTgtPortalAttributesTable Hi,=20 I have question about the IETF-ISCSI-DRAFT-MIB. =20 Question:=20 Currently iscsiTgtPortalAttributesTable is indexed by the = iSCSIInstIndex and PortalIndex.=20 But there is no information about the target node to which it is = associated with. According to ISCSI Spec=20 I can have target network portal that can belongs to multiple target = portal groups as long as these target portal groups belong to different target nodes. =20 How do I add network portal with ( IP : 10.1.1.10 : port 8070) to=20 iSCSI Instance =3D 1, TagetNode =3D 1, Tag =3D 2 and to iSCSIInstance =3D 1 TargetNode =3D 2, Tag =3D 3 ? In the current Draft MIB there is no association of Network portal = with TargetNode. =20 Is this information missing in the DRAFT MIB or am I assuming = something wrong? =20 Sorry for sending direct mail to you. =20 Please let me know if there is reflector ( forum) to post this type of = questions.=20 Thanks=20 Venkat=20 =20 =20 ------_=_NextPart_001_01C34AA3.DD748412 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message
Is=20 this issue closed? I'm waiting for the new draft in order to know how to = implement that function.
Thanks,
    Michele
-----Original Message-----
From: KRUEGER,MARJORIE=20 (HP-Roseville,ex1) [mailto:marjorie.krueger@hp.com]
Sent: = Thursday,=20 June 05, 2003 03:59
To: 'Venkat Movva';=20 mbakke@cisco.com
Cc: 'black_david@emc.com';=20 'Elizabeth.G.Rodriguez@123mail.net'; Ips@Ece.Cmu.Edu = (ips@ece.cmu.edu);=20 Michele Hallak - Stamler
Subject: RE: question about=20 iscsiTgtPortalAttributesTable

You are not assuming something wrong, this = has been=20 overlooked in the current MIB draft.  iSCSIPortal table is OK, = but=20 iSCSITargetPortal should be indexed by iSCSINodeIndex and=20 iscsiIntrPortalAttributesTable should be deleted as there is no such = thing as=20 an initiator portal group tag.  Or alternatively, this table = should just=20 be genericly  named (iSCSIPortalGroupTable) and indexed by=20 iscsiNodeIndex, and then an initiator implementation can decide if = they want=20 to populate entries with a conceptual portal group = tag.
 
What is the status of this draft?  Can = we update=20 this for the Vienna IETF draft?
 
Regards,

Marjorie Krueger
Networked Storage=20 Architecture
Networked Storage Solutions
Hewlett-Packard=20

-----Original Message-----
From: = Venkat Movva=20 [mailto:vmovva@istor.com]
Sent: Wednesday, June 04, 2003 = 4:46=20 PM
To: mbakke@cisco.com
Cc:=20 marjorie_krueger@hp.com
Subject: question about=20 iscsiTgtPortalAttributesTable

Hi,=20

     I have question about the=20 IETF-ISCSI-DRAFT-MIB. 

Question:=20

  =20 Currently = iscsiTgtPortalAttributesTable = is indexed by=20 the iSCSIInstIndex and PortalIndex.=20

  =20 But there is no information=20 about = the target node to = which it is associated=20 with. According to ISCSI Spec

   I can=20 have target network=20 portal that can belongs to multiple target portal groups = as long as=20 these

  =20 target = portal=20 groups belong to different target = nodes.  =

   =20 How do I add network portal = with ( IP :=20 10.1.1.10 : port 8070)  to

          &nbs= p;      iSCSI=20 Instance = =3D 1, TagetNode =3D 1, Tag =3D = 2

      and to  iSCSIInstance = =3D 1 =20 TargetNode =3D 2, Tag  =3D 3 ?


  In the current=20 Draft MIB there is no=20 association=20 of Network portal with TargetNode.  =20

  Is=20 this = information missing in the DRAFT MIB = or am=20 I assuming=20 something wrong?

 =20

 Sorry for=20 sending direct mail to you. 

 Please let=20 me know if there is reflector = ( forum) to post=20 this type of questions.

Thanks

Venkat=20

 


 







------_=_NextPart_001_01C34AA3.DD748412--