Re: SCSI URL scheme [WAS: Re: iSCSI: 2.2.6. Naming & mapping]

["John Hufferd/San Jose/IBM" <hufferd@us.ibm.com>]

Costa,
I can see how a Host can acquire the WWN information from the Storage
Controller.  I can even see a management application on that host, building
a name similar to what you said, and sending it to a Management Center,
(which can report on its status from time to time, etc.).

However, I need your help in the "path" part of your name.  What do you
think this is?  Does it have something to do with the initiator Side or the
Target Side?  Is it a IP address (or a name reducible to an IP address).  I
am also assuming that your WWN part is the EVPD (page code 83h) that was
talked about by Jim Hafner, is that right?

.
.
.
John L. Hufferd


Sent by:  owner-ips@ece.cmu.edu


To:   IP Storage <IPS@ece.cmu.edu>
cc:   csapuntz@cisco.com
Subject:  SCSI URL scheme [WAS: Re: iSCSI: 2.2.6. Naming & mapping]




Here is a proposal to extend the iSCSI URL scheme to support LUNs and
WWNs. It was originally proposed by Daniel Smith of IBM Almaden. This
extension is not required for the iSCSI transport protocol, but may be
useful for discovery and management.

A URL for the target has the following form:

scsi://hostname/path/with/

A URL referring to a specific LU has the following form:

scsi://hostname/path/with/?LUN=lunnumber?WWN=wwnnumber

If no LUN= term appears in the URL, then LUN 0 is assumed.

The WWN= term is optional. If present, the party should
verify that the WWN in the LU's Device Identification Inquiry
Page correspojnds to the WWN.

Note, the following URL:

scsi://gsg.cisco.com/tape/?WWN=0a050a4bcdefa

refers to LUN 0 of target scsi://gsg.cisco.com/tape/. After
connecting, the initiator should verify that the WWN
of the LU is 0a050a4bcdefa.

-Costa