HP Public Review comments on FCP
Kurt Chan
kc at core.rose.hp.com
Mon Mar 27 11:27:19 PST 1995
March 27, 1995
Kurt Chan
M/S 5601
Hewlett-Packard Corporation
8000 Foothills Blvd
Roseville, CA 95747
Telephone: (916) 785-5621
FAX: (916) 785-2875
EMAIL: kc at core.rose.hp.com
X3 Secretariat
Attention: Lynn Barra
1250 Eye Street NW., Suite 200
Washington, DC 2005-3922
------------------------------------------------------------------------
The following are Hewlett-Packard Corporation's public review comments
on Fibre Channel Protocol for SCSI (FCP) (X3T10-993D, revision 010).
Comments are organized as follows:
#xxx (?) y.y.y
Where :
#xxx is the comment number;
"?" is the type (E: Editorial, T: Technical);
y.y.y is the clause or subclause number.
------------------------------------------------------------------------
The following comments involve 3 principal changes:
1) The use of FCP_CMND and FCP_RSP IUs for the purposes of sending
Task Management functions and receiving a response from a Target
for those functions.
2) Including login parameters in the set of objects within a Target
which are restored to their default conditions upon receipt of
Target Reset,
3) Avoidance of the confusing wording regarding "ambiguous exchanges"
by making error recovery within FCP profile-specific. Various
profiles are explicit and complete in defining error recovery. The
standard should only provide mechanisms by which the appropriate
level of error recovery for the application can be assured.
------------------------------------------------------------------------
Comments:
#001 (T) 5.3, Table 5
- Change T1 to: Command or Task Management Function Request
- Delete T5. (May want to add explanatory note regarding its absence).
#002 (T) 5.3, Table 6
- Change I4 to: Command or Task Management Function Response
#003 (T) 7.1.2.2
Modify the first paragraph of TARGET RESET as follows:
TARGET RESET, when set to one,
a) performs a hard reset to the SCSI target as defined by SAM,
b) resets all tasks within the target for all initiators,
c) resets all internal states of the target to their initial power on
or default values,
d) causes all initiators to be implicitly logged out with the target
(implicit LOGO and implicit PRLO),
e) causes a unit attention condition to be created for all initiators
#004 (E) 7.1.2.2
Attempts to define the term "ambiguous exchange" and the use of this
concept to invoke error recovery is confusing and overly complex.
Replace the last two paragraphs of TARGET RESET with:
"The TARGET RESET is transmitted by the initiator (exchange
originator) using a new exchange. Additional FC-PH recovery may be
necessary following TARGET RESET"
#005 (E) 7.1.2.2
Attempts to define the term "ambiguous exchange" and the use of this
concept to invoke error recovery is confusing and overly complex.
Replace the last two paragraphs of CLEAR TASK SET with:
"The CLEAR TASK SET is transmitted by the initiator (exchange
originator) using a new exchange. Additional FC-PH recovery may be
necessary following CLEAR TASK SET."
#006 (E) 7.1.2.2
Attempts to define the term "ambiguous exchange" and the use of this
concept to invoke error recovery is confusing and overly complex.
Replace the second and third paragraphs of ABORT TASK SET with:
"The ABORT TASK SET is transmitted by the initiator (exchange
originator) using a new exchange. Additional FC-PH recovery may be
necessary following ABORT TASK SET."
#007 (T) 7.4.5, Table 20
Modify RSP_CODE = 00 as follows and add codes 04 and 05:
RSP_CODE Definition
00 No Failure or Task Management Function Complete
04 Task Management Function Not Supported
05 Task Management Function Failed
Insert the following text below the table:
"The task management function may or may not have been performed by
the target if RSP_CODE = 05 is returned, or if no FCP_RSP is
returned. Values 04 and 05 are not valid responses to SCSI
Commands."
#008 (T) B.1.9, page 53
Change the example to T1 instead of T5, and add the I4 response.
Delete the last sentence of the first paragraph.
More information about the T10
mailing list