Re: iSCSI- duplicate initiator name
Paul von Behren <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <[email protected]> |
There are differences between path management via iSCSI session and path management via SCSI standards (SPC ALUA/TPGS) or SCSI-based, vendor-specific path management. Outside of iSCSI, multipathing is typically done at the SCSI layer, providing per-LUN configuration options from the host drivers (e.g., customer wants path A dedicated to LUN 7 and LUNs 0-6 all share path B). A host/driver implmentation may want to contiue providing that capability even in iSCSI. iSCSI sessions hide the per-LUN paths. You could set up separate target nodes for each LUN and get the same effect in iSCSI, but you can also opt for consistency with other SCSI transports. This is one scenario where the same initiator may want multiple connections to the same target. Paul Inbal Zilbershmidt wrote: > Is it possible to have 2 leading connections from the same initiator? > Isn't a session implies an IT nexus? > As I understood, it is possible to have multiple connections in a > single session. > My question was regarding to a 2nd leading connection from a certain > initiator name. I caused such situation by giving two different > initiators the same name. > I wanted to know how should I deal with such case. > > > Thanks, > > > > Inbal , > > Voltaire Ltd. > > > ------------------------------------------------------------------------ > *From:* John Hufferd [mailto:[email protected]] > *Sent:* Wednesday, March 22, 2006 9:01 AM > *To:* Inbal Zilbershmidt; [email protected] > *Subject:* RE: [Ips] iSCSI- duplicate initiator name > > The important question is how do you know it is another initiator. If > it has the same name it could be from any portal on the Initiator > system. The initiator name applies to the Whole OS. In fact it can > also apply to a whole cluster that acts as a system coupled system. > So if it passes the authentication tests, it is assumed to be from > that OS, and multiple Sessions from the same OS is OK. > > > > . > > . > > . > > John L Hufferd > > Sr. Executive Director of Technology > > Brocade Communications Systems, Inc > > [email protected] <mailto:[email protected]> > > Office Phone: (408) 333-5244; eFAX: (408) 904-4688 > > Alt Office Phone: (408) 997-6136; Cell: (408) 627-9606 > > > > ------------------------------------------------------------------------ > > *From:* Inbal Zilbershmidt [mailto:[email protected]] > *Sent:* Tuesday, March 21, 2006 10:54 PM > *To:* [email protected] > *Subject:* [Ips] iSCSI- duplicate initiator name > > > > Hello, > > > > Maybe someone can help me: > > > > I wanted to know how a target should react in a case when an initiator > trying to connect to it, has the same name as other initiator already > connected. > > > > Thanks, > > > > Inbal , > > Voltaire Ltd. > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >Ips mailing list >[email protected] >https://www1.ietf.org/mailman/listinfo/ips > > _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips