Additional items for special review in FCP-2 revision 6

Robert Snively rsnively at Brocade.COM
Thu Feb 15 13:58:59 PST 2001


* From the T10 Reflector (t10 at t10.org), posted by:
* Robert Snively <rsnively at brocade.com>
*
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0979A.812450D4
Content-Type: text/plain; charset="iso-8859-1"

10.1 X36086_Heading2_101Initiator and target required in image pair

In clause 6, the text needs to document that process login requires a
complementary pair of one initiator capable device and one target
capable device. If this is violated, the attempt to perform a process
login is rejected, presumably by not creating an image pair.

Response:

The comment and correction was accepted by the working group in the
January 15, 2001 meeting.

Installation:

In 6.3.1, the text is modified to say:

	If the PRLI is requesting a binding action by setting the
Establish Image Pair bit to one, the PRLI accept reports the
capabilities of the responder to the Originator and establishes an image
pair. An image pair shall be established only if the FCP devices have
complementary initiator and target capabilities. If both FCP devices
have both initiator and target capabilities, a single image pair allows
both initiators to access the complementary target capabilities of the
other device in the pair. Some capabilities require support by both the
Originator and Responder before they can be used (see 6.3.5). The Image
Pair Established bit in the PRLI accept indicates that an image pair was
successfully established.

Please review.

10.2 Behavior when no image pair is established.

Attempts to pass a SCSI command to a device with which an image pair is
not established cause a process logout when the first SCSI command
violates the rule. Text describing this will be placed in the
appropriate part of clause 6.

Response:

The comment and correction was accepted by the working group in the
January 15, 2001.

Installation:

The text in 6.2 says:

	Any FCP IUs received by an initiator or target from an N_Port or
NL_Port that has not established an image pair with that initiator or
target shall be rejected with a P_RJT containing a reject reason code of
TYPE NOT SUPPORTED. (See FC-FS.)

This functionality is not specified by FC-FS, but is consistent with the
error codes defined by FC-FS. Considering this text, the proposed change
is in conflict and is not installed. 

Please review.

10.3 Only one image pair required for target/initiator 

What is the state of process logins with either both capabilities at
both ends or with asymmetric capabilities? This occurs with AEN
inherently. Are separate image pairs required for both directions? The
consensus is that this can be done with one image pair.

Response:

After discussion in the January 15, 2001 working group meeting, the
committee decided that one image pair is all that is required to connect
a port having both target and initiator capabilities to either a port
having both capabilities or a port having only one capability. This is
clarified in the appropriate part of clause 6.

Installation:

See 10.1.

10.4 PRLI performed only by initiators

PRLI shall never be issued by a target-only device. This was accepted as
a comment.

Response:

The comment was created by and accepted by the working group in the
January 15, 2001 meeting.

Installation:

The text of 6.2 is modified to read:

	PRLI requests shall only be initiated by devices having the
initiator capability. Devices having only target capability shall not
perform a PRLI request. An initiator and target shall have successfully
completed a PRLI with a target that establishes an image pair before any
FCP IUs are exchanged. An image pair may also be established by an
implicit PRLI established by methods outside the scope of this standard.
An image pair is removed by a PRLO (see 6.4). If an image pair is not
established by an initiator to a target, the initiator and target shall
not exchange any FCP IUs. Any FCP IUs received by an initiator or a
target from an N_Port or NL_Port that has not established an image pair
with that initiator or target shall be rejected with a P_RJT containing
a reject reason code of TYPE NOT SUPPORTED. (See FC-FS.)

Please review



------_=_NextPart_001_01C0979A.812450D4
Content-Type: text/html; charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

 10.1 Initiator and target required in image pair In clause 6, the text needs to document that process login requires a complementary pair of one initiator capable device and one target capable device. If this is violated, the attempt to perform a process login is rejected, presumably by not creating an image pair. Response: The comment and correction was accepted by the working group in the January 15, 2001 meeting. Installation: In 6.3.1, the text is modified to say: If the PRLI is requesting a binding action by setting the Establish Image Pair bit to one, the PRLI accept reports the capabilities of the responder to the Originator and establishes an image pair. An image pair shall be established only if the FCP devices have complementary initiator and target capabilities. If both FCP devices have both initiator and target capabilities, a single image pair allows both initiators to access the complementary target capabilities of the other device in the pair. Some capabilities require support by both the Originator and Responder before they can be used (see 6.3.5). The Image Pair Established bit in the PRLI accept indicates that an image pair was successfully established. Please review. 10.2 Behavior when no image pair is established. Attempts to pass a SCSI command to a device with which an image pair is not established cause a process logout when the first SCSI command violates the rule. Text describing this will be placed in the appropriate part of clause 6. Response: The comment and correction was accepted by the working group in the January 15, 2001. Installation: The text in 6.2 says: Any FCP IUs received by an initiator or target from an N_Port or NL_Port that has not established an image pair with that initiator or target shall be rejected with a P_RJT containing a reject reason code of TYPE NOT SUPPORTED. (See FC-FS.) This functionality is not specified by FC-FS, but is consistent with the error codes defined by FC-FS. Considering this text, the proposed change is in conflict and is not installed. Please review. 10.3 Only one image pair required for target/initiator What is the state of process logins with either both capabilities at both ends or with asymmetric capabilities? This occurs with AEN inherently. Are separate image pairs required for both directions? The consensus is that this can be done with one image pair. Response: After discussion in the January 15, 2001 working group meeting, the committee decided that one image pair is all that is required to connect a port having both target and initiator capabilities to either a port having both capabilities or a port having only one capability. This is clarified in the appropriate part of clause 6. Installation: See 10.1. 10.4 PRLI performed only by initiators PRLI shall never be issued by a target-only device. This was accepted as a comment. Response: The comment was created by and accepted by the working group in the January 15, 2001 meeting. Installation: The text of 6.2 is modified to read: PRLI requests shall only be initiated by devices having the initiator capability. Devices having only target capability shall not perform a PRLI request. An initiator and target shall have successfully completed a PRLI with a target that establishes an image pair before any FCP IUs are exchanged. An image pair may also be established by an implicit PRLI established by methods outside the scope of this standard. An image pair is removed by a PRLO (see 6.4). If an image pair is not established by an initiator to a target, the initiator and target shall not exchange any FCP IUs. Any FCP IUs received by an initiator or a target from an N_Port or NL_Port that has not established an image pair with that initiator or target shall be rejected with a P_RJT containing a reject reason code of TYPE NOT SUPPORTED. (See FC-FS.) Please review


------_=_NextPart_001_01C0979A.812450D4--




More information about the T10 mailing list