SCSI Primary Commands - 2.pdf

18 July 2001 T10/1236-D Revision 20For multiple port implementations, devices on other ports (i.e., the ports that do not include the initiator to which thereservation has been granted) also shall be denied access to the logical unit as described in the precedingparagraph.7.21.3 Third-party reservationThird-party reservations are mandatory if the RESERVE(10) command is implemented. The third-party reservationfor the RESERVE(10) command allows an application client to reserve a logical unit within a logical unit foranother SCSI device. This is intended for use in multiple initiator systems that use the COPY or EXTENDEDCOPY command.If the third-party (3RDPTY) bit is zero, then a third-party reservation is not requested. If the 3RDPTY bit is zero thenthe LONGID bit shall be ignored. If the 3RDPTY bit is one then the device server shall reserve the specified logicalunit for the SCSI device specified in the THIRD-PARTY DEVICE ID field. Device ID formats are protocol specific. Thedevice server shall preserve the reservation until it is superseded by another valid RESERVE command from theinitiator that made the reservation or until it is released by the same initiator, by a TARGET RESET taskmanagement function performed by any initiator, a hard reset condition, or by a power on cycle. The device servershall ignore any attempt to release the reservation made by any other initiator.After a third-party reservation has been granted, the initiator that sent the RESERVE command shall be treated likeany other initiator. Reservation conflicts shall occur in all cases where another initiator is not allowed access due tothe reservation.If independent sets of mode parameters are implemented, a third-party reservation shall cause the device server totransfer the set of mode parameters in effect for the application client that sent the RESERVE command to themode parameters used for commands from the third-party device. Any subsequent command issued by thethird-party device shall be executed according to the mode parameters in effect for the application client that sentthe RESERVE command.NOTE 34 This transfer of the mode parameters is applicable to device servers that store mode informationindependently for different initiators. This mechanism allows an application client to set the mode parameters of atarget for the use of a copy master (i.e., the third-party device). The third-party copy master may subsequentlyissue a MODE SELECT command to modify the mode parameters.If the THIRD-PARTY DEVICE ID value associated with the reservation release is smaller than 255, the LONGID bit maybe zero and the ID value sent in the CDB. Device ID formats are protocol specific. If the THIRD-PARTY DEVICE ID isgreater than 255, the LONGID bit shall be one. If the LONGID bit is one, the THIRD-PARTY DEVICE ID field in the CDBshall be ignored. If the LONGID bit is one, the parameter list length shall be at least eight. If the LONGID bit is oneand the parameter list length is less than eight, the device server shall return a CHECK CONDITION status with asense key of ILLEGAL REQUEST.Device servers that support device IDs greater than 255 shall accept commands with LONGID equal to one. Deviceservers whose devices IDs are limited to 255 or smaller may reject commands with LONGID equal to one withCHECK CONDITION status and a sense key of ILLEGAL REQUEST.dpANS SCSI Primary Commands - 2 (SPC-2) 157