C141-C008-01EN MAT3073FC, MAT3147FC, MAT3300FC SERIES MAU3036FC, MAU3073FC, MAU3147FC SERIES DISK DRIVES FIBRE CHANNEL INTERFACE SPECIFICATIONS
FOR SAFE OPERATION Handling of This Manual This manual contains important information for using this product. Read thoroughly before using the product. Use this product only after thoroughly reading and understanding especially the section "Important Alert Items" in this manual. Keep this manual handy, and keep it carefully. FUJITSU makes every effort to prevent users and bystanders from being injured or from suffering damage to their property. Use the product according to this manual.
Revision History (1/1) Edition Date Revised section (*1) (Added/Deleted/Altered) Details 01 2004.07.28 — — *1 Section(s) with asterisk (*) refer to the previous edition when those were deleted.
This page is intentionally left blank.
Preface This manual explains concerning the MAT3073FC, MAT3147FC, MAT3300FC, MAU3036FC, MAU3073FC, MAU3147FC series 3.5 inch hard disk drives with internal Fibre channel controller. The purpose of this manual is to provide the specifications and functions of Fibre channel (FC) for use of these magnetic disk drives incorporated into user systems, and to present the information necessary for creating host system software.
Preface Chapter 5 Sense Data and Error Recovery Methods This chapter describes the configuration and contents of sense data which report to the host system when an error occurs, etc., key information necessary for error recovery, recommended procedures for error recovery to be executed through host system software and retry processing. Chapter 6 Disk Media Management This chapter describes the procedure for initializing the disk media, methods of treating media defects and data recovery methods.
Preface CONVENTIONS USED IN THIS MANUAL The model name of disk drives covered by this manual differs in its ending suffix (Note 1) depending on its device type (three types), the electrical conditions of the Fibre channel interface used to connect the disk drive to the host system and its capacity and data format at the time it was shipped, but in this manual, except in cases where models need to be especially distinguished, a representative model name (Note 2) is used.
Preface Conventions for Alert Messages This manual uses the following conventions to show the alert messages. An alert message consists of an alert signal and alert statements. The alert signal consists of an alert symbol and a signal word or just a signal word. The following are the alert signals and their meanings: This indicates a hazardous situation likely to result in serious personal injury if the user does not perform the procedure correctly.
Preface MANUAL ORGANIZATION Product Manual 1. 2. 3. 4. 5. 6. Outline Specifications Data Format Installation Conditions Installation Procedure Diagnosis and Maintenance Interface Specifications (This Manual) 1. 2. 3. 4. 5. 6. Fibre Channel Interface Command Processing Data Buffer Management Command Specifications Sense Data and Error Recovery Methods Disk Media Management Maintenance Manual 1. 2. 3. 4. 5.
Preface REFERENCED STANDARDS The product specifications and functions described in this manual conform to the following standards: Specification (document) number vi Name Concerned organization NCITS TR-19 FIBRE CHANNEL PRIVATE LOOP SCSI DIRECT ATTACH (FC-PLDA) American National Standards Institute (ANSI) ANSI X3. 230-1994 FIBRE CHANNEL PHYSICAL AND SIGNALING INTERFACE (FC-PH) American National Standards Institute (ANSI) ANSI X3.
Contents CHAPTER 1 Fibre Channel Interface ........................................................... 1-1 1.1 Topologies in Fibre Channel Interface..................................................... 1-2 1.1.1 Node/port ............................................................................................. 1-3 1.1.2 Link...................................................................................................... 1-3 1.1.3 Arbitrated loop...............................................
Contents 1.7 Extended Link Service............................................................................1-38 1.7.1 N_Port login (PLOGI/PLOGI_ACC) ................................................1-40 1.7.1.1 Port/node name format ......................................................................1-42 1.7.1.2 Common service parameter ...............................................................1-44 1.7.1.3 Class 3 service parameter .................................................................
Contents 1.9.4.2 FCP response information ................................................................. 1-95 1.9.4.3 FCP sense information ...................................................................... 1-96 1.10 Errors on Loop (Refer to FC-PH , Section 29.9).................................. 1-97 1.11 Enclosure Service Interface (ESI) ........................................................ 1-99 1.11.1 Data transfer protocol .......................................................................
Contents 2.6 Sense Data Hold State ............................................................................2-21 2.7 Command Processing Exceptions ..........................................................2-21 2.7.1 Overlapping commands .....................................................................2-21 2.7.2 Illegal LUN specification ..................................................................2-22 2.7.3 Reserved operation code.............................................................
Contents 4.1.7 MODE SENSE EXTENDED (5A).................................................... 4-78 4.1.8 REZERO UNIT (01).......................................................................... 4-80 4.1.9 START/STOP UNIT (1B) ................................................................. 4-80 4.1.10 RESERVE (16)................................................................................... 4-82 4.1.11 RESERVE EXTENDED (56) ........................................................... 4-85 4.1.
Contents CHAPTER 5 4.4.3 WRITE BUFFER (3B) ....................................................................4-186 4.4.4 READ BUFFER (3C) ......................................................................4-193 4.4.5 READ LONG (3E)...........................................................................4-197 4.4.6 WRITE LONG (3F) .........................................................................4-199 4.4.7 WRITE SAME (41) .............................................................
Contents Glossary ......................................................................................................... GL-1 Acronyms and Abbreviations........................................................................ AB-1 Index .................................................................................................................
Contents Illustrations Figures Figure 1.1 Example of FC-AL connection............................................................ 1-2 Figure 1.2 Port bypass circuit ............................................................................... 1-4 Figure 1.3 Buffer-to-buffer frame transfer............................................................ 1-5 Figure 1.4 Data category on the loop.................................................................... 1-6 Figure 1.5 Format of ordered sets ...........
Contents Figure 1.36 Figure 1.37 Figure 1.38 Figure 1.39 Figure 1.40 Figure 1.41 Figure 1.42 Figure 1.43 Figure 1.44 Figure 1.45 Figure 1.46 Figure 1.47 Figure 1.48 Figure 1.49 Figure 1.50 Figure 1.51 Figure 1.52 Figure 1.53 Figure 1.54 Figure 1.55 Figure 1.56 Figure 1.57 Figure 1.58 Figure 1.59 Figure 1.60 Figure 1.61 Figure 1.62 Figure 1.63 Figure 1.64 Logout parameter pages ...................................................................1-65 Link service reject (LS_RJT) ..............................
Contents Figure 3.2 Example of data buffer operation during read..................................... 3-3 Figure 3.3 Example of data buffer operation during write ................................... 3-5 Figure 4.1 MODE SELECT parameter structure................................................ 4-19 Figure 4.2 Reserve right and the third party reserve function ............................ 4-84 Figure 4.3 SET LIMITS command: specifying the range where access is permitted........................................
Contents Tables Table 1.1 Frame header format..............................................................................1-8 Table 1.2 R_CTL .................................................................................................1-10 Table 1.3 Type .....................................................................................................1-10 Table 1.4 F_CTL..................................................................................................1-11 Table 1.
Contents Table 1.40 Port parameters ............................................................................... 1-113 Table 1.41 Link status page ............................................................................. 1-114 Table 1.42 Transmitting and receiving of frames at the interface .................... 1-119 Table 2.1 6-Byte CDB basic format...................................................................... 2-2 Table 2.2 10-Byte CDB basic format............................................
Contents Table 4.20 MODE SELECT parameters: verify error recovery parameters ..........................................................................................4-45 Table 4.21 MODE SELECT parameters: caching parameters ...........................4-47 Table 4.22 MODE SELECT parameters: control mode parameters ..................4-53 Table 4.23 TST ....................................................................................................4-54 Table 4.24 QErr ....................................
Contents Table 4.53 Read errors recovered without delays (page 03, code 0000) .......... 4-102 Table 4.54 Read errors recovered with possible delays (page 03, code 0001) ....................................................................... 4-103 Table 4.55 Total read errors posted (page 03, code 0002)................................ 4-103 Table 4.56 Total recoverable read errors posted to INIT (page 03, code 0003) ....................................................................... 4-104 Table 4.
Contents Table 4.86 Table 4.87 Table 4.88 Table 4.89 Table 4.90 Persistent reservations scope ...........................................................4-123 Persistent reservations type codes ...................................................4-124 PERSISTENT RESERVE OUT service action codes .....................4-126 PERSISTENT RESERVE OUT parameter list ...............................4-127 PERSISTENT RESERVE OUT service action and valid parameters .......................................................
Contents Table 4.120 Table 4.121 Table 4.122 Table 4.123 Table 4.124 Table 4.125 Table 4.126 Table 4.127 Table 4.128 Table 4.129 Address format.............................................................................. 4-184 ESI page code................................................................................ 4-184 ESI page format ............................................................................ 4-185 Short enclosure status .............................................................
CHAPTER 1 Fibre Channel Interface 1.1 Topologies in Fibre Channel Interface 1.2 Information Transmitted on the Loop 1.3 Physical Requirements, Electrical Requirements 1.4 Drive Operation on the Loop 1.5 Ordered Sets (Refer to FC-PH, Section 11.4 and FC-AL, Chapter 6) 1.6 Basic Link Service 1.7 Extended Link Service 1.8 Extended Link Service (Loop initialization) 1.9 FC-4 Device Data 1.10 Errors on Loop (Refer to FC-PH, Section 29.9) 1.11 Enclosure Service Interface (ESI) 1.
Fibre Channel Interface 1.1 Topologies in Fibre Channel Interface Three kind of topologies are defined in ANSI standards. (Arbitrated Loop, Fabric and Point-to-Point) The drive supports Arbitrated Loop and Fabric as the primary topologies for the drive connections. Figure 1.1 shows the example of connection for disk drives in FC-AL. Figure 1.1 Example of FC-AL connection BC are port bypass circuits on the back plane commonly, where Node mean the Target or initiator.
1.1 Topologies in Fibre Channel Interface 1.1.1 Node/port Any device connected to Fibre Channel topology is called “node”. In the application of this drive, the drive itself and the initiator are the nodes. Each node has at least one port to connect other nodes and the port is called N_port. Especially, in FC-AL, the port is called “NL_Port” where “NL” stands for node loop. The drive provides two ports and each port is connected to each FC-AL. See Figure 1.1. 1.1.
Fibre Channel Interface 1.1.4 Port bypass circuit (BC) Port bypass circuit is to bypass the drive if it cannot provide loop services. For example, by removing the drive, unable to obtain valid data, or by any special condition. The port bypass circuit is located external to the drive. (for example, on the back plane) Figure 1.2 shows the relationship between the drive and the circuit.
1.2 Information Transmitted on the Loop 1.1.6 Buffer-to-buffer frame transfer As shown in Figure 1.3, data transmission occurs from an output buffer in the node part to an input buffer in the node port. The basic unit of buffer-to-buffer transfer is the frame. Transmit Buffer 8bit 8bit 8bit 8bit in NL_Port 8B/10B Encoder Serializer Serial Transfer on FC loop Deserializer 8B/10B Decoder 8bit 8bit 8bit in NL_Port 8bit Receive Buffer Figure 1.3 Buffer-to-buffer frame transfer 1.
Fibre Channel Interface Figure 1.4 shows category of the data on the loop.
1.2 Information Transmitted on the Loop The K28.5 special character is always used as the first character of all ordered sets. K28.5 Dxx.y Dxx.y Dxx.y Figure 1.5 Format of ordered sets 1.2.1.1 Primitive signals Primitive Signals have a control function to indicate status of the drive or to perform some operation to the port being connected. Primitive Signals are recognized when one ordered set is detected. A minimum of six Primitive Signals must be transmitted between each frame.
Fibre Channel Interface 1.2.2 Frame structure (refer to FC-PH, chapter 17) A frame format is shown in Figure 1.6. byte count 4 fill words SOF word count 24 Frame Header Payload 6 1 4 4 CRC EOF 1 1 0-2048+64 (optional header) 0-528 min24 fill words min6 Figure 1.6 Frame format a) SOF; Start of frame indicates the beginning of the frame. b) Frame Header; Used as link control, drive protocol transfer and detect error condition. The frame header format is listed in Table 1.1. Table 1.
1.2 Information Transmitted on the Loop c) OX_ID; Originator Exchange Identifier, assigned by the originator of an exchange. This value is similar to Queue Tag in SCSI and must be unique for a pair between the initiator and the drive. RX_ID; Responder Exchange Identifier, generated by the responder for an exchange. OFFSET; Defines the relative displacement of the first byte of the payload from the base address of the command. Payload; Data field, must be multiple of four bytes.
Fibre Channel Interface Table 1.
1.2 Information Transmitted on the Loop Table 1.
Fibre Channel Interface (1) Link Data Link Data is used when the initiator transmit control code to the target or when the target responses to the initiator. Link Data supported by the drive are listed below. Link Service (1) BASIC LINK SERVICES Table 1.5 BASIC LINK SERVICES Basic Link Service Request Frames Abbr. Support ABTS Yes Abbr.
1.2 Information Transmitted on the Loop Table 1.6 EXTENDED LINK SERVICES (2/2) Extended Link Service Request Frames Abbr. Support Read Exchange Status Block RES No Request Sequence Initiative RSI No Read Sequence Status Block RSS No Extended Link Service Request Frames Abbr. Support Accept ACC Yes LS_RJT Yes Link Service Reject • Extended Link Services-Loop Initialization Table 1.
Fibre Channel Interface a) SCSI write operation Initiator Target (drive) 1) FCP_CMND_IU (WT) 2) FCP_XFER_RDY_IU 3) FCP_DATA_IU (Write) Exchange ; from command frame to response frame : 4) FCP_RSP_IU b) SCSI read operation Initiator Target (drive) 1) FCP_CMND_IU (RD) 3) FCP_DATA_IU (Read) Exchange ; from command frame to response frame : 4) FCP_RSP_IU Figure 1.
1.3 Physical Requirements, Electrical Requirements 1.3 Physical Requirements, Electrical Requirements 1.3.1 Interface connector The connector for the fibre channel loop bus is an unshielded SCA-2 connector conforming to SCSI-3 type which has two 20-pin rows spaced 1.27 mm (0.05 inch) apart. Figure 1.8 shows the fibre channel connector. See Section 1.3.2, 1.3.3 for signal assignments on the connector. Figure 1.
Fibre Channel Interface Table 1.8 lists signal assignments on the connector. Table 1.8 FC-SCA connector: CN1 Pin No. Signal Signal Pin No.
1.3 Physical Requirements, Electrical Requirements 1.3.2 Signal function in SFF8045 mode (1) +12V charge, +5V charge These signals are used to precharge of the internal circuits to avoid excessive surge current while hot plugging is being operated. Before power voltage pins (+12V and +5V) make contact, these precharge pins mate early. Precharge control circuits are external to the drive. The voltage provided to the precharge signals are defined in Table 1.9. Table 1.
Fibre Channel Interface (3) Active LED out The signal indicates that the drive starts and is active. Two alternative indication pattern is defined in SFF-8045 Specification Rev 4.2. One is “hot plug implementation” for the drives in hot plugged environments. The other is “legacy implementation” where the compatibility with previous SCSI indication system is required. The drive supports hot plug implementation described below. a) The Active LED out signal does not light if the drive is not connected.
1.3 Physical Requirements, Electrical Requirements The mating deskew time is minimum 250 msec. A 10 KΩ pull up register to 5V for each signal is asserted on the drive. The open and ground states should be controlled as in Table 1.12. Table 1.12 Electric requirement for input control State Current Voltage open 20 µA
Fibre Channel Interface (7) DEV_CTRL_CODE [2, 1, 0] DEV_CTRL_CODES Provide Link Rate, and Power Failure Warning (PFW) to the drive. Table 1.14 Electric requirement for DEV_CTRL_CODE inputs State Current Voltage high –20 µA
1.3 Physical Requirements, Electrical Requirements Table 1.
Fibre Channel Interface (8) Port out (+port A_out, +port B_out) Port out signals are output by the drive. These signals are differential copper with a termination of 50 Ω embedded in HDC Chip and 100 Ω to output ECL signal label on the loop . The output circuit is shown in Figure 1.9. 36Ω + Port Out TX+ 220Ω HDC outside of the drive 36Ω TX– – Port Out Figure 1.
1.3 Physical Requirements, Electrical Requirements This signal is asserted when; a) detecting of the Loop Port Bypass primitive sequence b) being removed of the drive from the loop c) loss of receive clock d) loss of transmission clock e) detecting hardware error within the drive This signal is negated when the drive detects a Loop Port Enable primitive sequence. (11) –Drive present ; This signal connected to the ground. 1.3.
Fibre Channel Interface 1.4 Drive Operation on the Loop This section describes the following as the operations which the drive is required to perform at FC level: • Loop initialization • Arbitration • Communication between the initiator and target 1.4.1 Loop initialization (1) Process Outline Loop Initialization is a process for the purpose listed below. • To obtain Arbitrated Loop Physical Address (AL_PA) because the drive has no valid address when powered on.
1.4 Drive Operation on the Loop (2) AL_PA This sub-section describes the addresses (AL_PA) used on the loop. AL_PA is an 8-bit character and when encoded to 10 bits, AL_PA has an equal number of ones or zeros to maintain neutral running disparity. Table 1.18 shows the AL_PA values and the priority used on the loop. Details of AL_PA is described in Table 1.16. Table 1.18 AL_PA value/priority Values (hex) Priority & Use 00 Highest priority and assigned for FL_port.
Fibre Channel Interface Table 1.19 LIP sequences LIP type Use Description LIP (F7, F7) LIP (F7, AL_PS) Initializing Loop A NL_Port requests to obtain AL_PA *1 LIP (AL_PD, AL_PS) Reset the port The source port (AL_PS) requests to reset the destination port (AL_PD). The selected port performs to reset after loop initialization. *2 LIP (F8, AL_PS) Loop failure The NL_Port has detected an input failure AL_PS is the AL_PA of the source port.
1.4 Drive Operation on the Loop Step Port Name n [1] Transmits LISM with its own port name to the next port. n+1 LISM (n) n+2 LISM (n+1) LISM (n+2) [2] Receives LISM from the upper loop port. LISM (n+2) LISM (n) [3] Compares the port name with its own port name and transmits LISM (n) LISM with lower port name. LISM (n+1) LISM (n) LISM (n+1) [4] Receives LISM from the upper loop port.
Fibre Channel Interface (5) LIFA/LIPA/LIHA/LISA This sub-section describes a process for each port to obtain AL_PA. Figure 1.12 shows the process for non loop master to obtain unique AL_PA after ending a process for selecting the loop master. Loop Master Other NL_Port on the loop LIFA LIPA LIHA LISA ; LIFA is used to gather all fabric-assigned AL_PAs. ; LIPA is used to gather all previously-acquired AL_PAs.
1.4 Drive Operation on the Loop 1.4.2 Arbitration For information to be exchanged between the ports connected to a loop, generally the two ports (send side and receive side) must occupy the loop (placed in pointto-point connection state). Arbitration is a process to win access right on the loop and must be done before communicating with another port. When the arbitration is finished, only a pair of a initiator and a target can communicate each other on the loop.
Fibre Channel Interface (1) Command Transfer Initiator Target When the initiator issues FCP_CMND_IU: ARBx OPN R_RDY FCP_CMND_IU CLS Figure 1.13 Command transfer (2) Transfer Ready (X_RDY) , Response Transfer (RSP) Initiator Target ARBx When the target issues FCP_XFER_RDY_IU or FCP_RSP_IU OPN R_RDY FCP_XFER_RDY_IU or FCP_RSP_IU CLS Figure 1.
1.4 Drive Operation on the Loop (3) Write Data Transfer Initiator Target When the target recognizes the sending of write data ARBx OPN R_RDY R_RDY R_RDY R_RDY Write Data 1 R_RDY Write Data 2 FCP_Data_IU R_RDY Write Data n CLS Figure 1.15 Write data transfer (4) Read Data Transfer Initiator Target ARBx When the target sends read data: OPN R_RDY Read Data 1 R_RDY Read Data 2 R_RDY : Read Data n CLS Figure 1.
Fibre Channel Interface 1.5 Ordered Sets (Refer to FC-PH, Section 11.4 and FC-AL, Chapter 6) Table 1.20 shows the Ordered Sets specification. This section describes handling of the Ordered Sets of this drive. Table 1.20 Ordered sets specification (1/2) No.
1.6 Basic Link Service Table 1.20 Ordered sets specification (2/2) No.
Fibre Channel Interface The Basic Link Services supported by this drive are the Abort Sequence (ABTS) and its responses, Basic Accept (BA_ACC) or Basic Reject (BA_RJT). Other Basic Link Services are discarded. The header field of the basic link service is defined in Figure 1.17. Figure 1.17 Header field of the basic link service (1) R_CTL.. (Routing Control) The high order four bits (8h) represent Basic Link Service, and the low order four bits each Basic Link Service. (2) D_ID..
1.6 Basic Link Service (6) SEQ_ID.. (Sequence Identifier) The drive does not check this item. For a response to ABTS, respond with the same SEQ_ID as received. (7) DF_CTL.. (Data Field Control) Set 00h because no optional header is used. (8) SEQ_CNT.. (Sequence Count) Set 0000h to indicate the first frame of a sequence. (9) OX_ID.. (Originator Exchange Identifier) − Assigned for the initiator to begin the exchange of ABTS. − For a response to ABTS, respond with the same OX_ID as received. (10) RX_ID..
Fibre Channel Interface 1.6.2 Basic accept (BA_ACC) xx Figure 1.19 Basic accept (BA_ACC) The drive responds with BA_ACC to the initiator when the received ABTS frame is correct. The payload field of the BA_ACC frame is described below. For the header fields, refer to Section 1.6, “Basic Link Service.” Word xx/ and byte y of the payload are represented by [PL:Wxx/By]. (1) SEQ_ID Valid.. [PL:W00/B0] 00h: Indicates that last SEQ_ID of word 0/byte 1 is invalid.
1.6 Basic Link Service (5) Lowest SEQ_CNT.. [PL:W02/B0-1] 0000h (6) Highest SEQ_CNT.. [PL:W02/B2-3] FFFFh 1.6.3 Basic reject (BA_RJT) xx Figure 1.20 Basic reject (BA_RJT) The drive responds with BA_RJT to the initiator when RX_ID of the received ABTS frame is not FFFFh. The payload field of the BA_RJT frame is described below. For the header field, refer to Section 1.6, "Basic Link Service." Word xx/ and byte y of the payload are represented by [PL:Wxx/By].
Fibre Channel Interface 1.7 Extended Link Service Table 1.22 Extended link data specification No.
1.7 Extended Link Service (1) R_CTL.. (Routing Control) The high order four bits (2h) represent Extended Link Service, and the low order four bits each Extended Link Service. (2) D_ID.. (Destination Identifier) − Destination address for the frame. (3) S_ID.. (Source Identifier) − Source address for the frame. (4) Type The Extended Link Service uses 01h. (5) F_CTL.. (Frame Control) − Set 290000h for the Extended Link Service Command.
Fibre Channel Interface 1.7.1 N_Port login (PLOGI/PLOGI_ACC) The initiator issues PLOGI to establish the connection with the drive by notifying the drive of the service parameter. The drive responds with PLOGI_ACC when the frame of the received PLOGI is correct. The payload field of the PLOGI frame is described in Figure 1.22, and that of the PLOGI_ACC is in Figure 1.23. For the header field, refer to Section 1.7, “Extended Link Service.” Word xx/ and byte y of the payload are represented by [PL:Wxx/By].
1.7 Extended Link Service 98 1 2 3 4 5 6 7 8 Figure 1.23 Payload field of the PLOGI_ACC frame (1) LS_Command code [PL:W00/B0] 03h: Indicates PLOGI. 02h: Indicates PLOGI_ACC. (2) N_port Common Service Parameters [PL:W01-04] For details, refer to "1.7.1.2 Common Service Parameter." (3) N_Port Name [PL:W05/-06] N_Port Name is used to specify two or more ports which a device has. In PLOGI, the N_Port Name of the initiator is entered and the drive saves the N_Port Name of the initiator.
Fibre Channel Interface (4) Node Name [PL:W07-08] Node Name is used to specify a device. In PLOGI, the N_Port Name of the initiator is entered and the drive saves the N_Port Name of the initiator. In PLOGI_ACC, the Node Name of the drive is entered. For details, refer to "1.7.1.1 Port/Node Name Format.
1.7 Extended Link Service (1) Name Address Authority (NAA) [bit63-60] 0x5: Denotes the format of IEEE Registered. (2) Company_ID [bit59-36] 0x00000E: Value registered in IEEE, denoting the company which has supplied the device. (3) Product ID [bit35-32] The value is used either 0x0. (4) Factory ID [bit31-28] The value is used either h 0x0 or 0x1. (5) Vendor Specified Identifier [bit27-4] Unique value assigned to each device.
Fibre Channel Interface 1.7.1.2 Common service parameter Table 1.24 Common service parameter Continuos Increase 5 (1) Highest version supported [Byte0] Latest version number of FC-PH supported by the device. 09h: Denotes FC-PH version 4.3. − For ACC, the drive responds with 20h. (2) Lowest version supported [Byte1] Lowest version number of FC-PH supported by the device. 09h: Denotes FC-PH version 4.3. − For ACC, the drive responds with 20h.
1.7 Extended Link Service b) 0b: Random Relative Offset [bit6] c) − The drive does not check this bit and does not support this function. − For ACC, the drive responds with 0b. 0b: Valid Vendor Version [bit5] − The drive does not check this bit and does not support this function. − For ACC, the drive responds with 0b. d) 0b: N_Port/F_Port [bit4] e) f) − The drive responds with LS_RJT (03h, 0Fh) when (this bit) = 1b. − For ACC, the drive responds with 0b.
Fibre Channel Interface (6) Total Concurrent Sequence [Byte9] − The drive does not check this field. − For ACC, the drive responds with FFh. (7) Relative Offset by category [Byte10-11] − The drive does not check this field. − For ACC, the drive responds with 0002h. (This indicates that Information Category is Solicited data when bit 1 = 1b.) (8) Point-to-point E_D_TOV value [Byte12-15] This field is significant for point-to-point connection and invalid for loop connection.
1.7 Extended Link Service (1) Service Options [Byte0] a) Class Valid [Byte0/bit7] − The drive responds with LS_RJT(03h, 01h) when (this bit) = 0. − For ACC, the drive responds with 1. b) Intermix Mode [Byte0/bit6] − c) This field is invalid for Class 3 and the drive ignores it. Stacked Connect Request [Byte0/bit5-4] − This field is invalid for Class 3 and the drive ignores it.
Fibre Channel Interface b) X_ID interlock [Byte4/bit5] − c) This field is invalid for Class 3 and the drive ignores it. 00: Error Policy [Byte4/bit4-3] − The drive supports Discard Policy only and responds with LS_RJT(03h, 05h) when (this bit) ≠‚00b. − Drive responds with 00b in this field. d) 00: Categories per Sequence [Byte4/bit1-0] − The drive does not check this field but supports only one category per sequence. − Drive responds with 00b in this field.
1.7 Extended Link Service 1.7.2 Port logout (LOGO/LOGO_ACC) Figure 1.24 Port logout (LOGO/LOGO_ACC) The initiator issues LOGO to establish the connection with the drive by notifying the drive of the service parameter. The drive responds with LOGO_ACC when the frame of the received LOGO is correct. The drive responds with LOGO when notifying the initiator that login has not been completed. The payload field of the LOGO/LOGO_ACC frame is described below.
Fibre Channel Interface 1.7.3 Process login (PRLI/PRLI_ACC) Figure 1.25 Process login (PRLI/PRLI_ACC) The initiator issues PRLI to the drive to establish an operating environment. The drive responds with PRLI_ACC when the frame of the received PRLI is correct. The payload field of the PRLI/PRLI_ACC frame is described below. For the header field, refer to Section 1.7, “Extended Link Service.” Word xx and byte y of the payload are represented by [PL:Wxx/By].
1.7 Extended Link Service 1.7.3.1 Service parameter pages Figure 1.26 Service parameter pages These pages are used by PRLI. (1) Type Code [PL:Byte4] 08h: Denotes SCSI FCP process. − The drive responds with LS_RJT(03h, 00h) when this field is not 08h. (2) Type Code Extension [PL:Byte5] 00h: Not used by SCSI FCP. − The drive responds with LS_RJT(03h, 00h) when this field is not 00h. (3) Originator Process Associator Validity [PL:Byte6/bit7] 0b: The drive neither supports nor checks this bit.
Fibre Channel Interface (5) Establish Image Pair [PL:Byte6/bit5] 1b: The drive establish connection with the initiator. 0b: The drive responds with ACC but does not establish connection with the initiator. (6) Originator Process Associator [PL:Byte8-11] 00000000h: The drive neither supports nor checks this field. (7) Responder Process Associator [PL:Byte12-15] 00000000h: The drive neither supports nor checks this field.
1.7 Extended Link Service 1.7.3.2 Service parameter response pages Figure 1.27 Service parameter response pages These pages are used by PRLI_ACC. (1) Type Code [Byte4] 08h: Denotes SCSI FCP process. − The drive responds with 08h by ACC. (2) Type Code Extension [Byte5] 00h: Not used by SCSI FCP. − The drive responds with 00h by ACC. (3) Originator Process Associator Validity [Byte6/bit7] 0b: The drive neither supports nor checks this bit.
Fibre Channel Interface (5) Establish Image Pair [Byte6/bit5] 1b: The drive establish connection with the initiator. 0b: The drive responds with ACC but does not establish connection with the initiator. − The drive responds with the value specified by PRLI. (6) Response Code [Byte6/bit3-0] 1h: Request executed. − The drive responds with 1h by ACC when PRLI is executed. (7) Originator Process Associator [Byte8-11] 00000000h: The drive does not support this field and responds with 0000h by ACC.
1.7 Extended Link Service 1.7.4 Process logout (PRLO/PRLO_ACC) Figure 1.28 Process logout (PRLO/PRLO_ACC) The initiator issues PRL0 to the drive to cancel the established login. The drive responds with PRLO_ACC when the frame of the received PRLO is correct. The payload field of the PRLO/PRLO_ACC frame is described below.
Fibre Channel Interface Figure 1.29 Payload field of the process logout (PRLO/PRLO_ACC) Word xx and byte y of the payload are represented by [PL:Wxx/By]. (1) LS_Command code [Byte0] 21h: Indicates PRLO. 02h: Indicates PRLO_ACC. (2) Page Length [Byte1] 10h: Logout Parameter page length (in bytes) of PRLO or Logout Parameter Response page length (in bytes) of PRLO_ACC. − The drive responds with LS_RJT(03h, 00h) when (this field) ≠‚10h. − For ACC, the drive responds with 10h.
1.7 Extended Link Service 1.7.4.1 Logout parameter pages Figure 1.30 Logout parameter pages These pages are used by PRLO. (1) Type Code [Byte4] 00h: The drive neither supports nor checks this field. (2) Type Code Extension [Byte5] 00h: The drive neither supports nor checks this field. (3) Originator Process Associator Validity [Byte6/bit7] 0b: The drive neither supports nor checks this bit. (4) Responder Process Asscociator Validity [Byte6/bit6] 0b: The drive neither supports nor checks this bit.
Fibre Channel Interface 1.7.4.2 Logout parameter response pages Figure 1.31 Logout parameter response pages These pages are used by PRLO_ACC. (1) Originator Process Associator Validity [Byte6/bit 7] 0b: The drive does not support this bit and responds with 0b by ACC. (2) Responder Process Asscociator Validity [Byte6/bit6] 0b: The drive does not support this bit and responds with 0b by ACC. (3) Type Code [Byte6/bit3-0] 1h: Request executed. − The drive responds with 1h by ACC when PRLO is executed.
1.7 Extended Link Service 1.7.5 Port discovery (PDISC/PDISC_ACC) The initiator issues PDISC to the drive to check if the drive address has changed immediately after initialization. The drive responds with PDISC_ACC when the frame of the received PDISC is correct. The payload field of the PDISC/PDISC_ACC frame is described below. For the header field, refer to Section 1.7, "Extended Link Service." The PDISC has same information as the PLOGI except LS Command, which is 50000000h.
Fibre Channel Interface Word xx and byte y of the payload are represented by [PL:Wxx/By]. (1) LS_Command code [PL:W00/B0] 52h: Indicates ADISC. 02h: Indicates ADISC_ACC. (2) Hard Address of Originator [PL:W01/B1-3] − For ADISC, the initiator sets the address set by the SEL signal in the low order 8 bits. − For ADISC_ACC, the drive sets the address set by the SEL signal in the low order 8 bits. (3) Port name [PL:W02-03] − For ADISC, Port_name of the initiator is set in Port name of Originator.
1.7 Extended Link Service 1.7.7 Reinstate recovery qualifier (RRQ/RRQ_ACC) Figure 1.33 Reinstate recovery qualifier (RRQ/RRQ_ACC) The initiator issues RRQ to the drive to notify the drive of reuse of Recovery Qualifier (S_ID, D_ID, OX_ID, RX_ID, SEQ_CNT) aborted by ABTS. The drive responds with RRQ_ACC when the frame of the received RRQ is correct. The payload field of the RRQ/RRQ_ACC frame is described below. Word xx and byte y of the payload are represented by [PL:Wxx/By].
Fibre Channel Interface 1.7.8 Read link error status block (RLS/RLS_ACC) Figure 1.34 Read link error status block (RLS/RLS_ACC) The initiator issues RLS to the drive when requesting the drive for Fibre Channel link error information. The drive responds with Link Error Status Block by RLS_ACC when the frame of the received RLS is correct. The payload field of the RLS/RLS_ACC frame is described below. Word xx and byte y of the payload are represented by [PL:Wxx/By].
1.7 Extended Link Service The drive responds with LS_RJT(03h, 1Fh) when this field is any value other than the above. (3) Link Error Status Block [PL:W01-06] This field is used by ACC of the drive. Individual ERRORS are counted in each Port respectively. a) Link Failure Count [PL:W01] The drive counts the number of times when synchronization is not achieved for a minimum of R_T_TOV (100ms) and enters it in this field.
Fibre Channel Interface 1.7.9 Third party process logout (TPRLO/TPRLO_ACC) Figure 1.35 Third party process logout (TPRLO/TPRLO_ACC) The initiator issues TPRLO to the drive to cancel the established login specified by Third Party Originator N_Port ID. The drive responds with TPRLO_ACC when the frame of the received TPRLO is correct. The payload field of the TPRLO/TPRLO_ACC frame is described below. Word xx and byte y of the payload are represented by [PL:Wxx/By].
1.7 Extended Link Service (3) Payload Length [PL:W00/B2-3] 18h: Payload length (24 bytes) of TPRLO or Payload length (24 bytes) of TPRLO_ACC. − The drive responds with LS_RJT(03h, 00h) when (this field) ≠‚ from 14h to 18h. − For ACC, the drive responds with 18h. (4) Logout Parameter pages [PL:W01-05] Forms the payload of TPRLO. For details, refer to "1.7.9.1 Logout Parameter pages." 1.7.9.1 Logout parameter pages Figure 1.36 Logout parameter pages These pages are used by TPRLO/TPRLO_ACC.
Fibre Channel Interface (2) Type Code Extension [PL:W01/B1] 00h: Not used by SCSI FCP. (the drive ignores this field) (3) Third Party Originator Process Association Validity [PL:W01/B2/bit7] 0b: The drive neither supports nor checks this bit. (4) Third Party Originator Process Association Validity [PL:W01/B2/bit6] 0b: The drive neither supports nor checks this bit.
1.7 Extended Link Service 1.7.10 Link service reject (LS_RJT) LS_RJT 0 1 2 Word Header 3 Byte SOF 0 R_CTL D_ID 23 xx 00 xx xx 1 2 3 S_ID xx TYPE xx F_CTL 01 98 SEQ_ID DF_CTL FF 00 00 xx xx FF 00 00 4 00 00 SEQ_CNT OX_ID 5 00 RX_ID FF PARAMETER Payload 0 1 xx 00 00 LS_Command Code 01 00 00 00 Reserved Reason Code Reason Explanation Vendor Unique= 0x00 CRC EOF Figure 1.
Fibre Channel Interface (3) Reason Explanation [PL:W01/B2] The Reason Explanation Code which the drive responds with is entered. 01h: Service Parameter error- Option. − Error was detected in Class 3 Service Parameter for PDISC or PLOGI. 03h: Service Parameter error- Initiator Control − Error was detected in Initiator Control of Class 3 Service Parameter for PLOGI or PDISC.
1.7 Extended Link Service 1.7.11 Fabric login (FLOGI/FLOGI_ACC) The drive issues FLOGI to Fabric to establish the public loop environment. The payload field of FLOGI frame is described in Figure 1.38, and that of FLOGI_ACC is in Figure 1.39. Figure 1.
Fibre Channel Interface Figure 1.39 Fabric login (FLOGI_ACC) Word xx/ and byte y of the payload are represented by [PL:Wxx/By]. (1) LS_Command code [PL:W00/B0] 04h: Indicates FLOGI. 02h: Indicates FLOGI_ACC. − The drive responds with LS_RJT(0Bh, 00h) when this field is an unsupported Link Service code. (2) Common Service Parameter [PL:W01-04] For details, refer to "1.7.1.2 Common Service Parameter." (3) N_Port Name [PL:W05-06] N_Port Name is used to specify two or more ports which a device has.
1.7 Extended Link Service (4) Node Name [PL:W07-08] Node Name is used to specify a device. In FLOGI, the N_Port Name of the drive is entered. In FLOGI_ACC, the Node Name of the initiator is entered. For details, refer to "1.7.1.1 Port/Node Name Format." (5) Class 1 Service Parameter [PL:W09-12] This drive does not Check Class 1 Service Parameter. (6) Class 2 Service Parameter [PL:W13-16] This drive does not check Class 2 Service Parameter. (7) Class 3 Service Parameter [PL:W17-20] For details, refer to "1.
Fibre Channel Interface RNC /RNC_ACC Payload Bit Byte 7 6 5 4 3 0 LS_Command 1 Reserved 2 2 1 0 Payload Length 3 RNC Flag 4 Reserved 5 Reserved 6 Reserved 7 VU Information Length 8 (MSB) : Vendor Identifier 15 (LSB) 16 : Capability Entry 255 Figure 1.40 RNC/RNC_ACC (2/2) (1) LS_Command Code [PL:W00/B0] 53h: Indicates RNC 02h: Indicates RNC_ACC (2) Payload Length [PL:W00/B2-3] If RNC Flag is "1", drive responds that payload length is 10h in RNC_ACC.
1.7 Extended Link Service (6) Capability Entry [PL:W04-W127] Drive does not check this field. If RNC Flag given from Initiator is "1", drive responds RNC_ACC as follows. − Payload Length = 10h − RNC Flag = 1 − VU Information Length = 0 − Vendor Identifier = 'FUJITSU' in ASCII If RNC Flag given from Initiator is "0", drive responds RNC_ACC as follows.
Fibre Channel Interface 1.7.13 FAN Fabric F_Port sends FAN to the drive to confirm Loop Fabric Address, Fabric Port Name and Fabric Name. Payload of FAN frame is described below.
1.8 Extended Link Service (Loop Initialization) 1.8 Extended Link Service (Loop Initialization) Word 0 1 Reserve 3 5 Byte 2 01 4 3 Header 0 22 1 2 Note) xxxxxx = ‘000000’···FL_Port or ‘0000EF’···NL_Port Figure 1.42 Extended link service (loop initialization) Listed below are the frames used by Loop Initialization in the Extended Link Service supported by this drive. 1.
Fibre Channel Interface (4) Type 01h is used for Extended Link Service. − F_CTL.. (Frame Control) − 380000h is set for Initialization frame of Extended Link Service. (5) SEQ_ID.. (Sequence Identifier) − The drive does not check this item. − The drive responds with 00h. (6) DF_CNTL.. (Data Field Control) Set 00h because no Optional Header is used. (7) SEQ_CNT.. (Sequence Count) − The drive does not check this item. − The drive responds with 0000h. (8) OX_ID..
1.8 Extended Link Service (Loop Initialization) 1.8.1 Loop initialization select master (LISM) 0 1 Word Header 0 2 3 Byte 22 Note) xx xx xx 00 Note) xx xx xx 01 38 00 00 00 00 00 00 FF FF FF FF 00 00 00 00 11 01 00 00 1 2 3 4 5 Payload 0 1 2 Port name (8 Byte) 3 4 Figure 1.43 Loop initialization select master (LISM) Frame sent to determine Loop Master in initialization. The payload field of the LISM frame is described below.
Fibre Channel Interface 1.8.
1.8 Extended Link Service (Loop Initialization) 1.8.
Fibre Channel Interface 1.9 FC-4 Device Data FC-4 Device Data indicates supported by this drive. 1.9.1 FCP CMND The initiator issues FCP_CMND frame when it issues SCSI_Command. The header field of the FCP CMND is defined in Figure 1.46.
1.9 FC-4 Device Data (4) Type The FCP_CMND frame uses 08h. (5) F_CTL.. (Frame Control) − Set 290000h for the FCP_CMD (Originator of Exchange, First Sequence of Exchange, Last Data frame of Sequence, Transfer Sequence Initiative.) (6) SEQ_ID.. (Sequence Identifier) − Set the optional value (7) DF_CTL.. (Data Field Control) Set 00h because no optional header is used. (8) SEQ_CNT.. (Sequence Count) − Set 0000h because it is used single frame sequence. (9) OX_ID..
Fibre Channel Interface (3) CDB [PL:W03-06] SCSI CDB is entered in the field. − The field is 16 byte length any time and the drive does not check an unused area of this field occurred by SCSI Command Type. − If Task Management Flag set, this field is invalid. For details of CBD, refer to 1.9.1.2 Command Descriptor Block. (4) Additinonal_FCP_CDB [PL:W07_n] The drive ignores this field.
1.9 FC-4 Device Data (1) Task Attribute [PL:W02/B1/bit2-0] The initiator specifies the Command Queue type. 0h: Simple Queue 1h: Head of Queue 2h: Ordered Queue 4h: ACA Queue 5h: Untagged − The drive handles ACA Queue as same as Simple Queue. (2) Task Management flag [PL:W02/B2] The initiator uses to control the task. a) Obsolete [B2/bit7] 0b: This drive does not support the bit. If this bit set, the drive respond FCP_RSP with "Task Management Function Not Support" of FCP_CODE.
Fibre Channel Interface e) f) Clear Task Set [B2/bit2] − This drive clears all commands queued when this drive receives the Target Reset. − The drive generates the UNIT ATTENTION condition internally for all of initiators except Clear Task Set issue initiator. If the drive receives the command after Clear Task Set, the drive will respond check condition (SenseKey=UNIT ATTENTION). − The drive aborts all of "Open Exchange".
1.9 FC-4 Device Data 1.9.1.
Fibre Channel Interface 101b, Group-5, 12 byte commands 110b, Group-6, Vendor specific 111b, Group-7, Vendor specific (2) Logical Block Address It can be specified the logical block address, 21 bit on 6 byte CDB and 32 bit on 10 byte CDB. The maximum logical block address of drive is described on the Read Capacity Command. (3) Transfer Length It can be specified by 255 block using 1 byte (in this field) in 6 byte CDB. It can be specified by 64K-1 block using 2 byte (in this field) in 10 byte CDB.
1.9 FC-4 Device Data 1.9.2 FCP XFER RDY In case of transferring the drive, the drive issues FCP XFER RDY frame to the initiator. The header field of the FCP XFER RDY is defined in Figure 1.49. Word Header 0 xx xx xx 00 xx xx xx 08 89 00 00 FF 00 00 00 xx xx FF FF 05 1 2 3 4 5 00 Payload 0 00 00 FCP T.16 Data_Relative offset 1 BURST_LEN 2 Reserve 3 00 Figure 1.49 Header field of the FCP XFER RDY (1) R_CTL..
Fibre Channel Interface (6) SEQ_ID.. (Sequence Identifier) − The drive responds FFh. (7) DF_CTL.. (Data Field Control) Set 00h because no optional header is used. (8) SEQ_CNT.. (Sequence Count) − It is responded 0000h because it is used single frame sequence. (9) OX_ID.. (Originator Exchange Identifier) − The drive responds the OX_ID of FCP CMND received from the initiator. (10) RX_ID.. (Responder Identifier) Set FFFFh to indicate that RX_ID is unused.
1.9 FC-4 Device Data 1.9.3 FCP DATA The header field of the FCP DATA is defined in Figure 1.50. Header 0 01 xx xx xx xx xx xx xx xx xx 1 00 2 00 3 xx 4 xx xx 00 xx xx FF FF 5 Relative offset Payload 0 1 2 ~ ~ ~ ~ Figure 1.50 Header field of the FCP DATA This frame is used for transferring between the initiator and the drive. The header field of the FCP DATA is defined below. (1) R_CTL..
Fibre Channel Interface (5) F_CTL.. (Frame Control) Table 1.26 F_CTL Section F_CTL value Write data frame (from initiator to drive) a) not last frame of sequence a1) with Relative Offset a2) without Relative Offset b) last frame of sequence x indicates 4 bit as below. bit 3 when x is 1: with Relative Offset when x is 0: without Relative Offset bit 2 0, Reserved bit 1-0 Fill Data Byte 0, 0.....0 byte of fill (4 byte valid) 0, 1.....1 byte of fill (3 byte valid) 1, 0.....
1.9 FC-4 Device Data (6) SEQ_ID.. (Sequence Identifier) − In case of transferred Data Frame from the initiator to the drive, the drive has the memory of the first frame SEQ_ID of the sequence and checks the frame SEQ_ID belonging to the sequence. − In case of the drive sends to the initiator the data frame, the drive institutes 00h to SEQ_ID in the first sequence. In case of issuing the sequence on and after twice in the command (exchange), SEQ_ID is used the added value one. (7) DF_CTL..
Fibre Channel Interface 1.9.4 FCP RSP The header field of the FCP RSP is defined in Figure 1.51. Header 0 xx xx xx 00 xx xx xx 08 98 00 00 FF 00 00 00 xx xx FF FF 00 00 00 00 07 1 2 3 4 5 Payload 0 Reserve 1 Reserve 2 FCP_Status 3 Residual Count 4 FCP_SNS_INFO length (n) 5 FCP_RSP_INFO length (m) ~ ~ FCP_Response Info. (m Byte) ~ ~ ~ ~ FCP_Sense Info. (n Byte) ~ ~ Figure 1.
1.9 FC-4 Device Data (4) Type SCSI FCP frame uses 08h. (5) F_CTL.. (Frame Control) − Set 980000h for the FCP_RSP (Responder of Exchange, last sequence of exchange, last data frame of sequence.) (6) SEQ_ID.. (Sequence Identifier) − The drive responds by FFh. (7) DF_CTL.. (Data Field Control) Set 00h because no optional header is used. (8) SEQ_CNT.. (Sequence Count) − It is responded 0000h because it is used single frame sequence. (9) OX_ID..
Fibre Channel Interface (4) FCP SNS LEN VALID [PL:W02/B2/bit1] When this bit is 1, the field of Length of Sense Information (FCP_SNS_INFO) is valid and FCP_RSP frame includes the FCP Sense Information field. (5) FCP RSP LEN VALID [PL:W02/B2/bit0] When this bit is 1, the field of Length of Response Information (FCP_RSP_INFO) is valid and FCP_RSP frame includes the FCP Sense Information field. (6) SCSI Status [PL:W02/B2/bit0] Refer to Section 2.2 Status Byte. 1.9.4.
1.9 FC-4 Device Data (4) FCP RSP LEN VALID [PL:W02/B2/bit0] When this bit is 1, the field of Length of Response Information (FCP_RSP_INFO) is valid and FCP_RSP frame includes the FCP Sense Information field. (5) SCSI Status [PL:W02/B2/bit0] Refer to Section 2.2 Status Byte. 1.9.4.2 FCP response information bit 7 6 5 4 3 2 1 0 WD Byte 6 0 Reserved 00h 1 Reserved 00h 2 Reserved 00h 3 7 Response Code (FCP RSP CODE) 0 Reserved 00h 1 Reserved 00h 2 Reserved 00h 3 Reserved 00h Figure 1.
Fibre Channel Interface 1.9.4.
1.10 Errors on Loop (Refer to FC-PH , Section 29.9) 1.10 Errors on Loop (Refer to FC-PH , Section 29.9) This section describes errors which may occur on the loop and actions to be taken for them. Table 1.27, Detail errors and action lists types of errors and actions for them by number. For details of the actions to be taken for errors, refer to Table 1.28, Actions by recipient. Table 1.
Fibre Channel Interface Table 1.27 Detail errors and action (2/2) Error Category 6) Frame_control Errors 7) Data Frame Errors Specific Error Seq Recp Action n) Protocol Error 2 o) Incorrect length 2 p) Unexpected Link_Continue 2 q) Unexpected Link_Response 2 r) Login Required 2 s) Excessive Sequences attempted 2 t) Unable to Establish Exchange 2 u) RO out of bounds 2 c) Buffer not available – Class 3 1 e) missing frame error detected 13 Note: The contents of Seq. Recp.
1.11 Enclosure Service Interface (ESI) 1.11 Enclosure Service Interface (ESI) Enclosure Service Interface provides the protocol defining the information between the enclosure and the drive. The drive starts to execute Enclosure Service when the drive receives “Send Diagnostic” command or “Receive Diagnostic Result” command with Enclosure Service page specified. a) SFF8045 Two modes in SFF8045 exist, which are Without Parallel ESI and With Parallel ESI.
Fibre Channel Interface Receive SCSI command from the initiator –Parallel ESI max 1µs Enclosure DLY max 1µs ESI Phase SEL_ID DISCOV. COMMAND READ/WRITE SEL_ID Figure 1.55 Enclosure service data transfer protocol Detail of DISCOV. (discovery) phase is shown in Figure 1.56. This process is executed every time when -Parallel ESI signal is asserted. The target of DISCOV. phase is that the drive acknowledges the enclosure can operate as SFF8067 mode.
1.11 Enclosure Service Interface (ESI) 1.11.
Fibre Channel Interface 1.11.3 COMMAND phase In COMMAND phase protocol, the drive transmits the command receiving from the initiator to the enclosure. Because the data bits are 4 bits width, the drive has to transmit the data even times. (1) COMMAND phase The drive communicates with the enclosure as shown in Figure 1.57. (c) (a) –DSK_WR min 100 nsec D (0:3) –ENCL_ACK (b) (d) Figure 1.
1.11 Enclosure Service Interface (ESI) COMMAND bytes length is always four bytes. • Page code in byte 0 is defined as SES page for communicating with the enclosure. • Bit 0 in byte 1 defines the direction of the data transfer. 0 …… from the drive to the enclosure 1 …… from the enclosure to the drive • Parameter Length in byte 2 and byte 3 defines data length. The value “0000h” is used when receiving the data (Receive Diagnostic Result command).
Fibre Channel Interface (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.
1.11 Enclosure Service Interface (ESI) START_1/START_2 1 sec max device delay 100 nsec min enclosure delay –PARALLEL ESI 1 usec max enclosure delay –DSK_WR SEL_6 –DSK_RD SEL_5 D(0:3) SEL_(0:3) –ENCL_ACK SEL_4 –SEL_ID (0:3) 1 second max enclosure delay *1 *2 *3 *4 *5 *1 Enclosure Services Processor changes START_1 and START_2 to indicate that it is requesting communication with the SCSI device.
Fibre Channel Interface START_1/START_2 1 sec max device delay –PARALLEL ESI 1 usec max enclosure delay 5 ms –DSK_WR SEL_6 –DSK_RD SEL_5 D(0:3) SEL_(0:3) –ENCL_ACK SEL_4 max drive delay –SEL_ID (0:3) 1 second max enclosure delay *1 *2 *3 *4 *5 *1 Enclosure Services Processor negates START_1 and START_2 to indicate that it is requesting communication with the SCSI device. *2 SCSI device asserts –PARALLEL ESI to indicate it is ready to begin communication with the Enclosure Services Processor.
1.11 Enclosure Service Interface (ESI) –Parallel_ESI ESI INTF SEL_ID Discovery Command Read Command Write SEL_ID Figure 1.62 EIE operation phases If any errors or timeouts are detected during the EIE operation, the SCSI device aborts the operation and continues normal operation. Errors are not reported. 1.11.6.
Fibre Channel Interface Table 1.32 Action code Action Code Description 00h Device Standard Inquiry Data 01h Device Addresses 02h Loop Position Map 03h Initiate Loop Initialization 04h Device Identification 05h Device Temperature 06h Port Parameters 07h Link Status 08h Spin-Down Control 09 to 0Fh Reserved * Not supported If the ESI request contains a valid Action Code and non-zero Parameter Length, the drive responds with a write operation with the requested information. Table 1.
1.11 Enclosure Service Interface (ESI) Table 1.34 Device standard inquiry data Bit 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (00h) 2 3 (MSB) 4 : 39 (MSB) Byte • 3 2 1 0 Page Length (24h) (LSB) Inquiry Data (LSB) Inquiry Data - The first 36 bytes of Standard Inquiry data. Reference SCSI Primary Commands - 2 (SPC-2) for a definition of this data. Note: the vendor specific, VS, bit in byte 6 is not valid.
Fibre Channel Interface Table 1.
1.11 Enclosure Service Interface (ESI) Table 1.36 Loop position map page Bit 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (02h) 2 3 (MSB) Byte 3 2 1 0 Page Length (m-3) (LSB) 4 Offset Port A (n-4) 5 : n (MSB) Loop Map Port A (LSB) n+1 Offset Port B (m–n+1) n+2 : m (MSB) Loop Map Port B (LSB) • Offset: The offset field frorn the FC-AL LILP frame. The offset field indicates the number of bytes in the Loop Map.
Fibre Channel Interface Table 1.38 Device identification page Bit 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (04h) 2 3 (MSB) 4 : n (MSB) Byte • 3 2 1 0 Page Length (n–3) (LSB) Device ID Data (LSB) Device ID Data: The device ID data is the contents of the SCSI Vital Product Data Device Identification page (83h). For a definition of this information, see the SPC-2 (SCSI Primary Commands-2) standard. Table 1.
1.11 Enclosure Service Interface (ESI) Table 1.
Fibre Channel Interface Table 1.
1.11 Enclosure Service Interface (ESI) Table 1.
Fibre Channel Interface The following fields are extracted from the FC-PH defined Link Error Status Block, LESB: • Link Failure Count - Count of the number of Loss of Sync conditions that have occurred on the port which exceeded 100 mS in duration. • Loss of Sync Count - Count of the number of short (< 100 mS) Loss of Synchronization conditions that have occurred on the port. • Loss of Signal Count - Count of the number of Loss of Signal conditions on the port.
1.12 Public Loop 1.12 Public Loop Public loop consists of the private loop through the multiple FL_Port or N_Port device through the multiple F_Port. (Shown as Figure 1.63) The FL_Port is the gateway to the Fabric for the Public NL_Ports on its Local Loop, allowing NL_Ports to act as if they were N_Ports and interact with other N_Ports and NL_Ports attached to the fabric. It can be communicated with all devices connected with F_Port/FL_Port. (ex. NFS Client can be communicated with SCSI Device #6 etc.
Fibre Channel Interface Example for Establishment Fabric side Drive side Completion of Loop Initialization FLOGI FLOGI ACC PLOGI PLOGI ACC RFC-4 RFC-4 ACC PLOGI PLOGI ACC PRLI PRLI ACC Figure 1.64 General public loop initialization sequence At this point, Public Loop establishes between Fabric and Drive. 1.13 Dual Loop This drive has a Dual Port configuration with two ports (A, B). Viewed from the Fibre Channel Interface, these two ports appear to exist as two independent devices.
1.13 Dual Loop Table 1.
This page is intentionally left blank.
CHAPTER 2 Command Processing 2.1 Command Format 2.2 Status Byte 2.3 Outline of Command Processing 2.4 Command Queuing Function 2.5 UNIT ATTENTION Condition 2.6 Sense Data Hold State 2.7 Command Processing Exceptions 2.8 Data Block Addressing In this chapter, the basic theory and specifications concerning IDD command processing functions are described. The IDD operates as the target (TARG) in the FC LOOP.
Command Processing Table 2.1 6-Byte CDB basic format Bit Byte 7 6 5 0 4 3 2 1 0 Operation Code 1 Reserved Logical Block Address (MSB) 2 Logical Block Address 3 Logical Block Address (LSB) 4 Transfer Data Length 5 Control Byte Table 2.
2.1 Command Format Table 2.3 12-Byte CDB basic format Bit Byte 7 6 5 4 0 3 2 1 0 0 0 0 0 0 Operation Code 1 Reserved 0 0 2 Logical Block Address (MSB) 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address (LSB) 6 Transfer Data Length (MSB) 7 Transfer Data Length (LSB) 8 Transfer Data Length (MSB) 9 Transfer Data Length (LSB) 10 0 0 0 11 0 0 0 Control Byte The meanings of each of the fields in the CDB are explained below.
Command Processing Group 2 (“010”): 10-byte CDB (Shown in Figure 2.2) Group 3 (“011”): Reserved Operation Code (Shown in Section (6)) Group 4 (“100”): 16-byte CDB Group 5 (“101”): 12-byte CDB (Shown in Section 2.3) b. Command code The command code specifies the type of command in each group. (2) LUN (Logical Unit Number) This IDD operates only by “0”, defined in the FCP_CMND frame. Concerning INQUIRY, this limitation does not apply.
2.1 Command Format b. Transfer byte length or parameter list length When the transfer data length is specified as the “Transfer Byte Length” or “Parameter List Length”, this field specifies the length of the data transferred between the INIT and IDD by that command in number of bytes. When zero is specified in this field, data transfer is not executed, except in cases where it is particularly stipulated in the specifications for individual commands in Chapter 4.
Command Processing e. Bit 0 (Link) This IDD does not support Link, so this bit should be set on “0”. (6) Handling an illegal CDB If there are errors in the contents of a CDB description (specification), or if there is an error in the specification of a parameter transferred from the INIT in accordance with a CDB specification, that command ends with the CHECK CONDITION status.
2.2 Status Byte (1) GOOD status This status indicates that execution of the command ended normally. (2) CHECK CONDITION status This status is reported in the case of a)~c) below. The IDD generates sense data when this status is reported and displays the detailed cause. The IDD transfers the generated sense data together with this status report in the same FCP_RSP frame. Therefore, it is unnecessary to gather sense data using the REQUEST SENSE command.
Command Processing 2.3 Outline of Command Processing 2.3.1 Single commands A diagram of processing of single commands, which are the most basic operations in the FC LOOP, is shown below. a. Read processing IDD (Driver side) [ALPA: y] INIT (Initiator side) [ALPA: x] A primitive.
2.3 Outline of Command Processing b. Write processing INIT (Initiator side) [ALPA: x] IDD (Driver side) [ALPA: y] ARB (x, x) A primitive.
Command Processing (1) Signal Interchanges on the FC Loop a. Acquisition of loop use rights The IDD performs arbitration with the other devices on the loop in order to use the loop. Arbitration is accomplished by setting its own ALPA in the ARB primitive and outputting it in the form ARB (ALPA, ALPA). Other devices connected to the loop output the ARB primitive they have received as the CFW (Current Fill Word) as long as they have no requests.
2.3 Outline of Command Processing c. Frame transfer The transfer source device, by receiving the R_RDY primitive, can judge that it is possible for the transfer destination device to receive frames, so, it can send frames. Since one frame can be output for one R_RDY primitive, when wanting to send 2 or more frames, after 1 frame is sent, the transfer source device must wait until another R_RDY primitive is sent from the transfer destination device.
Command Processing d. Disconnecting from the transfer destination device When the transfer source device completes transfer of the frames it is sending, it sends the CLS primitive, disconnecting from the transfer destination device and releasing its loop use rights. When the transfer destination device receives the CLS primitive, it resends it, returning the CLS primitive to the transfer source device.
2.3 Outline of Command Processing If connections are not established, operation is as follows. PLOGI is not implemented: The IDD responds with the LOGO (Extended Link Service) frame. If PLOGI is already implemented, PRLI is not implemented: The IDD responds with the PRLO (Extended Link Service) frame. PRLI is implemented without implementing PLOGI: This combination should not exist. Furthermore, this IDD supports connections with a maximum of 32 INITs (without relation to the port).
Command Processing An example of confirmation of connections that is performed by the INIT is shown below.
2.3 Outline of Command Processing (4) Write related command operations During write related command operations, before receiving of data, the INIT is notified in the FCP_XFER_RDY frame of the volume of data which the device can receive and the pointer for those data. The volume of data which can be received is called the Burst length, and the data pointer is called the Relative Offset.
Command Processing 2.4 Command Queuing Function The IDD is equipped with the command queuing function. Through command queuing, the IDD can receive multiple commands in advance and can execute them. For the queuing function, there are two methods, tagged and untagged. In tagged queuing, it is possible to receive multiple commands from each INIT. 2.4.1 Untagged queuing Using untagged queuing, the IDD can receive a command from an INIT while it is executing processing of a command from another INIT.
2.4 Command Queuing Function Note: Through the operation of the command queuing function, except for exceptions described on this page, the IDD does not respond to commands issued by the INIT with a BUSY status. This function is applied under the multi-initiator environment, and overhead for re-issuing commands caused by the BUSY status is unnecessary.
Command Processing In the case of an ORDERED QUEUE, the IDD executes commands in the order in which they are received. All the commands received with a SIMPLE QUEUE before commands received with an ORDERED QUEUE are executed before the commands received with an ORDERED QUEUE, without relation to the INIT. Commands received with a HEAD OF QUEUE are registered at the top of the queue for waiting execution.
2.5 UNIT ATTENTION Condition • Conditions for Reordering: If commands which are objects of reordering are issued by an INIT which permits reordering together with a SIMPLE QUEUE. • Commands which are Objects of Reordering: READ, READ EXTENDED, WRITE, WRITE EXTENDED If the INIT permits command reordering processing, the IDD changes the command processing order. It is necessary for the INIT to control concerning the validity of data. For details of the control mode page, see 4.1.
Command Processing (3) Commands cleared by another INIT If the following events have occurred, the command which is currently being executed and commands in the queue are cleared, and this Unit Attention condition is generated. • The CLEAR TASK SET is issued by any INIT. However, the Unit Attention condition hold state is not entered in the INIT that issued the CLEAR TASK SET, the INIT that issued the MODE SELECT or MODE SELECT EXTENDED command or the INIT that canceled the sense hold state. 2.5.
2.6 Sense Data Hold State (4) REPORT LUN command The REPORT LUN command is executed normally, but the Unit Attention condition is not cleared. 2.5.
Command Processing 1) If, during execution of a command received from an INIT, the IDD terminates execution of the command. If the command is still in the queue and has not yet been executed, the IDD clears that command. 2) The IDD reports the CHECK CONDITION status with for the command that caused the overlap. The sense data generated by the IDD at this time shows ABORTED COMMAND [= B]/Overlapped commands attempted [= 4E-00].
2.7 Command Processing Exceptions 2.7.4 Command processing in the not ready state If the initial self-diagnosis after the power is turned on is completed normally and the spindle motor reaches its rated speed, the IDD reads out the "System Information", such as information on MODE SELECT parameters or disk medium defects from the system space on the disk drive and initializes each type of control information. When this operation is completed, the IDD enters the Ready state.
Command Processing (2) Commands that can be executed even in the not ready state The IDD can execute any of the following commands when they are received, even when in the Not Ready state. • START/STOP UNIT command • RESERVE command • RELEASE command • WRITE BUFFER command • READ BUFFER command • INQUIRY command • REQUEST SENSE command: When the REQUEST SENSE command is executed normally and the IDD is in the sense data hold state, the sense data held at that time are transferred to the INIT.
2.7 Command Processing Exceptions 2.7.5 Error recovery processing When an error which it is possible to retry is detected in the IDD, the IDD attempts error recovery processing of the detected error during command execution. The INIT can specify whether or not to report detailed parameters and successfully recovered errors related to error recovery processing using either the MODE SELECT or the MODE SELECT EXTENDED command.
Command Processing The start of execution timing for this automatic readjustment operation is ordinarily impossible for the INIT to predict. The automatic readjustment operation is performed when there is no command being executed or waiting in the queue, but execution of commands issued immediately after the IDD starts a readjustment operation is caused to wait until the readjustment operation is completed. 2.7.
2.7 Command Processing Exceptions 3. LIP (F8, F7), LIP (F8, ALPS): LIP that is output when the device recognizes that the loop has been disconnected for some reason. LIP can implement loop initialization of all FC devices connected on the same FC LOOP and can return the state of the loop to the normal state. LIP (YX) initializes the only specific FC device (TARG) selected by the INIT to the same state as when the power is turned on.
Command Processing (4) ABORT TASK SET This processing is the same as the processing of SCSI equivalent messages, as can be understood from Table 2.10. However, this processing is transferred to the IDD by the FCP_CMND frame, and after processing is completed, notification is made of completion by the FCP_RSP frame. The operation sequence is the same as that in Figure 2.6. For an INIT which wants to clear only specific commands that it has issued, ABORT TASK SET or ABTS must be used.
2.7 Command Processing Exceptions Table 2.11 Reset processing during write Type of command Halting process of command execution WRITE WRITE EXTENDED WRITE AND VERIFY SEND DIAGNOSTIC (Write/Read Test) WRITE LONG WRITE SAME Data blocks which are currently being written are processed normally, including the ECC portion, and execution of the command is terminated at the point when that processing is completed.
Command Processing 2.7.7 Fatal hardware errors (1) Self-diagnostic errors If a fatal error was detected in the hardware through an initial self-diagnosis, offline self-diagnosis or on-line self diagnosis (SEND DIAGNOSTIC Command), turning of the spindle motor is stopped. When in this state, the IDD reports the CHECK CONDITION status for all Input/Output operation requests except the REQUEST SENSE command.
2.8 Data Block Addressing Figure 2.7 shows the configuration of data space on the disk drive. The number of cylinders allocated to user space can be specified by the user (by the MODE SELECT or MODE SELECT EXTENDED command). A spare sector area (replacement area) is assured in the user space for replacement of defective sectors.
Command Processing Physical cylinder [System space] Cylinder 0 Track 0 Cylinder 0 Track 1 Cell 0 (Cell) Cylinder 0 Zone 0 Track (m-1) Cell n-1 (Cell) Track 0 [User space] Alternate cell (b tracks) Zone 1 Cylinder (a-1) Zone (x-1) Alternate cylinder (c cylinders) Last cylinder (d-1) (Last cylinder) Figure 2.
2.8 Data Block Addressing 2.8.2 Logical block addressing The IDD uses logical data block addressing which is not dependent on the disk drive’s physical structure as the method of data access on the disk medium. The IDD makes correspondence between each physical sector and each logical data clock address during formatting. Access to the data on the disk medium is performed in logical data block units and the INIT specifies the logical data block address that is its object during access.
Command Processing (2) Alternate area The alternate area in user space (spare sectors within each cell and alternate cells) are excluded from the abovementioned logical data block addresses. Access to allocated sectors as alternate blocks within the alternate area is performed automatically by the IDD’s defect management (sector slip processing and alternate block processing), so it is not particularly necessary for the user to access the alternate area.
CHAPTER 3 Data Buffer Management 3.1 Data Buffer 3.2 Look-Ahead Cache Feature 3.3 Write Cache In this chapter, the configuration of the data buffer with which the IDD is equipped, its operation and the operation of the cache feature are described. 3.1 Data Buffer 3.1.1 Data buffer configuration and basic operation The IDD is equipped with a 6,797 KB data buffer, which makes it possible to efficiently execute data transfer operations between INIT (initiator) and a disk drive.
Data Buffer Management Segment Segment 7 Segment 6 Segment 5 Segment 4 Segment 3 Segment 2 Segment 1 Segment 0 Disk Media Valid Data INIT Write→ Write→ ←Read ←Read Figure 3.1 Data buffer configuration (in the case of 8 cache segments) The basic functions and operations of the data buffer in a read operation and a write operation are shown below. (1) Read operation Data read from the disk media are temporarily stored in the data buffer.
3.1 Data Buffer 5) If the number of blocks specified in the command to be transferred is larger than the capacity of a cache segment and if the data transfer rate of the INIT is lower than the data transfer rate of the disk drive, the empty space in the data buffer disappears from step 3) and the IDD may soon not be able to read data from the disk media (data overrun). In this case, the IDD relocates the block that caused the data overrun after waiting one disk revolution, and continues the reading process.
Data Buffer Management (2) Write operation After data transferred from the INIT are stored temporarily in the data buffer, they are written to the disk media. The basic write operation procedure is as shown below. 1) When the IDD receives a command, it transfers the XFER_RDY flame to INIT. Later it stores data transferred from the INIT to the data buffer (data pre-fetch). At this time, the IDD locates the position of the data block on the disk media specified by the command in parallel.
3.1 Data Buffer 1) If the amount of transfer data specified in a command is smaller than the capacity of the cache segment, all the data necessary for execution of the command are pre-fetched in a batch in the processing in 1) above, so the value specified in the buffer empty ratio has not meaning.
Data Buffer Management Table 3.1 Parameters for controlling reconnection timing [Disconnect/Reconnect Parameter (Page code = 2)] Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 0 1 X‘0E’ (Page Length) 2 Buffer Full Ratio Default Value: X‘00’ Variable Range: X‘00’ to X‘FF’ 3 Buffer Empty Ratio Default Value: X‘00’ Variable Range: X‘00’ to X‘FF’ 4 ~ ~ ~ ~ (Other parameters) ~ ~ 15 a.
3.2 Look-Ahead Cache Feature b. Buffer empty ratio This parameter specifies the timing for the IDD to start Loop OPEN processing when it is requested by the INIT to transfer data in the WRITE, WRITE EXTENDED or WRITE AND VERIFY command. In a write operation, after the IDD receives a command, the IDD begins transferring data (data pre-fetch) while locating the position of the target data blocks on the disk media in parallel.
Data Buffer Management 3.2.1 Caching operation When the IDD is executing a READ command or a READ EXTENDED command, it reads the requested data from the disk media and transfers it to the INIT while at the same time reading (looking ahead at) data blocks which are subsequent to the last logical data block specified in that command to the data buffer.
3.2 Look-Ahead Cache Feature c) Data transferred from the INIT and written to the disk media by the WRITE and WRITE EXTENDED, command are objects of caching. d) Data transferred from the INIT and written to the disk media by WRITE AND VERIFY command is not the objects of caching. (3) Disabling caching data Various data which are objects of caching in the data buffer are disabled in the following cases.
Data Buffer Management c) − RESERVE EXTENDED − WRITE BUFFER − WRITE SAME If the data buffer where data which are objects of caching are stored is used by any of the following commands, the data existing in that data buffer which are objects of caching are disabled. − READ − READ EXTENDED − WRITE − WRITE EXTENDED − WRITE AND VERIFY − VERIFY d) If any of the following events occurs, all the data which are objects of caching are disabled.
3.2 Look-Ahead Cache Feature Table 3.
Data Buffer Management 3.2.3 Look-Ahead operation, Look-Ahead volume 1) Excluding the conditions in 3) and 4) for the amount of data specified as the minimum pre-fetch volume, data are read for look-ahead irrespective of track boundaries or cylinder boundaries. Commands which are already in the queue or commands which are newly received while a look-ahead operation is in progress, are executed after the look-ahead operation is completed.
3.3 Write Cache 3.3 Write Cache The IDD is equipped with a write cache function in order to reduce the INIT's command processing time. If that operation is permitted by the MODE SELECT command (caching parameters: Page code = 8, WCE bit), at the point when the IDD completes the transfer of all data specified in the WRITE or WRITE EXTENDED command, it reports the GOOD status and terminates the command.
This page is intentionally left blank.
CHAPTER 4 Command Specifications 4.1 Control/Sense Commands 4.2 Data Access Commands 4.3 Format Commands 4.4 Maintenance, Diagnostic Commands This chapter describes detailed specifications of the SCSI commands which the IDD is equipped with and how to use them. 4.1 Control/Sense Commands 4.1.
Command Specifications 4.1.2 INQUIRY (12) Bit Byte 7 6 5 4 0 1 0 0 0 1 0 0 0 0 CmdDt EVPD 0 0 0 0 0 0 Page Code/Operation Cpde 0 0 0 4 5 2 X‘12’ 2 3 3 0 0 Transfer Byte Length 0 0 0 0 0 This command transfers the information showing the IDD's characteristics (INQUIRY data) to the application client. This command is executed immediately without queuing in a system which issues only commands with no tags or links.
4.1 Control/Sense Commands (1) EVPD (Enable Vital Product Data) a) If the specification in this bits is zero, the IDD transfers the standard INQUIRY data or the command supported data, mentioned later, to the application client. b) If the specification in this bits is one, product information called VPD (vital product data) is transferred to the application client.
Command Specifications Table 4.
4.1 Control/Sense Commands a. Qualifier field (0,0,0): The specified logical unit shows the type of input/output device shown in the "Device Type Code" field. Even if this code is reported, it does not mean that that logical unit is in the ready state. (0,0,1): The specified logical unit shows the type of input/output device shown in the "Device Type Code" field, but it shows that an actual input/output device is not connected to that logical unit. The IDD does not report this code.
Command Specifications e. Response data format field This field shows the code which shows the standard INQUIRY data format. The definition of the code is (0,0,0,1) for SCSI-1/CCS mode or (0,0,1,0) for SCSI-2 or SCSI-3 mode. f. Additional data length This field shows the length of the INQUIRY data (byte length) after byte 5.
4.
Command Specifications [Byte 6] − − − − − DualP (Dual port): Dual port function [1] Port: Connection port, '0'= connect to port A '1'= connect to port B [0/1] ACKBREQB (ACKB/REQB): Use the ACKB and REQB signals with the B cable or the Q cable [0] Addr32 (Wide SCSI address 32): 32 bit SCSI addressing [0] Addr16 (Wide SCSI address 16): 16 bit SCSI addressing [0] [Byte 7] − − − − − − − − h.
4.1 Control/Sense Commands j. Product Revision field The IDD's microcode version number is displayed in ASCII code in this field. k. Device Serial Number field The value following byte 4 of the device serial number in the VPD information is indicated in this field. Higher order digits which do not contain valid numbers are filled with ASCII code spaces (X '20'). l. Clocking field "0" as Reserved. m. QAS (Quick Arbitrate Supported) bit "0" as Reserved. n.
Command Specifications (6) Command support data Table 4.5 shows the format and contents of the command support data transferred to the INIT by this command if "0" is specified in the "EVPD" bit and "1" is specified in the "CmdDt" bit. Table 4.5 Command support data Bit Byte 7 6 0 5 4 3 Qualifier 1 0 0 2 1 0 Device Type Code 0 0 0 2 Version 3 X'00' (Reserved) 4 X'00' (Reserved) 5 CDB Size (m-5) Support 6 ~ ~ CDB Usage Data ~ m a.
4.1 Control/Sense Commands Table 4.6 Support "Support" Bit 2 1 0 Description 0 0 0 Data about the requested SCSI operation code is not currently available. 0 0 1 The device server does not support the tested SCSI operation code. All data after byte 1 is undefined. 0 1 0 Reserved 0 1 1 The device server supports the tested SCSI operation code in conformance with an SCSI standard.
Command Specifications (7) VPD information When "1" is specified in the "EVPD" bits of the CDB, the VPD information described below is transferred to the INIT by this command. The INIT specifies the type of VPD information required in the "Page code" field of the CDB. The type of VPD information supported by the IDD and its page code number are as shown in Table 4.7. Table 4.
4.1 Control/Sense Commands The values indicated in the "Qualifier" and "Device Type Code" fields in byte 0 are the same as those in the previously mentioned standard INQUIRY data. The "Page code" field in byte 1 indicates the page code (X '00') of this VPD information itself. Also, the "Page length" field in byte 3 indicates the length (byte length) after byte 4.
Command Specifications c. Operation mode This VPD information reports the IDD's current operation mode. The format of this VPD information is shown in Table 4.10. Table 4.
4.1 Control/Sense Commands 4.1.3 READ CAPACITY (25) Bit Byte 7 6 5 4 0 1 3 2 1 0 0 0 0 0 X‘25’ 0 0 0 0 2 Logical Block Address (MSB) 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address (LSB) 6 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 PMI 9 0 0 0 0 0 0 0 0 This command transfers information related to the disk drive's capacity and the data block size to the INIT.
Command Specifications Table 4.11 READ CAPACITY data Bit Byte 7 6 5 4 3 2 0 Logical Block Address (MSB) 1 Logical Block Address 2 Logical Block Address 3 Logical Block Address (LSB) 4 Block Length (MSB) 5 Block Length 6 Block Length 7 Block Length (LSB) 1 0 4.1.
4.1 Control/Sense Commands When the "PF (page format)" bit in CDB byte 1 is "1," it indicates that the MODE SELECT parameters transferred from the INIT by this command are in the "Page Descriptor" format. The IDD disregards the value specified in this bit and regards the MODE SELECT parameters transferred from the INIT as being in the "Page Descriptor" format and executes this command.
Command Specifications The IDD has a common set of "Current", "Save" and "Default" values of all the MODE SELECT parameters for all the INITs. When the IDD's power is switched on, when TARGET RESET is received, when LIP (YX) is received - When TPRLO (Third Party Process Log-out... Extended Link Service) Global bit = 1, the "Current" MODE SELECT parameter values are changed to the "Save" parameter values, if they exist, and are changed to the "Default" parameter values if the "Save" values do not exist.
4.
Command Specifications If the IDD performs rounding processing ("rounding up" or "rounding down") of parameter values specified by the INIT, in some cases a "CHECK CONDITION" status (RECOVERED ERROR [=1] / Rounded parameter [37-00]) is reported, and in some cases it is not reported. Whether or not a "CHECK CONDITION" status is reported is determined by the type of "rounding up" or "rounding down" and the conditions.
4.1 Control/Sense Commands Table 4.
Command Specifications a. Header − Media type X '00' (default type) must be specified in this field. − Byte 2 Bits 7 and 4 of this field have meaning only in the header transferred to the INIT by the MODE SENSE and MODE SENSE EXTENDED commands. The values specified in these bits are disregarded in the MODE SELECT and MODE SELECT EXTENDED commands. "0" must always be specified by the INIT in the other bit positions.
4.1 Control/Sense Commands If less than 512 bytes is specified in this field, the IDD performs rounding processing (there is a rounding processing report), setting the data block length at 512 bytes. If more than 528 bytes is specified, rounding processing is performed (there is a rounding processing report), setting the data block length at 528 bytes. If the block length is not 4byte boundary, rounding processing is performed to change 4-byte boundary.
Command Specifications Table 4.
4.1 Control/Sense Commands In the diagram that shows the configuration of each individual "Page Descriptor," the default column shows that parameter's "default" value and the "variable" column shows whether or not it is possible to vary that parameter ("1" indicates that it can be varied). The INIT can know those values and attributes by using the MODE SENSE or MODE SENSE EXTENDED command. (1) Read/Write error recovery parameters (page code = 1) Table 4.
Command Specifications If transfer of this page descriptor is requested by the MODE SENSE or MODE SENSE EXTENDED command, the IDD reports X '0A' as the page length (byte 1). However, if either X '0A' or X '06' is specified for the page length in the MODE SELECT or MODE SELECT EXTENDED command, the IDD treats it as though the correct page length was specified.
4.1 Control/Sense Commands c. TB (transfer block) "1": Data blocks which contain errors that are impossible to correct are transferred to the INIT during a read operation. "0": Data blocks which contain errors that are impossible to correct are not transferred to the INIT during a read operation. d. RC (read continuous) This bit specifies continuous transfer of all the data requested by a command unaccompanied by a delay for executing error recovery processing.
Command Specifications h. DCR (disable correction) "1": Even when a correctable data check has been detected, data correction according to the ECC is prohibited. However, On-the-fly correction processing is not prohibited. "0": When a correctable data check has been detected, data correction according to the ECC is applied. The IDD disregards this bit and operates according to the default value (=0). i.
4.1 Control/Sense Commands l. Data strobe offset count (not supported) This field specifies in two's-complement notation an incremental position to where the recovered data strobe is adjusted from its nominal setting. Any value specified in this field does not preclude the device server from using positive or negative data strobe offset during error recovery. However, after any error recovery is completed the device server returns the data strobe offset to the value specified in this field.
Command Specifications Table 4.15 Combination of error recovery flags (1/4) EER PER DTE DCR 0 0 0 0 0 0 0 1 Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. If possible, data correction is executed afterward according to the ECC. 2. When error recovery has succeeded, processing of the command is continued. 3. The contents of recovered errors are not reported. 4.
4.1 Control/Sense Commands Table 4.15 Combinations of error recovery flags (2/4) EER PER DTE DCR 0 1 0 1 0 0 1 1 C141-C008 1 1 0 1 Error Recovery Procedure 1. Rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter. Data correction is not executed according to the ECC. 2. When error recovery has succeeded, processing of the command is continued. 3.
Command Specifications Table 4.15 Combinations of error recovery flags (3/4) EER PER DTE DCR 1 0 0 0 Error Recovery Procedure 1. When a correctable data check is detected, immediately, correction is executed according to the ECC. For data checks which cannot be corrected, rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter.
4.1 Control/Sense Commands Table 4.15 Combinations of error recovery flags (4/4) EER PER DTE DCR 1 1 1 0 1 1 1 1 Error Recovery Procedure 1. When a correctable data check is detected, immediately, correction is executed according to the ECC. For data checks which cannot be corrected, rereading is tried repeatedly up to the number of times specified in the "Read Retry Count", "Write Retry Count" or "Verify Retry Count" parameter.
Command Specifications (2) Disconnect/reconnect parameters (page code = 2) The format of the page descriptor in this MODE SELECT parameter is shown in Table 4.16. Table 4.16 MODE SELECT parameters: disconnect/reconnect parameters Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 0 1 X‘0E’ or X‘0A’ (Page Length) 2 Buffer Full Ratio Default X‘00’ Variable X‘FF’ 3 X‘00’ Variable X‘FF’ 4-5 (See the "Note.") Bus Inactivity Limit Default X‘0000’ Variable X‘0000’ 6-7 (See the "Note.
4.1 Control/Sense Commands If transfer of this page descriptor is required by the MODE SENSE or MODE SENSE EXTENDED command, the IDD reports X '0E' as the page length (byte 1). However, if either X '0E' or X '0A' is specified for the page length in the MODE SELECT command, the IDD regards it as if the correct page length was specified.
Command Specifications Note: If the value specified for the "buffer full ratio" or the "buffer empty ratio" is not within double the integral boundary of the logical data block length, the IDD rounds up the specified value to the value which is the nearest data block boundary. Also, if zero is specified in any of these parameters, the IDD treats that parameter as though 1 logical data block has been specified.
4.1 Control/Sense Commands The IDD disregards the value specified in this parameter and operates in accordance with the default value (00). h. EMDP (enable modify data pointer) (not supported) This bit indicates whether or not the initiator allows the data transfer to be reordered by the target. The IDD are not supported a MODIFY DATA POINTER message. Therefore, The IDD disregards the value specified in this bit, and operates according to the "Default" value. i.
Command Specifications (3) Format parameters (page code = 3) The Page descriptor format of this MODE SELECT parameter is shown in Table 4.17. Table 4.17 MODE SELECT parameters: format parameters Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 1 1 X‘16’ (Page Length) 2-3 Track Count/Zone Default X‘T.B.D’ Variable X‘0000’ 4-5 Alternate Sector Count/Zone Default X‘00F0’ (MATxxxx) or X’(T.B.
4.1 Control/Sense Commands a. Parameters for specifying alternate processing areas for defective blocks (bytes 2 to 9) The following 4 parameters specify the position and number of spare sectors for performing defective block alternate allocation processing on the disk media. See Chapter 3, "Data Format" of Product Manual for details of the IDD's alternate block processing. − Track count/zone (bytes 2 to 9) This parameter specifies the number of tracks a unit for alternating blocks.
Command Specifications b. Parameters specifying track format (bytes 10, 11) − Sector count/track This parameter specifies the number of physical sectors per 1 track. In the IDD, the number of physical sectors in a track is set unilaterally according to the data format specified by the "Data Block Length" parameter in the block descriptor or the "Data byte length/Physical sector" parameter in this page descriptor, so this parameter cannot be changed. The IDD disregards the value specified in this field.
4.1 Control/Sense Commands − Track skew factor This parameter indicates the number of physical sectors existing between the data block with the highest order logical block address on a track and the data block with the next logical block address on the next track of the same cylinder (track skew). This parameter cannot be changed. The IDD disregards the value specified in this field and sets the optimum track skew value in the specified data block length.
Command Specifications − SURF (surface addressing) When this bit is "1," it indicates that after logical data block address allocation is performed over all the sectors in order on the same memory surface (same head), it is proceeding to the next memory surface (next head) after all the sectors have been done. When this bit is "0," it indicates that after logical data block address allocation is performed over all the sectors in order in the same cylinder (all heads), it is proceeding to the next cylinder.
4.1 Control/Sense Commands (4) Drive parameters (page code = 4) The page descriptor format of this MODE SELECT parameter is shown in Table 4.19. Table 4.
Command Specifications When transfer of this page is requested by the MODE SENSE or MODE SENSE EXTENDED command, the IDD reports X '16' as the page length. However, in the MODE SELECT and MODE SELECT EXTENDED commands, if either X '16,' X '12' or X '0A' is specified, it is treated as if the IDD has specified the correct page length.
4.1 Control/Sense Commands (5) Verify error recovery parameters (page code = 7) The page descriptor format of this MODE SELECT parameter is shown in Table 4.20. Table 4.20 MODE SELECT parameters: verify error recovery parameters Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 0 1 1 1 EER PER DTE DCR 1 X‘0A’ (Page Length) 2 (Reserved) Default 0 0 0 0 1 0 0 0 Variable 0 0 0 0 1 1 1 1 3 (See the Note.) Number of retries during VERIFY.
Command Specifications a. Error recovery flags − EER (enable early recovery) − PER (post error) − DTE (disable transfer on error) − DCR (disable correction) The definitions and functions of these control flags are the same as for the read/write error recovery parameters. See item (1) concerning the details. b. Number of retries during VERIFY This parameter specifies the number of times reading of the disk media should be retried when a "Data Check" type error is detected in a read operation.
4.1 Control/Sense Commands (6) Caching parameters (page code = 8) The page descriptor format of this MODE SELECT parameter is shown in Table 4.21. Table 4.
Command Specifications The parameters defined in this page descriptor control the range of look-ahead data in the Look-Ahead cache feature and enable or disable the caching operation. See Section 3.2, "Look-Ahead Cache Feature" and Section 3.3, "Write Cache" concerning details of the Look-Ahead cache feature and parameter setting methods. a. RCD (read cache disable) This bit can be specified, and its operation is as specified.
4.1 Control/Sense Commands "1": This enables the write cache. Write data remains in the buffer memory, the cache is made the object even for a read command, and when all of the write data has been received, "GOOD" status is reported without disconnecting. Sequential writing is performed without waiting for rotation. "0": This prohibits operation of the write cache function.
Command Specifications "1": Data put into the cache via a READ command was replaced sooner than data placed into the cache by other means. "0": Indicates the device server was not distinguish between retaining the indicated data and data placed into the cache memory by other means. h. Write retention priority (not supported) This field advises the device server the retention priority to assign for data written into the cache that has also been transferred from the cache memory to the medium.
4.1 Control/Sense Commands l. Maximum pre-fetch control block count (not supported) This parameter specifies the maximum quantity of logical data blocks prefetched to the data buffer with the READ command or READ EXTENDED command. In the IDD the maximum pre-fetch quantity cannot be limited. This parameter cannot be changed. The IDD disregards the specification in this field. m. DRA (disable read-ahead) (not support) This bit specifies whether or not activate the read-ahead operation.
Command Specifications This parameter indicates the same value for all initiators and if it is changed by any initiator, a UNIT ATTENTION condition (UNIT ATTENTION [=6] / Mode select parameter changed [=2A-01]) is generated for all the initiators that did not change it. This parameter can be changed though the IDD disregards the specification of this field. The IDD divided the Cache Segments according to the inherent algorithm.
4.1 Control/Sense Commands (7) Control mode parameters (page code = 0A) The page descriptor format of this MODE SELECT parameter is shown in Table 4.22. Table 4.
Command Specifications a. TST (task set type) This field specifies the type of task set defined below. Table 4.23 TST Value Description 000b Task set per logical unit for all initiators 001b Task set per initiator per logical unit 010b-111b Reserved The IDD operates according to "000b". If other value is specified in this field, the IDD reports a "CHECK CONDITION" status (ILLEGAL REQUEST [=5] / Invalid parameter in list [=26-00]). b.
4.1 Control/Sense Commands Since the IDD does not support the reporting function of exception condition, the IDD disregards the specification in this bit. e. DQue (disable queuing) This bit specifies whether the IDD will execute processing of tagged commands or not. "1": The IDD prohibits tagged queuing processing. The IDD clears queued commands and generates a UNIT ATTENTION condition (Command cleared by another initiator [=2F-00]) for each of the INITs that issued the commands which were cleared.
Command Specifications g. RAC (report check) (not supported) The IDD is not supported in this bit. Therefore, the IDD always report "0", and ignore specified value. h. SWP (soft write protect) (not supported) This bit specifies whether or not to execute for the device server write operation to the medium. The IDD is not supported this bit. Therefore, the IDD always report "0", and ignore specified value. i.
4.1 Control/Sense Commands (8) Notch parameters (page code = 0C) Table 4.
Command Specifications Note: Normally, the number of tracks (logical heads) per cell is set in the track count/zone, but in the case of notching only, the total track count (number of cylinders in the zone x number of logical heads) of the affected zone is reported. If this parameter is issued, only the format parameter of the zone specified by the MODE SENSE command can be referred to without changing the number of accessible blocks.
4.1 Control/Sense Commands • Starting Boundary This field is enabled by the MODE SENSE command. This field indicates the beginning of the active notch or, if the active notch is zero, the beginning of the logical unit (IDD). • Ending Boundary This field is valid in the MODE SENSE command. This field indicates the ending of the active notch or, if the active notch is zero, the ending of the logical unit (IDD) (see Table 4.18).
Command Specifications b. TEST "1": If "0" is set for DExcpt, a failure prediction is reported with a failure prediction reporting condition that is generated when the time specified with Interval Timer has elapsed. The method and number of times of this reporting are determined according to the specifications in the MRIE and Report Count fields. At this time, the sense key of 0x5D and the additional sense code of 0xFF are reported.
4.1 Control/Sense Commands Table 4.27 MRIE (1/2) MRIE X’00’ Descriptor No reporting of informational exception conditions: This method instructs the target to not report informational exception conditions. X’01’ Asynchronous event reporting: This method instructs the target to report informational exception conditions by using the rules for asynchronous event reporting as described in the SCSI-3 Architecture Model and the relevant Protocol Standard.
Command Specifications Table 4.27 MRIE (2/2) MRIE Descriptor X’05’ Generate no sense: This method instructs the target to report informational exception conditions by returning a CHECK CONDITION status on any command. The sense key shall be set to NO SENSE and the additional sense code shall indicate the cause of the informational exception condition. (setting prohibited) The command that has the CHECK CONDITION shall complete without error before any informational exception condition may be reported.
4.1 Control/Sense Commands The "Report Count" field indicates the number of timer to report an informational exception conditions to the application client. A value of zero in the Report Count field indicates there is no limit on the number of timers the target shall report an information exception condition. (10) Fibre channel control parameters (page code = 19) Table 4.
Command Specifications a. DTOLI (disable target originated loop initialization) This bit is possible to specify and operates according to the specification. This bit specifies concerning LIP. "1": − An Initializing LIP is not issued when the IDD enters the loop. − If the Initializing LIP is received, operation corresponds to the Initialization LIP. − When a Loop Failure is detected, the Loop Failure LIP [LIP (F8, x)] is issued.
4.1 Control/Sense Commands d. RHA (require hard address) This bit is possible to specify and operates according to the specification. This bit specifies settings concerning enabling or disabling the Soft Address. "1": In Loop Initialization, even if a hard address cannot be fixed, a soft address is not used. In this case, the IDD enters a Non-participating State. In the Non-participating State, if Loop Initialization is detected, try fixing a hard address again.
Command Specifications Note: It is prohibited that "1" is specified in DTIPE and PLPB simultaneously. If DTIPE=PLPB=1 is specified, it responds with CHECK CONDITION (ILLEGAL REQUEST, VALID FIELD IN THE PARAMETER LIST). h. RR_TOV UNITS (resource recovery timeout value UNITS) (not supported) This field specifies the time unit of the RR_ROV field. The value specified in this field is ignored, and the default value 001b is always valid for operation. Table 4.30 RR_TOV UNITS RR_TOV UNITS i.
4.1 Control/Sense Commands k. ORIGINATOR CMR (not supported) This field specifies the minimum number of MCM circuits for each port that is an IDD originator. The value specified in this field is ignored, and the default value X'00' is always valid for operation. l. RESPONDER CMR (not supported) This field specifies the minimum number of MCM circuits for each port that is an IDD responder. The value specified in this field is ignored, and the default value X'00' is always valid for operation. m.
Command Specifications a. Number of retries during a seek error This parameter specifies the number of times repositioning is retried when a seek error is detected. When zero is specified in this field, repositioning retries are prohibited. The value specified in this field is applicable for all commands which are accompanied by a seek operation. b. RFJ (reserved by Fujitsu) All the bits in byte 3 are reserved by Fujitsu. The user should specify "0" in this bit.
4.1 Control/Sense Commands 4.1.
Command Specifications Table 4.
4.1 Control/Sense Commands 4.1.6 MODE SENSE (1A) Bit Byte 7 6 5 4 0 1 0 0 0 0 PC 1 0 DBD 0 0 0 0 0 0 0 0 0 0 Page Code 0 0 4 5 2 X‘1A’ 2 3 3 0 0 Transfer Byte Length 0 0 0 0 0 This command reports the values for each type of parameter related to the disk drive's physical attributes, data format, timing for FC interface Loop OPEN/CLOSE processing, error recovery procedures, etc., as well as the attributes of those parameters, to the INIT.
Command Specifications Table 4.
4.1 Control/Sense Commands Table 4.35 MODE SENSE data type specifications PC 00 Type of Parameter Transferred to the INIT Current Values: Reports each "Current" parameter value. The "Current" values are either of the following values. 01 • Values specified by a MODE SELECT or MODE SELECT EXTENDED command which is finally normally terminated.
Command Specifications The "Transfer Byte Length" field in the CDB specifies the total number of bytes of MODE SENSE data which can be transferred to the INIT by this command. The IDD transfers the number of bytes of all the MODE SENSE data specified in the "Page code" field or the portion of MODE SENSE data with the length specified in the "Transfer Byte Length" field, whichever is smaller.
4.1 Control/Sense Commands Table 4.
Command Specifications (1) Header a. Sense data length This field indicates the length (number of bytes) of the parameter list (MODE SENSE data) which it is possible to transfer to the INIT by this command. The length of the "Sense data length" field itself is not included in this value.
4.1 Control/Sense Commands means the maximum number of logical data blocks that it is possible to rank in the "User Space"). b. Data block length This field indicates the length (byte length) of 1 logical data block on the disk media. (3) Page descriptor The "Page descriptor" is configured from a parameter field which follows a 2byte page header, and is divided into units called "Page" for each parameter's functional attributes. See the description of the MODE SELECT command (Section 4.1.
Command Specifications 4.1.
4.1 Control/Sense Commands Table 4.
Command Specifications 4.1.8 REZERO UNIT (01) Bit Byte 7 6 5 4 0 3 2 1 0 X‘01’ 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 This command moves the read/write heads of the disk drive to the initial position (physical cylinder 0 / physical track 0). A data block with the physical block address of zero exists at the initial position.
4.1 Control/Sense Commands It is possible to select the disk drive's spindle motor starting mode through the extrnal setting terminal. If prohibition of motor starting control is set by this command at the setting terminal, the spindle motor starts automatically when the IDD's power is switched on. It is possible to delay the starting time by the value of SEL_ID.
Command Specifications 4.1.10 RESERVE (16) Bit Byte 7 6 5 4 0 3 2 1 0 X‘16’ 1 0 0 0 3rd Pty 3rd Pty Dev ID 0 2 × × × × × × × × 3 × × × × × × × × 4 × × × × × × × × 5 0 0 0 0 0 0 0 0 Together with the RELEASE command, this command controls exclusive access to the logical unit (IDD) under a multi-initiator environment. The IDD is reserved by this command for the INIT which issued this command.
4.1 Control/Sense Commands (2) Reserve right and third party reserve function The third party reserve function is not supported by the drive. If the "3rd Pty" bit in byte 1 of the CDB is "0," the IDD is reserved by the INIT which issued this command and that INIT has the Reserve right for the IDD. If the "3rd Pty" bit is "1," the third party reserve function is specified. An INIT which specifies the third party reserve function and issues this command can reserve the IDD for use by another FC device.
Command Specifications • Reserve right and the third party reserve function Remark In order to clarify the jurisdiction related to reserve and release, the term "Reserve Right" is used in this manual. INIT #A INIT #B FC interface TARG #0 TARG/INIT #1 Figure 4.2 Reserve right and the third party reserve function 1. 2.
4.1 Control/Sense Commands − 3. Commands issued by INIT #B to TARG #0 are rejected with a RESERVATION CONFLICT status, except the INQUIRY, REQUEST SENSE and RELEASE commands. A RELEASE command is terminated normally, but it has no influence on the TARG #0 reserve right. An example of the third party reserve function is applicable when using the COPY command.
Command Specifications 4.1.12 RELEASE (17) Bit Byte 7 6 5 4 0 3 2 1 0 X‘17’ 1 0 0 0 3rd Pty 3rd Pty Dev ID 0 2 × × × × × × × × 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 This command releases the reserve state of an IDD in relation to the INIT that issued this command. When a reserve state in relation to the INIT that issues this command, or an IDD does not exist, this command is terminated normally with a GOOD status.
4.1 Control/Sense Commands 4.1.13 RELEASE EXTENDED (57) Bit Byte 7 6 5 4 0 3 2 1 0 X‘57’ 1 0 0 0 3rd Pty 0 0 0 0 2 × × × × × × × × 3 Third Party Devices ID 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 7 × × × × × × × × 8 × × × × × × × × 9 0 0 0 0 0 0 0 0 4 3 2 1 0 Same as RELEASE command. 4.1.
Command Specifications 2) When the command which the IDD is currently executing terminates abnormally due to the occurrence of an irrecoverable error at the FC interface. 3) When an irrecoverable error occurs in a write command that is currently being executed after the "Good" status was reported by the WCE bit specification (deferred error). 4) When a failure state occurs (INITIAL SEEK failure, SA READ failure, etc.
4.1 Control/Sense Commands This command reports the "CHECK CONDITION" status and terminates abnormally only in the cases where the conditions shown below are detected. In this case, new sense data are generated and the sense data held up to that time are lost. 1) When sending of sense data is impossible due to an IDD hardware error. 2) When an irrecoverable error is detected on the FC interface. 3) If an overlapped command occurs. 4) A error in a specification other than the LUN field of the CDB.
Command Specifications 4.1.15 LOG SELECT (4C) Bit Byte 7 6 5 4 1 2 3 2 1 0 X'4C' 0 3 0 PC 0 0 0 0 PCR SP 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 7 Parameter List Length (MSB) 8 Parameter List Length (LSB) 9 0 0 0 0 0 This command provides a means for an application client to manage statistical information maintained by the IDD about IDD.
4.1 Control/Sense Commands CHAPTER 4 Command Specifications 4.1 Control/Sense Commands Table 4.38 PC (page control) Value Description 00b Current threshold values 01b Current cumulative values 10b Default threshold values 11b Default cumulative values The "PC" bits are ignored by the drive. The drive assumes that current cumulative parameters are selected. The "Parameter List Length" field specifies the length in bytes of the parameter list that is located in the Data-Out Buffer.
Command Specifications a. Page code This field identifies which log page is being transferred. The log pages that can be transferred by this command are shown in Table 4.40. Table 4.
4.1 Control/Sense Commands a. Parameter code This field identifies the log parameter being transferred for that log page. b. Byte 2 1) DU (Disable Update) "1": The IDD does not update the log parameter value except in response to a LOG SELECT command that specifies a new value for the parameter. "0": The IDD updates the log parameter value to reflect all events that are noted by that parameter.
Command Specifications 7) LP (List Parameter) "1": The parameter is a data counter. "0": The parameter is a list parameter. If these bits are specified by LOG SELECT command, the IDD terminates normally. But the IDD's action is not changed. For LOG SENSE command, these bits always report value defined in each log page (see 4.2). 4.1.
4.1 Control/Sense Commands The "PC" bits are ignored by the drive. The drive assumes that current cumulative parameters are selected. The "Page Code" field identifies which page of data is being requested. If the page code is reserved or not implemented, the device server terminates the command with CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00]). The "Page Code" assignments for the log pages are listed in Table 4.42. Table 4.
Command Specifications • Log parameters This clause describes the log page structure and the log pages that are applicable to all FC devices. Pages specific to each device type are described in the command standard that applies to that device type. The LOG SENSE command returns a single log page specified in the page code field of the command descriptor block. (1) Support log page (X'00') The supported log page returns the list of log pages implemented by the drive. Table 4.
4.1 Control/Sense Commands (2) Buffer overrun/underrun page (X'01') Table 4.
Command Specifications • Count Basis 0h : Undefined 1h : Per command, optional 2h : Per failed reconnect, optional 3h : Per unit of time, optional 4h-7h : Reserved The drive does not support this field. Zero is always reported. • Data Underrun Count of data underruns which occur during write operation when a buffer empty condition prevents continued transfer of data to the media from the buffer. The drive does not support this field due to a hardware limitation. Zero is always reported.
4.1 Control/Sense Commands • Write errors recovered without delays (page 02, code 0000) Table 4.
Command Specifications • Total write errors posted (page 02, code 0002) Table 4.48 Total write errors posted (page 02, code 0002) Bit Byte 7 6 5 4 3 2 1 0 (MSB) 4 X'0002' (Parameter code) (Total Posted Errors) 5 6 DU DS TSD ETC 0 0 0 0 7 (LSB) TMC 0 LBIN LP 0 0 0 X'04' (Parameter Length) 8 (MSB) 9 Counter Value 10 11 (LSB) The Counter Value indicates the count of all posted errors to the interface during write operations.
4.1 Control/Sense Commands • Total write bytes processed (page 02, code 0005) Table 4.50 Total write bytes processed (page 02, code 0005) Bit 7 Byte 6 5 4 3 2 1 0 (MSB) 4 X'0005' (Parameter code) (Total Bytes Processed) 5 6 DU DS TSD ETC 0 0 0 0 7 (LSB) TMC 0 LBIN LP 0 0 0 X'0A' (Parameter Length) 8 (MSB) 9 ~ ~ ~ ~ ~ ~ Total Write Bytes Processed (10 bytes) 16 17 (LSB) The Total Write Bytes Processed indicates the total processed bytes during write operations.
Command Specifications (4) Read error count page (X'03') Table 4.52 Read error count page (X'03') Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 0 0 1 1 1 X‘00’ (Reserved) 2 Page Length (MSB) 3 Page Length (LSB) All of the following parameters have this header. Page Length will be defined based on the value of Parameter Pointer. (CDB 5-6) • Read errors recovered without delays (page 03, code 0000) Table 4.
4.1 Control/Sense Commands • Read errors recovered with possible delays (page 03, code 0001) Table 4.
Command Specifications • Total recoverable read errors posted to INIT (page 03, code 0003) Table 4.
4.1 Control/Sense Commands • Total unrecoverable read errors posted to INIT (page 03, code 0006) Table 4.
Command Specifications • Verify errors recovered without delays (page 05, code 0000) Table 4.
4.1 Control/Sense Commands • Total verify errors posted (page 05, code 0002) Table 4.62 Total verify errors posted (page 05, code 0002) Bit Byte 7 6 5 4 3 2 1 0 (MSB) 4 X'0002' (Parameter code) (Total Posted Errors) 5 6 DU DS TSD ETC 0 0 0 0 (LSB) TMC 0 LP 0 0 0 7 X'04' (Parameter Length) 8 (MSB) 9 LBIN Counter Value 10 11 (LSB) The Counter Value indicates the count of all posted errors to the interface during verify operations.
Command Specifications • Total verify bytes processed (page 05, code 0005) Table 4.64 Total verify bytes processed (page 05, code 0005) Bit 7 Byte 6 5 4 3 2 1 0 (MSB) 4 X'0005' (Parameter code) (Total Bytes Processed) 5 6 DU DS TSD ETC 0 0 0 0 7 (LSB) TMC 0 LBIN LP 0 0 0 X'0A' (Parameter Length) 8 (MSB) 9 ~ ~ ~ ~ ~ ~ Total Verify Bytes Processed (10 bytes) 16 17 (LSB) The Total Verify Bytes Processed indicates the total processed bytes during verify operation.
4.1 Control/Sense Commands (6) Non-medium error count page (X'06') Table 4.
Command Specifications • Temperature (page 0D, code 0000) Table 4.68 Temperature (page 0D, code 0000) Bit Byte 7 6 5 4 3 2 1 0 (MSB) 4 X'0000' (Parameter code) (Temperature) 5 6 DU DS TSD ETC 0 1 0 0 (LSB) TMC 0 LBIN LP 1 1 0 7 X'02' (Parameter Length) 8 X'00' (Reserved) 11 Temperature (degrees Celsius) The Temperature sensed in the device at the time the LOG SENSE command is performed shall be returned in the parameter code 0000h.
4.1 Control/Sense Commands (8) Start-stop cycle counter page (X'0E') Table 4.70 Start-stop cycle counter page (X'0E') Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 1 1 1 0 1 X‘00’ (Reserved) 2 Page Length (MSB) 3 Page Length (LSB) All of the following parameters have this header. Page Length will be defined based on the value of Parameter Pointer. (CDB 5-6) • Date of manufacture (page 0E, code 0001) Table 4.
Command Specifications • Accounting date (page 0E, code 0002) Table 4.
4.1 Control/Sense Commands The Specified cycle count over device lifetime is a parameter provided by the device sever. The specified cycle count over device lifetime parameter shall not be savable by the application client using the LOG SELECT command. The parameter value is a 4-byte binary number. The value indicates how operation or reliability outside the limits specified by the manufacture of the device. • Start-stop cycle counter (page 0E, code 0004) Table 4.
Command Specifications (9) Application client page (X'0F') Table 4.75 Application client page (X'0F') Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 0 1 1 1 1 1 X‘00’ (Reserved) 2 Page Length (MSB) 3 Page Length (LSB) All of the following parameters have this header. Page Length will be defined based on the value of Parameter Pointer. (CDB 5-6) • General usage application client parameter data (page 0F, code 0000-003F) Table 4.
4.1 Control/Sense Commands (10) Self-test result page (X'10') Table 4.77 Self-test result page (X'10') Bit Byte 0 7 6 5 4 3 2 1 0 0 0 0 1 0 0 1 0 1 X‘00’ (Reserved) 2 Page Length (MSB) 3 Page Length (LSB) All of the following parameters have this header. Page Length will be defined based on the value of Parameter Pointer. (CDB 5-6) • Self-test result parameter data (page 10, code 0001-0014) Table 4.
Command Specifications When the self-test is initiated, the value specified in the SELF-TEST CODE field in the CDB is reported to the SELF-TEST CODE field by a SEND DIAGNOSTICS command. The values reported to the “Self-Test Result Value” field are defined in Table 4.79. Table 4.79 Self-test results values Value Description 0h The self-test completed without error.
4.1 Control/Sense Commands (11) SMART status page (X'2F') Table 4.80 SMART status page (X'2F') [Fujitsu unique page] Bit Byte 0 7 6 5 4 3 2 1 0 0 0 1 0 1 1 1 1 1 X‘00’ (Reserved) 2 Page Length (MSB) 3 Page Length (LSB) 4 ~ ~ ~ ~ ~ ~ SMART Status Parameter n This page contains parameters which allow the application client to check the predictive drive failure condition of the IDD.
Command Specifications 4.1.17 PERSISTENT RESERVE IN (5E) (not supported) Bit 7 Byte 6 5 4 0 3 2 1 0 X'5E' 1 0 0 0 Service Action 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 7 Allocation Length (MSB) 8 Allocation Length (LSB) 9 0 0 0 0 0 This command is used to obtain information about persistent reservations and reservation keys that are active within a device server.
4.1 Control/Sense Commands • READ KEYS The READ KEYS service action requests that the device server return a parameter list containing a header and a list of each currently registered initiator's reservation key. If multiple initiators have registered with the same key, then that key value shall be listed multiple times, once for each such registration.
Command Specifications The "Generation" field shall contain a 32-bit counter maintained by the device server that shall be incremented every time a PERSISTENT RESERVE OUT command requests a REGISTER, a REGISTER AND IGNORE EXISTING KEY, a CLEAR, a PREEMPT, or a PREEMPT AND ABORT service action.
4.1 Control/Sense Commands (3) PERSISTENT RESERVE IN parameter data for READ RESERVATIONS The format for the parameter data provided in response to a PERSISTENT RESERVE IN command with the READ RESERVATIONS service action is shown in Table 4.84. Table 4.
Command Specifications Table 4.
4.1 Control/Sense Commands • Persistent reservations scope The value in the "Scope" field shall indicate whether a persistent reservation applies to an entire logical unit or to an element. The values in the "Scope" field are defined in Table 4.86. Table 4.
Command Specifications Table 4.87 Persistent reservations type codes Code Name 0h 1h Description Reserved Write Exclusive Reads Shared: Any application client on any initiator may execute tasks that request transfers from the storage medium or cache of the logical unit to the initiator.
4.1 Control/Sense Commands 4.1.18 PERSISTENT RESERVE OUT (5F) (not supported) Bit Byte 7 6 5 4 0 1 3 2 1 0 X'5F' 0 0 0 2 Service Action Type Scope 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 7 Parameter List Length (MSB) 8 Parameter List Length (LSB) 9 0 0 0 0 0 This command is used to request service actions that reserve a logical unit or element for the exclusive or shared use of a particular initiator.
Command Specifications The parameter list shall be 24 bytes in length and the "Parameter List Length" field shall contain 24 (18h). If the parameter list length is not 24, the device server shall return a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Parameter list length error [=1A-00]). (1) PERSISTENT RESERVE OUT service actions When processing the PERSISTENT RESERVE OUT service actions, the device server shall increment the generation value as specified in 4.1.17 (2).
4.1 Control/Sense Commands (2) PERSISTENT RESERVE OUT parameter list The parameter list required to perform the PERSISTENT RESERVE OUT command are defined in Table 4.89. All fields shall be sent on all PERSISTENT RESERVE OUT commands, even if the field is not required for the specified service action and scope values. Table 4.
Command Specifications 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.
4.1 Control/Sense Commands Table 4.
Command Specifications 4.1.19 REPORT LUNS (A0) Bit Byte 7 6 5 4 0 3 2 1 0 X'A0' 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 Allocation Length (MSB) 7 Allocation Length 8 Allocation Length 9 Allocation Length (LSB) 10 0 0 0 0 0 0 0 0 11 0 0 0 0 0 0 0 0 This command requests that the peripheral device logical unit inventory be sent to the application client.
4.1 Control/Sense Commands Table 4.91 REPORT LUNS parameter list Bit Byte 7 0 (MSB) ~ ~ 6 5 4 3 (LSB) 8 (MSB) ~ (LSB) ~ ~ ~ ~ n-7 ~ (MSB) ~ n ~ First LUN 15 ~ ~ ~ Reserved 7 LUN List ~ (MSB) ~ ~ 0 (LSB) 4 ~ 1 LUN List Length (N-7) 3 Header 2 ~ Last LUN (LSB) The "LUN List Length" field shall contain the length in bytes of the LUN list that is available to be transferred.
Command Specifications 4.1.
4.1 Control/Sense Commands Table 4.92 REPORT DEVICE IDENTIFIER parameter list Bit Byte 7 0 (MSB) ~ ~ 6 5 4 3 0 ~ (LSB) 4 (MSB) ~ n 1 Identifier Length (n-4) 3 ~ 2 ~ Identifier (LSB) The "Identifier Length" field specifies the length in bytes of the "Identifier" field. If the "Allocation Length" field in the CDB is too small to transfer all of the identifier, the length shall not be adjusted to reflect the truncation.
Command Specifications 4.1.
4.2 Data Access Commands Table 4.93 SET DEVICE IDENTIFIER parameter list Bit Byte 7 0 (MSB) ~ 6 5 4 ~ 3 2 1 0 Identifier n (LSB) The "Identifier" field shall be a vendor specific value, to be returned in subsequent REPORT DEVICE IDENTIFIER commands. 4.2 Data Access Commands 4.2.
Command Specifications When the specifications in the "Logical block address" field and "Transfer block count" field in the CDB exceed the maximum logical block address in the IDD, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Logical block address out of range [=21-00]) and the reading of data from the disk media is not executed. Error recovery processing during execution of this command can be specified by the MODE SELECT parameter.
4.2 Data Access Commands The functions of this command are the same as those of the Group 0 READ command (Section 4.2.1) with the exception that it is possible to specify 4-byte logical block addresses and 2-byte transfer block counts. However, when zero is specified for the "Transfer block count," the command is terminated normally without seek and pre-fetch being performed. • FUA (force unit access) When this bit is "0", it indicates that the IDD satisfy the command by accessing the cache memory.
Command Specifications When the specifications in the "Logical block address" field and "Transfer block count" field in the CDB exceed the maximum logical block address in the IDD, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Logical block address out of range [=21-00]) and writing of data to the disk media is not executed.
4.2 Data Access Commands 4.2.
Command Specifications 4.2.
4.2 Data Access Commands 4.2.
Command Specifications 4.2.7 SEEK (0B) Bit Byte 7 6 5 4 0 1 3 2 1 0 X‘0B’ 0 0 0 Logical Block Address (MSB) 2 Logical Block Address 3 Logical Block Address (LSB) 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 This command executes a seek operation of the cylinder/track where the logical data block specified in the "Logical block address" field in the CDB exists. When disconnect processing is permitted, the IDD performs disconnect processing after receiving the CDB.
4.2 Data Access Commands 4.2.8 SEEK EXTENDED (2B) Bit Byte 7 6 5 4 0 1 3 2 1 0 0 0 0 0 X‘2B’ 0 0 0 0 2 Logical Block Address (MSB) 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address (LSB) 6 0 0 0 0 0 0 0 0 7 0 0 0 0 0 0 0 0 8 0 0 0 0 0 0 0 0 9 0 0 0 0 0 0 0 0 This command executes a seek operation of the cylinder/track where the logical data block specified in the "Logical block address" field in the CDB exists.
Command Specifications 4.2.
4.2 Data Access Commands n: Value specified in the "Logical block address" field n–1 n n+1 n+2 n+3 n+m+1 n+m m: Value specified in the "Block count" field Range where access is permitted by linked commands Figure 4.
Command Specifications 1. Commands which come under restrictions in read operations or write operations when "1" is specified in the "RdInh" (read inhibit) or "WrInh" (write inhibit) flag are as follows. “RdInh” − READ − READ EXTENDED (*) − READ LONG − VERIFY (*) − WRITE AND VERIFY (*) − PRE-FETCH “WrInh” − FORMAT UNIT − REASSIGN BLOCKS − WRITE − WRITE AND VERIFY (*) − WRITE EXTENDED (*) − WRITE LONG − WRITE SAME * When zero is specified in the processing block count, that command is not executed.
4.2 Data Access Commands 4.2.10 SYNCHRONIZE CACHE (35) Bit Byte 7 6 5 4 0 1 3 2 1 0 0 0 Immed 0 0 0 0 0 0 0 X‘35’ 0 0 0 0 2 Logical Block Address (MSB) 3 Logical Block Address 4 Logical Block Address 5 Logical Block Address (LSB) 6 0 0 0 0 0 7 Block Count (MSB) 8 Block Count (LSB) 9 0 0 0 0 0 This command matches the logical block data in the data buffer with the same logical block data recorded on the disk media.
Command Specifications 4.3 Format Commands 4.3.1 FORMAT UNIT (04) Bit Byte 7 6 5 4 0 3 2 1 0 X‘04’ 1 0 0 0 2 0 0 0 FmtData CmpLst 0 0 3 Interleave factor (MSB) 4 Interleave factor (LSB) 5 0 0 0 0 0 Defect List Format 0 0 0 0 0 0 This command initializes (formats) the entire area of the disk media that can be accessed from the INIT (User Space).
4.3 Format Commands (1) Defect list In order to register or specify the positions of defects on the disk media in connection with defect management processing that can be specified from the INIT, the following types of “Defect List” are defined. a. P List: primary defect list Defect position information (permanent defects) is registered in this list at the time the disk drive is shipped from the factory. The P List registers areas on the disk media which clearly cannot be accessed from the INIT.
Command Specifications (2) Specifying the initialization method The INIT can specify the method of defect processing executed by this command in the “FmtData (format data)” bit and “CmpLst (complete list)” bit of CDB byte 1 and the “Defect List Format” field. When “1” is specified in the “FmtData (format data) bit, it indicates that the format parameters (header and defect list), described later, are transferred from the INIT when this command is executed.
4.3 Format Commands (3) Format parameters Table 4.96 lists the data format of the Format parameter transferred from the INIT when “1” is specified in the “FmtData (format data)” bit of the CDB. Table 4.
Command Specifications a. Header The top of the format parameter transferred from the INIT is a 4-byte header. The INIT can specify the method used for defect processing that is executed by this command by control flags within the header. − − FOV (format option valid) 0: Indicates that the INIT does not specially specify concerning the functions specified by the control flags in bits 6 to 4 of byte 1 (see following “DPRY” to “STPF”.).
4.3 Format Commands − STPF (stop format): Default value: “1” When the defect list (P List or G List) necessary for executing the defect processing specified in this command, cannot be read from the disk media, this bit indicates whether to continue (“0” is specified) or terminate (“1” is specified) command processing, but in the IDD, this bit’s specification is disabled, and the specified value is disregarded.
Command Specifications b. Defect list (D List) The defect list (D List) contains defect position information about the disk media specified by the INIT and is configured from one or more “Defect descriptors.” “Defect descriptors must be described in the format specified in the “Defect List Format” field of the CDB. The configurations which it is possible to specify for the “Defect descriptors” in the defect list (D List), and their description formats, are shown below.
4.3 Format Commands − Physical sector address format defect descriptor Table 4.98 lists this description format of the defect descriptor. A defect descriptor with this format specifies the physical sector number of the data block which includes the defect on the disk media together with the cylinder No. and the head (track) No. When specifying multiple defect descriptors, the cylinder No. must be specified in the top position and the physical sector No.
Command Specifications − Cautions in specifying the D list The P List, containing defect position information, is always recorded on the IDD when it is shipped from the factory. Also, information on defect positions for which alternate block processing has been implemented during operation are recorded as the G List.
4.3 Format Commands (4) Defect processing during initialization Table 4.99 shows each combination of control flag specification values and the contents of processing executed by the IDD. Furthermore, see Chapter 3 “Data Format” of the “Product Manual” concerning alternate block allocation processing methods. Table 4.
Command Specifications Table 4.99 FORMAT UNIT command defect processing (2/2) CDB Byte 1 FmtData 1 CmpLst 0 Header Defect list format 1 0 0 FOV 1 DPRY 1 Defect List Length >0 1 0 1 Defect Processing Method 1) Alternate block allocation is performed for defects registered in the previously existing G List and the defects described in the D List transferred from the INIT. 2) The P List is saved, but it is not used in defect processing.
4.3 Format Commands 4.3.2 REASSIGN BLOCKS (07) Bit Byte 7 6 5 4 0 3 2 1 0 X‘07’ 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 This command allocates alternate data blocks for defective data blocks specified in the “Defect Data” list transferred form the INIT. The INIT specifies the logical block address of one or more defective data blocks in the “Defect Data” list which it transfers to the IDD.
Command Specifications The format of the “Defect Data” list transferred from the INIT by this command is shown in Table 4.100. Table 4.
4.3 Format Commands Furthermore, if the addresses of logical data blocks specified in the defect descriptor list overlap each other, This command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in parameter list [=26-00] and none of the alternate block allocation processing in that command is executed. The IDD allocates alternate blocks to the specified data blocks in order from the top of the defect descriptor list.
Command Specifications If this command is terminated with a CHECK CONDITION status, the sense code/sub-sense code in the sense data is other than “No defect spare location available [=32-00], and a valid logical block address (other than X ‘FFFFFFFF’) is displayed in the “Command inherent information” field, it is necessary for the INIT to reissue this command by the following procedure after executing recovery processing (shown in Section 5.2) in accordance with the contents of the sense data. 1.
4.3 Format Commands 4.3.3 READ DEFECT DATA (37) Bit Byte 7 6 5 4 0 3 2 1 0 0 0 0 X‘37’ 1 0 0 0 0 0 2 0 0 0 PList GList 3 0 0 0 0 0 0 0 0 4 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 6 0 0 0 0 0 0 0 0 0 0 0 7 Transfer Byte Length (MSB) 8 Transfer Byte Length (LSB) 9 0 0 0 0 0 Defect List Format This command transfers the list described in the defect position information of the disk media (defect data) to the INIT.
Command Specifications Table 4.102 Defect data format Defect List Format Defect Data Format 0 0 0 Block Address Format 1 0 0 Byte Distance from the Index Format 1 0 1 Physical Sector Address Format The “Transfer byte length” field in the CDB specifies the defect data length (number of bytes) that can be received by the INIT.
4.3 Format Commands c. Defect list format This field indicates the description format of the defect descriptor list that is actually transferred to the INIT. It is possible for the IDD to transfer defect data in 3 different formats which it can specify in the CDB, and the values in this field are the same as the values specified in the “Defect List Format” field in the CDB. d.
Command Specifications 3. Even if defect data of the type specified in the CDB do not exist in the defect list (P List or G List) (if the defect list is empty), “1” is displayed in the “PList” bit and the “GList” bit in the header transferred to the INIT corresponding to the specification in the CDB. 4.
4.3 Format Commands 6. The number of defects reported by this command differs depending on the defect data format. − When data are in the “Block Address Format,” defect position information is not reported for portions which cannot be clearly accessed from the INIT. − When data are in the “Block Address Format” or the “Physical Sector Address Format,” even if defects exist in multiple locations within that sector, that defect information is reported by one defect descriptor.
Command Specifications 4.3.
4.4 Maintenance, Diagnostic Commands Table 4.105 READ DEFECT DATA command (B7): defect data configuration Bit Byte 7 6 5 4 0 0 0 0 PList GList 2 Reserved 3 Reserved 4 ~ 2 1 0 X‘00’ 1 Heade 3 Defect List Format Defect List Length (MSB) ~ ~ ~ : 7 Defect List Length (LSB) 8 Defect Descriptor List ~ ~ ~ ~ Defect Data n 4.4 Maintenance, Diagnostic Commands 4.4.
Command Specifications (1) Self-diagnosis test When the “SelfTest (self test)” bit is “1,” and “Self-Test Code” field is “000” in the CDB, this command specifies execution of the self-diagnosis test which the IDD is equipped to perform. At this time, the “PF (page format)” bit and the “Parameter list length” field in the CDB have no meaning and the values specified there are disregarded.
4.4 Maintenance, Diagnostic Commands Table 4.107 Error recovery control flags during the self-diagnosis test PER DTE Diagnostic test operation 0 0 The diagnostic test continues when error recovery is successful. The contents of recovered errors are not reported. When an error which cannot be recovered from is detected, the diagnostic test terminates at that point with an error. 0 1 – – – – – (Setting prohibited) – – – – 1 0 The diagnostic test continues when error recovery is successful.
Command Specifications (2) Parameter specification When “0” is specified in the “SelfTest (self test) bit in the CDB, the IDD executes the operations specified in the parameter list transferred from the INIT by this command. In this case, the IDD reports a GOOD status and terminates this command at the point when preparation of the “response data” is completed after completing the specified operations. The INIT can read the execution results (response data) by the RECEIVE DIAGNOSTIC RESULTS command.
4.4 Maintenance, Diagnostic Commands Table 4.108 SEND DIAGNOSTIC command: parameter list configuration Bit 7 Byte 6 5 4 0 2 1 0 0 0 0 Page Code 1 Header 3 0 0 0 0 0 2 Page Parameter Length (MSB) 3 Page Parameter Length (LSB) 4 Page ~ Parameter ~ ~ ~ Parameter ~ ~ n • Page code This field specifies the code which identifies the type of parameter page being transferred from the INIT and the operation that should be executed.
Command Specifications • Page parameter length This field specifies the byte length of the page parameter after byte 4. The INIT must specify the same value as the length specified for each of the parameter pages, which will be explained later. • Page parameter This field specifies each of the inherent parameters in each page code. Depending on the page code, this field may not be necessary (page parameter length = 0). a.
4.4 Maintenance, Diagnostic Commands Table 4.
Command Specifications REQUEST [=5] / Invalid field in parameter list [=26-00]) and address conversion is not executed. Details of the address conversion algorithm executed when this parameter page is specified and the data format, etc. of the conversion results reported to the INIT are explained in RECEIVE DIAGNOSTIC RESULTS command (Section 4.4.2).
4.4 Maintenance, Diagnostic Commands The Self-Test executes the following test segments in ascending order by number: 1. Buffer RAM test 2. Flash ROM test 3. Pre-SMART test 4. Low Level Format test 5. Random seek test 6. Sequential seek test 7. Data compare test 8. Random read test 9. Sequential read test 10. SMART test (4) ESI page When it is connected to SFF-8067 Enclosure via the SCA connector, it is possible that an ESI page code is sent out by using this command.
Command Specifications Table 4.114 ESI page Page Code (Hex) Function 01 reserve SES page 02 Enclosure Control 03 reserve SES page 04 Enclosure String Out 05 Enclosure Threshold Out 06 Enclosure Array Control 07 reserve SES page 08 reserve SES page 09-0F reserve SES page 80-8F Vender specific SES page Table 4.
4.4 Maintenance, Diagnostic Commands (5) Fault LED test page Table 4.116 Fault LED test page Bit Byte 7 6 5 4 3 2 0 X ‘A0’ (Page Code) 1 reserved 2 X ‘00’ (Page parameter length) 3 X ‘02’ (Page parameter length) 4 reserved 5 reserved 1 0 FLTLED This page is a page of the Fault LED test The value of that bit isn’t confirmed with firmware in reserved in the parameter and the written territory. (Taking usually “0” is recommended.
Command Specifications 4.4.2 RECEIVE DIAGNOSTIC RESULTS (1C) Bit Byte 7 6 5 4 0 3 2 1 0 X‘1C’ 1 0 0 0 0 0 0 0 PCV 2 0 0 0 0 0 0 0 0 0 0 0 3 Transfer Byte Length (MSB) 4 Transfer Byte Length (LSB) 5 0 0 0 0 0 This command transfers data (response data) which show the results of executing the SEND DIAGNOSTIC command from the IDD to the INIT.
4.4 Maintenance, Diagnostic Commands Table 4.117 lists the format of response data transferred to the INIT from the IDD by this command. The response data are configured from a 4-byte “Page header” and the “Page parameters” which follow it. Table 4.
Command Specifications (1) Page code list This response data reports the “Page code” list of the parameter page supported by the IDD in the SEND DIAGNOSTIC command and the RECEIVE DIAGNOSTIC RESULTS command after byte 4. The format and contents of this response data are shown in Table 4.118. Table 4.
4.4 Maintenance, Diagnostic Commands (2) Logical/physical address conversion This response data reports the execution results of address conversion specified in the “Logical/Physical Address Conversion” parameter in the SEND DIAGNOSTIC command in bytes after byte 4. The format and contents of this response data are shown in Table 4.119. Table 4.
Command Specifications The “Address Format Before Conversion” field in byte 4 and the “Address Format After Conversion” field in byte 5 are the same values as the codes which show the expression format for address information specified by the SEND DIAGNOSTIC command parameters. The “Address Format After Conversion” field shows the expression format of the address information reported in bytes 6 to 13 of this response data. “Address format” codes are as shown in Table 4.120. Table 4.
4.4 Maintenance, Diagnostic Commands Be sure to set up PCV in 1 when you transfer information on ESI. PCV works supposing that it is ignored and 00 is set up in the page code even if any page code is specified when 0 is set up. Information from Enclosure is transferred to INIT by specifying the above page code with CDB with the designation of PCV=1 by the following page format. Remark: The page code 0x09-0x0F is a reserve in the specification of SES/ESI.
Command Specifications 4.4.3 WRITE BUFFER (3B) Bit Byte 7 6 5 4 0 1 3 2 0 0 0 X‘3B’ 0 0 0 0 Mode 2 Buffer Address (MSB) 3 Buffer Address 4 Buffer Address 5 Buffer Address (LSB) 6 Transfer Byte Length (MSB) 7 Transfer Byte Length 8 Transfer Byte Length (LSB) 9 1 0 0 0 0 0 0 This command is used in combination with the READ BUFFER command to diagnose the normality of the IDD’s data buffer memory or the FC bus, or to download microcode to the IDD.
4.4 Maintenance, Diagnostic Commands Table 4.
Command Specifications Table 4.
4.4 Maintenance, Diagnostic Commands (3) Mode = 0, 0, 1, 0: Data only, with address specification In this mode, data transfer from the INIT includes buffer data only without the 4byte header being added. The top address of the data buffer where the data transferred from the INIT are to be stored can be specified in the “Buffer address” field. The “Transfer byte length” field in the CDB specifies the total number of bytes of data transferred by the INIT.
Command Specifications (5) Mode = 0, 1, 0, 1 : Microcode download, with saving In this mode, the controller’s microcode or control information is transferred to the IDD’s control memory area and written to the disk. “0” must be specified in the “Buffer ID” field and the “Buffer address” field. The "Transfer byte length" field specifies the total number of transfer bytes of data transferred from the INIT.
4.4 Maintenance, Diagnostic Commands During downloading of microcode, the supply of power to the drive must not be cut off (such as an instantaneous power failure). If a power failure occurs, for instance, while downloading the microcode to the FLASH-ROM, the IDD may be severely damaged. The worst-case scenario in this event would be an inoperable drive. In addition, any operation (e.g., command, link service, or reset) from the interface during that time is not recommended.
Command Specifications (7) Mode = 0, 1, 1, 1 : Microcode Download with offset, with saving In this mode the INIT may split the transfer of the controller's microcode or control information over two or more WRITE BUFFER commands. If the last WRITE BUFFER command of a set of one or more commands completes successfully, the microcode or control information shall be saved in a non-volatile memory space.
4.4 Maintenance, Diagnostic Commands 4.4.4 READ BUFFER (3C) Bit 7 Byte 6 5 4 0 3 2 1 0 0 0 X‘3C’ 1 0 0 0 0 Mode 2 X‘00’ (Buffer ID) 3 Buffer Offset (MSB) 4 Buffer Offset 5 Buffer Offset (LSB) 6 Transfer Byte Length (MSB) 7 Transfer Byte Length 8 Transfer Byte Length (LSB) 9 0 0 0 0 0 0 This command is used in combination with the WRITE BUFFER command to diagnose the normalcy of the IDD’s data buffer memory and the FC interface.
Command Specifications (1) Mode = 0, 0, 0, 0: Header + data, without address specification When this mode is specified, the data stored in the IDD’s data buffer are transferred to the INIT after the 4-byte header. Zero must be specified in the “Buffer offset” field in the CDB. The “Transfer byte count” field in the CDB specifies the total number of bytes of the header and buffer data which can be received by the INIT.
4.4 Maintenance, Diagnostic Commands (2) Mode = 0, 0, 0, 1: Header + data, with address specification The format of the data transferred to the INIT when this mode is specified is the same as the format of the data in the case of Mode = 0, 0, 0, 0, with the data stored in the IDD’s data buffer transferred to the INIT following the 4-byte header. In this mode, the address in the data buffer can be specified in the “Buffer offset” field in the CDB.
Command Specifications (4) Mode = 0, 0, 1, 1: Buffer descriptor When this mode is specified, the IDD transfers only the 4-byte buffer descriptor to the INIT. the IDD’s data buffer attributes are indicated in the 4-byte buffer descriptor. Zero must be specified in the “Buffer offset” field in the CDB when this mode is specified. The IDD transfers the data length specified in the “Transfer byte length” field in the CDB or 4 bytes, whichever portion of data is smaller, to the INIT.
4.4 Maintenance, Diagnostic Commands (6) Mode = 1, 0, 1, 1 : Echo buffer descriptor In this mode, a maximum of four bytes of READ BUFFER descriptor information is returned. The device server shall return the descriptor information for the echo buffer. The "Buffer Offset" field is reserved in this mode. The allocation length should be set to four or greater. The device server shall transfer the lesser of the allocation length or four bytes of READ BUFFER descriptor.
Command Specifications This command reads the logical data block data and its ECC byte, specified in the “Logical block address” field in the CDB, from the disk media and transfers it to the INIT. Normally, this command is used in combination with the WRITE LONG command to perform checks of the ECC function. The operation object in this command is 1 data block only. Remark The Pad Byte and Sync Byte patterns are not included in the transfer data.
4.4 Maintenance, Diagnostic Commands 4.4.
Command Specifications • Sense Key • Sense Code/Sub-sense Code : 24-00 = Invalid field in CDB • “VALID” Bit : “1” • “ILI” bit : “1” • Information Field: (“Transfer byte length in the CDB) – (Original “Transfer byte length”) : 05 = ILLEGAL REQUEST Remark: The calculation formula for the information field expresses 1 logical data block as n physical sectors and n sub-sectors, and when negative, as a complement of 2.
4.4 Maintenance, Diagnostic Commands A "PBdata" bit of one requests that the device server replace the first eight bytes of the data to be written to the current physical sector with the physical address of the sector currently being written using the physical sector format. The IDD is not supported a "PBdata" bit. Therefore, if "PBdata" bit is one, this command is terminated with CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CDB [=24-00]).
This page is intentionally left blank.
CHAPTER 5 Sense Data and Error Recovery Methods 5.1 Sense Data 5.2 INIT Error Recovery Methods (Recommended) 5.3 Disk Drive Error Recovery Processing In this chapter, the configuration and contents of sense data reported to the INIT (initiator) when an error occurs, etc., key information for interpreting error states, recommended procedures for error recovery processing that should be executed by software in the INIT and error recovery processing executed internally by the IDD are described. 5.
Sense Data and Error Recovery Methods 2) In the REQUEST SENSE command, even if a Transfer byte length that is shorter than the length of the sense data supported by the device which is the object of the command, the command will terminate normally, but in that case, some of the sense data only will be received and the remaining information will be lost. Sufficient caution should be exercised with regard to the devices connected to the INIT and all the sense data of those devices should be read. Table 5.
5.1 Sense Data 5.1.2 Sense data basic information Bytes 0 to 17 of the sense data are basic information which show the contents of the error that has occurred. The INIT can know the contents of the error and the key information that is necessary for recovery processing by analyzing this basic information. Each field and the meanings of bits in the sense data basic information are explained below.
Sense Data and Error Recovery Methods (6) Additional sense data length This field indicates the length (number of bytes) after byte 8 of the sense data. The value shown in this field shows the length of sense data provided by the IDD without relation to the value specified in the “Transfer byte length” in the CDB of the REQUEST SENSE command. The length of the IDD’s sense data is fixed at 48 bytes and this field always indicates X ‘28’ (40 bytes).
5.1 Sense Data Table 5.
Sense Data and Error Recovery Methods Table 5.3 Sense key Sense Key Name Explanation 0 NO SENSE The specific sense key does not exist. 1 RECOVERED ERROR 1) Indicates that the command which was executed last was terminated normally with a recovery operation by the IDD. If multiple errors which were successfully recovered from during processing of a single command occurred, the last error to have occurred is reported. 2) Rounding processing of the MODE SELECT parameter was performed.
5.1 Sense Data Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (1/6) Name Explanation Sense key C* Q* 00 00 No additional sense information No specific sense code exists. 0 01 00 No index/sector signal The target sector was not detected by the sector counter within the specified time. 4 03 00 Peripheral device write fault A write operation to the disk media was terminated abnormally.
Sense Data and Error Recovery Methods Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (2/6) Q* 11 00 Unrecovered Read Error Unrecovered read error occurs during reading data field (LBA Miscompare Error detected by SCSI portion) 01 Read retries exhausted Unrecovered error was detected during data read (retry out).
5.1 Sense Data Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (3/6) Q* 1C 01 Primary defect list not found The defect list (P List) header is incorrect. 3 02 Grown defect list not found The defect list (G List) header is incorrect. 3 90 SA information list not found The SA information (MODE SELECT parameter) header is incorrect.
Sense Data and Error Recovery Methods Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (4/6) Q* 31 00 Medium format corrupted The media format is different from the original format. (The media was not formatted after the data format specification was changed by the MODE SELECT command.) 3 01 FORMAT command failed For some reason, formatting cannot be completed and reformatting is necessary. 3 00 No defect spare location available No usable alternate block area exists.
5.1 Sense Data Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (5/6) C* Q* Name Explanation 44 nn Internal target failure An error was detected in self-diagnosis.
Sense Data and Error Recovery Methods Table 5.4 Additional Sense Code and Additional Sense Code Qualifier (6/6) C* Q* 4E 00 Name Overlapped commands attempted Sense key Explanation 1) Before execution of an untagged command was completed, the same INIT issued a new command to the same LUN. B 2) Before execution of a tagged command was completed, the same INIT issued a command to the same LUN with the same tag. Or, an untagged command was issued when not in the sense hold state.
5.1 Sense Data 5.1.3 Sense data additional information Bytes 18 to 47 of sense data are defined as a Fujitsu unique field, and indicate the additional information which is explained below. (1) PORT/LINKRATE PORT: Connected PORT is shown. 0: PORT-A 1: PORT-B LINK RATE: LINK RATE working at present is indicated. 111 It is working with 1.0625GHz. 110 It is working with 2.1250GHz.
Sense Data and Error Recovery Methods 5.2 INIT Error Recovery Methods (Recommended) When a single command or a series of linked commands are not terminated with a status reported, the INIT should execute error recovery processing corresponding to the state in which the command was terminated. Here, the procedure for analyzing the command execution termination state and recommended procedures for error recovery processing executed by the INIT in accordance with the results are explained. 5.2.
5.2 INIT Error Recovery Methods (Recommended) (1) TASK FULL status This status indicates that the IDD is currently executing processing of another command and that a new command cannot be received. The INIT that receives this status can reissue the original command. Under a multi-initiator environment, when an INIT receives this status, the time until the IDD can receive the next command depends on the operating state with other INITs, so ordinarily, it cannot be predicted.
Sense Data and Error Recovery Methods executed, or if there are other commands in the stack, execution of the command is caused to wait until all the other commands have been processed. The execution wait time is dependent upon the type of command issued by the other INITs and the contents of its specifications. • If the IDD has executed error recovery processing (retried) for an error that occurred on the FC bus or in the disk drive, command completion time will be longer than normal.
5.2 INIT Error Recovery Methods (Recommended) Table 5.5 Sense data error classification (1/3) L* Recovery Method (See Table 5.6.) No sense data showing the error contents are held. None 4 00 Sync byte not found for data field Need 8 15 xx Positioning error 17 xx Recovered data without ECC 18 xx Recovered data with error correction applied.
Sense Data and Error Recovery Methods Table 5.5 Sense data error classification (2/3) K* C* Q* Outline of Error 3 31 00 Medium form at corrupted 31 01 FORMAT command failed The data format on the disk media is not correct. L* Recovery Method (See Table 5.6.) Need 18 Need 7 None 19 Need 13 Need 20 Need 10 None 2 None 3 The data format on the disk media is not correct. 4 03 xx Peripheral device write fault This is an error of the disk drive’s write system.
5.2 INIT Error Recovery Methods (Recommended) Table 5.5 Sense data error classification (3/3) K* C* Q* 6 29 xx Outline of Error Power on, reset, or BUS DEVICE RESET occurred L* Recovery Method (See Table 5.6.) None 14 None 21 None 25 None 27 The IDD was initialized by a Power on, RESET condition or BUS DEVICE RESET message. 6 2A 01 Mode parameters changed The MODE SELECT parameters were changed by another INIT.
Sense Data and Error Recovery Methods Table 5.6 Error recovery processing procedures (1/4) Recovery Method Recovery Processing Procedure 0 It is not necessary to perform the error recovery processing. Continue processing. 1 Error recovery processing is impossible. Terminate processing. 2 This is a programming error and error recovery processing is impossible. Terminate processing and correct the error in the system (INIT) programming.
5.2 INIT Error Recovery Methods (Recommended) Table 5.6 Error recovery processing procedures (2/4) Recovery Method 9 Recovery Processing Procedure 1) Issue the MODE SENSE command and when a RECOVERED ERROR is reported, read the "Current" value in the changed MODE SELECT or MODE SELECT EXTENDED parameter. 2) If the value actually set in that parameter page is within the INIT's permissible range, perform recovery method 0.
Sense Data and Error Recovery Methods Table 5.6 Error recovery processing procedures (3/4) Recovery Method 13 Recovery Processing Procedure 1) Issue a TARGET RESET or Lip (y, x). 2) After waiting 2 seconds or longer, reissue the original command (Retry), and if the spindle motor's start mode is set on "Start by Command," issue the START instruction by the START/STOP UNIT command ("Immed" = 0) before retrying. 3) If the retry procedure 2) does not terminate normally, perform recovery method 1.
5.2 INIT Error Recovery Methods (Recommended) Table 5.6 Error recovery processing procedures (4/4) Recovery Method Recovery Processing Procedure 19 Initialize the entire disk media surface. It is desirable at this time to increase the number of spare sectors as much as possible. If this error occurs repeatedly, it is necessary to perform alternate block allocation processing through the system (shown in Chapter 5) or reconfirm the use conditions of the disk drive, such as the installation environment.
Sense Data and Error Recovery Methods 5.2.3 Error logging In order to collect information that is effective in maintenance, it is desirable for the INIT to accumulate (log) error information related to the FC interface which it has detected itself (Loop error, command completion wait time-out, etc.) and error information reported by the IDD.
5.3 Disk Drive Error Recovery Processing If the error cannot be recovered from even when retry processing is executed the specified number of times, the IDD terminates the command which is currently being executed with a CHECK CONDITION status. The sense key in the sense data at this time is "HARDWARE ERROR [=4]" and the sense code indicates "Mechanical positioning error [=15-01]" or "Positioning error detected by read of medium [=15-02].
Sense Data and Error Recovery Methods (4) Other internal IDD errors If an irrecoverable error other than those in items (1) to (3) above is detected internally in the IDD, the IDD terminates the command that is currently being executed with a CHECK CONDITION status. The sense key in the sense data at this time is "HARDWARE ERROR [=4]." 5.3.
5.3 Disk Drive Error Recovery Processing 2. When errors in the data area are recovered from by ECC correction processing, before implementing alternate block allocation processing, rewriting of the recovered data and a verify check (rereading) are performed. If data are recovered by rewriting, alternate block allocation of that data block is not performed.
Sense Data and Error Recovery Methods (3) Auto alternate block allocation processing during a write operation 2 (servo auto alternate) This function is enabled by specifying "1" in the AWRE flag in the MODE SELECT parameters. Furthermore, this function is applicable to the following commands only. • WRITE command • WRITE EXTENDED command • WRITE AND VERIFY When this function is permitted, if, during WRITE/WRITE EXTENDED command detects any Servo error (e.g.
5.3 Disk Drive Error Recovery Processing b. c. − AWRE (automatic write reallocation enabled) − ARRE (automatic read reallocation enabled) − TB (transfer block) − EER (enable early recovery) − PER (post error) − DTE (disable transfer on error) − DCR (disable correction) − Number of retries during read (See Table 5.7) − Number of retries during write (See Table 5.
This page is intentionally left blank.
CHAPTER 6 Disk Media Management 6.1 Defect Management 6.2 Disk Media Initialization 6.3 Data Block Verification Methods (Recommended) 6.4 Alternate Block Allocation Processing In this chapter, disk media defect management methods, treatment methods for media defects which occur during operation, reinitialization procedures and other disk media management methods are discussed.
Disk Media Management The P List and G List are recorded in the system space on the disk media. The INIT can read the contents of these lists by the READ DEFECT DATA command. (2) Alternate block allocation Alternate data blocks are allocated in defective sector units for defective data blocks (= sectors) on the disk media by the IDD's internal defect management methods. a. Spare sector area Spare sectors for allocation as alternate blocks are secured in one or both of the following areas.
6.1 Defect Management c. Alternate block allocation processing Alternate block allocation processing is implemented by the FORMAT UNIT command, REASSIGN BLOCKS command or "Auto Alternate Block Allocation Processing.
Disk Media Management 6.2 Disk Media Initialization 6.2.1 Initialization during installation The disk drive is initialized for the inherent (default) data format for each respective model name (model class) when it is shipped from the factory, so ordinarily, it is not necessary to initialized (format) the disk media when it is installed in a system.
6.2 Disk Media Initialization (2) Issuing the FORMAT UNIT command Issue the FORMAT UNIT command and initialize the entire disk media surface. In this FORMAT UNIT command, the entire disk media surface is initialized using the P List, then after initialization, the data blocks are verified. If any defective blocks are detected in the Verify operation, alternate blocks are allocated for those data blocks.
Disk Media Management (2) FORMAT UNIT command Issue the FORMAT UNIT command in either of the following two formats and initialize the entire disk media surface. a) Specify "1" in the "FmtData" bit, "0" in the "CmpLst" bit and "000" in the "Defect List Format" field. Also, prepare only a 4-byte header, specify "0" in the "FOV," "DPRY," "DCRT" and "STPF" bits and zero in the "Defect List Length" field.
6.3 Data Block Verification Methods (Recommended) 6.3 Data Block Verification Methods (Recommended) The recommended procedure for verifying from the INIT the normalcy of logical data blocks located on the disk media is as shown below. It is desirable for the INIT to verify the data blocks after initialization of the disk media is completed or when executing alternate block allocation processing by the REASSIGN BLOCKS command.
Disk Media Management (3) Reading and verification of data Issue the READ, READ EXTENDED or VERIFY command and verify that the data written to the disk media in item (2) were read correctly. To verify reading of data, it is recommended that reading of the same data block be done at lease 2 times, but the number of times verification is performed is determined by the conditions on the system. If reading of all data is completed normally, it can be recognized that use of that data block can be used normally.
6.4 Alternate Block Allocation Processing 3) If the REASSIGN BLOCKS command is terminated normally, verify that logical data block according to the procedure in Section 6.3. If that data block is judged to be correct, allocate an alternate block and terminate processing. When the data block is judged to be defective, return to 2) and issue the REASSIGN BLOCKS command again, then try reallocating another alternate block for that logical data block.
This page is intentionally left blank.
Glossary CDB Command Descriptor Block A series of data which describes commands related to input/output operations, sent from the initiator to the target. Command This is a command to a target to perform an input/output operation, and it is described as the CDB. Common Command Set (CCS) SCSI standard logical specifications established by a working group of the American National Standard Institute (ANSI). Requirements and features for supported direct-access devices (e.g.
Glossary Target (TARG) This is the FC device that executes the input/output operations initiated by the initiator (INIT). In this manual, target is abbreviated "TARG.
Acronyms and Abbreviations DTE Disable Transfer on Error A ACK AEN ALT ARRE ACKnowledge Asynchoronous Event Notification ALTernated (block) Automatic Read Reallocation Enabled ASCII American Standard Code for Information Interchange ASG ASiGned block ATN ATTeNtion AWG American Wire Gauge AWRE Automatic Write Reallocation Enabled E ECC EER EVPD F FC FG FIFO FmtData FOV FUA B bpi bits per inch BSY BuSY BytChk Byte Check Target Certification list Control/data Common command set Common descriptor block C
Acronyms and Abbreviations O OEM Original Equipment Manufacturer P P list Primary defect list P/N Parts/Number PBdata Physical Block data PC board Printed Circuit board PCA Printed Circuit Assembly PER Post ERror PF Page Format PLOSync Phase Lock Oscillator Syncronous PMI Partial Medium Indicator PR4ML Partial Response class 4 Maximum Likelihood SCSI SCT SEL SelfTest SG SP SPR SR SSEC STPF SURF T TB TPI TRM Read Continuous Read Cache Disable Request Relative Humidity ReMovaBle ReSeT ReSerVed Transfer
Index +port A_in ............................................... 1-22 +port A_out ............................................. 1-22 +port B_in ............................................... 1-22 +port B_out ............................................. 1-22 10-Byte CDB basic format........................ 2-2 12-Byte CDB basic format........................ 2-3 6-Byte CDB basic format.......................... 2-2 A abort sequence ......................................... 1-35 ABORT TASK SET ............
Index BC..............................................................1-4 bit 0............................................................2-6 bit 1............................................................2-5 bit 2............................................................2-5 bit 3............................................................2-5 bit 4............................................................2-5 bit 5............................................................2-5 bit 6...................
Index CONTROL_MCM .................................. 4-66 correctable bit length......................4-28, 4-46 correctable data read error....................... 5-25 correction of defect descriptor .............. 4-162 count basis ............................................... 4-98 cylinder count.......................................... 4-44 cylinder skew factor ................................ 4-41 D D list ................................... 4-149, 4-154, 6-1 D(3) to D(0).............................
Index disk drive error and number of retry .......5-29 disk drive error recovery processing .......5-24 disk media initialization ............................6-4 disk media management ............................6-1 DLM ........................................................4-65 Dlmm .......................................................4-37 DPOFUA bit ............................................4-76 DPRY.....................................................4-152 DQue.......................................
Index example of data buffer operation during write .......................................... 3-5 example of establishing logical connection .......................................... 2-12 example of exchange............................... 1-14 example of FC-AL connection.................. 1-2 expanded sense data format ...................... 5-2 extended link data specification.............. 1-38 extended link service......................1-38, 1-75 EXTENDED LINK SERVICE................
Index header field of basic link service.............1-34 header field of extended link service.......1-38 header field of FCP CMND.....................1-80 header field of FCP DATA......................1-89 header field of FCP DATA RDY ............1-87 header field of FCP RSP..........................1-92 HSEC .......................................................4-41 I IC ............................................................4-49 ILI ..............................................................
Index M maintenance command.......................... 4-169 mated ....................................................... 1-18 maximum burst size ................................ 4-36 maximum number of notch ..................... 4-58 maximum pre-fetch ................................. 4-50 maximum pre-fetch control block count................................................... 4-51 MCM time out value ............................... 4-67 MCM_TOV .............................................
Index overlapping command .............................2-21 P P list .................................... 4-149, 4-164, 6-1 page code ......................4-3, 4-23, 4-92, 4-95, 4-173, 4-181 page code = 0A........................................4-53 page code = 0C ........................................4-57 page code = 1...........................................4-25 page code = 19.........................................4-63 page code = 1C ........................................4-59 page code = 2.......
Index primitive sequence .................................... 1-7 primitive signal.......................................... 1-7 PRLI ........................................................ 1-50 PRLI_ACC .............................................. 1-50 PRLO..............................................1-55, 1-56 PRLO_ACC....................................1-55, 1-56 process for selecting loop master ............ 1-27 process login............................................ 1-50 process logout..........
Index report log exception condition.................4-54 REPORT LUN command........................2-21 REPORT LUNS (A0) ............................4-130 REPORT LUNS parameter list .............4-131 REQUEST SENSE (03) ..........................4-87 REQUEST SENSE command ........2-20, 2-24 require hard address.................................4-65 RESERVATION CONFLICT status............................................2-7, 5-15 RESERVE EXTENDED (56).................4-85 RESERVE (16).........................
Index service parameter response page............. 1-53 SES sense code...................................... 1-104 SET DEVICE IDENTIFIER (A4)......... 4-134 SET DEVICE IDENTIFIER parameter list.................................... 4-135 SET LIMITS (33).................................. 4-144 SET LIMITS command......................... 4-145 setting parameter by MODE SELECT command .............................. 6-7 SFF8045 .................................................. 1-99 SFF8067 ......................
Index total verify error posted .........................4-107 total write byte processed ......................4-101 total write error posted ..........................4-100 TPRLO.....................................................1-64 TPRLO_ACC ..........................................1-64 track count/zone.......................................4-39 track skew factor......................................4-41 transfer block ...........................................4-27 transfer block count .............
Comments concerning this manual can be directed to one of the following addresses: FUJITSU LIMITED Storage Products Group 4-1-1 Kamikodanaka, Nakahara-ku, Kawasaki, 211-8588, Japan TEL: 81-44-754-2130 FAX: 81-44-754-8346 FUJITSU COMPUTER PRODUCTS OF AMERICA, INC. 2904 Orchard Parkway, San Jose, California 95134-2009, U.S.A. TEL: 1-408-432-6333 FAX: 1-408-894-1709 FUJITSU CANADA INC. 2800 Matheson Blvd.
This page is intentionally left blank.
READER’S COMMENT FORM Your comments or suggestions on this document are cordially solicited. For any comments and suggestions you may have, please complete and submit this form to your FUJITSU representative. The comments and suggestions will be used in planning future editions. Thank you for your cooperation.
This page is intentionally left blank.
MAT3073FC, MAT3147FC, MAT3300FC SERIES MAU3036FC, MAU3073FC, MAU3147FC SERIES DISK DRIVES FIBRE CHANNEL INTERFACE SPECIFICATIONS C141-C008-01EN MAT3073FC, MAT3147FC, MAT3300FC SERIES MAU3036FC, MAU3073FC, MAU3147FC SERIES DISK DRIVES FIBRE CHANNEL INTERFACE SPECIFICATIONS C141-C008-01EN
This page is intentionally left blank.
