Datasheet

Command Specifications
4-128 C141-C008
The "Service Action Reservation Key" field contains information needed for four
service actions; the REGISTER, REGISTER AND IGNORE EXISTING KEY,
PREEMPT, and PREEMPT AND ABORT service actions. For the REGISTER
and REGISTER AND IGNORE EXISTING KEY service action, the "Service
Action Reservation Key" field contains the new reservation key to be registered.
For the PREEMPT and PREEMPT AND ABORT service actions, the "Service
Action Reservation Key" field contains the reservation key of the persistent
reservations that are being preempted. The "Service Action Reservation Key"
field is ignored for all other service actions.
If the scope is an Element reservation, the "Scope-specific Address" field shall
contain the Element address, zero filled in the most significant bytes to fit the
field. If the service action is REGISTER, REGISTER AND IGNORE EXISTING
KEY, or CLEAR or if the scope is a Logical Unit reservation, the "Scope-specific
Address" field shall be set to zero.
The "Activate Persist Through Power Loss (APTPL)" bit shall be valid only for
the REGISTER, or the REGISTER AND IGNORE EXISTING KEY service
action. In all other cases, the "APTPL" bit shall be ignored. Support for an
"APTPL" bit equal to one is optional. If a device server that does not support the
"APTPL" bit value of one receives that value in a REGISTER or a REGISTER
AND IGNORE EXISTING KEY service action, the device server shall return a
CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in
parameter list [=26-00]).
If the last valid "APTPL" bit value received by the device server is zero, the loss
of power in the target shall release the persistent reservation for all logical units
and remove all reservation keys. If the last valid "APTPL" bit value received by
the device server is one, the logical unit shall retain any persistent reservation(s)
that may be present and all reservation keys for all initiators even if power is lost
and later returned
Table 4.6 summarizes which fields are set by the application client and
interpreted by the device server for each service action and scope value. The
"APTPL" bit PERSISTENT RESERVE OUT parameter is not summarized in
table 4.6, since it is specified above.