fcp4-r2a

Knight, Frederick Frederick.Knight at netapp.com
Mon Jan 3 06:21:12 PST 2011


Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1101030_f.htm">HTML-formatted message</a>

As per letter ballot comments, D.1.1 was correctly adjusted to match
SPC-4; but D.1.2 is missing the corresponding chance (it is still based
on old SPC revs).
Step 2 and step 3 of D.1.2 need to be updated:
2) For each loop ID found in step 1, perform login and Process Login,
and if the device is determined to be an FCP target, issue an INQUIRY
command to LUN 0 (see 6.2 and SPC-4);
3) If the INQUIRY command succeeds, issue a REPORT LUNS command to LUN 0
to obtain a list of the logical units accessible through the target
FCP_Port (see SPC-4); and
Replace with
2)     For each loop ID found in step 1, perform login and Process
Login, and if the device is determined to be an FCP target, issue a
REPORT LUNS command to LUN 0 or to the REPORT LUNS well known logical
unit to obtain a list of the logical units accessible through the target
FCP_Port (see SPC-4);
3)     issue an INQUIRY command to each logical unit identified in the
list obtained from the REPORT LUNS command to identify the peripheral
device type of each logical unit (see 6.2 and SPC-4); and
Fred Knight



More information about the T10 mailing list