RE: iSCSI Naming and Discovery

[julian_satran@il.ibm.com]

Joshua & John,

If the troublesome item is for a "knowledgeable" gateway to to FC to get a
hold on LUNs
then this can be done within the current draft.
The LUN in the PDUs is an 8byte "object" opaque to iSCSI.
An initiator can choose to put there a WWN to be replaced (rewritten) by
the gateway with
a LUN or nay such commbination.  This operation is stateless.

Julo

"Joshua Tseng/Nishan Systems" <joshua.tseng@NishanSystems.com> on
05/10/2000 22:26:01

Please respond to "Joshua Tseng/Nishan Systems"
      <joshua.tseng@NishanSystems.com>

To:   ips@ece.cmu.edu
cc:    (bcc: Julian Satran/Haifa/IBM)
Subject:  RE: iSCSI Naming and Discovery




John,

>Joshua,
>I think the LU being part of the "/Modifier" is a bit problematical.  You
>should focus on the connections each end, and let the LU stuff be
>transparent to your Gateway.  They will of course use Report LUNs and
>Inquiry and use their approprate LU number, I am having problems
>understanding why a gateway would need to know the LU number.
>
>Could you resend your note without the LUN stuff so that we can see, a
>little easier, what you think is really needed.

You are right...my bad.  The LUN is carried in the iSCSI PDU.
What is needed in the Fibre Channel World Wide Port Name (WWPN),
which the gateway will need in order to address the Fibre Channel
device.  The gateway/proxy should register this attribute key in
the name server (yes Doug--an LDAP-based server) for retrieval by
the iSCSI initiator, who can use it in the /modifier when addressing
the Fibre Channel target.

Josh