Datasheet

Fibre Channel Interface
1-104 C141-C008
(a) ; The drive asserts –DSK_RD and requests the data to the enclosure.
(b) ; The enclosure asserts –ENCL_ACK after enabling the data on D (0:3).
(c) ; The drive reads the data and negates –DSK_RD.
(d) ; The enclosure negates –ENCL_ACK by –DSK_RD being negated.
(2) WRITE phase
WRITE phase is the same as COMMAND phase.
The protocol is shown in Figure 1.57.
1.11.5 SES sense codes
Table 1.30 ASC/ASCQ defined for ESI conditions
ASC/ASCQ Definition
35h/01h Unsupported Enclosure Function
35h/02h Enclosure Services Unavailable
35h/03h Enclosure Transfer Failure
35h/04h Enclosure Transfer Refused
1.11.6 Enclosure Initiated ESI transfer
Enclosure initiated ESI (EIE) provides a means for the enclosure to request
information or action from a SCSI device that supports an 8067 ESI interface.
The transfer of information is independent of the SCSI interface. The format of
the information, however, is similar to the SES information transferred on the
SCSI interface for ease of implementation.
1.11.6.1 EIE discovery
A discovery phase is defined to allow the enclosure to initiate an information
request and allow the SCSI device to detect the request. If the SCSI device
supports detection of the Un-Mated condition of the START_1 and START_2
signals, Case 1, and supports Enclosure Initiated ESI (EIE) transfers, it monitors
the START_1 and START_2 signals. On detecting a transition from a valid
mated condition, Case 2, 3, or 4, to a different case, the device asserts
–PARALLEL ESI. To avoid a false spin-down due to a hand shake timeout,
initiating an EIE transfer by changing from a mated condition to the unmated
condition is not recommended. If the enclosure is requesting a transfer with a
case change, it returns the START_1 and START_2 signals to the original mated
condition a minimum of 100 nanoseconds before asserting the –ENCL_ACK
signal. Figure 1.60 illustrates a successful discovery of an EIE transfer request.
Table 1.11 shows the detail of “Case”.