Dheeraj Sangamkar wrote: > I would like to know how each of the Host Channel TargetId and LUN are > enumerated and assigned to each SCSI device. Randomly. The [h:c:i:l] tuple is a Linux SCSI core internal artifact and is *not* to be confused with initiator port identifier, target port identifier, and logical unit identifier (a.k.a. LUN). [...] > How are LUN Ids enumerated? Does the order in which the response > REPORT_LUN command gives LUNs, determine the LUN ID assignment for a > SCSI disk discovered on a remote target on an array connected via FC? The SCSI core does not care about LUNs and does not even pass LUNs through from transport layer to application clients. You can obtain LUNs from transport-layer specific sysfs attributes, but not from the Linux SCSI core layer. -- Stefan Richter -=====-==--= --=- =---- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
