Fibre Channel Interface
Fibre Channel Interface
©1997–2004, Seagate Technology LLC All rights reserved Publication number: 77767496, Rev. D February 2004 Seagate and Seagate Technology are registered trademarks of Seagate Technology LLC. SeaTools, SeaFONE, SeaBOARD, SeaTDD, and the Wave logo are either registered trademarks or trademarks of Seagate Technology LLC. Other product names are registered trademarks or trademarks of their owners. Seagate reserves the right to change, without notice, product offerings or specifications.
Revision status summary sheet Revision Date Sheets Affected Sheets Affected A B C 03/21/1997 08/01/2000 01/03/2003 L. Newman/J. Coomes and W. Whittington L. Newman/J. Coomes L. Newman D 02/05/2004 K. Schweiss/J. Coomes and W. Paulsen All All No change except for new Seagate logo. Document migration/conversion only.
Contents 1.0 Publication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 General interface description. . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 6.4 Exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Credit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.0 Classes of service (FC-2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Class 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.4.2 ESI write transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enclosure-initiated ESI transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5.1 EIE Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5.2 EIE operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.5.
12.11 12.12 12.13 12.14 12.15 12.16 12.17 12.18 12.19 12.20 12.21 12.22 12.23 12.24 12.25 12.26 12.27 12.28 12.29 12.30 12.31 12.32 12.33 12.34 12.35 12.36 12.37 12.38 12.39 viii 12.10.1 Error Counter pages, Write, Read, Read Reverse, and Verify (code 02, 03, 04, and 05h) 196 12.10.2 Non-Medium Error page (code 06h). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 12.10.3 Temperature page (code 0Dh) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.40 Reserve (10) command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.40.1 Logical unit reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.40.2 Third-party reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.40.3 Superseding reservations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.40.
13.2.3.2 13.2.3.3 14.0 Background mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 Elements common to foreground and background self-test modes . . 357 Seagate Technology support services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Figure 10. Figure 11. Figure 12. Figure 13. Figure 14. Figure 15. Figure 16. Figure 17. Figure 18. Figure 19. Figure 20. Fibre Channel standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Arbitrated loop topology (dual port private loop) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii Fibre Channel Interface Manual, Rev.
1.0 Publication overview This publication provides some general information about Fibre Channel as well as detailed information about how Seagate disc drives implement Fibre Channel Arbitrated Loop technology. This publication will continue to be revised as Fibre Channel technology advances and as Seagate Fibre Channel drives change to meet data storage needs. You will observe that many references are made to SCSI throughout this publication. This is because Fibre Channel transports the SCSI command set.
1.3 General interface description This manual describes the Seagate Technology LLC Fibre Channel/SCSI (Small Computer Systems Interface) as implemented on Seagate Fibre Channel (FC) disc drives. The disc drives covered by this manual are classified as intelligent peripherals.
2.0 Introduction to Fibre Channel Fibre Channel is an American National Standards Institute (ANSI) interface that acts as a general transport vehicle to simultaneously deliver the command sets of several existing interface protocols including SCSI-3, IPI-3, HIPPI-FP, IP, and ATM/AAL5. Proprietary and other command sets may also use and share the Fibre Channel, but these are not yet defined as part of the Fibre Channel standard.
Networks Networks allow many devices to communicate with each other at will. This is usually accompanied by software support to route transactions to the correct provider and to verify access permission. Networks are used for transferring data with “error-free delivery” and voice and video where “delivery on time” is the primary requirement with error-free delivery being a secondary consideration.
3.0 Fibre Channel standards Figure 1 shows the various documents involved in the ANSI set of standards relating to Fibre Channel. This model is not static—it is growing as others areas of interest are developed.
Copies of ANSI documents relating to Fibre Channel can be purchased from: Global Engineering 15 Inverness Way East Englewood, CO 80112-5704 (800) 854-7179 or (303) 792-2181 Fax: (303) 792-2192 3.1 General information The FC-PH standard is the foundation upon which all others are based. Each topology, command set, and protocol has its own standard. These are all separate to allow future growth and to allow designers to more easily use only those parts that affect their products.
3.1.1.6 FC-4 FC-4 defines the interface mapping between the lower levels of the Fibre Channel and the various command sets. These various command sets are known as upper layer protocols (ULPs). Examples of upper layer protocols include SCSI, IPI, HIPPI, and IP. 3.1.2 Relationship between the levels FC-0, FC-1, and FC-2 are integrated into the FC-PH document. The other documents are separate so that each implementation may use the technology best suited to the environment in which it will be used. 3.1.
8 Fibre Channel Interface Manual, Rev.
4.0 Introduction to topologies Topologies include all the elements necessary to successfully connect two or more nodes (also known as devices). See Section 4.1. There are several topologies available with Fibre Channel, but all of them have certain common components: nodes, ports, and links. These components are discussed in this section. The ANSI Fibre Channel standard defines three topologies: 1. Arbitrated loop (Fibre Channel Arbitrated Loop, FC-AL) 2. Fabric 3.
As stated above, ports used in a FC-AL topology are called node loop ports (NL_Ports). Other port types exist as documented in the following table.
The arbitrated loop topology is used to connect from two to 126 node ports. See Figure 2. NL_Port 6 (Fibre A) NL_Port 1 (Fibre A) NL_Port 6 (Fibre B) NL_Port 1 (Fibre B) NL_Port 5 (Fibre A) NL_Port 2 (Fibre A) NL_Port 5 (Fibre B) NL_Port 2 (Fibre B) NL_Port 4 (Fibre A) NL_Port 3 (Fibre A) NL_Port 4 (Fibre B) NL_Port 3 (Fibre B) Node A Node B Node F Node C Node E Figure 2.
Port Bypass Circuit From Previous Drive Port Bypass Circuit N–1 To Next Drive MUX Port Bypass Circuit N+1 Select Drive N–1 Serial In Serial Out Drive N+1 Drive N Figure 3. 12 Port bypass circuit physical interconnect Fibre Channel Interface Manual, Rev.
5.0 Data encoding (FC-1) Fibre Channel devices don’t transmit 8-bit bytes. If this were to occur, the receiving node would not understand the transmitter’s intentions. To fix this situation, the data is encoded prior to transmission. Encoding allows the creation of special transmission code characters with unique bit patterns for data management and word alignment so the receiving node will know what to do with the bytes.
• If the number of ones and zeros in a sub-block are equal, running disparity is neutral and the value of running disparity at the end of the sub-block remains the same as the preceding character even if it is separated by neutral characters. Note. The rules of running disparity prohibit consecutive positive or consecutive negative characters even if they are separated by neutral disparity characters.
5.3 Data hierarchy A hierarchy of data types is presented in Figure 6. Transmission word (40 bits — 4 10-bit encoded bytes) 8B/10B encoded byte 1 (10 bits) 8B/10B encoded byte 4 (10 bits) Byte (8 bits) Bit Bit Bit Bit Bit Bit Figure 6. FC data hierarchy 5.3.
Table 3: Primitive signals Primitive signal Signal Beginning running disparity Idle IDLE Negative K28.5 D21.4 D21.5 D21.5 BC 95 B5 B5 Receiver_Ready R_RDY Negative K28.5 D21.4 D10.2 D10.2 BC 95 4A 4A Ordered set (FC-1) Ordered set (hex) Idle (IDLE) An Idle is transmitted on the loop to indicate the node is operational and ready for frame transmission and reception. Idles are transmitted when frames, R_RDY, or primitive sequences are not being transmitted.
Seagate disc drives use only those listed in bold type (Seagate Fibre Channel disc drives are Class 3 devices and use only Class 3 delimiters). Table 4: Frame delimiters Delimiter function Delimiter Beginning running disparity SOF Connect Class 1 SOFc1 Negative K28.5 D21.5 D23.0 D23.0 BC B5 17 17 SOF Initiate Class 1 SOFi1 Negative K28.5 D21.5 D23.2 D23.2 BC B5 57 57 SOF Normal Class 1 SOFn1 Negative K28.5 D21.5 D23.1 D23.1 BC B5 37 37 SOF Initiate Class 2 SOFi2 Negative K28.5 D21.
Start-of-frame Initiate Class 3 (SOFi3) SOFi3 indicates the beginning of the first frame of a sequence of frames (an exchange). (This includes all single frame sequences, commands, link services, transfer readys, and response frames.) SOFi3 is also used in the first data frame of a sequence. Start-of-frame Normal Class 3 (SOFn3) SOFn3 indicates the beginning of any frame other than the first frame of an exchange (see SOFi3 above).
Open full-duplex (OPNyx) After successful arbitration, the transmitting port (x) opens the receiving port (y) for control and data frame transmission and reception. Any FC port can transmit or receive an OPN. Open half-duplex (OPNyy) After successful arbitration, the initiator opens the target (y) for control and data frame transmission and reception of control frames. Data frame transmission from the target is not allowed.
Table 6: Primitive sequences Primitive sequences Sequence Beginning running disparity Offline OLS Negative K28.5 D21.1 D10.4 D21.2 BC 35 8A 55 Not_Operational NOS Negative K28.5 D21.2 D31.5 D5.2 BC 55 BF 45 Link_Reset LR Negative K28.5 D9.2 D31.5 D9.2 BC 49 BF 49 Link_Reset_Response LRR Negative K28.5 D21.1 D31.5 D9.
Note. There are six sequences that invoke loop initialization. There is no operational difference between them except that bytes 3 and 4 identify the reason for the loop initialization. Loop initialization, no valid AL_PA (LIP) The L_Port is attempting to acquire an AL_PA. Loop initialization, loop failure, no valid AL_PA (LIP) The transmitting L_Port detects a loop failure at its receiver. Since it has not completed initialization, it uses ‘F7’ (D23.7) rather than a valid AL_PA.
22 Fibre Channel Interface Manual, Rev.
6.0 Framing protocol (FC-2) The entire responsibility of moving frames between N_Ports is assigned to the Fibre Channel layer called the framing protocol (FC-2). This protocol is primarily concerned with constructing and managing frames, sequences, and exchanges. Navigation assistance The field descriptions that are provided for most tables have sidebar labels which identify the table they are associated with. This helps orient you when nested tables occur within a section.
All frames also have a header and a Cyclic Redundancy Check (CRC) field. The payload data field is optional (but normally present) with the size and contents determined by the type of frame. Bytes Fill Words Transmission Words 4 24 0 to 2112 SOF Frame Header Payload Data Field 1 6 0 to 528 Figure 8. Frame structure 6.1.1.1 Start-of-frame (SOF) delimiter 4 Fill Bytes CRC 1 4 24 Fill EOF Words 1 6 Start-of-frame (SOF) delimiters signal the beginning of a frame.
8 F_CTL (Frame Control) This 3-byte (24-bit) field contains control information relating to the frame content as defined below. Table 9: 8 Frame Control (F_CTL) bit definitions Bit Definition Description 23 Exchange context 0 = Frame is from the exchange originator. 1 = Frame is from the exchange responder. 22 Sequence context 0 = Initiator 1 = Recipient 21 First sequence 0 = Not the first sequence of the exchange. 1 = First sequence of the exchange.
8 OX_ID (Originator Exchange Identifier) This 2-byte field is assigned by the originator of an exchange. For SCSI FCP frames, this value is analogous to the Queue Tag used in Parallel SCSI and must be unique for an initiator/drive pair. 8 R_CTL (Routing Control) This one-byte field provides routing bits and information bits to categorize the frame function.
Table 10: Routing Control values (Continued) High order bits 1000 8 Low order bits Use 0000 No operation Not supported 0001 Abort sequence (ABTS) Request 0010 Remove connection Not supported 0011 Reserved Not supported 0100 Basic_Accept (BA_ACC) Reply 0101 Basic_Reject (BA_RJT) Reply 01100111 Reserved Not supported RX_ID (Responder Exchange Identifier) This 2-byte identifier is a unique identifier generated by the responder for an exchange established by an originator and identif
6.1.1.3 Data field (payload) The data field, also known as the payload, is aligned on word boundaries. The payload length must be an integer multiple of four bytes and is limited to 2,112 bytes. If the data field is not an integer multiple of four bytes, valid fill bytes are inserted to meet the requirement. F_CTL bits 0 and 1 indicate how many fill bytes are used. Fill bytes are only permitted in the last frame of a sequence. These fill bytes can be any valid byte value.
These two independent fields (OX_ID and RX_ID) allow each N_Port to identify the resources needed to manage a frame or sequence as it arrives. Each N_Port involved with the exchange can use a link service request to view the contents of the control information in the other port in the exchange; however, no other N_Ports are allowed to request information for the exchange since they are not involved with that particular exchange.
the source N_Port. This type of credit is not used in Class 3 therefore it is not applicable to Seagate drives. 30 Fibre Channel Interface Manual, Rev.
7.0 Classes of service (FC-2) There are five classes of service currently available or being defined. Classes of service are simply different communication methods used between nodes. Seagate drives use only Class 3; however, brief explanations of the other classes are provided as well. 7.1 Class 1 Class 1 is like a direct face-to-face meeting with no interruptions or delays. It is a dedicated full-bandwidth connection between two nodes.
• EE_Credit not required • Busy and Reject not needed due to alternate credit model • Errors are recovered at the exchange level 7.3.1 Class 3 flow control Class 3 flow control is a simple model which does not require EE_Credits. With Class 3, there is only buffer-tobuffer flow control in one direction and there are no link level responses to Class 3 frames. 7.4 Classes 4 and 5 Classes 4 and 5 are being defined by Fibre Channel committees to aid audio and video applications.
8.0 FC Arbitrated Loop concepts This section describes some basic Fibre Channel Arbitrated Loop (FC-AL) concepts. Seagate disc drives support FC-AL as the topology for connectivity in Fibre Channel environments. Fibre Channel is a serial data channel that provides logical point-to-point service to two communicating devices. With FC-AL, you can have a maximum of one point-to-point circuit at any one time.
Table 12: 8B/10B characters with neutral disparity D xx.
Table 13: AL_PA addressing Values (hex) 00 Use Reserved for the FL_Port (if present) 01-EF Contains 127 valid addresses F0 Reserved for fairness F1-F6 These values do not have neutral running disparity F7-F8 Reserved for loop initialization FB, FD, and FE Reserved for future use FF Reserved to address all ports in broadcast mode In the parallel SCSI world, the higher the bus address, the higher the priority the device has. The opposite is true with FC-AL. See Table 14.
A buffer on the drive receives each of the following loop initialization frames: LISM, LIFA, LIPA, LIHA, LISA, LIRP, and LILP. All other frames may be discarded if the L_Port’s buffer is full. If the NL_Ports finds that there are not any more NL_Ports attached, but that there is only an F_Port or N_Port attached, the NL_Port configures itself to operate as an N_Port by going into N_Port mode. An L_Port begins the loop initialization procedure in the initializing state at the request of the node.
The loop initialization process begins when any NL_Port forces the loop into the INITIALIZING state. See Figure 11. This initializing port begins transmitting loop initialization primitive sequences (LIPs). Any NL_Port can cause this by sending any of the LIPS listed in Table 15. All LIPs cause the 4-step initialization process to occur. A loss of signal will also force the loop to initialize.
Loop Initialization Select Master (LISM) 12-byte payload 11010000 8-byte port name The loop master is determined as follows: • Each NL_Port selects an initial AL_PA of ‘EF’. The FL_Port (if present) selects an AL_PA of ‘0’. • Each port transmits LISM with the D_ID and S_ID fields of the header set to its AL_PA. The payload is set to the port name which includes the world wide name (WWN). • Each port examines the payload in the inbound LISM.
Loop Initialization Previously Assigned (LIPA) 20-byte payload 11030000 16-byte bit map of AL_PAs The loop master transmits the bit map resulting from the LIFA. The L_Port checks to see if the bit that corresponds to its previously acquired AL_PA is set. If not, the L_Port sets it to ‘1’. If the L_Port’s bit has already been set by another port, it will attempt to assume a soft-assigned AL_PA (LISA).
Loop Initialization Soft Assigned (LISA) 20-byte payload 11050100 16-byte bit map of AL_PAs The loop master transmits the bit map resulting from the LIHA. The L_Port checks to see if there are any free addresses left in the bit map by checking for the first available ‘0’. The L_Port sets it to ‘1’. If there are no zeroes in the bit map, all 126 NL_Port addresses have been taken and the port is not allowed to actively participate in the loop.
Loop Initialization Loop Position (LILP) 132-byte payload 11070000 128-byte map of AL_PA physical positions When the loop master gets the LIRP frame back from the loop, it contains the AL_PAs and physical location of each participating port on the loop. The loop master retransmits the completed position map (now called the LILP) to the next port on the loop.
- lower than the Port_Name in the payload, the NL_Port transmits a LISM loop initialization sequence with the payload containing its Port_Name. - higher than the Port_name in the payload, the NL_Port retransmits the received Loop Initialization Sequence. Each L_Port continues with steps 2a through 2d. c. If the L_Port receives an ARB(F0), it continues at step 4. d. If it receives anything else, the value is discarded and the port continues with steps 2a to 2d. 3.
LISA The L_Port primes the AL_PA bit map with the AL_PA bit map of the previous LIHA loop initialization sequence. The L_Port sets the first available bit to 1 (unless a bit was set in LIFA, LIPA, or LIHA) which corresponds to its soft assigned AL_PA. If a bit was available, the L_Port adjusts its AL_PA according to which bit it set. If no bits are available, the L_Port remains in the nonparticipating mode; the L_Port may attempt to re-initialize at the request of the node.
reinitialize at 10.3 at the request of the node. If the L_Port does not support the AL_PA position mapping loop initialization sequences, it sets byte 2 of the loop initialization identifier to 00h. The L_Port retransmits the loop initialization sequence. LIRP If LIRP is received, the L_Port reads the left-most byte (offset), increment it by one, store the offset, and store its AL_PA into the offset position. The L_Port retransmits the loop initialization sequence.
8.2.
8.2.2 Loop reinitialization Loop reinitialization occurs when an L_Port is added to the loop, removed from the loop, or for error recovery.
replaced, that port has won arbitration of the loop and is free to open the loop between its receiver and transmitter and is also free to stop retransmitting received transmission words. This means the NL_Port is no longer in repeat mode and all words transmitted on its outbound fiber are generated by the NL_Port.
When a fair NL_Port has arbitrated for and won access to the loop and does detect that another L_Port is arbitrating, the NL_Port closes the loop at the earliest possible time and arbitrates again in the next access window before opening a different L_Port. 8.3.2 Access unfairness Some loops may require that certain NL_Ports have more access to the loop than just one access per access window. Examples of this situation include an NL_Port for a subsystem controller or file server.
8.4.2 Blocking switch emulation When two NL_Ports open communication with each other (see the OPNyx discussion in Section 8.3), communication between other devices is effectively blocked (other than to retransmit frames or insert fill words). This is known as a blocking environment since the two communicating ports block operation between any other L_Ports. 8.4.3 Non-meshed environment FC-AL is called a non-meshed environment due to the fact that there is only one route to any other port.
8.4.4 Assigned AL_PA values All AL_PAs that are used in the loop protocol are listed in table 12. The AL_PAs are assigned to the 16-byte AL_PA bit maps of table 16 as shown in table 17.
9.0 Fibre Channel link services Link service frames are used to perform functions at the Fibre Channel layer. They are used to establish the operating parameters, perform channel level error recovery, and check the status of the physical link between two devices. Link service frames are divided into two groups, Basic and Extended. Navigation assistance The field descriptions that are provided for most tables have sidebar labels which identify the table they are associated with.
9.1 Basic link services The drive supports the Abort Sequence (ABTS) and two basic services replies, Basic Accept (BA_ACC) and Basic Reject (BA_RJT). All other basic link services are discarded by the drive. Basic link service functions are identified by the R_CTL field of the header.
18 DF_CTL (Data Field Control) Set to 00h to indicate no optional Fibre Channel headers are used. 18 F_CTL (Frame Control) Set to 090000h for the ABTS. This indicates the ABTS is from the originator of the exchange, this is the last frame of the sequence, and sequence initiative is transferred for the drive to send the reply back. For the reply frames, the drive sets the F_CTL to 990000h.
9.1.2 Basic Accept (BA_ACC) BA_ACC is sent by the drive in response to all correctly structured ABTS. If the ABTS identifies an exchange in execution or buffered for execution, the drive will discard the exchange. The R_CTL is 84h.
9.1.3 Basic Reject (BA_RJT) BA_RJT is sent by the drive in response to an ABTS with a RX_ID not set to FFFFh. The R_CTL is 85h. Table 20: BA_RJT Payload Bit Byte Table number 20 Reserved 1 Reason Code 2 Reason Explanation 3 Vendor Unique 5 4 3 2 1 0 Field definitions (listed alphabetically) Reason Code (Logical Error) is the only Reason code sent by the drive if the RX_ID sent with the ABTS is not FFFFh. Reason Explanation 03h 20 6 0 03h 20 7 No Additional Explanation.
9.2 Extended link services The type of extended link service is identified by the LS Command Code in the first word of the payload. The R_CTL field of the frame header identifies whether the extended link service is a request or a reply to a request. The accept for extended link services varies with the function. A description of the accept for each request is included with the description of the request.
Table number 21 Field definitions (listed alphabetically) D_ID (Destination Identifier) Frame destination address. 21 DF_CTL (Data Field Control) Set to 00 to indicate no optional Fibre Channel headers are used. 21 F_CTL (Frame Control) Set to 290000h for extended link service requests. This indicates the frame is from the originator of the exchange, this is the last frame of the sequence, and sequence initiative is transferred for the responder to send the reply back.
9.2.1 Port Login (PLOGI) (02x) Port Login (PLOGI) is sent by the initiator to a drive to establish the Fibre Channel operating parameters. The PLOGI causes any open exchanges (commands) the initiator may have queued in the drive to be discarded.
Table 23: Port/Node Name format Bit Byte 7 6 5 4 3 0 0 0 1 0 (MSB Network Address ID 2 (LSB) (MSB) 3 Company Identifier Assigned by IEEE 4 5 (LSB) (MSB) 6 Unique Drive Identifier Assigned by Seagate 7 23 0 N_Port Identifier 1 2 1 (LSB) Company Identifier Assigned by IEEE This Seagate-unique value is registered with the IEEE. 23 N_Port Identifier Used by the drive to identify the name of a specific port or node.
Table 24: Bit Byte N_Port Common Service Parameters 7 6 5 0 Highest ANSI FC-PH Version 1 Lowest ANSI FC-PH Version 2 4 3 2 1 0 (MSB) Buffer to Buffer Credit 3 4 (LSB) Contin Increasing Offset Random Relative Offset Valid Vendor Version F_Port Alternate Credit Model E_D_TOV Resolution 0 Reserved 0 Reserved Dynamic Half Duplex Continuous Increase SEQ_CNT Payload Length Common Features 5 0 0 0 0 0 0 (MSB) Reserved 6 0 0 0 Reserved Receive Data Field Size 7 8 (LSB) Reser
24 Common Features This is a bit significant field which requests options that are used in all classes of service by initiator login. Below is a list of the features and the drive requirements. The drive returns an LS_RJT to PLOGI requests that do not satisfy the requirements. Table 25: 24 Common Features bits Feature Drive requirement Continuously Increasing Offset Must be a one (1). Random Relative Offset Not checked. Port Login Accept returns a value of zero (0). Not supported.
Table 26: Class Service Parameters Bit Byte 7 6 0 Class Valid Intermix Mode 5 4 Stacked Connect Request 3 2 1 0 Sequence Delivery 0 Reserved 0 Reserved 0 Reserved ACK_N Capable 0 Reserved 0 Reserved Service Options 1 2 Reserved Initial Process Associator X_ID Reassignment ACK_0 Capable Initiator Control 3 Reserved 4 ACK_0 Capable ACK_N Capable X_ID Interlock 0 Reserved Error Policy Categories per Sequence Recipient Control 5 6 Reserved 0 0 0 0 (MSB) Reserved Receive
26 Initiator Control The transmit capabilities of the initiator in the PLOGI. The drive returns an LS_RJT to PLOGI requests that do not satisfy the drive’s requirements. The Initiator Control bits in the PLOGI ACC indicate the capabilities of the drive. The drive returns zero (0) for all bits that are not applicable for class 3 services and for all reserved bits. Table 27: 26 Initiator Control fields Option Drive requirement X_ID (Exchange Identifier) Reassignment Not applicable.
Table 28: 26 Recipient Control fields Option Drive requirement Categories per Sequence The drive does not check the Categories per Sequence bits in the PLOGI. The drive originates only one category per sequence. The drive returns 00 in the PLOGI ACC to indicate it only supports receiving one category per sequence. Service Options These bits are only checked for class 3 service parameters. The drive returns an LS_RJT to PLOGI requests that do not satisfy the drive’s requirement.
Table 30: Port Login Accept Payload (PLOGI ACC) Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 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 LS Command Code 4-19 N_Port Common Service Parameters 20-27 Port Name 28-35 Node Name 36-51 Class 1 Service Parameters 52-67 Class 2 Service Parameters 68-83 Class 3 Service Parameters 84-99 Reserved 100-115 Table number 30 Vendor Version Field definitions (listed alphabetically) Class 1 and 2 Service P
9.2.2 Port Logout (PLOGO) (03x) Port Logout (PLOGO) is sent by the target in response to any frame from an initiator that has not completed N_Port Login. PLOGO may also be sent by an initiator when it has no further need for a target.
9.2.3 Fabric Login (FLOGI) (04) Fabric Login (FLOGI) is sent by the drive to the fabric to establish the Fibre Channel operating parameters in a public loop environment. When the drive sends FLOGI, any open exchanges (commands) queued in the drive are discarded.
Table 34: Bit Byte F_Port Common Service Parameters 7 6 5 0 Highest ANSI FC-PH Version 1 Lowest ANSI FC-PH Version 2 4 3 2 1 0 (MSB) Buffer to Buffer Credit 3 4 (LSB) Contin Increasing Offset Random Relative Offset Valid Vendor Version F_Port Alternate Credit Model E_D_TOV Resolution Multicast Broadcast Dynamic Half Duplex Continuous Increase SEQ_CNT Payload Length Common Features 5 6 Hunt Groups Dedicated Simplex 0 0 0 0 0 0 Reserved 0 (MSB) Reserved Receive Data Fie
34 Common Features This is a bit significant field which indicates the options that are supported by the drive. Below is a list of the features. The drive returns an LS_RJT to FLOGI ACC for requests that do not satisfy the drive’s requirements.
Table 36: Class 3 Service Parameters Bit Byte 7 6 0 Class Valid Intermix Mode 5 4 Stacked Connect Request 3 2 1 0 Sequence Delivery Dedicated Simplex Camp-on Buffered Class 1 0 0 0 Service Options 1 0 0 0 0 Priority Reserved 2 3 4 5 6 7 8 Reserved 9 10 11 12 13 14 15 Table number 36 Field definitions (listed alphabetically) Service Options The following class 3 service parameters are sent by the drive.
Table 38: Fabric Login Accept Payload (FLOGI ACC) Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 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 LS Command Code 4-19 F_Port Common Service Parameters 20-27 Port Name 28-35 Node Name 36-51 Class 1 Service Parameters 52-67 Class 2 Service Parameters 68-83 Class 3 Service Parameters 84-99 Reserved 100-115 Table number 38 Vendor Version Field definitions (listed alphabetically) Class 1 and 2 Service
9.2.4 Process Login (PRLI) Process Login (PRLI) is sent by the initiator to a target to establish the SCSI FCP operating features.
39 Data Overlay Allow Not supported by the drive. The Data Overlay Allowed bit is not checked. 39 Data/Response Mix Allowed 1 39 39 Allows the drive to send the FCP RSP in the same sequence as the data. The drive does not support the Data/ Response Mix. It will accept a PRLI with the Allow bit set, but will return zero (0) in the accept to indicate the function cannot be used. Establish Image Pair 1 The drive establishes a SCSI login for the initiator.
The PRLI recipient returns a PRLI Accept or a LS_RJT to a PRLI request. The PRLI Accept may indicate success or failure of the process login request in the Response Code field. A LS_RJT is returned to a PRLI with a basic format error, e.g. page length error, payload length, and type code.
40 Data Overlay Allow Not supported by the drive. The Data Overlay Allowed bit is not checked. 40 Data/Response Allowed 1 40 40 Allows the drive to send the FCP RSP in the same sequence as the data. The drive does not support the Data/ Response Mix. It will accept a PRLI with the Allow bit set, but will return a 0 in the accept to indicate the function cannot be used. Establish Image Pair 1 The drive establishes a SCSI login for the initiator.
40 Type Code 08h 40 Type Code Extension 0 40 SCSI FCP process as included in the frame header for FCP frames. Not defined for SCSI FCP and must be set to zero (0). Wr XFR RDY Disable (Write Transfer Ready Disable) 1 FCP_XFR_RDY will not be sent to request write data. 0 The drive requires this bit to be set to zero (0). The drive also requires the use of the WR_XFR_RDY bit. 76 Fibre Channel Interface Manual, Rev.
9.2.5 Process Logout (PRLO) Process Logout (PRLO) is sent by the initiator to a target to remove an existing SCSI login. This frees target resources for use by other initiators.
41 Payload Length Length of PRLO payload (in bytes). The count includes the LS Command Code. The drive supports one service parameter page per PRLO. The Payload Length must be 14h (20 decimal). 41 Process Associators Not supported by the drive. The process associator fields are not checked by the drive. 41 41 Type Code 00h All FC-4 processes between the initiator and target are removed. The drive treats 08h and 00h the same. 08h The SCSI-FCP process will be removed.
Table 42: PRLO Accept Payload Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 0 0 0 LS Command Code 1 0 0 0 1 0 Page Length 2 0 0 0 0 0 0 0 0 3 0 0 0 1 0 1 0 0 Payload Length 4 Reserved 5 Reserved 6 Orig Proc Assc Valid 7 Reserved 8 Resp Proc Assc Valid 0 Reserved 0 Reserved Response Code (MSB) 9 Originator Process Associator 10 11 (LSB) 12 (MSB) 13 Responder Process Associator 14 15 (LSB) 16 17 Reserved 18 19 Table number 42 Field definitions (
42 Response Code The result of the PRLO request. Codes 1, 4, and 7 are supported by the drive. 0 Reserved. 1 Request executed. 2 Reserved. 3 Reserved. 4 The Image Pair does not exist. 5 Reserved. 6 Reserved 7 The destination port is unable to process a multiple page PRLO request. The PRLO request may be retried as a single page request. 80 Fibre Channel Interface Manual, Rev.
9.2.6 Third Party Process Logout (TPRLO) Third Party Process Logout (TPRLO) is sent by the initiator to a target to remove an existing SCSI login. This frees target resources for use by other initiators.
43 Page Length The length must be in the range of 10h to 14h. 43 Payload Length Length of TPRLO payload (in bytes). The count includes the LS Command Code. The drive supports one service parameter page per TPRLO. The Payload Length must be in the range of 14h to 18h. 43 Process Associators Not supported by the drive. The originator and responder process associator valid bits must be set to zero (0). The process associator fields are not checked by the drive.
Table 44: TPRLO Accept Payload Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 0 0 0 LS Command Code 1 0 0 0 1 0 Page Length 2 0 0 0 0 0 0 0 0 3 0 0 0 1 0 1 0 0 Payload Length 4 Reserved 5 Reserved 6 Third Party Orig Proc Assc Valid 7 Third Party Resp Proc Assc Valid Third Party Orig N_Port ID Validity Global Process Logout Reserved Reserved 8 (MSB) 9 Third Party Originator Process Associator 10 11 (LSB) 12 (MSB) 13 Third Party Responder Process As
44 44 Process Associators Not supported by the drive. The process associator fields are not checked by the drive. Response Code The result of the TPRLO request. Codes 1, 4, and 7 are supported by the drive. 44 0 Reserved. 1 Request executed. 2 Reserved. 3 Reserved. 4 The Image Pair does not exist. 5 Reserved. 6 Reserved 7 The destination port is unable to process a multiple page TPRLO request. The TPRLO request may be retried as a single page request.
9.2.7 Read Link Error Status Block (RLS) Read Link Error Status Block (RLS) is sent by the initiator to request the drive to return the Fibre Channel link error information. The error information is contained in the Link Error Status Block (LESB) that is returned in the accept to the RLS. The drive maintains a separate LESB for each port.
The RLS Accept includes the LS Command Code and the LESB. The LESB counts are not cleared by a reset. There is no protocol for clearing the counts. The requester must compare the current values with those read previously.
46 Invalid Transmission Word Number of invalid transmission words received while in word sync. Reference the specific drive product manual to determine if this field is supported. 46 Link Failure Count Number of times synchronization was lost for greater than R_T_TOV (Receiver Transmitter Timeout Value). A Link Failure results in sending Loop Initialization Primitive Sequence (LIP). 46 Loss of Signal Count Not supported.
9.2.8 Reinstate Recovery Qualifier (RRQ) The Reinstate Recovery Qualifier (RRQ) is sent by the initiator to the drive to indicate the Recovery Qualifier (S_ID, D_ID, OX_ID, RX_ID, SEQ_ID, and SEQ_CNT) for an aborted exchange may be reused. The drive allows reuse of the Recovery Qualifier immediately after sending the accept to an ABTS and does not require RRQ. It returns accepts to all RRQs.
Table 48: RRQ Accept Payload Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 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 LS Command Code Table number 48 Field definitions (listed alphabetically) LS Command Code (Link Services Command Code) Not supported by the drive. Fibre Channel Interface Manual, Rev.
9.2.9 Port Discovery (PDISC) Port Discovery (PDISC) is sent by an initiator to a drive after loop initialization to verify addresses have not changed. The PDISC transfers the same information as the PLOGI except that the LS Command code in the first word of the payload is 50000000h. The PDISC does not cause the open exchanges (commands) to be discarded if the initiator address and parameters have not changed. For other contents of the payload, see Section 9.2.1, Port Login (PLOGI).
9.2.10 Discover Address (ADISC) Discover Address (ADISC) is sent by an initiator to a drive after loop initialization to verify addresses have not changed or to verify the drive was able to obtain the hard address select through the interface connector (SEL Lines) during loop initialization. The ADISC allows the drive to compare the initiator’s address and Port Name with previous login values.
49 Node Name of Originator This is the unique 8 byte identifier for the initiator sending the ADISC. Refer to Table 23 for the format of the Node Name. 49 N_Port ID of Originator This is the 24 bit NL_Port Identifier used in the S_ID of the ADISC. The lower 8 bits are the AL_PA the initiator acquired during loop initialization. 49 Port Name of Originator This is the unique 8 byte identifier for the initiator port sending ADISC. Refer to Table 23 for the format of the Port Name.
Table 50: ADISC Accept Payload Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 1 0 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 LS Command Code 4 5 Reserved (MSB) 6 Hard Address of Responder 7 8 (LSB) (MSB) : Port Name of Responder 15 16 (LSB) (MSB) : Node Name of Responder 23 24 25 (LSB) Reserved (MSB) 26 N_Port ID of Responder 27 Table number 50 (LSB) Field definitions (listed alphabetically) Hard Address of Responder This is the 24 bit NL_P
9.2.11 Report Node Capabilities (RNC) Report Node Capabilities (RNC) is sent to a target node to request that the node report on its capabilities. The node does this by returning a list of specifications and the supported revision level of the specification. Table 51: Bit Byte RNC Payload 7 6 0 LS Command Code 1 Reserved 2 (MSB) 5 3 4 3 2 1 0 Payload Length (LSB) Table number 51 4 RNC Flags 5 Reserved 6 Reserved 7 VU Information Length 8 . .
If either bit 5 or bit 4 = 1 - The Document Identifier is vendor unique. This feature is not supported. Bits 4 and 5 must = 0. 52 High Revision - RNC Accept Payload only This field contains the highest revision of the specified document that is supported. The values in the revision fields represent decimal revisions between 0.0 (00h) and 25.5 (FFh). 52 Low Revision - RNC Accept Payload only This field contains the lowest revision of the specified document that is supported.
9.2.12 Link Service Reject (LS_RJT) Link Service Reject (LS_RJT) is a reply to an extended link service request that has been rejected. A reason code is included to communicate additional information about the reject.
9.3 FC common transport FC common transport (CT) provides a transport for service applications such as the fabric name server. The type of FC common transport service is identified by the command code in the third word of the payload. The R_CTL field of the frame header identifies whether the common transport service is a request or a response to a request. The response for a common transport service varies with the function.
Table number 54 Field definitions (listed alphabetically) D_ID (Destination Identifier) Frame destination address. 54 DF_CTL (Data Field Control) Set to 00 to indicate no optional Fibre Channel headers are used. 54 F_CTL (Frame Control) Set to 290000h for CT service requests. This indicates the frame is from the originator of the exchange, this is the last frame of the sequence, and sequence initiative is transferred for the responder to send the reply back.
9.3.1 Register FC-4 Types Name Service (RFT_ID) Register FC-4 Types Name Service (RFT_ID) is used to register the drive’s Port_Identifier and FC-4 type (SCSI-FCP) with the fabric name server. Table 55: RFT_ID Payload Bit Byte 7 6 5 0 0 0 0 1 2 3 0 0 0 0 0 0 4 1 1 5 0 0 0 6 0 0 0 7 0 0 0 8 9 0 0 0 0 0 0 10 0 0 0 11 0 0 0 12 0 0 0 13 0 0 0 14 0 0 0 15 0 0 0 16 0 0 0 17 18 19 20* 21* 22* MSB 0 0 0 0 0 0 0 0 0 0 0 0 23* . . . 51* 0 . . .
Table number 55 Field definitions (listed alphabetically) Command Code: RFT_ID 0217h 55 00h 55 RFC-4 Explanation Code Used only for reject responses. FC-CT Revision Revision level of the FC-CT. 55 FC Service Sub Type 02h 55 FC Services Type Code FCh 55 Single Exchange. Reason Code 00h 55 FC Services. Options 00h 55 Name Service. Used only for reject responses.
10.0 Enclosure services interface (ESI) ESI provides a path for the drive to input data from the enclosure and, optionally, transfer data to the enclosure. All transfers between the drive and its enclosure are initiated by the drive in response to SCSI Send Diagnostic and Receive Diagnostic Results commands from the host system. There are two levels of ESI capability defined by specifications developed in the Small Form Factor (SFF) industry group.
In case 2, the drive continues the discovery process. The drive waits up to 1 second for the enclosure to assert the –ENCL_ACK (SEL_4)) low. The time is allowed for the enclosure processor to complete processing other possible ESI requests through other devices. If –ENCL_ACK is not asserted within one second, the drive assumes the enclosure has 8067 support but is not responding. The SCSI diagnostic command is failed with ASC/ASQ 35 02.
10.2.1 8045 ESI pinouts The table below is a mapping of the Select pins to the SFF 8045 ESI function. The sense of the ESI information is complemented and the address function of the select pins is true. The drive returns the true state of the ESI in the diagnostic page. Table 56: Pin SFF 8045 ESI pinouts ESI function SEL 6 –ESI In 6 SEL 5 –ESI In 5 SEL 4 –ESI In 4 SEL 3 –ESI In 3 SEL 2 –ESI In 2 SEL 1 –ESI In 1 SEL 0 –ESI In 0 Fibre Channel Interface Manual, Rev.
10.3 8067 mode Transfers on an 8067 interface are started by the drive pulling the –P_ESI pin low to enter the Discovery phase. For each transfer, there are three phases: 1. Discovery 2. ESI command 3. Data The data phase is either a read or write to the enclosure depending on the SCSI command. -Parallel_ESI 1 µsec max 1 µsec max SEL/ESI Bus SEL_ID Discovery Figure 14. ESI transfer phases 10.3.
10.3.2 8067 ESI interface pinouts In 8067, the ESI function becomes a bi-directional interface. Three pins are defined for control functions and the remaining four pins become a 4-bit nibble interface. Table 58 is a mapping of the Select pins to the 8067 ESI interface function. 8067 specifies that open-collector type drivers be used for signals on the P_ESI and Select lines.
10.4 ESI command transfer -P_ESI SEL_6/-DSK_WR SEL_5/-DSK_RD SEL_4/-ENCL_ACK SEL(3:0)/DATA -SEL(3:0) CMD Nibble 1 Discovery Figure 15. ESI command transfers 10.4.1 ESI read transfer CMD Nibble 2 CMD Nibble 8 ESI Command Data To receive data from the enclosure, the drive pulls –DSK_RD pin low to request information from the enclosure. The enclosure responds by driving the Data pins with ESI and pulling –ENCL_ACK low to signal that the data is valid.
DSK_WR going high by allowing –ENCL_ACK to return to high. This sequence may be repeated for as many bytes, two nibble each, sent by the host. The drive exits the ESI mode by allowing –P_ESI low to return to a high. -P_ESI 1 µsec max SEL_6/-DSK_WR SEL_6 SEL_5/-DSK_RD SEL_5 SEL_4/-ENCL_ACK SEL_4 SEL(3:0)/DATA Data Nibble 1 Data Nibble 2 Figure 17. ESI writes 10.
START_1/ START_2 1 sec max device delay 100 nsec min enclosure delay –PARALLEL ESI 1 µsec 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.2 second max enclosure delay [1] [1] [2] [3] [4] [5] [2] [3] [4] [5] Enclosure Services Processor negates START_1 and START_2 to indicate that it is requesting communication with the drive.
START_1/ START_2 1 sec max device delay –PARALLEL ESI 1 µsec 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.2 second max enclosure delay [1] [1] [2] [3] [4] [5] [2] [3] [4] [5] Enclosure Services Processor negates START_1 and START_2 to indicate that it is requesting communication with the drive.
–PARALLEL ESI ESI INTF SEL_ID Figure 20. Discovery Command Read Command Write SEL_ID EIE Operation Phases If any errors or timeouts are detected during the EIE operation, the drive aborts the operation and continues normal operation. Errors are not reported. 10.5.
Note: The Initiate Loop Initialization Action Code (03h) does not include a transfer of information to the enclosure. The Action Specific bits in the Enclosure Request define the operation to be performed. See Table 62. 04h Device Identification (see Section 10.5.3.4). 05h Device Temperature (see Section 10.5.3.5). 06h Port Parameters (see Section 10.5.3.6). 07h Link Status (see Section 10.5.3.7). 08h Spin-Down Control (see Section 10.5.3.8). 09h ESI Data Validation (see Section 10.5.3.9).
Table 63: Enclosure Initiated ESI Page Format Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code 2 3 (MSB) 4 (MSB) 3 2 1 0 Page Length (n – 3) (LSB) Data . . n Table number 63 (LSB) Field definitions (listed alphabetically) Action Code The Action Code requested by the enclosure. 63 Data The first n - 4 bytes of ESI data. 63 ESI Page 00h 63 Identifies the ESI page code used (00h). Page Length The length of the ESI page (n - 3 bytes).
10.5.3.1 Device Standard Inquiry Data page Table 64: Device Standard Inquiry Data page Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (00h) 2 3 (MSB) 4 (MSB) 3 2 1 0 Page Length (24h) (LSB) Inquiry Data . . 39 Table number 64 (LSB) Field definitions (listed alphabetically) Action Code 00h 64 ESI Page 00h 64 Device Standard Inquiry Data Identifies the ESI page code used (00h). Inquiry Data The first 36 bytes of Standard Inquiry data. Refer to Section 12.
10.5.3.
64 Port_Identifier The FC 24-bit address assigned to the port. The lower byte is the current FC-AL AL_PA for this port. If the port does not have a Port_Identifier, a value of FF FF FFh is returned in the Port_Identifier field. 64 Port Name The 64-bit Fibre Channel unique Name_Identifier assigned to the port. 64 Port Position The offset value for this port's AL_PA in the FC-AL AL Loop Initialization Loop Position (LILP) Frame.
10.5.3.3 Loop Position Map page Table 66: Loop Position Map page Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (02h) 2 3 (MSB) 4 3 2 1 0 Page Length (m – 3) (LSB) Offset Port A (n – 4) 5 (MSB) Loop Map Port A . . n n+1 (LSB) Offset Port B (m – n + 1) n+2 (MSB) Loop Map Port B . . m Table number 66 Field definitions (listed alphabetically) Action Code 02h 66 Device Address ESI Page 00h 66 (LSB) Identifies the ESI page code used (00h).
10.5.3.4 Device Identification page Table 67: Device Identification page Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (04h) 2 3 (MSB) 4 (MSB) 3 2 1 0 Page Length (n – 3) (LSB) . Device ID Data . n Table number 67 Field definitions (listed alphabetically) Action Code 04h 67 (LSB) Device Identification. Device ID Data This field contains the same data as the SCSI Vital Product Data Device Identification page (83h). See Section 12.6.
10.5.3.5 Device Temperature page Table 68: Device Temperature page Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (05h) 2 3 (MSB) 4 Temperature 3 2 1 0 Page Length (06h) (LSB) 5 . Reserved . 9 Table number 68 Field definitions (listed alphabetically) Action Code 05h 68 ESI Page 00h 68 Device Temperature Identifies the ESI page code used (00h). Temperature The value of the drive temperature sensor in degrees Celsius, offset by +20 degrees.
10.5.3.6 Port Parameters page Table 69: Port Parameters page Bit Byte 7 6 5 4 0 0 0 0 0 ESI Page (00h) 1 0 0 0 0 Action Code (06h) 2 3 (MSB) 4 69 Reserved 0 LSP CHG 0 Port A Link Fail Port A Bypass 0 0 Port B Link Fail Port B Bypass 0 Port A Link Rate Reserved 0 Port B Link Rate Reserved Field definitions (listed alphabetically) Action Code 06h 69 0 (LSB) 8 Table number 1 Drive Capabilities 6 9 2 Page Length (06h) 5 7 3 Port Parameters.
10.5.3.7 Link Status page All fields are supported unless specifically listed as not supported under Field Definitions below. When the drive changes a value in this page, the drive sets the LSP CHG bit in the Port Parameter page. The enclosure may poll the Port Parameter page to determine if it needs to read and process the Link Status page. When the Link Status page is read by the enclosure, the LSP CHG bit is cleared.
Table 70: Link Status page (Continued) Bit Byte 7 52 . 55 (MSB) 56 . 59 (MSB) 60 . 63 (MSB) 64 . 67 (MSB) 68 . 71 (MSB) 72 . 75 (MSB) 76 . 79 (MSB) 80 . 83 (MSB) 84 . 87 (MSB) 88 .
70 Link Failure Count Count of the number of Loss of Sync conditions that have occurred on the port which exceeded 100 ms in duration. 70 LIP F7 Initiated Count Count of the number of loop initialization processes originated by the port with LIP – F7’s (Initialize LIP). 70 LIP F7 Received Count Count of the number of loop initialization processes initiated on the port by receiving LIP – F7’s (Initialize LIP).
10.5.3.8 Spin-Down Control Action Specific Bits Table 71: Table number 71 71 71 Spin-Down Control Action Specific Bits Bit Byte 7 6 5 4 3 0 0 0 0 0 0 2 1 0 Read Status Enable Spin Down Enable SpinDn Ctrl Field definitions (listed alphabetically) Read Status 0 Device updates the state of the Enable Spin-Down and Enable SpinDn Ctrl as directed by the corresponding bits in the request.
72 Page Length 06h The maximum length of the ESI page (in bytes). 10.5.3.9 ESI data validation ESI Data Validation (EDV) provides a mechanism to verify correct data is transferred over the ESI. This function is optional with support discovered by negotiation. When EDV is enabled, a checksum is calculated and appended to each ESI transfer phase, ESI command, data, and Enclosure request. The drive will request ESI data validation when the following occur: 1.
11.0 SCSI operations SCSI information is transported in Fibre Channel frames. All SCSI Fibre Channel Protocol (SCSI-FCP) operations start with an FCP CMND (Command) frame and end with an FCP RSP (Response) frame. Operations initiated with an FCP CMND may be SCSI commands such as read or write data. The operations also include control operations called Task Management functions. Task Management functions provide reset and Task Set (queue) control.
11.2 FCP CMND The content of the FCP CMND frame is shown below. Details of the FCP CMND contents are in Tables 74 and 75.
Table number 74 Field definitions (listed alphabetically) DF_CTL (Data Field Control) 00h 74 No optional Fibre Channel headers are used. D_ID (Destination Identifier) The address of the drive. This value must match the current address of the drive. 74 F_CTL (Frame Control) 290000h for FCP CMND frames. This indicates the frame is the first sequence of the exchange and last frame of that sequence. Sequence initiative is also transferred so the drive may respond to the FCP CMND.
Table 75: FCP CMND Payload Bit Byte 0 7 6 5 4 3 2 1 0 (MSB) : Logical Unit Number 7 (LSB) 8 0 0 0 0 0 0 0 0 Reserved 9 0 0 0 0 0 Task Attribute Reserved 10 Term Task Clear ACA Target Reset 0 0 0 0 0 11 0 Clear Task Set Abort Task Set 0 Reserved 0 0 Read Data Write Data Reserved Reserved 12 (MSB) : CDB 27 28 (LSB) (MSB) 29 DL 30 31 Table number 75 (LSB) Field definitions (listed alphabetically) Abort Task Set Clears only the queue of commands from the
If the DL value equals the actual transfer length in the CDB, the Residual Over Run and Residual Under Run bits in the FCP RSP will be cleared. 75 Logical Unit Number (LUN) Addresses physical devices or virtual devices attached to a target. 0 75 Zero is the only valid LUN number for the drives supported by this manual. The drive will reject Inquiry, Test Unit Ready, and Request Sense commands that select an invalid LUN by sending Check Condition status in the FCP RSP frame.
11.2.1 Command Descriptor Block (CDB) A request by an initiator to a disc drive is performed by sending a Command Descriptor Block (CDB) to the disc drive. For several commands, the request is accompanied by a list of parameters sent in FCP DATA frames. See the specific commands for detailed information. The Command Descriptor Block always has an operation code as the first byte of the command. This is followed by command parameters (if any) and a control byte.
Table 77: Typical CDB for six-byte commands Bit 7 6 5 4 3 2 1 0 Byte 0 Operation Code 1 0 0 0 (MSB) Reserved Logical Block Address (if required) 2 3 Table number 77 (LSB) 4 Transfer Length (if required) 5 Control Byte Field definitions (listed alphabetically) Control Byte See Section 11.2.1.6. 77 Logical Block Address See Section 11.2.1.2. 77 Operation code See Section 11.2.1.3. 77 Transfer Length See Section 11.2.1.5.
78 Logical Block Address See Section 11.2.1.2. 78 Operation Code See Section 12.0. 78 RelAdr (Relative Address) See Section 11.2.1.4. 78 Transfer Length See Section 11.2.1.5 11.2.1.2 Logical block address The logical block address in the Command Descriptor Block begins with block zero and is continuous up to the last logical block on drive. Group 0 command descriptor block contains 21-bit logical block addresses. Groups 1 and 2 command descriptor blocks contain 32-bit logical block addresses.
The Transfer Length field of the commands used to return sense data (e.g., Request Sense, Inquiry, Mode Sense, etc.) to an initiator is called the Allocation Length field. The Allocation Length field specifies the number of bytes that the initiator has allocated for returned data. The disc drive terminates the data in the FCP DATA sequence when Allocation Length bytes have been transferred or when all available data have been transferred to the initiator, whichever is less. 11.2.1.
11.3 FCP XFER RDY The FCP XFER RDY (Transfer Ready) frame is sent by the drive when it requests data for a transfer to the drive. Examples of commands resulting in data transfers to the drive are Write, Mode Select, and Write Buffer.
Table number 80 Field definitions (listed alphabetically) DF_CTL (Data Field Control) 00h 80 No optional Fibre Channel headers are used. D_ID (Destination Identifier) The address of the initiator that originated the command for which the data is being requested. 80 F_CTL (Frame Control) Set to 890000h for FCP CMND frames. This indicates the frame is sent by the responder of the exchange, not the originator, and the frame is the last of the Fibre Channel sequence.
Table 81: FCP XFER RDY Payload Bit Byte 0 7 6 5 4 3 2 1 0 (MSB) 1 Relative Offset 2 3 4 (LSB) (MSB) 5 Burst Length 6 7 8 (LSB) (MSB) 9 Reserved 10 11 Table number 81 (LSB) Field definitions (listed alphabetically) Burst Length The amount of data (in bytes) requested by the drive for transfer in this Fibre Channel sequence.
11.4 FCP DATA The payload of FCP DATA frames transfer the user data associated with a command. Note: EOFt is used on the last frame of a sequence. Single frame sequences end with an EOFt. All other FCP DATA frames use EOFn.
Table number 82 Field definitions (listed alphabetically) DF_CTL (Data Field Control) 00h 82 Indicates no optional Fibre Channel headers are used. D_ID (Destination Identifier) The address of the drive if transfer is data to the drive and the address of the initiator originating the command if the transfer is from the drive. 82 F_CTL (Frame Control) This field is determined by the direction of the transfer and whether or not the frame is the last frame of the sequence.
82 SEQ_ID (Sequence Identifier) For transfers to the drive, the drive captures the SEQ_ID from the first frame of the sequence and requires all subsequent frames of the sequence to have the same SEQ_ID. For transfers to the initiator, the drive sets the SEQ_ID to 00h for the first data sequence of a command (exchange). The SEQ_ID is sequentially increased for additional data sequences, if required, for the command.
11.5 FCP RSP An FCP Response (RSP) frame is returned by the drive for each FCP CMND operation unless the drive receives: 1. 2. 3. 4. 5.
Table number 84 Field definitions (listed alphabetically) DF_CTL (Data Field Control) 00h 84 Indicates no optional Fibre Channel headers are used. D_ID (Destination Identifier) The address of the initiator that originated the command. 84 F_CTL (Frame Control) Set to 990000h for FCP RSP frames.
Table 85: FCP RSP Payload Bit Byte 0 7 6 5 4 3 2 1 0 (MSB) : Reserved 9 (LSB) 10 0 11 SCSI Status 12 (MSB) 0 0 Reserved 13 0 Resid Under Run Resid Over Run Sense Length Valid RSP Length Valid Residual Count 14 15 16 (LSB) (MSB) 17 Length of Sense Information 18 19 20 (LSB) (MSB) 21 Length of Response Information 22 23 Table number 85 24 : 31 (MSB) 32 : 51 (MSB) (LSB) SCSI Extended Sense Information (LSB) Length of Response Information The Length of Response Inform
85 Resid Under Run (Residual Under Run) 1 85 The number of bytes transferred was less than the DL of the FCP CMND by the byte count in the Residual Count field, bytes 12–15. Response Information Format is shown in Table 86.
85 28h Task Set (queue) Full. This status is implemented if tagged queuing is implemented. This status is returned when a command is received and the command can not be accepted because the command queue is full. The command is not executed. 30h ACA Active. This status is returned when an auto contingent allegiance (ACA) exists with another initiator. The initiator may reissue the command after the ACA condition has been cleared.
11.5.1 Extended Sense Data format The drive is capable of sending 18 bytes of extended sense data. The Extended Sense Data format is summarized in Table 87. The 1s and 0s shown in the tables below represent the logical 1s and 0s as sent by the disc drive.
87 Additional Sense Length 10 (Max) Specifies additional sense bytes are to follow. This is limited to a maximum of 10 (decimal) additional bytes. If the Allocation Length of the Command Descriptor Block is too small to transfer all of the additional sense bytes, the additional sense length is not adjusted to reflect the truncation. 87 Command Specific Data These four bytes contain data for the command. 87 EOM (End of Medium) Always zero (0) for disc drives. 87 Error Code 70h Current error.
11.5.1.1 Sense Key Specific Valid (SKSV) and Sense Key Specific Refer to the appropriate tables in this section for sense key specific values. Table 88: Sense Key Specific reference tables Sense Key field value SKSV 05h (Illegal Request) 1 These fields point to illegal parameters in command descriptor blocks and data parameters sent by the initiator.
Table 90: Bit Byte Actual Retry Count bytes 7 15 SKSV 16 (MSB) 6 5 90 3 2 1 0 Reserved Actual Retry Count 17 Table number 4 (LSB) Field definitions (listed alphabetically) Actual Retry Count Returns implementation-specific information on the actual number of retries used in attempting to recover an error or exception condition. Note. 90 This field relates to the retry count fields specified within the Verify Error Recovery Page (07h) parameters of the Mode Select command. See Table 151.
Table 92 lists the sense keys in the extended sense data format that are used by the disc drive. Table 92: Sense Key Applicable disc drive sense keys Description 0h No Sense: There is no specific sense key information to be reported for the disc drive. This would be the case for a successful command or when the ILI bit = 1. 1h Recovered Error: The last command completed successfully with some recovery action performed by the disc drive.
Table 93 lists the extended sense, additional sense, and additional sense qualifier codes.
Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 (ASC) Byte 13 (ASCQ) Description 19 00 Defect list error 1A 00 Parameter list length error 1C 00 Defect list not found 1D 00 Miscompare during verify operation 20 00 Invalid command operation code 21 00 Logical block address out of range 24 00 Invalid field in CDB 25 00 Logical unit number not supported 26 00 Invalid field in parameter list 26 01 Invalid field parameter –
Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 (ASC) Byte 13 (ASCQ) Description 35 00 Enclosure services failure 35 01 Unsupported enclosure function 35 02 Enclosure services unavailable 35 03 Enclosure services transfer failure 35 04 Enclosure services transfer refused 37 00 Parameter rounded 3F 01 Microcode changed 3F 02 Changed operating definition 3F 05 Device identifier changed 3F 91 WWN mismatch, ETF WWN is vali
Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 (ASC) Byte 13 (ASCQ) Description 55 01 XOR cache is not available 55 03 Insufficient reservation resources 55 04 Insufficient registration resources 5B 00 Log exception 5B 01 Threshold condition met 5B 02 Log parameter value at maximum 5C 00 Servo RPL status change 5C 01 Servo RPL spindles synchronized 5C 02 Servo RPL spindles not synchronized 5D 00 Failure prediction thr
posted unless required by the error handling parameters of the Mode Select command. The occurrence of the error may be logged if statistical or error logging is supported. 2. If a deferred error can be associated with a causing initiator and with a particular function or a particular subset of data, and the error is either unrecovered or required to be reported by the mode parameters, a deferred error indication is returned to the causing initiator.
12.0 Commands This section contains information about the commands used by Seagate Fibre Channel disc drives. This section is organized to provide rapid access to command information. Navigation assistance All commands are: • Listed alphabetically by command name. • Cross-referenced by command name and command operation code. The field descriptions that are provided for most tables have sidebar labels which identify the table they are associated with.
Table 94: Commands sorted by command name Command type Command name Change Definition (obsolete) Length Direct access 6 10 12 16 32 Op All code devices devices bytes bytes bytes bytes bytes Variable 40h x Reference 12.1 (see page 160) Compare (obsolete) 39h x 12.2 (see page 160) Copy (obsolete) 18h x 12.3 (see page 160) Copy and Verify (obsolete) 3Ah x Format Unit 04h x Inquiry 12h Lock-Unlock Cache (10) 36h Lock-Unlock Cache (16) 92h Log Select 4Ch x x 12.
Table 94: Commands sorted by command name (Continued) Command type Command name Length Direct access 6 10 12 16 32 Op All code devices devices bytes bytes bytes bytes bytes Variable Start/Stop Unit 1Bh x Synchronize Cache (10) 35h x Synchronize Cache (16) 91h x Test Unit Ready 00h Verify (10) 2Fh x Verify (12) AFh x Verify (16) 8Fh x Write (6) 0Ah x Write (10) 2Ah x Write (12) AAh x Write (16) 8Ah x Write and Verify (10) 2Eh x Write and Verify (12) AEh x x x Refe
Table 95: Commands sorted by operation code Command type Op code 00h Command name Test Unit Ready 01h Rezero Unit 03h Request Sense 04h Format Unit 07h 08h 0Ah Write (6) Length Direct access 6 10 12 16 32 All devices devices bytes bytes bytes bytes bytes Variable x (obsolete) x 12.53 (see page 316) x 12.41 (see page 302) x 12.38 (see page 298) x x 12.5 (see page 161) Reassign Blocks x x 12.32 (see page 285) Read (6) x x 12.21 (see page 262) x x 12.
Table 95: Commands sorted by operation code Command type Op code 5Ah Command name Length Direct access 6 10 12 16 32 All devices devices bytes bytes bytes bytes bytes Variable Mode Sense (10) x x Reference 12.14 (see page 246) 5Eh Persistent Reserve In x x 12.16 (see page 249) 5Fh Persistent Reserve Out x x 12.17 (see page 254) 7Fh XDRead (32) x x 0003h 7Fh XDWrite (32) x x 0004h 12.71 (see page 347) 7Fh XPWrite (32) x x 0006h 12.
12.1 Change Definition command 40h Obsolete. If this command is received, the disc drive sends a Check Condition status and a sense key of Illegal Request. 12.2 Compare command 39h Obsolete. A Check Condition status is sent if a Compare command is received. 12.3 Copy command 18h Obsolete. If received, the disc drive sends a Check Condition status and a sense key of Illegal Request. 12.4 Copy and Verify command 3Ah Obsolete.
12.5 Format Unit command 04h The Format Unit command ensures that the medium is formatted so all of the user-addressable data blocks can be accessed. There is no guarantee that the medium has or has not been altered. In addition, the medium may be certified and control structures may be created for the management of the medium and defects. The drive allows an initiator to specify (or not specify) sectors which are to be reallocated during the format process.
96 Interleave This field requests that logical blocks be related in a specific fashion to the physical blocks to facilitate data transfer speed matching. 0 The target uses its default interleave. 1 Consecutive logical blocks will be placed in consecutive physical order. Š2 One or more (respectively) physical blocks separate consecutive logical blocks.
Table 97: Format Unit parameter definition (format variations) CDB–Byte (see Table 96) FMT DATA CMP LIST Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Comments 0 X X X X Default format: No data is transferred. The disc drive reallocates all sectors in the P list plus any sector which fails to Format Verify phase (C type flaws). Any previous G list is erased. Defect List Format Block format [2] 1 0 0 X X Format with G and no D: A four-byte Defect List header must be sent by the initiator.
12.5.1 Format Unit parameter list Parameter Reference Defect List Header See Table 98 Initialization Pattern Descriptor See Table 99 Defect Descriptors See Tables 101, 102, and 103 12.5.1.
98 Immed (Immediate) 0 Status will be returned after the first operation has completed. 1 The target will return status as soon as the command descriptor block has been validated, and the entire defect list has been transferred. Check individual drive’s Product Manual, Volume 1, for applicability of this feature. 98 IP (Initialization Pattern) This field indicates the type of pattern the target uses to initialize each logical block within the initiator accessible portion of the medium (Table 100).
99 Initialization Pattern Length The number of bytes contained in the initialization pattern. If the length exceeds the current logical block size, this is an error. The initialization pattern is sent by the host for the drive to write in each logical block by the Format command. 99 Pattern Type 00h Use default pattern. If the initialization pattern length is not zero, this is an error and the drive terminates the command with Check Condition status.
A value for Defect Bytes from Index of FFFFFFFFh (i.e., reassign the entire track) is illegal for the disc drive. Table 103: Defect descriptor bytes–Physical Sector format Byte Description 0 Cylinder Number of Defect (MSB) 1 Cylinder Number of Defect 2 Cylinder Number of Defect (LSB) 3 Head Number of Defect 4 Defect Sector Number (MSB) 5 Defect Sector Number 6 Defect Sector Number 7 Defect Sector Number (LSB) Information in this table is repeated for each defect.
12.6 Inquiry command 12h The Inquiry command requests that information regarding parameters of the disc drive be sent to the initiator. The Enable Vital Product Data (EVPD) option allows the initiator to request additional information about the disc drive. See Section 12.6.1. Several Inquiry commands may be sent to request the vital product data pages instead of the standard data shown in Table 105 on page 170.
Additional Inquiry command information The Inquiry command returns Check Condition status only when the disc drive cannot return the requested Inquiry data. If an Inquiry command is received from an initiator with a pending unit attention condition (i.e., before the disc drive reports Check Condition status), the disc drive performs the Inquiry command and does not clear the Unit Attention condition.
Disc drive inquiry data The disc drive standard inquiry data contains 36 required bytes, followed by a number of bytes of disc drive specific data that is drive dependent. See individual drive’s Product Manual, Volume 2. Refer to the standard Inquiry data in Table 105.
105 ANSI-Approved Version 2h 105 Indicates this device complies with ANSI lX3.131-199x (SCSI-2) and the SCSI-3 features as described in this manual. BQue (Basic Queuing) The following BQue values are valid only when the CMD QUE bit = 0. 105 105 0 The device does not support tagged tasks (command queuing) for this logical unit. This value is always used if the CmdQue bit is 1.
105 RelAdr (Relative Addressing) This function is not supported by drives described in this manual. 105 Reserved Byte 56 through byte 95 are filled with 00h. 105 105 105 Response Data Format 0 The Inquiry data format is as specified in the ANSI SCSI-1 standard. 1 Indicates compatibility with some products that were designed prior to the development of the ANSI SCSI-2 standard (i.e., CCS). 2 Indicates that the data is in the format specified in the SCSI-2 standard.
12.6.1 Vital product data pages The initiator requests the vital product data information by setting the EVPD bit to one and specifying the page code of the desired vital product data. If the disc drive does not implement the requested page it returns Check Condition status. The sense key is set to Illegal Request and the additional sense code is set to Invalid Field in CDB. This section describes the vital product data page structure and the vital product data pages that are applicable to the disc drive.
12.6.2 Unit Serial Number page (80h) The Unit Serial Number page provides the product serial number for the drive. Table 108: Unit Serial Number page (80h) Bit Byte 0 2 0 0 Page Length (08h) 3 4 : 11 108 6 5 4 3 Peripheral Qualifier Page Code (80h) 1 Table number 7 2 1 0 0 0 Peripheral Device Type 0 0 0 0 Product Serial Number Field definitions (listed alphabetically) Page Code Page 80h provides the product serial number for the disc drive.
12.6.
12.6.4 Device Identification page (83h) The device identification page provides the Node Name for the drive.
110 Page Length The length (in bytes) of the Device Identification page. If the allocation length is too small to transfer all the page, the page length is not adjusted to reflect the truncation. 110 Peripheral Qualifier and Peripheral Device Type 00h A direct-access device (magnetic disc) is connected to this logical unit. Each identification descriptor contains information identifying the logical unit. If the logical unit is accessible through any other path, it returns the same identification.
of constructing the remainder of the Identifier field is to concatenate the Product Identification field from the standard Inquiry Data field and the product serial number field from the Unit Serial Number page. 02h The Identifier field contains an IEEE Extended Unique Identifier, 64-bit (EUI-64). In this case, the Identifier Length field is set to 8. Note that the IEEE guidelines for EUI-64 specify a method for unambiguously encapsulating an IEEE 48-bit identifier within an EUI-64. 04 - 0Fh Reserved.
12.6.
12.6.6 Date Code page (C1h) Table 114: Bit Byte 0 1 2 3 Table number 114 Date Code page (C1h) 7 6 5 4 3 Peripheral Qualifier Page Code (C1h) 0 0 Page Length (0Ch) 4 : 11 Product Date Code 12 : 19 Compile Date 2 1 0 0 0 Peripheral Device Type 0 0 0 0 Field definitions (listed alphabetically) Compile Date The field contains 8 ASCII bytes of data for a date of the form MMDDYYYY. 114 Page Code C1h 114 Page Length 0Ch 114 The length (in bytes) of the product date code.
12.6.7 Jumper Settings page (C2h) Table 115: Jumper Settings page (C2h) Bit Byte 0 2 0 0 Page Length (02h) 3 115 3 4 S2 5 Rsvd S1 2 1 0 Peripheral Device Type 0 0 0 0 0 0 Rsvd Rsvd Rsvd Rsvd Rsvd Rsvd Sel. ID Provides the status of the option selections at the disc drive connector. Page Length The length (in bytes) of the Jumper Settings page.
Table 116: AL_PA Select-ID mapping AL_PA (hex) Sel. ID (hex) AL_PA (hex) Sel. ID (hex) AL_PA (hex) Sel.
12.6.8 Device Behavior page (C3h) The Device Behavior page (VPD page C3h) is used by regression tests to determine what behavior should be expected from a particular firmware package.
12.7 Lock-Unlock Cache (10) command 36h The Lock-Unlock Cache (10) command requests that the device server disallow or allow logical blocks within the specified range to be removed from the cache memory by the device server's cache replacement algorithm. Locked logical blocks may be written to the medium when modified, but a copy of the modified logical block shall remain in the cache memory. Multiple locks may be in effect from more than one application client.
12.8 Lock-Unlock Cache (16) command 92h The Lock-Unlock Cache (16) command requests that the device server disallow or allow logical blocks within the specified range to be removed from the cache memory by the device server's cache replacement algorithm. Locked logical blocks may be written to the medium when modified, but a copy of the modified logical block shall remain in the cache memory. Multiple locks may be in effect from more than one application client.
119 Operation Code 92h 119 The operation code for the Lock-Unlock Cache (16) command. RelAdr (Relative Addressing) This function is not supported by drives described in this manual. 186 Fibre Channel Interface Manual, Rev.
12.9 Log Select command 4Ch The Log Select command provides a means for an initiator to manage statistical information about the drive operation. This information is logged within the drive and can be sent to the initiator in response to a Log Sense command from the initiator. The Log Select command format is shown in Table 120. The initiator sends zero or more pages of control parameters in the Log Page format of Table 123.
The drive only updates the cumulative values to reflect the number of events experienced by the drive, but the initiator can set the threshold or cumulative log (00 or 01) parameter values using the Log Select command with the PC field set as applicable. The drive sets the current log values to default values in response to a Log Select command with the parameter list length set to zero and the PC field set to the applicable value (10b or 11b).
Table 121 summarizes the Log Select Command field settings used when updating the cumulative/threshold value settings and the resulting action that will occur based on these field settings. Table 121: Log Select Command field setting summary PCR PC Parameter List Length Resulting action 1 xx 0 All cumulative counter and threshold log page values will be set to “zero” on all log pages. 0 11 0 All cumulative counter log page values will be set to “zero” on all log pages.
12.10 Log Sense command 4Dh The Log Sense command provides a means for an initiator to retrieve statistical information maintained by the drive about the drive operation. It is a complementary command to the Log Select command. This information is stored in logs (counters) in the drive and is sent to the initiator as inbound data of the Log Sense command. The Log Sense command format that the initiator sends is shown in Table 122. The format of the data pages sent back by the drive is shown in Table 123.
The parameter values returned are from one of the following: • The specified parameter values in the log counters as of the last update (updated by Log Select command, Log Sense command or done automatically by the drive for cumulative values). • If saved values are available, the saved values are used after the last LIP reset. • If saved values are not available, the default values are used after the last LIP reset.
Table number 123 Field definitions (listed alphabetically) Log Parameter Each Log Parameter structure begins with a four-byte parameter header followed by one or more bytes of parameter value data. Log Parameter structures are in the format given in Table 124. 123 Log Parameter Structures Most log pages contain one or more special data structures called Log Parameters.
Since the drive uses volatile memory to hold cumulative values, they will be lost when a power cycle occurs. Unless the initiator commands the drive to save them to nonvolatile memory using a Log Select or Log Sense command with the SP bit set to one. The DU bit is not defined for threshold values (indicated by the PC field of the Log Sense command descriptor block) nor for list parameters (indicated by the LP bit).
124 TMC (Threshold Met Criteria) This field defines the basis for comparison of the cumulative and threshold values. See Table 125 for meanings of values in this field. The TMC field is only valid when the ETC bit is one.
Table 127: Supported log pages Bit 7 6 5 4 3 2 1 0 Byte 0 Reserved 1 Reserved 2 (MSB) Page Code (00h) Page Length (n–3) 3 (LSB) 4 : n Table number 127 Field definitions (listed alphabetically) Page Code 00h 127 Supported Page List Supported log pages page code. Page Length The length (in bytes) of the Supported Log Pages page. If the allocation length is too small to transfer all of the page, the page length is not adjusted to reflect the truncation.
12.10.1 Error Counter pages, Write, Read, Read Reverse, and Verify (code 02, 03, 04, and 05h) Table 128 defines the parameter code field for the write, read, read reverse, and verify error counter pages.
12.10.2 Non-Medium Error page (code 06h) Log page code 06h specifies non-medium errors. Table 129: Non-Medium Error page (code 06h) Bit Byte Table number 129 0 Page Code (06h) 1 Parameter Code 6 5 4 3 2 1 0 Field definitions (listed alphabetically) Page Code 06h 129 7 Non-Medium Error page code. Parameter Code 0000h The number of recoverable error events other than write, read, or verify errors (0000h is the only code supported for this page). Fibre Channel Interface Manual, Rev.
12.10.3 Temperature page (code 0Dh) Log page code 0Dh provides the temperature of the drive and Fibre Channel link error and initialization counts. Table 130: Temperature log page (code 0Dh) Table number 130 Bit Byte 7 6 0 PS Reserved 3 2 1 0 2 1 0 0 1 1 Page Code (0Dh) Reserved 2 3 Page Length (92h) Field definitions (listed alphabetically) Page Code Temperature page. Page Length 92h 130 4 1 06h 130 5 Length of the page.
Table 132: Command Initiate Parameter Format Bit Byte 7 6 5 0 1 0 3 02h 4 Reserved 1 1 5 132 3 2 1 0 1 1 Parameter Code (80FFh) 2 Table number 4 0 00 Reserved CIP Field definitions (listed alphabetically) Parameter Code 80FFh Command Initiate Port Code. This field identifies the port on the drive that receives the Log Sense command and requested transfer of this page. 0 = Port A. 1 = Port B.
8109h 4 bytes LIP F8 Received Count, Port A. Count of the number of LIP F8s (Failure LIP) which the drive has received on Port A. 8110h 4 bytes Link Failure Count, Port B. Count of the number of Loss of Sync conditions that have occurred on Port B which exceeded 100 msecs in duration. 8111h 4 bytes Loss of Synchronization Count, Port B. Count of the number of short (< 100 msecs) Loss of Synchronization conditions that have occurred on Port B. 8114h 4 bytes Invalid Transmission Word Count, Port B.
12.10.4 Device Self-Test Results Log page (code 10h) This page provides the results from the 20 most recent device self-tests. Results from the most recent test or the test currently in progress is reported in the first self-test log parameter; results from the second most recent self-test is reported in the second self-test log structure parameter and so on. If fewer than 20 device self-tests have occurred, the unused entries are zero filled.
134 Self-Test Results Log Parameter fields See Table 135 below. Table 135: Device Self-Test Results Log parameter data format Bit 7 6 5 4 3 2 1 0 Byte 0 (MSB) Parameter Code (0001h to 0014h) (LSB) 1 2 0 DU 0 DS 0 TSD 0 ETC TMC 1 LBIN 1 LP Parameter Control Bits 3 Parameter Length (10h) 4 Self-Test Code 5 Self-Test Segment Number 6 Reserved Self-Test Results Value (MSB) Timestamp 7 8 (LSB) (MSB) . . .
135 135 Parameter Control Bits DU 0 Value provided by device server DS 0 Device server supports saving of parameter TSD 0 Device server manages saving of parameter ETC 0 No threshold comparison is made on this value TMC xxx Ignored when ETC is 0 LBIN 1 The parameter is in binary format LP The parameter is a list parameter 1 Parameter Length 10h 135 This value is always 10h.
12.10.5 Cache Statistics page (code 37h) Log Page code 37h specifies Cache Statistics page. Table 136: Cache Statistics page Bit Byte 0 1 Table number 136 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 Parameter Code Field definitions (listed alphabetically) Parameter Code 00h The number of logical blocks that have been sent to an initiator. 01h The number of logical blocks that have been received from an initiator.
12.10.6 Factory Log page (code 3Eh) Log Page code 3Eh specifies factory status parameters. Table 137: Factory Log page Bit Byte 0 1 Table number 136 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 Parameter Code Field definitions (listed alphabetically) Parameter Code 0000h Power-on Time. The number of drive power-on minutes. Currently, the Power-on Time parameter is the only parameter in this Log Page that is visible to OEM/customers.
12.11 Mode Select (6) command 15h The Mode Select command provides a means for the initiator to specify medium, logical unit, or peripheral device parameters to the disc drive. The drive also implements the Mode Sense command (see 12.13). Initiators should issue Mode Sense prior to Mode Select to determine supported pages, page lengths, and other parameters. The drive maintains a common set of mode parameters shared by all initiators.
The target terminates all the Mode Select commands with Check Condition status, sets the sense key to Illegal Request and sets the additional sense code to Invalid Field In Parameter List, and does not change any mode parameters for the following conditions: • If the Strict mode is enabled (see Table 146) and the initiator attempts to change any field that is not changeable by the host as reported by the target. In this case, no parameters are changed by this command.
Table 139: Mode Select (6) parameter list Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Reserved 1 0 0 0 0 Medium Type 2 0 0 0 0 Reserved Block Descriptor Length Either 00h or 08h 3 Block descriptor 0 0 0 0 0 Density Code 1 0 0 0 0 0 Number of Blocks (MSB) 2 0 0 0 0 0 Number of Blocks 3 0 0 0 0 0 Number of Blocks (LSB) 4 0 0 5 Block Length (MSB) 6 Block Length 7 Block Length (LSB
139 Mode Select Page Headers And Their Parameters See Mode Sense command (see Section 12.13) for detailed descriptions. 139 Number of Blocks This field contains the number of accessible logical blocks on the logical unit. The maximum Number of Blocks depends on the Block Length in the Block Descriptor, the Format parameters, and the Rigid Disc Drive Geometry parameters.
12.12 Mode Select (10) command 55h The Mode Select (10) command provides a means for the initiator to send a list of drive operating mode parameters to the drive. Table 141: Mode Select (10) command (55h) Bit 7 6 5 4 3 2 1 0 0 1 0 1 0 1 0 1 Byte 0 1 Reserved 2 Reserved 3 Reserved 4 Reserved 5 Reserved 6 Reserved 7 PF Reserved SP (MSB) Parameter List Length 8 9 (LSB) Control See the Mode Select (6) command (Section 12.11) for a description of the fields in this command.
12.13 Mode Sense (6) command 1Ah The Mode Sense command provides a means for the disc drive to report its medium, logical unit, or peripheral device parameters to the initiator. It is a command complementary to the Mode Select command.
1 0 Return Default values. The Default values are the values to which the disc drive sets the Current values after a reset condition unless valid Saved values are available. 1 1 Return Saved values. The saved values are the values the disc drive stores in nonvolatile memory. The Saved values of any changeable parameter can be set to new values via a Mode Select command with the SMP bit set to 1. For nonchangeable parameters, the Default value is used. 212 Fibre Channel Interface Manual, Rev.
Table 143: Mode Sense (6) parameter list Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Sense Data Length 0 1 0 0 Reserved 2 0 0 WP DPO-FUA Reserved 3 0 0 Reserved 0 0 0 Block Descriptor Length (8 decimal) Block descriptor data 0 0 0 0 0 0 Number of Blocks (MSB) 1 0 0 0 0 0 Number of Blocks 2 0 0 0 0 0 Number of Blocks 3 0 0 0 0 0 Number of Blocks (LSB) 4 0 0 0 0 0 Reserved 5 Block Length (MS
143 Mode Sense Page Headers and Their Parameters See Table 144. 143 Number of Blocks The number of logical blocks of the medium that meets the Block Length in the Block Descriptor. 0 143 All of the remaining logical blocks of the logical unit have the medium characteristics specified by the Block Descriptor. Sense Data Length The length (in bytes) of the following Mode Sense data that is available to be transferred to the initiator. The Sense Data Length does not include itself.
Table 145: Mode sense page code section reference Page description Reference table 00h Unit Attention page 146 (page 216) 01h Error Recovery 147 (page 218) 02h Disconnect/Reconnect Control 148 (page 221) 03h Format Parameters 149 (page 223) 04h Rigid Disc Drive Geometry 150 (page 226) 07h Verify Error Recovery page 151 (page 228) 08h Caching page 152 (page 230) 0Ah Control Mode page 153 (page 233) 0Ch Notch and Partition page 154 (page 235) 10h XOR Control Mode page 155 (page
12.13.1 Unit Attention page (00h) The Unit Attention page is the last page reported by the drive. See your individual drive’s Product Manual, Volume 1, Mode Sense Data section, for a table showing codes that indicate which of these bits are changeable by the host using the Mode Select command.
146 PS (Parameter Savable) This bit is only used with the Mode Sense command. This bit is not used with the Mode Select command. 1 146 146 The drive is capable of saving the page in a nonvolatile vendor-specific location. Rnd (Round) 1 The drive treats and reports rounded parameters as described in Section 11.6. 0 The drive rounds the parameter and handles command completion reporting as if the parameter had not been rounded.
12.13.2 Error Recovery page (01h) The disc drive Error Recovery page implementation is defined in Table 147. This table summarizes the function and default for each byte/bit. See individual drive’s Product Manual, Volume 1, section showing changeable values. A value of zero (0) means this bit function is not directly changeable by an initiator; a value of 1 means the bit function is directly changeable by an initiator (see Mode Select command).
147 Correction Span The size of the largest read data error (in bits) which ECC correction can correct. If errors longer than or equal to 255 (FFh) bits can be corrected, 255 (FFh) shall be reported in this field. 147 Data Strobe Offset Count 0 147 147 Zero is the default value and is not changeable. This feature is not programmable by the initiator. Data Strobe Offsets are performed as part of the disc drive’s retry algorithms.
147 Read Retry Count The maximum number of times the disc drive attempts its read recovery algorithms. A Retry Count of zero inhibits non-ECC retries from being performed. 147 Recovery Time Limit The maximum number of milliseconds that is allowed for recovery time. A hex FFFF indicates that the Recovery Time Limit is unlimited. 147 147 TB (Transfer Block) 1 The data block that is not recovered will be transferred to the initiator. 0 The failing data block will not be transferred.
12.13.3 Disconnect/Reconnect Control page (02h) The Disconnect/Reconnect Control page implementation is defined in Table 148. This table summarizes the function and defines the default values. See individual drive’s Product Manual, Volume 1, section showing changeable values. A value of zero (0) means this bit function is not directly changeable by an initiator; a value of 1 means the bit function is directly changeable by an initiator (see Mode Select command).
The buffer full ratio is taken to be a percentage of the smaller of: the buffer size or the remaining transfer length. For example, if the buffer full ratio is 80h (128 Decimal) (indicating a 128/256 or 50% value), the transfer length of a read command is 20h blocks, and the buffer size is 30h blocks, the arbitration begins when 10h blocks (50% of the transfer length of 20h blocks) is in the buffer. 148 Bus Inactivity Limit Not supported (bytes 4 and 5).
12.13.4 Format Parameters page (03h) The Format Parameters page implementation is defined in Table 149. This table summarizes the function and defines the default values for each bit. See the individual drive’s Product Manual, Volume 1, Mode Sense Data section for changeable values. The only time this page of parameters may be sent is immediately before sending a Format Unit command to the disc drive.
Table number 149 Field definitions (listed alphabetically) Alternate Sectors Per Zone The number of spare sectors to be reserved for the defined defect management zone. 0 149 No sectors are to be reserved in each zone for defect management. This is to accommodate hosts that want to manage the defects themselves. Alternate Tracks Per Volume The number of spare tracks to be reserved at the end of the drive volume. The disc drive uses these locations for replacing defective sectors.
149 Sectors Per Track The average number of physical sectors the disc drive has per disc track. This value depends on the selected sector size and ZBR zones. The number of user accessible sectors per track may be fewer than the reported value, since sectors per track includes sectors set aside for defect management. This value cannot be used to calculate drive user-accessible capacity. Note.
12.13.5 Rigid Disc Drive Geometry Parameters page (04h) The Rigid Disc Drive Geometry Parameters page implementation is defined in Table 150. This table summarizes the function and defines the default value. See the individual drive’s Product Manual, Volume 1, Mode Sense Data section, for changeable values.
150 Landing Zone Cylinder Not applicable. 150 Medium Rotation Rate On Mode Sense commands, these bytes return drive nominal rotation rate in revolutions per minute for synchronous spindle operation. The bytes have no meaning for Mode Select. 150 Number of Cylinders The number of physical cylinders used for data storage. This may or may not include spare cylinders set aside for flaw reallocation. See individual drive’s Product Manual, Volume 1, which specifies what the drive reports.
12.13.6 Verify Error Recovery page (07h) The Verify Error Recovery page specifies the error recovery parameters the target uses during the Verify command and the verify operation of the Write and Verify command.
151 151 EER (Enable Early Recovery) 1 The disc drive applies on-the-fly T>1 ECC correction as soon as possible, before attempting other retry mechanisms, and without reporting successful corrections to the host as recovered error. Seek error retries and message system errors are not affected by this bit. When this bit is set to 1, the DCR bit must be zero (0).
12.13.7 Caching Parameters page (08h) for Mode Sense/Mode Select The Caching Parameters page defines the parameters that affect the use of the cache.
152 Demand Read Retention Priority The cache replacement algorithm does not distinguish between retention in the cache of host-requested data and prefetch data. Therefore, this half byte is always zero (0). 152 Disable Prefetch Transfer Length Prefetch is disabled for any SCSI Read command whose requested transfer length exceeds this value.
If the Non-Cache Segment Size field = 0 or the Non-Cache Segment Size field value + Cache Segment Size field > buffer size, then the vendor determines the cache function. 152 Number of Cache Segments The number of segments into which the host requests the drive divide the cache. 152 Page Code 08h 152 Page Length 12h 152 Caching Parameters page for Mode Sense/Mode Select page code. The length of the Caching Parameters page (in bytes).
12.13.8 Mode Sense/Mode Select Control Mode page (0Ah) The Control Mode page provides controls over several SCSI-2 features which are applicable to all device types such as tagged queuing, extended contingent allegiance, asynchronous event notification, and error logging. See the individual drive’s Product Manual, Volume 1, Mode Sense Data table for changeable values.
the test. Device servers supporting Self-Test Code field values other than 000b for the Send Diagnostic command (see Section 12.47) support the Extended Self-Test Completion Time field. 153 153 GLTSD (Global Logging Target Save Disable) 0 The target provides a target-defined method for saving log parameters (Logged to disk). 1 Either the target has disabled the target-defined method for saving log parameters or, when set by the initiator, specifies that the target-defined method will be disabled.
12.13.9 Notch page (0Ch) The Notch page contains parameters for direct access devices that implement a variable number of blocks per cylinder and support this page. Each section of the drive with a different number of blocks per cylinder is referred to as a notch. These values are not changeable. Note.
154 154 LPN (Logical or Physical Notch) 0 The notch boundaries are based on the physical parameters of the drive. The cylinder is considered most significant, the head least significant. 1 The notch boundaries are based on logical blocks on the drive. Maximum Number of Notches The maximum number of notches supported by the drive. 154 154 ND (Notched Drive) 0 The device is not notched. All other parameters in this page will be returned as zero (0) by the drive. 1 The drive is notched.
12.13.10 XOR Control Mode page (10h) The XOR Control Mode page provides the initiator with the means to obtain or modify certain XOR target operating parameters.
155 PS (Parameter Savable) This bit is only used with the Mode Sense command. This bit is not used with the Mode Select command. 1 155 The drive is capable of saving the page in a nonvolatile vendor-specific location. Rebuild Delay The minimum time (in milliseconds) between successive Read commands during a rebuild operation. 155 XORDis This bit enables and disables XOR operations within a device. 0 Enables XOR operations. 1 Disables XOR operations.
12.13.11 Fibre Channel Interface Control page (19h) The Fibre Channel Interface Control page controls options relevant to Fibre Channel protocol. It is intended for the control of features unique to Fibre Channel protocol that are not suitable for control by login or other techniques defined for Fibre Channel. Both the current and saved values of Mode page 19h, byte 3, are changeable using the Mode Select command.
156 156 DLM (Disable Loop Master) 1 Indicates that a target attached to an FC-AL-2 loop shall not participate in loop master arbitration and shall not become loop master. The target shall only repeat LISM frames it receives. 0 The target may participate in loop master arbitration in the normal manner and, if successful, may become loop master during the loop initialization process. Targets not attached to an arbitrated loop shall ignore the DLM bit.
12.13.12 Power Condition page (1Ah) The Power Condition page provides the initiator the means to control the length of time a logical unit will delay before changing its power requirements. There is no notification to the initiator that a logical unit has entered into one of the power conditions. On receipt of this command, the device adjusts itself to the power condition which allows the command to execute.
157 Standby Condition Timer The inactivity time (in 100 millisecond increments) that the logical unit shall wait before entering the Standby condition. 242 Fibre Channel Interface Manual, Rev.
12.13.13 Informational Exceptions Control page (1Ch) The Informational Exceptions Control page (see Table 158) defines the methods used by the target to control the reporting and the operations of specific informational exception conditions. This page only applies to informational exceptions that report an additional sense code of Failure Prediction Threshold Exceeded to the application client. Mode page 1Ch may be used by the drive to implement the S.M.A.R.T. system. S.M.A.R.T.
158 MRIE (Method of Reporting Informational Exceptions) Indicates the methods that are used by the target to report informational exception conditions (see Table 159). The priority of reporting multiple information exceptions is vendor specific. Table 159: Method of Reporting Informational Exceptions field MRIE 158 No reporting of informational exception condition. This method instructs the target to not report information exception conditions. 1h Asynchronous event reporting.
158 158 Perf (Performance) 0 Informational exception operations that are the cause of delays are acceptable. 1 The target does not cause delays while doing informational exception operations. A Perf bit set to one may cause the target to disable some or all of the informational exceptions operations, thereby limiting the reporting of informational exception conditions. Report Count Indicates the number of times to report an informational exception condition to the application client.
12.14 Mode Sense (10) command 5Ah The Mode Sense (10) command provides a means for the drive to report drive operating mode parameters to the initiator. It is a complementary command to the Mode Select (10) command.
Table 161: Mode Sense (10) data Bit 7 6 5 4 3 2 1 0 Byte 0 (MSB) Sense Data Length 1 (LSB) 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 (LSB) Medium Type 3 0 0 0 WP DPO-FUA Reserved 4 Reserved 5 Reserved 6 (MSB) 0 0 Reserved 0 0 0 Block Descriptor Length (8 decimal) 7 Table number 161 0 0 0 0 0–7 Block Descriptor Data (see Table 143) 0–n Mode Sense Page Headers and Their Parameters 1 Field definitions (listed alphabetically) Block Descriptor Data See Table 1
12.15 Move Medium command A7h Not implemented. If the drive receives this command, a Check Condition status is sent. 248 Fibre Channel Interface Manual, Rev.
12.16 Persistent Reserve In command 5Eh Use the Persistent Reserve In command to obtain information about persistent reservations and reservation keys that are active within a device server. Use this command in conjunction with the Persistent Reserve Out command (see Section 12.17). Note. The actual length of the Persistent Reserve In parameter data is available in a parameter data field.The Allocation Length field in the CDB indicates how much space has been reserved for the returned parameter list.
12.16.1 Persistent Reserve In parameter data for read keys The format for the parameter data provided in response to a Persistent Reserve In command with the Read Keys service action is shown in Table 163. Table 163: Persistent Reserve In parameter data for read keys Bit Byte 7 0 (MSB) 6 5 4 3 2 1 0 Generation 3 (LSB) 4 (MSB) Additional Length (n - 7) 7 (LSB) Reservation key list 8 (MSB) First reservation key 15 Table number 163 (LSB) . . . (MSB) n-7 : n (MSB) . . .
12.16.2 Persistent Reserve In parameter data for read reservation The format for the parameter data provided in response to a Persistent Reserve In command with the Read Reservation service action is shown in Table 164.
Table 165: Persistent Reserve In Reservation Descriptor Bit Byte 7 0 (MSB) 6 5 : 4 3 2 1 Reservation Key 7 8 (LSB) (MSB) : Scope-specific Address 11 12 (LSB) Reserved 13 14 0 Scope Type (MSB) Obsolete (no longer used) 15 165 (LSB) Reservation Key The reservation key is the registered reservation key under which the reservation is held. If initiators use unique keys, the application should be able to associate the reservation key with the initiator that holds the reservation.
165 Type This field determines the characteristics of the persistent reservation being established for all data blocks within the extent or logical unit. The required device server support descriptions below are divided into two paragraphs. The first paragraph defines the required handling for read operations. The second paragraph defines the required handling for write operations.
12.17 Persistent Reserve Out command 5Fh The Persistent Reserve Out command is used to request service actions that reserve a logical unit or element for the exclusive or shared use of a particular initiator. This command is used in conjunction with the Persistent Reserve In command and should not be used with the Reserve and Release commands. Initiators performing Persistent Reserve Out service actions are identified by a reservation key provided by the application client.
166 Service Action When processing Persistent Reserve Out service actions, the device server increments the generation value as specified in Section 12.16.1 (see page 250). 166 00h Register. Register a reservation key with the device server. 01h Reserve. Create a persistent reservation with a specified scope and type. 02h Release. Release a persistent reservation for the requesting initiator. 03h Clear. Clear all reservation keys and all persistent reservations. 04h Preempt.
12.17.1 Persistent Reserve Out parameter list The parameter list for the Persistent Reserve Out command is defined in Table 167. All fields are sent on all Persistent Reserve Out commands, even if the field is not required for the specified service action and scope values.
Table 168: Persistent Reserve Out service actions and valid parameters Parameters Service action 167 Allowed scope Service action reservation key Type Element or element parameters Register Ignored Ignored Valid Ignored Reserve Logical Unit Element Valid Valid Ignored Ignored Ignored Valid Release Logical Unit Element Valid Valid Ignored Ignored Ignored Valid Clear Ignored Ignored Ignored Ignored Preempt Logical Unit Element Valid Valid Valid Valid Ignored Valid Preempt and Cl
12.18 Prefetch (10) command 34h The Prefetch (10) command requests that the drive read and transfer the specified logical blocks to the drive's cache memory. No data shall be transferred to the initiator.
12.19 Prefetch (16) command 90h The Prefetch (16) command requests that the drive read and transfer the specified logical blocks to the drive's cache memory. No data shall be transferred to the initiator.
169 Transfer Length The Transfer Length field specifies the number of contiguous logical blocks of data that shall be transferred to the drive's cache memory. 0 The contiguous logical blocks up to and including the last logical block of the logical unit shall be transferred to the drive's cache memory. Any value other than 0 indicates the number of logical blocks that shall be transferred. The drive may elect to not transfer logical blocks that already are contained in the cache memory.
12.20 Prevent/Allow Medium Removal command 1Eh Not implemented. If the drive receives this command, the drive terminates with Check Condition status and sets an Illegal Request sense key. Fibre Channel Interface Manual, Rev.
12.21 Read (6) command 08h The Read (6) command requests the disc drive to transfer data to the initiator. Table 171: Read (6) command (08h) Bit Byte 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 0 0 1 0 0 0 (MSB) Reserved Logical Block Address 2 3 Table number 171 (LSB) 4 Transfer Length 5 Control Field definitions (listed alphabetically) Control See Control Bytes in Section 11.2.1.6. 171 Logical Block Address The logical block at which the read operation will begin.
The disc drive contains a large buffer and implements an optional prefetch and segmented cache function whereby the requested Read data is read into the buffer, plus an additional amount, depending on the cache control parameters. See Prefetch and Multisegmented Cache Control section in the individual drive’s Product Manual, Volume 1, for more information. This command is terminated with a Reservation Conflict status and no data is read if any reservation access conflict (see Section 12.39) exists.
12.22 Read (10) command 28h The Read (10) command requests that the target transfer data to the initiator. This command is implemented with the drive-specific parameters shown in Table 172. This command operates the same as the Read (6) command (see Section 12.21) except that in the CDB for this command a four-byte logical block address and a two-byte transfer length may be specified. The data value most recently written in the addressed logical block is returned to the Host.
172 RelAdr (Relative Address) This function is not supported by drives described in this manual. 172 Transfer Length The number of contiguous logical blocks of data transferred. A Transfer Length of zero (0) indicates that no logical blocks are transferred. This condition is not considered an error. Any other value indicates the number of logical blocks that are transferred. If any of the following conditions occur, this command returns a Check Condition status and the sense key is set as indicated.
12.23 Read (12) command A8h The Read (12) command requests that the target transfer data to the initiator.
173 RelAdr (Relative Address) This function is not supported by drives described in this manual. 173 Transfer Length The number of contiguous logical blocks of data transferred. A Transfer Length of zero (0) indicates that no logical blocks are transferred. This condition is not considered an error. Any other value indicates the number of logical blocks that are transferred. If any of the following conditions occur, this command returns a Check Condition status and the sense key is set as indicated.
12.24 Read (16) command (88h) The Read (16) command requests that the target transfer data to the initiator.
0 174 The target satisfies the command by accessing the cache memory. For read operations, any logical blocks that are contained in the cache memory are transferred to the initiator directly from the cache memory. Logical Block Address The logical block at which the read operation begins, if RelAdr bit is zero (see RelAdr bit description). 174 RelAdr (Relative Address) This function is not supported by drives described in this manual.
12.25 Read Buffer command 3Ch The Read Buffer command is used in conjunction with the Write Buffer command as a diagnostic function for testing disc drive memory and the integrity of the FC-AL. This command will not alter the medium. Command format is shown in Table 175.
12.25.1 Read Combined Descriptor Header and Data mode (000b) In this mode, a four-byte Read Buffer header followed by the data bytes are returned to the initiator in a data transfer. The Buffer ID and Buffer Offset fields are not used by drives supported by this manual, and must be zero.
nates the Data In phase when allocation length bytes of header plus data have been transferred or when all available header and buffer data have been transferred to the initiator, whichever is less. 177 Offset Boundary This field contains the boundary alignment with the selected buffer for subsequent Write Buffer and Read Buffer commands. This is interpreted as a power of two. 272 Fibre Channel Interface Manual, Rev.
12.26 Read Capacity (10) command 25h The Read Capacity (10) command provides a means for the initiator to request the capacity of the disc drive information.
In response to the Read Capacity (10) command, the drive returns eight bytes of Read Capacity data to the host. The contents of the eight bytes are listed in Table 179. Table 179: Read Capacity data Byte 274 Description 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) Fibre Channel Interface Manual, Rev.
12.27 Read Capacity (16) command 9Eh The Read Capacity (16) command provides a means for the application client to request information regarding the capacity of the block device. This command is implemented as a service action of the Service Action In operation code.
1 180 The information returned is the Logical Block Address and Block Length (in bytes) of the last Logical Block Address after which a substantial delay (defined as approximately one millisecond for the typical disc drive) in data transfer is encountered. This returned Logical Block Address is greater than or equal to the Logical Block Address specified in the Command Descriptor Block. This reported Logical Block Address is the last block prior to a cylinder boundary.
12.28 Read Defect Data (10) command 37h The Read Defect Data command requests that the target transfer the medium defect data to the initiator. If the drive is unable to access any medium defect data, it terminates the command with Check Condition status. The sense key is set to either Medium Error if a medium error occurred or No Sense if the list does not exist and the additional sense code is set to Defect List Not Found.
182 Defect List Format Bits 2, 1, 0 in the CDB should be 1 0 0, respectively, to signify a defect list in the Bytes from Index format, or 1 0 1, respectively, to signify a defect list in the Physical Sector format. If neither of these two, the disc drive responds with the defect list in the drive’s default format (physical sector) and creates the Check Condition status with Recovered Error sense key (1h) and additional sense error code (1C) at the end of the Read Defect Data transfer.
Table 183: Defect List Header description Bit 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 G 1 0 0 or 1 0 1 Byte 0 Reserved 1 0 0 0 Reserved P CDB Defect List Format Table number 183 2 Defect List Length (MSB) (Value is 8 times the number of defects) 3 Defect List Length (LSB) 4–n Defect Descriptor Bytes Field definitions (listed alphabetically) CDB (Command Descriptor Block) The disc drive interprets the P and G bits (bits 4 and 3 of byte 2 of the CDB) as follows: 183 183 Bit P
12.29 Read Defect Data (12) command B7h The Read Defect Data (12) command requests that the target transfer the medium defect data to the initiator. If the logical unit is reserved, a reservation conflict occurs when a Read Defect Data (12) command is received from an initiator other than the one holding a logical unit reservation. This command is rejected with Reservation Conflict status if the reservation conflict is due to a logical unit reservation.
1 0 Return the manufacturer’s original ETF list only. This list reflects the manufacturer’s original ETF list. These defects may or may not have been reallocated, depending on the last Format command received (the last format may or may not have requested the P list flaws be reallocated during the format function). 1 1 Return all lists. The returned list contains all of the requested drive’s defect lists (i.e., P, G, C, and D) regardless of whether these lists have been reallocated by the drive.
Table 185: Defect List (12) Header description Bit 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 0 G 1 0 0 or 1 0 1 Byte 0 Reserved 1 0 0 0 Reserved P CDB Defect List Format 2 Reserved 3 Reserved 4 (MSB) 5 Defect List Length 6 7 (LSB) 0–n Table number 185 Defect Descriptor Bytes Field definitions (listed alphabetically) CDB (Command Descriptor Block) The disc drive interprets the P and G bits (bits 4 and 3 of byte 2 of the CDB) as follows: 185 185 Bit P Bit G Interpretation 0
12.30 Read Element Status command B4h Not implemented. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev.
12.31 Read Long command 3Eh The Read Long command requests that the target transfer data to the initiator. The data passed during the Read Long command shall include the data bytes and the ECC bytes recorded on the medium. The most recent data written, or to be written, in the addressed logical block shall be returned. Read Long is independent of the Read-Write Error Recovery mode page but does allow retries.
12.32 Reassign Blocks command 07h The Reassign Blocks command requests the target to reassign the defective logical blocks to an area on the logical unit reserved for this purpose. After sending the Reassign Blocks command, the initiator transfers a defect list that contains the logical block addresses to be reassigned. The disc drive reassigns the physical medium used for each logical block address in the list.
Reassign Blocks defect list The Reassign Blocks defect list contains a four-byte header followed by one or more defect descriptors. The length of each defect descriptor is four bytes. If the logical unit has insufficient capacity to reassign all of the defective logical blocks, the command terminates with a Check Condition status and the sense key is set to Hardware Error and the additional sense code set to No Defect Spare Location Available.
12.33 Receive Diagnostic Results command 1Ch The Receive Diagnostic Results command requests analysis data after completion of a Send Diagnostic command or SCSI-3 Enclosure Services (SES) pages be sent to the initiator. The disc drive supports the optional Page format, wherein the initiator sends additional pages after a Send Diagnostic command.
189 Page Code The Page Code number of the Diagnostic page to be received. See Table 190 for page code numbers and descriptions. Table 190: Receive Diagnostics page code descriptions 189 Page Code Description Reference Table 00h List of Supported Diagnostic Pages 191 01h - 0Fh SCSI Enclosure Services Pages 193 40h Address Translation Page 194 none Default Self Test Diagnostic Results 197 PCV (Page Code Valid) 0 The Page Code is ignored.
Enclosure Services Information (ESI) The drives supported by the manual do not process the contents of the SCSI Enclosure Service (SES) pages. The drive attempts to transfer the page contents to or from the enclosure using the Enclosure Services Interface (ESI) as directed by the command. Errors detected in the transfer are returned to the initiator in response to the command.
Translate Address page The Translate Address page allows the initiator to translate a logical block address into a physical sector address or a physical sector address to a logical block address. The address to be translated is passed to the target during the data transfer associated with the Send Diagnostic command and the results are returned to the initiator during the Data In phase following the Receive Diagnostic Results command.
194 Translated Format The value from the Send Diagnostic command translate format field (see Table 209). The values are 000 (Logical block format) or 101 (Physical sector address format).
Table 197: Default self-test diagnostic data bytes Bit Byte 0 7 6 5 4 3 2 1 0 (MSB) Additional Length 1 (LSB) 2 FRU Code (most probable) 3 FRU Code 4 FRU Code 5 FRU Code (least probable) 6 (MSB) Error Code 7 (LSB) 8-n Table number 197 Additional Vendor-Unique Fault Information Field definitions (listed alphabetically) Additional Length This 2-bytes value indicates the number of additional bytes included in the diagnostic data list.
12.34 Release (6) command 17h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.35 Release (10) command 57h Obsolete. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev.
12.36 Report Device Identifier command A3h The Report Device Identifier command (see Table 198) requests that the drive send device identification information to the initiator.
Report Device Identifier Parameter List This list contains the length (in bytes) of the parameter list and the logical unit’s identifier. The execution of a Report Device Identifier command may require you to enable nonvolatile memory within the logical unit. If the nonvolatile memory is not ready, the device server returns Check Condition status rather than wait for the device to become ready.
12.37 Report LUNs command A0h The Report LUNs command requests that the peripheral device logical unit numbers of known logical units in the target be sent to the application client. The Report LUNs command returns information about only those logical units to which commands may be sent. When the HiSupport bit is one (see Table 105, Disc drive inquiry data format), the device server supports the Report LUNs command.
The device server shall report the Logical Unit Numbers of configured logical units using the format shown in Table 201. Table 201: Report LUNs parameter list format Bit 7 6 5 4 3 2 1 0 Byte 0 (MSB) LUN List Length (n-7) 3 4 (LSB) (MSB) Reserved 7 (LSB) LUN List 8 (MSB) First LUN 15 (LSB) . . .
12.38 Request Sense command 03h The Request Sense command requests that the disc drive transfer sense data to the initiator in the format shown in Table 202. The sense data is valid after a Check Condition status returned on the prior command. Sense data is returned in the Fibre Channel Protocol Response frame with the Check Condition bypassing the need for the Request Sense command. Sense data must be cleared upon execution of any subsequent command.
12.39 Reserve (6) command 16h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.40 Reserve (10) command 56h Obsolete. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev.
12.40.1 Logical unit reservation When the Extent bit is zero, this command requests the entire disc drive to be reserved for exclusive use of the initiator until the reservation is superseded by another valid Reserve command from the initiator that made the reservation, released by a Release command from the same initiator, by a LIP Reset from any initiator, or be a hard Reset condition. A logical unit reservation is not granted if the logical unit is reserved by another initiator.
12.40.4 Parameter list format for third-party addressing The parameter list for the ten-byte Reserve and Release commands. Third-party addressing is eight bytes in length. The following table defines the format for the parameter list.
12.41 Rezero Unit command 01h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.42 Search Data Equal command 31h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.43 Search Data High command 30h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.44 Search Data Low command 32h Obsolete. If the drive receives this command, a Check Condition status is sent. 12.45 Seek (6) command 0Bh Obsolete.
12.46 Seek (10) command 2Bh The Seek (10) command requests that the disc drive seek to the specified Logical Block Address. This command is implemented with the disc drive specific parameters listed in Table 204.
12.47 Send Diagnostic command 1Dh This command requests that the disc drive perform diagnostic tests on itself, or perform other optional operations. Table 205 shows the format of the Send Diagnostic command as implemented by the disc drive. When the Self Test bit is zero, this command is usually followed by a Receive Diagnostic Results command and a subsequent data transfer that returns data to the initiator.
Table 206: Supported Send Diagnostic pages Table number Page Code Description Reference 00h Supported Diagnostic pages Table 208 01h - 0Fh SCSI Enclosure Services Information (ESI) pages Table 207 40h Translate Address page Table 209 Field definitions (listed alphabetically) 206 Enclosure Services Information (ESI) The drives supported by the manual do not process the contents of the SCSI Enclosure Service (SES) pages.
- accept the parameter list, and if no errors are detected in the parameter list, return Good status. The requested diagnostic operation and the preparation of the parameter data to be returned are performed upon receipt of a Receive Diagnostic Results command. 1 205 205 Directs the device server to complete the target’s Default Self-Test.
12.47.1 Supported Diagnostic page–Send Diagnostic This page instructs the disc drive to make available the list of all supported diagnostic pages to be returned by a subsequent Receive Diagnostic Results command. The definition of this page for the Send Diagnostic command includes only the first four bytes (Receive Diagnostic version given in Table 191). If the page length field is not zero, the disc drive terminates the Send Diagnostic command with a Check Condition status.
12.47.2 Translate Address page–Send Diagnostic The translate address page allows the initiator to translate a logical block address into a physical sector address or a physical sector into a logical block address. The address to be translated is passed to the disc drive with Send Diagnostic command and the results are returned to the initiator during the data in phase following the Receive Diagnostic Results command.
12.47.3 Diagnostic page–Send Diagnostic The Diagnostic page instructs the drive to turn the drive fault LED on or off. This page is used only by the Send Diagnostic command (see Table 210). Table 210: Diagnostic page–Send Diagnostic command Bit Byte 7 0 Page Code (A0h) 1 Reserved 2 6 5 4 3 2 1 0 (MSB) Page Length (0002h) 3 (LSB) Reserved 4 5 Table number 210 Page Code Diagnostic page-Send Diagnostic command page code.
12.48 Set Device Identifier command A4h The Report Device Identifier command (see Table 211) requests that the device identifier information in the logical unit be set to the value received in the Set Device Identifier parameter list. On successful completion of the command, a Unit Attention is generated for all initiators except the one that issued the service action. When reporting the Unit Attention condition, the additional sense code is set to Device Identifier Changed.
Set Device Identifier Parameter List Table 212: Report Device Identifier parameter list Bit 7 6 5 4 3 2 1 0 Byte 0 : n Table number 199 Identifier Field definitions (listed alphabetically) Identifier This field contains the vendor-specific value to be returned in Report Device Identifier commands. Fibre Channel Interface Manual, Rev.
12.49 Set Limits command 33h Not implemented. If the drive receives this command, a Check Condition status is sent. 312 Fibre Channel Interface Manual, Rev.
12.50 Start/Stop Unit command 1Bh The Start/Stop Unit command requests that the target enable the logical unit for further operations (start), or stop spindle rotation (stop). The disc drive is able to execute the following commands when the drive spindle is not rotating, or in a simulated stopped condition.
12.51 Synchronize Cache (10) command 35h The Synchronize Cache (10) command ensures that logical blocks in the cache memory, within the specified range, have their most recent data value recorded on the physical medium. If a more recent data value for a logical block within the specified range exists in the cache memory than on the physical medium, then the logical block from the cache memory is written to the physical medium.
12.52 Synchronize Cache (16) command 91h The Synchronize Cache (16) command ensures that logical blocks in the cache memory, within the specified range, have their most recent data value recorded on the physical medium. If a more recent data value for a logical block within the specified range exists in the cache memory than on the physical medium, then the logical block from the cache memory is written to the physical medium.
12.53 Test Unit Ready command 00h The Test Unit Ready command provides a means to verify the logical unit is ready. This is not a request for a self test. If the logical unit (drive) can accept an appropriate medium access command without returning Check Condition status, the drive returns a Good status. If the drive cannot become operational or is in a state such that an initiator action (e.g.
12.54 Verify (10) command 2Fh The Verify (10) command requests that the target verify the data written on the medium. This command is implemented with the disc drive specific parameters listed in Table 217. The drive disconnects while this command is being executed if the initiator supports disconnect/reconnect.
12.55 Verify (12) command AFh The Verify (12) command requests that the target verify the data written on the medium. This command is implemented with the disc drive specific parameters listed in Table 218. The drive disconnects while this command is being executed if the initiator supports disconnect/reconnect.
218 Verification Length The number of contiguous logical blocks of data that are verified. A Verification Length of zero indicates that no logical blocks are verified (an Implied Seek is still performed). This condition is not considered an error. Any other value indicates the number of logical blocks that are verified. Fibre Channel Interface Manual, Rev.
12.56 Verify (16) command 8Fh The Verify (16) command requests that the target verify the data written on the medium. This command is implemented with the disc drive specific parameters listed in Table 218. The drive disconnects while this command is being executed if the initiator supports disconnect/reconnect.
219 RelAdr (Relative Address) This function is not supported by drives described in this manual. 219 Verification Length The number of contiguous logical blocks of data that are verified. A Verification Length of zero indicates that no logical blocks are verified (an Implied Seek is still performed). This condition is not considered an error. Any other value indicates the number of logical blocks that are verified. Fibre Channel Interface Manual, Rev.
12.57 Write (6) command 0Ah The Write (6) command requests that the disc drive write the data transferred by the initiator to the medium (discs). Table 220: Write (6) command (0Ah) Bit 7 6 5 4 3 2 1 0 0 0 0 0 0 1 0 1 0 1 0 0 0 (MSB) Byte Reserved Logical Block Address 2 3 Table number 220 (LSB) 4 Transfer Length 5 Control Field definitions (listed alphabetically) Control See Control Bytes in Section 11.2.1.6.
If any of the following conditions occur, this command is terminated with a Check Condition status, and if extended sense is implemented, the sense key is set as indicated in the following table. This table does not provide an exhaustive enumeration of all conditions that may cause the Check Condition status. Condition Sense key Invalid logical block address Volume Overflow. Set the extended sense information bytes to the logical block address of the first invalid address.
12.58 Write (10) command 2Ah The Write (10) command requests that the disc drive write to the medium the data transferred by the initiator. This command is implemented with the disc drive specific parameters listed in Table 221. Refer also to the Write Caching section in the individual drive’s Product Manual, Volume 2, for information on write cache control.
This command operates the same as the Write (6) command (Section 12.57) except that in the CDB for this command a four-byte logical block address and a two-byte transfer length may be specified. This command terminates with a Reservation Conflict status if any reservation access conflict (see Section 12.39) exists, and no data is written. If any of the following conditions occur, this command terminates with a Check Condition status and the sense key is set as indicated in the following table.
12.59 Write (12) command AAh The Write (12) command requests that the disc drive write to the medium the data transferred by the initiator. This command is implemented with the disc drive specific parameters listed in Table 221. Refer also to the Write Caching section in the individual drive’s Product Manual, Volume 2, for information on write cache control.
This command operates the same as the Write (6) command (Section 12.57) except that in the CDB for this command a four-byte logical block address and a four-byte transfer length may be specified. This command terminates with a Reservation Conflict status if any reservation access conflict (see Section 12.39) exists, and no data is written. If any of the following conditions occur, this command terminates with a Check Condition status and the sense key is set as indicated in the following table.
12.60 Write (16) command 8Ah The Write (16) command requests that the disc drive write to the medium the data transferred by the initiator. This command is implemented with the disc drive specific parameters listed in Table 221. Refer also to the Write Caching section in the individual drive’s Product Manual, Volume 2, for information on write cache control.
222 Transfer Length The number of contiguous logical blocks of data that are transferred. A Transfer Length of zero (0) indicates no logical blocks are transferred. This condition is not considered an error and no data is written. Any other value indicates the number of logical blocks that are transferred. This command operates the same as the Write (6) command (Section 12.57) except that in the CDB for this command a eight-byte logical block address and a four-byte transfer length may be specified.
12.61 Write and Verify (10) command 2Eh The Write and Verify (10) command requests that the target write the data transferred from the initiator to the medium and then verify that the data is correctly written. The data is only transferred once from the initiator to the drive.
12.62 Write and Verify (12) command AEh The Write and Verify (12) command requests that the target write the data transferred from the initiator to the medium and then verify that the data is correctly written. The data is only transferred once from the initiator to the drive.
225 Transfer Length The number of contiguous logical blocks of data that are transferred. A transfer length of zero indicates that no logical blocks are transferred. This condition is not considered an error and no data is written. Any other value indicates the number of logical blocks that are transferred. For systems that support disconnection, the disc drive disconnects during the execution of this command. 332 Fibre Channel Interface Manual, Rev.
12.63 Write and Verify (16) command 8Eh The Write and Verify (16) command requests that the target write the data transferred from the initiator to the medium and then verify that the data is correctly written. The data is only transferred once from the initiator to the drive.
226 RelAdr (Relative Address) This function is not supported by drives described in this manual. 226 Transfer Length The number of contiguous logical blocks of data that are transferred. A transfer length of zero indicates that no logical blocks are transferred. This condition is not considered an error and no data is written. Any other value indicates the number of logical blocks that are transferred.
12.64 Write Buffer command 3Bh The Write Buffer command may be used in conjunction with the Read Buffer command as a diagnostic function for testing the disc drive’s data buffer memory and the FC-AL integrity. When used in a diagnostic mode, the medium is not accessed during the execution of this command. Additional modes are provided for downloading and saving executable microcode. The function of this command and the meaning of the fields within the Command Descriptor Block depend on the Mode field.
Table 228: Mode definitions Bit 2 Bit 1 Bit 0 0 0 0 Write combined header and data (Section 12.64.1) 0 1 0 Write data (Section 12.64.2) 1 0 0 Download microcode 1 0 1 Download microcode and save (Section 12.64.3) 1 1 0 Download microcode with offsets 1 1 1 Download microcode with offsets and save (Section 12.64.4) 336 Mode Definition Fibre Channel Interface Manual, Rev.
12.64.1 Combined Header and Data mode (000b) In this mode, data to be written to the disc drive’s data buffer is preceded by a four-byte header. The Byte Transfer Length includes a four-byte header and the Write Buffer data. A transfer length of zero indicates that no data transfer takes place. This condition does not create the Check Condition status.
12.64.4 Download Microcode with Offsets and Save mode (111b) In this mode, the initiator may split the transfer of the vendor-specific microcode or control information over two or more write buffer commands. If the logical unit cannot accept this command because of some device condition, the logical unit terminates each write buffer command with this mode (111b) with a Check Condition status, a sense key of Illegal Request, and sets the additional sense code to Command Sequence Error.
12.65 Write Long command 3Fh The Write Long command requests that the target write to the medium the data transferred by the initiator. The data passed during the WRITE LONG command is implementation specific, but shall include the data bytes and the ECC bytes to be written to the single logical block addressed in the command. The Read Long command is usually issued before issuing a Write Long command.
12.66 Write Same (10) command 41h The Write Same (10) command requests that the target write the single block of data transferred by the initiator to the medium multiple times.
12.67 Write Same (16) command 93h The Write Same (16) command requests that the target write the single block of data transferred by the initiator to the medium multiple times.
12.68 XDRead (10) command 52h The XDRead (10) command requests that the target transfer the xor data generated by an XDWrite or Regenerate command to the initiator. If the logical unit is reserved, a reservation conflict occurs when an XDRead command is received from an initiator other than the one holding the logical unit reservation. The command is rejected with Reservation Conflict status if the reservation conflict is due to a logical unit reservation.
12.69 XDRead (32) command 7Fh The XDRead (32) command requests that the target transfer the xor data generated by an XDWrite or Regenerate command to the initiator. If the logical unit is reserved, a reservation conflict occurs when an XDRead command is received from an initiator other than the one holding the logical unit reservation. The command is rejected with Reservation Conflict status if the reservation conflict is due to a logical unit reservation.
Table number 234 Field definitions (listed alphabetically) Additional CDB Length (18h) The Additional CDB Length field indicates the number of additional CDB bytes. This value in the Additional CDB Length field shall be a multiple of 4. If the number of CDB bytes delivered by the service delivery subsystem is not sufficient to contain the number of bytes specified by the Additional CDB Length field, the command shall be terminated with a Check Condition status.
12.70 XDWrite (10) command 50h The XDWrite (10) command requests that the target xor the data transferred with the data on the medium. The resulting xor data is stored by the target until it is retrieved by an XDRead command. The resulting xor data is retrieved by an XDRead command with starting logical block address and transfer length fields that match, or is a subset of, the starting logical block address and transfer length of this command.
For write operations, logical blocks may be transferred directly to the cache memory. Good status may be returned to the application client prior to writing the logical blocks to the medium. Any error that occurs after the Good status is returned is a deferred error, and information regarding the error is not reported until a subsequent command. 1 The device server accesses the media in performing the command prior to returning Good status.
12.71 XDWrite (32) command 7Fh The XDWrite (32) command requests that the target xor the data transferred with the data on the medium. The resulting xor data is stored by the target until it is retrieved by an XDRead command. The resulting xor data is retrieved by an XDRead command with starting logical block address and transfer length fields that match, or is a subset of, the starting logical block address and transfer length of this command.
Table number 236 Field definitions (listed alphabetically) Additional CDB Length The Additional CDB Length field indicates the number of additional CDB bytes. This value in the Additional CDB Length field shall be a multiple of 4. If the number of CDB bytes delivered by the service delivery subsystem is not sufficient to contain the number of bytes specified by the Additional CDB Length field, the command shall be terminated with a Check Condition status.
12.72 XDWriteRead (10) command 53h The XDWriteRead (10) command requests that the target xor the data transferred (data-out) with the data on the medium and return the resulting xor data (data-in). This is the equivalent to an XDWrite (10) command followed by an XDRead (10) command with the same Logical Block Address and Transfer Length. This command is only available on transport protocols supporting bidirectional commands.
12.73 XDWriteRead (32) command 7Fh The XDWriteRead (32) command requests that the target xor the data transferred (data-out) with the data on the medium and return the resulting xor data (data-in). This is the equivalent to an XDWrite (32) command followed by an XDRead (32) command with the same Logical Block Address and Transfer Length. This command is only available on transport protocols supporting bidirectional commands.
238 Control See Section 11.2.1.6. 238 DPO (Disable Page Out) 1 238 238 Disable Write 0 The data transferred from the initiator is written to the medium after the xor operation is complete. 1 The data is not written to the medium. FUA (Force Unit Access) 1 238 No data is cached. The DPO bit is only meaningful if the RCD bit of Mode Select Page 8 is set false (caching enabled). The Write command does not return Good status until the logical blocks have actually been written on the media.
12.74 XPWrite (10) command 51h The XPWrite (10) command requests that the target xor the data transferred with the data on the medium and then write the xor data to the medium. If the logical unit is reserved, a reservation conflict occurs when a XPWrite command is received from an initiator other than the one holding the logical unit reservation. The command is rejected with Reservation Conflict status if the reservation conflict is due to a logical unit reservation.
12.75 XPWrite (32) command 7Fh The XPWrite (32) command requests that the target xor the data transferred with the data on the medium and then write the xor data to the medium. If the logical unit is reserved, a reservation conflict occurs when a XPWrite command is received from an initiator other than the one holding the logical unit reservation. The command is rejected with Reservation Conflict status if the reservation conflict is due to a logical unit reservation.
240 240 1 The disc drive assigns the logical blocks accessed by this command the lowest priority for being fetched into or retained by the cache. The host knows the logical blocks accessed by the command are not likely to be accessed again in the near future and should not be put in the cache memory nor retained by the cache memory. 0 The host expects that logical blocks accessed by this command are likely to be accessed again in the near future.
13.0 Drive features This section describes several features included for disc drives. Refer to the individual drive’s product manual to determine if your drive supports these features. 13.1 Self-Monitoring Analysis and Reporting Technology Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.) is designed to recognize conditions that indicate imminent drive failure and provide sufficient warning to the host system of impending failure.
The following are examples of segments: a. An electrical segment wherein the logical unit tests its own electronics. The tests in this segment are vendor specific, but some examples of tests that might be included are: a read/write circuitry test and/or a test of the read/write head elements; b. A seek/servo segment wherein a device tests its capability to find and servo on data tracks; and c. A read/verify scan segment wherein a device performs read scanning of some or all of the medium surface.
While the device server is performing a self-test in the background mode, it shall terminate with a Check Condition status any Send Diagnostics command it receives that meets one of the following criteria: a. The Self-test bit is one; or b. The Self-test Code field contains a value other than 000b or 100b. When terminating the Send Diagnostics command, the sense key is set to Not Ready and the additional sense code is set to Logical Unit Not Ready, Self-test In Progress.
Table 241: Device Self-test mode summary When status is returned How to abort the Device Self-test Processing of subsequent commands while Device Self-test is executing Foreground After the self-test is complete Abort Task task management function If the command is Inquiry, Report LUNs, or Request Sense, process normally. Otherwise, terminate with Check Condition status, Not Ready sense key, and Logical Unit Not Ready, Self-test In Progress additional sense code.
14.0 Seagate Technology support services Online Services Internet www.seagate.com for information about Seagate products and services. Worldwide support is available 24 hours daily by e-mail for your questions. Presales Support: www.seagate.com/support/email/email_presales.html or DiscPresales@Seagate.com Technical Support: www.seagate.com/support/email/email_disc_support.html or DiscSupport@Seagate.com mySeagate my.seagate.
Presales, Technical Support and Customer Service Presales Support Our Presales Support staff can help you determine which Seagate products are best suited for your specific application or computer system. Technical Support If you need help installing your drive, consult your system's documentation or contact the dealer's support services department for assistance specific to your system. Seagate technical support is also available to assist you online at support.seagate.
European Support Services For presales and technical support in Europe, dial the toll-free number for your specific country. If your country is not listed here, dial our presales and technical support call center at +1-405-324-4714 from 8:00 A.M. to 11:45 A.M. and 1:00 P.M. to 5:00 P.M. (Central Europe time) Monday through Friday. The presales and technical support call center is located in Oklahoma City, USA. For European warranty service, dial the toll-free number for your specific country.
Asia/Pacific Support Services For Asia/Pacific presales and technical support, dial the toll-free number for your specific country. The Asia/ Pacific toll-free numbers are available from 6:00 A.M. to 10:45 A.M. and 12:00 P.M. to 6:00 P.M. (Australian Eastern time) Monday through Friday, except as noted. If your country is not listed here, direct dial one of our technical support locations. Warranty service is available from 9:00 A.M. to 6:00 P.M. April through October, and 10:00 P.M. to 7:00 P.M.
Appendix A. Glossary This section contains a glossary of terms used in this publication. ABTS Abort Sequence. ABTX Abort Exchange. ACC Accept. ACK Acknowledgment. Active The state of Sequence Initiator until all the Data frames for the Sequence have been transmitted. The state of Sequence Recipient until all the Data frames for the Sequence have been received. The period of time during which frames of a Sequence (or an Exchange) are actively being transmitted or received.
Arbitrated loop topology A topology where L_Ports use arbitration to establish a point-to-point circuit. A configuration that allows multiple ports to be connected serially. Attenuation The transmission medium power loss expressed in units of dB. Available BB_Credit Also called “Available buffer-to-buffer credit.” A transmitter uses this variable to determine permission to transmit frames, and if so, the allowable number of frames to transmit.
Beginning Running Disparity The Running Disparity present at a transmitter when Encoding of the Special Code associated with an Ordered Set is initiated, or at a receiver when Decoding of the Special Character associated with an Ordered Set is initiated. BER See Bit error rate. Bit error rate (BER) The statistical probability of a transmitted bit being erroneously received in a communication system.
Center wavelength (LED) The average of the two wavelengths measured at the half amplitude points of the power spectrum. Centre wavelength (laser) The nominal value of the central wavelength of the operating, modulated laser. This is the wavelength where the effective optical power resides. Character Any Transmission Character associated by FC-1 transmission code with a FC-2 data byte or special code. Transmission characters are generated and interpreted only by FC-1.
Code balance The numerical sum of the 1 bits in any 10 bits in the transmitted bit stream divided by 10 (e.g., 1110100011 has a code balance of 6/10 = 60%). Code bit The smallest time period used by FC-0 for transmission on the media. Code violation An error condition that occurs when a received transmission character cannot be decoded to a valid data byte or special code using the validity checking rules specified by the transmission code.
Connectionless frames Frames participating in connectionless service (i.e., Class 1 frames with SOFc1, Class 2, and Class 3 frames referred to individually or collectively). Connectionless service Communication between two N_Ports performed without a dedicated connection. Continuously increasing relative offset The relationship specified between relative offset values contained in frame (n) and frame (n+1) of an information category within a single Sequence. COR Camp-On Request.
Decoding Validity checking of received transmission characters and generation of valid data bytes and special codes from those characters. Dedicated connection A communicating circuit guaranteed and retained by the Fabric for two given N_Ports. Dedicated duplex A synonym for Class 1 dedicated connection. Dedicated simplex A unidirectional Class 1 connection with ACKs transmitted in Class 2. Delimiter An ordered set used to indicate a frame boundary.
ECL Emitter Coupled Logic. EE_buffer The buffer associated with end-to-end flow control. EE_Credit End-to-End Credit. EE_Credit_CNT End-to-End Credit Count. EIA Electronic Industries Association. Electrical fall time The time interval for the falling edge of an electrical pulse to transition from its 90% amplitude level to its 10% amplitude level. Electrical rise time The time interval for the rising edge of an electrical pulse to transition from its 10% amplitude level to its 90% amplitude level.
Exchange Status Block A logical construct which contains the state of an exchange. An originator N_Port has an Originator Exchange Status Block and the responder N_Port has a Responder Exchange Status Block for each concurrently active Exchange. Exchange_Identifier (X_ID) A generic reference to OX_ID and RX_ID (see Exchange). Exclusive connection A Class 1 dedicated connection without Intermix (see dedicated connection).
Fabric The entity which interconnects various N_Ports attached to it and is capable of routing frames by using only the D_ID information in a FC-2 frame header. Fabric_Name A Name_Identifier associated with a fabric. FACT Fabric Activate Alias.
Fibre A general term used to cover all transmission media specified in FC-PH. Fibre Channel Name A Name_Identifier which is Fibre Channel unique. Fibre optic cable A jacketed optical fibre or fibres. FL_Port An F_Port that contains Arbitrated Loop functions associated with Arbitrated Loop topology. FOTP Fiber optic test procedure. FQXID Fully qualified exchange identifier. Fractional bandwidth A portion of the total bandwidth available on a path.
Hex Hexadecimal notation. HG Hunt Group. Hunt Group A set of N_Ports with a common alias address identifier managed by a single node or common controlling entity. However, FC-PH does not presently specify how a Hunt Group can be configured. Hz Hertz = 1 cycle per second. ID Identifier. Idle See “Idle Word.” Idle Word (Idle) An ordered set of four transmission characters which are normally transmitted between frames. The Idle Word is also referred to as an Idle.
Initial Relative Offset A relative offset value specified at the sending end by an upper level for a given block or subblock and used by the sending FC-2 in the first frame of that block or subblock (see subblock, block, and Relative Offset). Initial Relative Offset value may be zero or non-zero. Initialization For FC-1 level the period beginning with power on and continuing until the transmitter and receiver of that level become operational.
Jitter, deterministic (DJ) Timing distortions caused by normal circuit effects in the transmission system. Deterministic jitter is often subdivided into duty cycle distortion (DCD) caused by propagation differences between the two transitions of a signal and data dependent jitter (DDJ) caused by the interaction of the limited bandwidth of the transmission system components and the symbol sequence. Jitter, random (RJ) Jitter due to thermal noise which may be modeled as a Gaussian process.
Local F_Port The F_Port to which an N_Port is directly attached by a link (see remote F_Port). LOGI Log in. Logical unit A target resident entity that implements a device model and executes SCSI commands sent by an application client. Logical unit identifier Identifier used by an initiator to reference the logical unit. Login_BB_Credit On FC-AL, equal to the number of receive buffers that a receiving NL_ port must have available when a loop circuit is established.
m Meter. MAC Media Access Control. Mandatory A function which is required to be supported by a compliant implementation of FC-PH. MAS Master of link. Mb Mega bit. MB Mega byte. MBd Mega baud. Meaningful A control field or bit shall be applicable and shall be interpreted by the receiver, wherever it is specified as meaningful. Wherever it is specified as “not meaningful,” it shall be ignored (see valid). MM Multimode.
N_Port Identifier A fabric-unique address identifier by which an N_Port is uniquely known. The identifier may be assigned by the fabric during the initialization procedure. The identifier may also be assigned by other procedures not defined in FC-PH. The identifier is used in the S_ID and D_ID fields of a frame. N_Port Name A Name_Identifier associated with an N_Port. NA Not applicable. NAA Network Address Authority. NACT N_Port Activate Alias.
Not Operational A receiver or transmitter that is not capable of receiving or transmitting an encoded bit stream respectively, based on the rules defined by FC-PH for error control. For example, FC-1 is Not Operational during Initialization. ns Nanosecond. NTP Network Time Protocol. OESB Originator Exchange Status Block. OFC Open fibre control. Offset Relative Offset. OFSTP Optical fiber system test practice. OLS Online primitive sequence.
OPN Initiator The port on an Arbitrated Loop that sent the OPN primitive. Optical fibre Any filament or fibre, made of dielectric material, that guides light. Optional Characteristics that are not required by FC-PH. However, if any optional characteristic is implemented, it shall be implemented as defined in FC-PH. Ordered set A transmission word composed of a special character in its first (leftmost) position and data characters in its remaining positions.
Power on state In this state, any circuits or optical devices respond to controls resulting from higher levels. ppm Parts per million. Preferred Address On FC-AL, the AL_PA which an NL_Port attempts to acquire first during loop initialization. Following power-on reset, the preferred address of a private NL_Port is its hard address (if any). Following receipt of a LIP other than LIP(AL_PD,AL_PS), the preferred address of a private NL_Port is its previously acquired address.
Public loop device A device with at least one public NL_Port. Public NL_Port An NL_Port which can observe the rules of either public or private loop behavior. A public NL_Port may have open Exchanges with both private and public NL_Ports concurrently. QoSF Quality of Service Facilitator. QoSR Quality of Service Request. R_CTL Routing Control. R_A_TOV Resource_Allocation_Timeout value. R_RDY Receiver_Ready. R_T_TOV Receiver_Transmitter_Timeout Value.
Receiver sensitivity g The minimum acceptable value of average received signal at point R to achieve a BER <10-12. It takes into account power penalties caused by use of a transmitter with a worst-case output. In the case of an optical path, it does not include power penalties associated with dispersion, jitter, effects related to the modal structure of the source or reflections from the optical path. These effects are specified separately in the allocation of maximum optical path penalty. Note.
Responder The logical function in an N_Port responsible for supporting the Exchange initiated by the Originator in another N_Port. Responder Exchange_Identifier (RX_ID) An identifier assigned by a Responder to identify an Exchange and meaningful only to the Responder. RFI Radio Frequency Interference. RIIN reflection induced intensity noise. RJ Random jitter. RJT Reject. RlN Relative intensity noise. RMC Remove connection. RMS Root mean square. RNC Report node capability. RO Relative offset.
RVC_ID Responder VC_ID. RVCS Read virtual circuit status. Rx Receiver. RX_ID Responder_Exchange_Identifier. s or sec Second(s). S/N signal-to-noise ratio. S_ID Source_Identifier. S_Length Security_Length. S_Type Security_Type. SBCCS Single byte command code sets. SCN State change notification. SCR Stacked connect request. SCSI Small Computer System Interface. SCSI device A device that originates or services SCSI commands. SEQ-CNT Sequence count. SEQ_ID Sequence ID.
Sequence A set of one or more data frames with a common Sequence_ID (SEQ_ID), transmitted unidirectionally from one N_Port to another N_Port with a corresponding response, if applicable, transmitted in response to each data frame. Sequence initiator The N_Port which initiates a sequence and transmits data frames to the destination N_Port.
Spectral width 1. FWHM (Full Width Half Maximum) The absolute difference between the wavelengths at which the spectral radiant intensity is 50 percent of the maximum power. This form is typically used for LED optical sources. 2. RMS The weighted root mean square width of the optical spectrum. See FOTP-127. This form is typically used for laser optical sources. SRSB Sequence recipient status block. SSB Sequence status block.
Task attribute The queuing specification for a task (Simple, Ordered, Head of Queue, ACA). Task identifier The information uniquely identifying a task. Task management function A peer-to-peer confirmed service provided by a task manager that can be invoked by an application client to affect the execution of one or more tasks. TP Twisted pair. TPLS Test process login status. Transceiver A transmitter and receiver combined in one package.
ULP Upper layer protocol. ULP Upper Level Protocol. ULP process A function executing within an FC node which conforms to Upper Layer Protocol (ULP) defined protocols when interacting with ULP processes residing in other FC nodes. Uncategorized information category One of the information categories indicated in the frame header. Unrecognized ordered set A transmission word containing a K28.5 in its first (leftmost) position but not defined to have meaning by FCPH.
VC_RDY Virtual circuit ready. Vendor unique Functions, code values, and bits not defined by FC-PH and set aside for private usage between parties using FC-PH. Caution: different implementations of FC-PH may assign different meanings to these functions, code values, and bits. Virtual circuit (VC) A unidirectional path between two communicating N_Ports that permits Class 4 service to be used. Two virtual circuits are required to form a Class 4 circuit.
392 Fibre Channel Interface Manual, Rev.
Index Numerics 10-bit character 13 8045 ESI pinouts 103 8045 mode 102 8067 ESI command 104 8067 ESI interface pinouts 105 8067 information format 105 8067 mode 104 A Abort Prefetch Caching Parameters page 230 Abort Sequence 52, 53 Abort Task Set FCP CMND Payload 128 Aborted Command disc drive sense keys 149 ABPF. See Abort Prefetch ABTS. See Abort Sequence ACA. See Auto Contingent Allegiance access fairness algorithm 47, 48 access unfairness 48 access window 47 ACK.
Allow Login Without Loop Initialization Fibre Channel Interface Control page 239 Alternate Credit Model F_Port Common Service Parameters 68, 69 N_Port Common Service Parameters 60, 61 Alternate Sector Translate Address page–Receive Diagnostic 290 Alternate Sectors Per Zone Format Parameters page 223, 224 Alternate Track Translate Address page–Receive Diagnostic 290 Alternate Tracks Per Volume Format Parameters page 223, 224 Alternate Tracks Per Zone Format Parameters page 223, 224 ALTSEC.
Read Buffer command 270 Write Buffer command 335 Buffer ID and Buffer Offset fields Download and Save Microcode mode 337 Buffer Offset Read Buffer command 270 Write Buffer command 335 buffer to buffer credit 29 transfer 14 Buffer to Buffer Credit F_Port Common Service Parameters 68 N_Port Common Service Parameters 60 Buffered Class 1 Class 3 Service Parameters 70 Service Option Class 3 fields 70 Burst Length FCP XFER RDY Payload 136 Bus Inactivity Limit Disconnect/Reconnect Control page 221, 222 Busy Timeou
Compile Date Date Code page 180 Complete List Format Unit command 161 Concurrent Sequences Class Service Parameters 62 Connect Time Limit Disconnect/Reconnect Control page 221, 222 Continuous Increase SEQ_CNT F_Port Common Service Parameters 68 N_Port Common Service Parameters 60, 61 Continuously Increasing Offset F_Port Common Service Parameters 68, 69 N_Port Common Service Parameters 60, 61 Control Format Unit command 161 Inquiry command 168 Lock-Unlock Cache (10) command 184 Lock-Unlock Cache (16) comman
FCP CMND header 126, 127 FCP DATA frame header 137, 138 FCP RSP header 140, 141 FCP XFER RDY header 134, 135 Frame header format 24 Data Length FCP CMND Payload 128 Data Overlay Allow PRLI Accept Payload 74, 75 PRLI Payload 72, 73 Data Protect disc drive sense keys 149 Data Strobe Offset Count Error Recovery page 218, 219 Data Structure Type Frame header format 27 data transfer 330, 331, 333 Data Transfer Disconnect Control Disconnect/Reconnect Control page 221, 222 Data/Response Allowed PRLI Accept Payload
Write (16) command 328 Write and Verify (10) command 330 Write and Verify (12) command 331 Write and Verify (16) command 333 XDWrite (10) command 345, 348 XDWrite (32) command 347 XDWriteRead (10) command 349 XDWriteRead (32) command 350, 351 XPWrite (10) command 352 XPWrite (32) command 353 Disable Page Out–Force Unit Access Mode Sense data 247 Mode Sense parameter list 213 Disable Prefetch Transfer Length Caching Parameters page 230, 231 Disable Primary Defect List header 164 Disable Queuing Control Mode
Enable Spin-Down Spin-Down Control Status page 123 Enable Threshold Comparison Log Parameter structure 192, 193 Enable Vital Product Data Inquiry command 168 enclosure request 124 enclosure requested information 110 Enclosure Services disc drive inquiry data 170, 171 enclosure services interface 101 command format 104 Enclosure Services Interface Page Device Address page 114 Device Identification page 117, 123 Device Standard Inquiry Data 113 Device Temperature page 118 Enclosure Initiated ESI Page Format 1
FC Services Type Code RFT_ID Payload 99, 100 FC-0 6 FC-1 6 FC-1.5 6 FC-2 6 FC-3 6 FC-4 7 FC-AL. See Fibre Channel Arbitrated Loop FC-CT Revision RFT_ID Payload 99, 100 FCP CMND. See Fibre Channel Protocol Command FCP DATA. See Fibre Channel Protocol Data FCP RSP. See Fibre Channel Protocol Response FCP XFER RDY. See Fibre Channel Protocol Transfer Ready FCP_Port Identifier.
Persistent Reserve In parameter data for read reservations 251 Persistent Reserve In parameter data for ready keys 250, 251 Global Logging Target Save Disable Control Mode page 233, 234 Global Process Logout TPRLO Accept Payload 83 TPRLO Payload 81 GLTSD.
Interleave Format Parameters page 223, 224 Format Unit command 161, 162 intermediate status 258, 260 intermediate–condition met status 258, 260 Intermix Mode Class 3 Service Parameters 70 Class Service Parameters 62 Service Option Class 3 fields 70 Service Option fields 64 Interval Timer Informational Exceptions Control page 243 Invalid CRC Count.
LIP F8 Received Count Link Status page 120, 121 LIP Loop A/B Initiate LIP Action Specific Bits 111, 123 LIPA 42, 43 LIRP 43, 44 LISA 43 LISM 36, 41 List Binary Log Parameter structure 192, 193 List Parameter Log Parameter structure 192, 193 Lock Lock-Unlock Cache (10) command 184 Lock-Unlock Cache (16) command 185 Lock-Unlock Cache (10) command 184 Lock-Unlock Cache (16) command 185 Log Errors Informational Exceptions Control page 243 Log Page codes 194 Log Page format 191 Log Parameter Log Page format 191,
Loss of Signal Count Link Status page 120, 121, 122 RLS Accept Payload 86, 87 Loss of Synchronization Count Link Status page 120, 121, 122 RLS Accept Payload 86, 87 Low Revision Capability Entries 94 LP. See List Binary LP. See List Parameter LPN. See Logical or Physical Notch LS Command Code. See Link Services Command Code LS_RJT. See Link Service Reject LUN List Length Report LUNs parameter list format 297 LUN.
PLOGI Payload 58, 67 Node Port End to End Credit Class Service Parameters 62, 63 Node Port ID of Originator ADISC Payload 91, 92 Node Port ID of Responder ADISC Accept Payload 93 Node Port Identifier LOGO Payload 66 Node/Port Name format 59 Node/Port Name format 59 nodes 23 Non-Cache Segment Size Caching Parameters page 230, 231 Non-Medium Error page 197 non-meshed environment 49 Normal Auto Contingent Allegiance CDB Control Byte 133 disc drive inquiry data 170, 171 Reassign Blocks command 285 Not Ready 147
Firmware Numbers page 179 Format Parameters page 223, 224 Implemented Operating Definition page 175 Informational Exceptions Control page 243, 244 Inquiry command 168 Jumper Settings page 181 Log Page format 191, 192 Log Sense command 190 Mode Select page descriptor header 209 Mode Sense command 211, 246 Mode Sense page descriptor header 214 Non-Medium Error page 197 Notch page 235, 236 Power Condition page 240, 241 Rigid Disc Drive Geometry Parameters page 226, 227 Self-test Results Log page 201 Supported
Self-test Results Log parameter data format 202 Temperature Parameter format 198 Write, Read, and Verify Error Counter pages 196 Parameter Code Reset Log Select command 187, 188 Parameter Control Bits Device Self-test Results Log parameter data format 202, 203 Parameter Length Device Self-test Results Log parameter data format 202, 203 Enclosure Request 110, 111 Log Parameter structure 192, 193 Parameter list format third-party addressing 301 Parameter List Length CDB 132 Log Select command 187, 188 Mode Se
PLPB. See Prevent Loop Port Bypass PM. See Performance Mode PMI.
protocol 6 PS. See Parameter Savable Q QErr. See Queue Error Management Queue Algorithm Modifier Control Mode page 233, 234 Queue Error Management Control Mode page 233, 234 R R_CTL. See Routing Control RAC. See Report A Check Random Relative Offset F_Port Common Service Parameters 68, 69 N_Port Common Service Parameters 60, 61 RAREA. See Reserved Area RC. See Read Continuous RCD. See Read Cache Disable RD XFR RDY.
Prefetch (16) command 259 Read (10) command 264, 265 Read (12) command 266, 267 Read (16) command 268, 269 Read Capacity (10) command 273 Read Capacity (16) command 275, 276 Read Long command 284 Synchronize Cache (10) command 314 Synchronize Cache (16) command 315 Verify (10) command 317 Verify (12) command 318 Verify (16) command 320, 321 Write (10) command 324 Write (12) command 326 Write (16) command 328 Write and Verify (10) command 330 Write and Verify (12) command 331 Write and Verify (16) command 33
Rotational Offset Rigid Disc Drive Geometry Parameters page 226, 227 Round Unit Attention page 216, 217 rounding 154 Routing Control basic link services header 52, 53 common transport header 97 extended link services header 56, 57, 98 FCP CMND header 126, 127 FCP DATA frame header 137, 138 FCP RSP header 140, 141 FCP XFER RDY header 134, 135 Frame header format 24, 26 RPL. See Rotation Position Locking RRQ. See Reinstate Recovery Qualifier RSP Length Valid.
Sense Key Specific Valid 147 Extended Sense Data 145, 146 Field Pointer bytes 147, 148 Format Indication bytes 148 Sense Length Valid FCP RSP Payload 142, 144 SEQ_CNT. See Sequence Count SEQ_ID.
Spin-Down Control Status 123 SSEC.
TPRLO Accept Payload 84 TPRLO Payload 82 Third Party Originator Process Associator TPRLO Accept Payload 83 TPRLO Payload 81 Third Party Process Logout 81 Third Party Process Logout Accept Payload 83 Third Party Process Logout Payload 81 Third Party Resp Proc Assc Valid TPRLO Accept Payload 83 TPRLO Payload 81 Third Party Responder Process Associator TPRLO Accept Payload 83 TPRLO Payload 81 third-party reservation 300 Threshold Met Criteria Log Parameter structure 192, 194 Timestamp Device Self-test Results
Write (10) command 325 Write (12) command 327 Write (16) command 329 Write (6) command 323 Unit Attention page 216 Unit Serial Number page 173, 174 UnitOFL.
XDRead (10) command 342 XDRead (32) command 343 XDWrite (10) command 345 XDWrite (32) command 347 XDWriteRead (10) command 349 XDWriteRead (32) command 350 XOR Control Mode page 237 XORDis XOR Control Mode page 237, 238 XPWrite (10) command 352 XPWrite (32) command 353 Index-24 Fibre Channel Interface Manual, Rev.
Seagate Technology LLC 920 Disc Drive, Scotts Valley, California 95066-4544, USA Publication Number: 77767496, Rev.
