Page 1 Fibre Channel Interface...
Page 3 Fibre Channel Interface...
Page 4 Seagate Technology LLC. Other product names are registered trade- marks or trademarks of their owners. Seagate reserves the right to change, without notice, product offerings or specifications. No part of this publication may be reproduced in any form without written permission of Seagate Technology LLC.
Page 5 Revision status summary sheet Revision Date Sheets Affected 03/21/1997 L. Newman/J. Coomes and W. Whittington 08/01/2000 L. Newman/J. Coomes 01/03/2003 L. Newman 02/05/2004 K. Schweiss/J. Coomes and W. Paulsen Sheets Affected No change except for new Seagate logo. Document migration/conversion only.
Page 7: Table Of Contents
Publication overview ............. 1 Acknowledgements .
Page 8 Exchanges ............. . . 28 Credit .
Page 9 10.4.2 ESI write transfer ..........106 10.5 Enclosure-initiated ESI transfer .
Page 10 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) .
Page 11 12.40 Reserve (10) command ........... 299 12.40.1 Logical unit reservation .
Page 12 Seagate Technology support services ........
Page 13 Figure 1. Fibre Channel standards ........... . . 5 Figure 2.
Page 14 Fibre Channel Interface Manual, Rev. D...
Page 15: Publication Overview
No method exists at present to inform an initiator if a target supports SCSI-3 features as opposed to only SCSI- 2 features. A few SCSI-3 features are supported by Seagate drives, but no attempt has been made herein to differentiate between SCSI-2 and SCSI-3 features. Therefore, when an Inquiry command reports what the ANSI-approved version of the drive is, it reports SCSI-2, where SCSI-2 means SCSI-2 features plus some SCSI-3 features.
Page 16: General Interface Description
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. The interface supports multiple initiators, self-configuring host software, automatic features that relieve the host from the necessity of knowing the physical architecture of the target (logical block addressing is used), and some other miscellaneous features.
Page 17: Introduction To Fibre Channel
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.
Page 18: The Advantages Of Fibre Channel
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 require- ment with error-free delivery being a secondary consideration.
Page 19: Fibre Channel Standards
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. FC-SB FC-FP Mapping of Single-Byte Mapping of Command Code Sets HIPPI-FP FC-ATM...
Page 20: General Information
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 General information The FC-PH standard is the foundation upon which all others are based. Each topology, command set, and pro- tocol has its own standard.
Page 21: Fc-4
• FC-FG (Fibre Channel Fabric Generic) • FC-SW (Fibre Channel Cross-point switch) • FC-AL (Fibre Channel Arbitrated Loop) The FC-FG and FC-AL documents are of the most interest for Seagate disc drive interconnection. 3.1.4 FC Implementation Guide (FC-IG) FC-IG provides some implementation guidance for all Fibre Channel systems.
Page 22 Fibre Channel Interface Manual, Rev. D...
Page 23: Introduction To Topologies
Ports are the link to the outside world for a Fibre Channel node. See Figure 2. As stated above, each node has at least one port to provide access to other nodes. Each Seagate Fibre Channel drive has two ports.
Page 24: Links
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. Table 1: Fibre Channel port types Port type Location Associated topology N_Port Node Point-to-point or Fabric NL_Port Node in N_Port mode—Point-to-point or Fabric...
Page 25: Topology And Port Login
The ports in an arbitrated loop topology are called NL_Ports (Node Loop Ports). Each of the NL_Ports has an input and output connection. Seagate Fibre Channel drives support dual ports (specified with a “1” in byte 6, bit 4 of the disc drive inquiry data). The actual ports are located on the host’s backpanel, not on the disc drive.
Page 26: Figure 3. Port Bypass Circuit Physical Interconnect
From Previous Port Bypass Circuit N–1 Drive N–1 Figure 3. Port bypass circuit physical interconnect Port Bypass Circuit Drive To Next Drive Select Serial Serial Drive N Fibre Channel Interface Manual, Rev. D Port Bypass Circuit N+1 Drive N+1...
Page 27: Data Encoding (Fc-1)
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 align- ment so the receiving node will know what to do with the bytes.
Page 28: Buffer-To-Buffer Data Transfers
• If the number of ones and zeros in a sub-block are equal, running disparity is neutral and the value of run- ning disparity at the end of the sub-block remains the same as the preceding character even if it is separated by neutral characters.
Page 29: Data Hierarchy
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) Byte (8 bits) Bit Bit Bit Bit Bit Bit Bit Figure 6. FC data hierarchy 5.3.1 Transmission words Transmission words are the lowest level of control on Fibre Channel other than the control character used to...
Page 30: Primitive Signals Used As Frame Delimiters
Table 3: Primitive signals Beginning running Primitive signal Signal disparity Idle IDLE Negative Receiver_Ready R_RDY Negative 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. This maintains word synchronization and minimum spacing between frames.
Page 31 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 SOF Connect Class 1 SOFc1 SOF Initiate Class 1...
Page 32: Primitive Signals Custom Made For Arbitrated Loop Topologies
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 sin- gle frame sequences, commands, link services, transfer readys, and response frames.) SOFi3 is also used in the first data frame of a sequence.
Page 33: Primitive Sequences
Mark may be used for synchronization within the loop (for example, spindle sync in a RAID application). The third character of the ordered set ‘ t ’ (MK_TP) is a vendor-unique sync code. Seagate drives pass through this primitive signal without responding to it.
Page 34: Primitive Sequences Custom Made For Arbitrated Loop Topologies
Table 6: Primitive sequences Primitive sequences Sequence Offline Not_Operational Link_Reset Link_Reset_Response Offline (OLS) Offline is transmitted to indicate that the port is initiating the initialization protocol prior to going offline. The sequence will be transmitted for a minimum of 5 msec before further action is taken. Not_Operational (NOS) Not_Operational is transmitted to indicate that the port has detected a loop failure or is offline.
Page 35 There are six sequences that invoke loop initialization. There is no operational difference between Note. 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.
Page 36 Fibre Channel Interface Manual, Rev. D...
Page 37: Framing Protocol (Fc-2)
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.
Page 38: Start-Of-Frame (Sof) Delimiter
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 Frame Header Words Transmission Words Figure 8.
Page 39 F_CTL (Frame Control) This 3-byte (24-bit) field contains control information relating to the frame content as defined below. Table 9: Frame Control (F_CTL) bit definitions Definition Exchange context Sequence context First sequence Last sequence End of sequence End connection Chained sequence Sequence initiative X_ID reassigned Invalid X_ID...
Page 40 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. R_CTL (Routing Control) This one-byte field provides routing bits and information bits to categorize the frame function.
Page 41 Table 10: Routing Control values (Continued) High order bits Low order bits 0000 No operation 0001 Abort sequence (ABTS) 0010 Remove connection 0011 Reserved 1000 0100 Basic_Accept (BA_ACC) 0101 Basic_Reject (BA_RJT) 0110- Reserved 0111 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 identified by an OX_ID.
Page 42: Data Field (Payload)
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 inte- ger 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.
Page 43: Credit
These two independent fields (OX_ID and RX_ID) allow each N_Port to identify the resources needed to man- age 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.
Page 44 N_Port. This type of credit is not used in Class 3 therefore it is not applicable to Seagate drives. Fibre Channel Interface Manual, Rev. D...
Page 45: Classes Of Service (Fc-2)
Class 3 service multiplexes frames at frame boundaries to or from one or more N_Ports without acknowledg- ment of receipt. Seagate drives use Class 3 exclusively. Class 3 reduces the complexity of the ports and provides better perfor- mance for disc applications.
Page 46: Class 3 Flow Control
• 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-to- buffer flow control in one direction and there are no link level responses to Class 3 frames.
Page 47: Fc Arbitrated Loop Concepts
FC Arbitrated Loop concepts This section describes some basic Fibre Channel Arbitrated Loop (FC-AL) concepts. Seagate disc drives sup- port 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.
Page 48 Table 12: 8B/10B characters with neutral disparity D xx.y Total * character with neutral disparity. Reserved (see Table 13 on page 35). Of the 134 neutral disparity characters, seven are reserved. This leaves 127 valid non-reserved addresses. 126 of these addresses may be used by NL_Ports and one (00) may be used by a FL_Port (if present). Hex value 2A, 4A, 6A, AA, CA 2B, 4B, 6B, AB, CB...
Page 49: Loop Initialization
Table 13: AL_PA addressing Values (hex) Reserved for the FL_Port (if present) 01-EF Contains 127 valid addresses 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 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.
Page 50: Figure 10. Loop Initialization Sequences
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.
Page 51 The loop initialization process begins when any NL_Port forces the loop into the INITIALIZING state. See Fig- ure 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.
Page 52 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).
Page 53 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’.
Page 54 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’.
Page 55 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.
Page 56 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 Initial- ization Sequence. Each L_Port continues with steps 2a through 2d. c.
Page 57 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.
Page 58 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.
Page 59: Loop Initialization State Machine
8.2.1 Loop initialization state machine * Exit OLD-PORT State LISM rcvd = LISM xmit LIP or LP_TOV timeout occurred between events Notes: CLS received * Not supported by drives covered by this manual. ** The L_Port must set the appropriate AL_PA bit before transmitting the Loop Initialization Sequences.
Page 60: Loop Reinitialization
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. ENTER HERE REQ(initialize) REQ(arbritrate as x) ARBITRATING Rcvd my ARBx ARBITRATION Transmit OPNy|OPNr ARB_PEND = 1 Figure 12. Loop state machine (simplified) Accessing another L_Port Each port has its own private arbitration primitive (ARBx) signal.
Page 61: Access Fairness
When a Seagate drive is operating as a target, it closes the loop when it has transmit- ted all of the frames it needed to send. Seagate drives do not hold the loop open to monitor the input stream for ARBs.
Page 62: Access Unfairness
When a fair NL_Port has arbitrated for and won access to the loop and does detect that another L_Port is arbi- trating, 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.
Page 63: Blocking Switch Emulation
8.4.2 Blocking switch emulation When two NL_Ports open communication with each other (see the OPNyx discussion in Section 8.3), commu- nication 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.
Page 64: Assigned Al_Pa Values
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. Table 17: AL_PA mapped to bit maps AL_PA Bit map AL_PA...
Page 65: Fibre Channel Link Services
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.
Page 66: Basic Link Services
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. Table 18: Basic link services header Byte...
Page 67: Abort Sequence (Abts)
DF_CTL (Data Field Control) Set to 00h to indicate no optional Fibre Channel headers are used. 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.
Page 68: Basic Accept (Ba_Acc)
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. Table 19: BA_ACC Payload Byte SEQ_ID Valid...
Page 69: Basic Reject (Ba_Rjt)
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 Byte Reserved Reason Code Reason Explanation Vendor Unique Field definitions (listed alphabetically) Table number Reason Code...
Page 70: Extended Link Services
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.
Page 71 Field definitions (listed alphabetically) Table number D_ID (Destination Identifier) Frame destination address. DF_CTL (Data Field Control) Set to 00 to indicate no optional Fibre Channel headers are used. 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.
Page 72: Port Login (Plogi) (02X)
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 22: PLOGI Payload Byte...
Page 73 200h Port B Network Address ID Defines the name as the IEEE extended format. Unique Drive Identifier Assigned by Seagate Assigned by Seagate. Uniquely assigned to each disc drive. Vendor Version Vendor-unique. Fibre Channel Interface Manual, Rev. D (MSB Company Identifier Assigned by IEEE...
Page 74 Table 24: N_Port Common Service Parameters Byte Highest ANSI FC-PH Version Lowest ANSI FC-PH Version (MSB) Contin Random Increasing Relative Offset Offset Reserved (MSB) (MSB) (MSB) Field definitions (listed alphabetically) Table number Buffer to Buffer Credit Not checked by the drive. The drive requires the Alternate Credit Model and assumes a Buffer to Buffer Credit of zero. When the drive opens a device on the loop, it waits until it receives a R_RDY or a Close.
Page 75 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 require- ments.
Page 76 Table 26: Class Service Parameters Byte Class Intermix Valid Mode Reserved X_ID Reassignment Reserved ACK_0 ACK_N Capable Capable Reserved Reserved (MSB) (MSB) Reserved (MSB) Reserved Reserved Field definitions (listed alphabetically) Table number Concurrent Sequences Must be greater than 0. The drive returns FFh in the PLOGI ACC. Stacked Connect Sequence Request...
Page 77 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.
Page 78 Table 28: Recipient Control fields Option Categories 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 29: Service Option fields Option Class Valid Intermix Mode...
Page 79 Table 30: Port Login Accept Payload (PLOGI ACC) Byte N_Port Common Service Parameters 4-19 Port Name 20-27 Node Name 28-35 Class 1 Service Parameters 36-51 Class 2 Service Parameters 52-67 Class 3 Service Parameters 68-83 Reserved 84-99 Vendor Version 100-115 Field definitions (listed alphabetically) Table number...
Page 80: Port Logout (Plogo) (03X)
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. Table 31: LOGO Payload Byte...
Page 81: Fabric Login (Flogi) (04)
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.
Page 82 Table 34: F_Port Common Service Parameters Byte Highest ANSI FC-PH Version Lowest ANSI FC-PH Version (MSB) Contin Random Increasing Relative Offset Offset Hunt Dedicated Groups Simplex (MSB) Field definitions (listed alphabetically) Table number Buffer to Buffer Credit The drive sets the Alternate Credit Model and sets the Buffer to Buffer Credit to zero. Buffer to Buffer Credit Valid F_Port...
Page 83 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 35: Common Features bits Feature...
Page 84 Table 36: Class 3 Service Parameters Byte Class Intermix Valid Mode Priority Field definitions (listed alphabetically) Table number Service Options The following class 3 service parameters are sent by the drive. Table 37: Service Option Class 3 fields Option Class Valid Intermix Mode Stacked Connect Request Sequence Delivery...
Page 85 Table 38: Fabric Login Accept Payload (FLOGI ACC) Byte F_Port Common Service Parameters 4-19 Port Name 20-27 Node Name 28-35 Class 1 Service Parameters 36-51 Class 2 Service Parameters 52-67 Class 3 Service Parameters 68-83 Reserved 84-99 Vendor Version 100-115 Field definitions (listed alphabetically) Table number...
Page 86: Process Login (Prli)
9.2.4 Process Login (PRLI) Process Login (PRLI) is sent by the initiator to a target to establish the SCSI FCP operating features. Table 39: PRLI Payload Byte Orig Proc Resp Proc Assc Valid Assc Valid Reserved (MSB) (MSB) Reserved Reserved Reserved Data Overlay...
Page 87 Data Overlay Allow Not supported by the drive. The Data Overlay Allowed bit is not checked. Data/Response Mix Allowed Allows the drive to send the FCP RSP in the same sequence as the data. The drive does not support the Data/ Response Mix.
Page 88 The PRLI recipient returns a PRLI Accept or a LS_RJT to a PRLI request. The PRLI Accept may indicate suc- cess 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 89 Data Overlay Allow Not supported by the drive. The Data Overlay Allowed bit is not checked. Data/Response Allowed Allows the drive to send the FCP RSP in the same sequence as the data. The drive does not support the Data/ Response Mix.
Page 90 Type Code SCSI FCP process as included in the frame header for FCP frames. Type Code Extension Not defined for SCSI FCP and must be set to zero (0). Wr XFR RDY Disable (Write Transfer Ready Disable) FCP_XFR_RDY will not be sent to request write data. The drive requires this bit to be set to zero (0).
Page 91: Process Logout (Prlo)
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. Table 41: PRLO Payload Byte Orig Proc Resp Proc Assc Valid Assc Valid Reserved (MSB)
Page 92 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). Process Associators Not supported by the drive. The process associator fields are not checked by the drive. Type Code All FC-4 processes between the initiator and target are removed.
Page 93 Table 42: PRLO Accept Payload Byte Reserved Reserved Orig Proc Resp Proc Assc Valid Assc Valid Reserved (MSB) (MSB) Field definitions (listed alphabetically) Table number LS Command Code (Link Services Command Code) PRLO Accept Payload. Page Length Length of the service parameter page in bytes. For a SCSI FCP service page, the length is 10h. Payload Length Length of PRLO payload (in bytes).
Page 94 Response Code The result of the PRLO request. Codes 1, 4, and 7 are supported by the drive. Reserved. Request executed. Reserved. Reserved. The Image Pair does not exist. Reserved. Reserved The destination port is unable to process a multiple page PRLO request. The PRLO request may be retried as a sin- gle page request.
Page 95: Third Party Process Logout (Tprlo)
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. Table 43: TPRLO Payload Byte Third Party Third Party Orig Proc Resp Proc...
Page 96 Page Length The length must be in the range of 10h to 14h. Payload Length Length of TPRLO payload (in bytes). The count includes the LS Command Code. The drive supports one service parame- ter page per TPRLO. The Payload Length must be in the range of 14h to 18h. Process Associators Not supported by the drive.
Page 97 Table 44: TPRLO Accept Payload Byte Reserved Reserved Third Party Third Party Orig Proc Resp Proc Assc Valid Assc Valid Reserved (MSB) (MSB) (MSB) Field definitions (listed alphabetically) Table number Global Process Logout Only the process login for the port identified in the N_Port ID field and type code is removed. All process logins for the specified type code are removed.
Page 98 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. Reserved. Request executed. Reserved. Reserved. The Image Pair does not exist.
Page 99: Read Link Error Status Block (Rls)
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.
Page 100 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. Table 46: RLS Accept Payload Byte (MSB)
Page 101 Invalid Transmission Word Number of invalid transmission words received while in word sync. Reference the specific drive product manual to deter- mine if this field is supported. 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).
Page 102: Reinstate Recovery Qualifier (Rrq)
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.
Page 103 Table 48: RRQ Accept Payload Byte Field definitions (listed alphabetically) Table number LS Command Code (Link Services Command Code) Not supported by the drive. Fibre Channel Interface Manual, Rev. D LS Command Code...
Page 104: Port Discovery (Pdisc)
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.
Page 105: Discover Address (Adisc)
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.
Page 106 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. 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.
Page 107 Table 50: ADISC Accept Payload Byte Reserved (MSB) (MSB) (MSB) Reserved (MSB) Field definitions (listed alphabetically) Table number Hard Address of Responder This is the 24 bit NL_Port Identifier. The lower 8 bits are the AL_PA the drive attempts to acquire in the LIHA sequence dur- ing loop initialization.
Page 108: Report Node Capabilities (Rnc)
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: RNC Payload Byte...
Page 109 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. 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).
Page 110: Link Service Reject (Ls_Rjt)
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. Table 53: LS_RJT Payload Byte Reserved Reason Code Reason Explanation Vendor Unique...
Page 111: Fc Common Transport
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.
Page 112 Field definitions (listed alphabetically) Table number D_ID (Destination Identifier) Frame destination address. DF_CTL (Data Field Control) Set to 00 to indicate no optional Fibre Channel headers are used. 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.
Page 113: Register Fc-4 Types Name Service (Rft_Id)
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 Byte *Bytes 20-51 contain a bit map of supported FC-4 types. The 1 in byte 22 indicates type 08h (SCSI-FCP) Fibre Channel Interface Manual, Rev.
Page 114 Field definitions (listed alphabetically) Table number Command Code: RFT_ID 0217h RFC-4 Explanation Code Used only for reject responses. FC-CT Revision Revision level of the FC-CT. FC Service Sub Type Name Service. FC Services Type Code FC Services. Options Single Exchange. Reason Code Used only for reject responses.
Page 115: Enclosure Services Interface (Esi)
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.
Page 116: 8045 Mode
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.
Page 117: 8045 Esi Pinouts
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.
Page 118: 8067 Mode
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 SEL/ESI Bus SEL_ID...
Page 119: 8067 Esi Interface Pinouts
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.
Page 120: Esi Command Transfer
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) Discovery Figure 15. ESI command transfers 10.4.1 ESI read transfer To receive data from the enclosure, the drive pulls –DSK_RD pin low to request information from the enclo- sure. The enclosure responds by driving the Data pins with ESI and pulling –ENCL_ACK low to signal that the data is valid.
Page 121: Enclosure-Initiated Esi Transfer
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.
Page 122: Figure 18. Enclosure Initiated Esi Request
START_1/ START_2 –PARALLEL ESI –DSK_WR SEL_6 –DSK_RD SEL_5 D(0:3) SEL_(0:3) –ENCL_ACK SEL_4 Enclosure Services Processor negates START_1 and START_2 to indicate that it is requesting communi- cation with the drive. The drive asserts –PARALLEL ESI to indicate it is ready to begin communication with the Enclosure Ser- vices Processor.
Page 123: Eie Operations
START_1/ START_2 –PARALLEL ESI –DSK_WR SEL_6 –DSK_RD SEL_5 D(0:3) SEL_(0:3) –ENCL_ACK SEL_4 Enclosure Services Processor negates START_1 and START_2 to indicate that it is requesting communi- cation with the drive. The drive asserts –PARALLEL ESI to indicate it is ready to begin communication with the Enclosure Ser- vices Processor.
Page 124: Enclosure Requested Information
–PARALLEL ESI ESI INTF SEL_ID Figure 20. 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.3 Enclosure requested information If the enclosure services interface transfer is initiated by the enclosure, the drive sends ESI Command Phase information as defined in the SFF-8067 Specification for 40-pin SCA-2 Connector w/Bidirectional ESI, Rev.
Page 125 Note: The Initiate Loop Initialization Action Code (03h) does not include a transfer of information to the enclo- sure. The Action Specific bits in the Enclosure Request define the operation to be performed. See Table 62. Device Identification (see Section 10.5.3.4). Device Temperature (see Section 10.5.3.5).
Page 126 Table 63: Enclosure Initiated ESI Page Format Byte (MSB) (MSB) Field definitions (listed alphabetically) Table number Action Code The Action Code requested by the enclosure. Data The first n - 4 bytes of ESI data. ESI Page Identifies the ESI page code used (00h). Page Length The length of the ESI page (n - 3 bytes).
Page 127: Device Standard Inquiry Data Page
10.5.3.1 Device Standard Inquiry Data page Table 64: Device Standard Inquiry Data page Byte (MSB) (MSB) Field definitions (listed alphabetically) Table number Action Code Device Standard Inquiry Data ESI Page Identifies the ESI page code used (00h). Inquiry Data The first 36 bytes of Standard Inquiry data. Refer to Section 12.6 for a definition of this data. Note: the vendor specific, VS, bit in byte 6 is not valid.
Page 128: Device Address Page
10.5.3.2 Device Address page Table 65: Device Address page Byte (MSB) (MSB) Port A (01h) (MSB) Port A Position (MSB) Port B (02h) (MSB) Port B Position (MSB) Field definitions (listed alphabetically) Table number Action Code Device Address ESI Page Identifies the ESI page code used (00h).
Page 129 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. Port Name The 64-bit Fibre Channel unique Name_Identifier assigned to the port.
Page 130: Loop Position Map Page
10.5.3.3 Loop Position Map page Table 66: Loop Position Map page Byte (MSB) Offset Port A (n – 4) (MSB) Offset Port B (m – n + 1) n + 1 n + 2 (MSB) Field definitions (listed alphabetically) Table number Action Code Device Address...
Page 131: Device Identification Page
10.5.3.4 Device Identification page Table 67: Device Identification page Byte (MSB) (MSB) Field definitions (listed alphabetically) Table number Action Code 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.4 for the complete SCSI Vital Product Data device Identification information.
Page 132: Device Temperature Page
10.5.3.5 Device Temperature page Table 68: Device Temperature page Byte (MSB) Temperature Reserved Field definitions (listed alphabetically) Table number Action Code Device Temperature ESI Page Identifies the ESI page code used (00h). Temperature The value of the drive temperature sensor in degrees Celsius, offset by +20 degrees. The range expresses a temperature between –19 and +235 degrees Celsius.
Page 133: Port Parameters Page
10.5.3.6 Port Parameters page Table 69: Port Parameters page Byte (MSB) Drive Capabilities Reserved Reserved Field definitions (listed alphabetically) Table number Action Code Port Parameters. Drive Capabilities This is a bit-significant field that indicates which device control codes defined by SFF 8045 are supported by the drive. The corresponding device control code is supported.
Page 134: Link Status Page
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.
Page 135 Table 70: Link Status page (Continued) Byte (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) (MSB) Field definitions (listed alphabetically) Table number Action Code Link Status. ESI Page Identifies the ESI page code used (00h). Invalid CRC Count The count of the number of write data frames that have been received with invalid CRCs on the port. These errors are only detected when this drive is the target of the data transfer.
Page 136 Link Failure Count Count of the number of Loss of Sync conditions that have occurred on the port which exceeded 100 ms in duration. LIP F7 Initiated Count Count of the number of loop initialization processes originated by the port with LIP – F7’s (Initialize LIP). LIP F7 Received Count Count of the number of loop initialization processes initiated on the port by receiving LIP –...
Page 137: Spin-Down Control Action Specific Bits
10.5.3.8 Spin-Down Control Action Specific Bits Table 71: Spin-Down Control Action Specific Bits Byte Field definitions (listed alphabetically) Table number Read Status Device updates the state of the Enable Spin-Down and Enable SpinDn Ctrl as directed by the corresponding bits in the request.
Page 138: Esi Data Validation
Page Length 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 func- tion 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.
Page 139: Scsi Operations
11.1.1 FC-4 mapping layer All devices communicating with a Seagate Fibre Channel disc drive must implement the SCSI-FCP mapping protocol. The FC-4 mapping layer uses the services provided by FC-PH to execute the steps required to per- form the functions defined by the FC-4.
Page 140: Fcp Cmnd
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 Table 74: FCP CMND frame header Byte (MSB) (MSB) (MSB) SEQ_ID (MSB) (MSB) SOFi3 Frame header Payload EOFt R_CTL...
Page 141 Field definitions (listed alphabetically) Table number DF_CTL (Data Field Control) 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. 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.
Page 142 Table 75: FCP CMND Payload Byte (MSB) Term Task Clear ACA (MSB) (MSB) Field definitions (listed alphabetically) Table number Abort Task Set Clears only the queue of commands from the initiator originating the Abort Task Set. CDB (Command Descriptor Block) Always 16 bytes long.
Page 143 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. Logical Unit Number (LUN) Addresses physical devices or virtual devices attached to a target. Zero is the only valid LUN number for the drives supported by this manual.
Page 144: Command Descriptor Block (Cdb)
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.
Page 145 Table 77: Typical CDB for six-byte commands Byte Transfer Length (if required) Control Byte Field definitions (listed alphabetically) Table number Control Byte See Section 11.2.1.6. Logical Block Address See Section 11.2.1.2. Operation code See Section 11.2.1.3. Transfer Length See Section 11.2.1.5. Table 78: Typical CDB for ten-byte commands Byte...
Page 146: Logical Block Address
11.2.1.4 Relative address bit Relative addressing is a technique of accessing logical blocks relative to the logical blocks accessed in a previ- ous linked command. Seagate fibre channel drives do not support relative addressing. 11.2.1.5 Transfer length The Transfer Length field specifies the amount of data to be transferred, usually the number of blocks. For sev- eral commands, the Transfer Length indicates the requested number of bytes to be sent as defined in the com- mand description.
Page 147: Control Byte
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 trans- ferred to the initiator, whichever is less.
Page 148: Fcp Xfer Rdy
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 80: FCP XFER RDY header Byte...
Page 149 Field definitions (listed alphabetically) Table number DF_CTL (Data Field Control) 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. 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 origina- tor, and the frame is the last of the Fibre Channel sequence.
Page 150 Table 81: FCP XFER RDY Payload Byte (MSB) (MSB) (MSB) Field definitions (listed alphabetically) Table number Burst Length The amount of data (in bytes) requested by the drive for transfer in this Fibre Channel sequence. The maximum length the drive will request is the remaining data to complete the transfer, the Maximum Burst Size in the Disconnect/Reconnect SCSI mode (page 2), or the maximum length that may be transferred in a Fibre Channel sequence, whichever is less.
Page 151: Fcp Data
11.4 FCP DATA The payload of FCP DATA frames transfer the user data associated with a command. FCP DATA format Frame Header Payload (Data) EOFn or EOFt Table 82: FCP DATA frame header Byte (MSB) (MSB) (MSB) SEQ_ID (MSB) (MSB) (MSB) Fibre Channel Interface Manual, Rev.
Page 152 Field definitions (listed alphabetically) Table number DF_CTL (Data Field Control) 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 trans- fer is from the drive.
Page 153 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).
Page 154: Fcp Rsp
11.5 FCP RSP An FCP Response (RSP) frame is returned by the drive for each FCP CMND operation unless the drive receives: 1. A Clear Task Set 2. An Abort Task Set 3. A Target Reset 4. A Loop Initialization Primitive Sequence (LIP) Reset 5.
Page 155 Field definitions (listed alphabetically) Table number DF_CTL (Data Field Control) Indicates no optional Fibre Channel headers are used. D_ID (Destination Identifier) The address of the initiator that originated the command. F_CTL (Frame Control) Set to 990000h for FCP RSP frames. This indicates the frame is sent by the responder of the exchange, not the originator, the frame is the last frame of the sequence (FCP RSP is a single frame sequence for this drive), and the sequence is the last for the Fibre Channel exchange.
Page 156 Table 85: FCP RSP Payload Byte (MSB) SCSI Status (MSB) (MSB) (MSB) (MSB) (MSB) Field definitions (listed alphabetically) Table number Length of Response Information The Length of Response Information contains the byte length of the FCP response information in the frame. Valid lengths for the response information are 0, 4, and 8.
Page 157 Resid Under Run (Residual Under Run) 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. The response information codes supported are: Value Definition Task Management function Complete or No Failure...
Page 158 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. ACA Active.
Page 159: Extended Sense Data Format
(MSB) (40) (41) (42) (43) Additional Sense Code (ASC) (44) Additional Sense Code Qualifier (ASCQ) (45) Reserved for Seagate internal use only (46) SKSV (47) (48) (49) 18-n (50-n) *Fibre Channel frame byte number shown in parenthesis. Field definitions (listed alphabetically)
Page 160 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.
Page 161: Sense Key Specific Valid (Sksv) And Sense Key Specific
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 SKSV Sense Key field value 05h (Illegal Request) 01h (Recovered Error) 04h (Hardware Error) or 03h (Medium Error) 02h (Not Ready)
Page 162 Table 90: Actual Retry Count bytes Byte SKSV (MSB) Field definitions (listed alphabetically) Table number Actual Retry Count Returns implementation-specific information on the actual number of retries used in attempting to recover an error or exception condition. This field relates to the retry count fields specified within the Verify Error Recovery Page (07h) parameters of the Note.
Page 163 Table 92 lists the sense keys in the extended sense data format that are used by the disc drive. Table 92: Applicable disc drive sense keys Sense Description 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.
Page 164 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) Byte 12 Byte 13 Description (ASC) (ASCQ) No additional sense information No index/sector signals found No seek complete (no drive command complete) Peripheral device write fault...
Page 165 Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 Byte 13 Description (ASC) (ASCQ) Defect list error Parameter list length error Defect list not found Miscompare during verify operation Invalid command operation code Logical block address out of range Invalid field in CDB Logical unit number not supported...
Page 166 Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 Byte 13 Description (ASC) (ASCQ) Enclosure services failure Unsupported enclosure function Enclosure services unavailable Enclosure services transfer failure Enclosure services transfer refused Parameter rounded Microcode changed Changed operating definition...
Page 167: Current And Deferred Errors
Table 93: Error codes for bytes 12 and 13 of sense data (values are in hexadecimal) (Continued) Byte 12 Byte 13 Description (ASC) (ASCQ) XOR cache is not available Insufficient reservation resources Insufficient registration resources Log exception Threshold condition met Log parameter value at maximum Servo RPL status change Servo RPL spindles synchronized...
Page 168: Parameter Rounding
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.
Page 169: Commands
12.0 Commands This section contains information about the commands used by Seagate Fibre Channel disc drives. This sec- tion 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.
Page 170 Table 94: Commands sorted by command name Command name code Change Definition (obsolete) Compare (obsolete) Copy (obsolete) Copy and Verify (obsolete) Format Unit Inquiry Lock-Unlock Cache (10) Lock-Unlock Cache (16) Log Select Log Sense Mode Select (6) Mode Select (10) Mode Sense (6) Mode Sense (10) Move Medium...
Page 171 Table 94: Commands sorted by command name (Continued) Command name code Start/Stop Unit Synchronize Cache (10) Synchronize Cache (16) Test Unit Ready Verify (10) Verify (12) Verify (16) Write (6) Write (10) Write (12) Write (16) Write and Verify (10) Write and Verify (12) Write and Verify (16) Write Buffer...
Page 172 Table 95: Commands sorted by operation code code Command name Test Unit Ready Rezero Unit (obsolete) Request Sense Format Unit Reassign Blocks Read (6) Write (6) Seek (6) (obsolete) Inquiry Mode Select (6) Reserve (6) (obsolete) Release (6) (obsolete) Copy (obsolete) Mode Sense (6) Start/Stop Unit...
Page 173 Table 95: Commands sorted by operation code code Command name Mode Sense (10) Persistent Reserve In Persistent Reserve Out XDRead (32) XDWrite (32) XPWrite (32) XDWriteRead (32) Read (16) Write (16) Write and Verify (16) Verify (16) Prefetch (16) Synchronize Cache (16) Lock-Unlock Cache (16) Write Same (16) Read Capacity (16)
Page 174: Change Definition Command
12.1 Change Definition command 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 Obsolete. A Check Condition status is sent if a Compare command is received. 12.3 Copy command Obsolete.
Page 175: Format Unit Command
12.5 Format Unit command 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.
Page 176 Primary Defect Type: P type flawed sectors are identified at the time of shipment in a list of defects (permanent flaws) supplied by Seagate and stored on the disc in an area that is not directly accessible by the user. (This list may be referred to as an ETF List).
Page 177 Table 97: Format Unit parameter definition (format variations) CDB–Byte (see Table 96) Defect List Format DATA LIST Bit 4 Bit 3 Bit 2 Bit 1 Block format [2] Bytes from Index format Physical Sector format Byte 1 of the Defect List header determines whether the P and C defects are reallocated. See Table 98. See individual drive’s Product Manual, Volume 1, for support/non-support.
Page 178: Format Unit Parameter List
12.5.1 Format Unit parameter list Parameter Defect List Header Initialization Pattern Descriptor Defect Descriptors 12.5.1.1 Defect List header Table 98: Defect List header Byte Reserved (MSB) Field definitions (listed alphabetically) Table number DCRT (Disable Certification) The disc drive does not perform a verify function during formatting (thus no C list for this format is created or reallo- cated).
Page 179: Initialization Pattern Descriptor
Immed (Immediate) Status will be returned after the first operation has completed. 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. 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).
Page 180 This section describes the format of the defect list that follows the Defect List header described in Table 98. Three formats are possible: • Block format (Seagate does not support the block format, except as a customer special option) • Index format (see Table 102) •...
Page 181 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 Cylinder Number of Defect (MSB) Cylinder Number of Defect Cylinder Number of Defect (LSB) Head Number of Defect Defect Sector Number (MSB) Defect Sector Number...
Page 182: Inquiry Command
12.6 Inquiry command 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.
Page 183 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.
Page 184 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.
Page 185 The disc drive does not support tagged command queuing. The disc drive supports tagged command queuing. Copyright Notice The 48 bytes of ASCII data “Copyright (c) XXXX Seagate All rights reserved,” where “XXXX” indicates the current year (for example: 1997). Drive Serial Number The 8 bytes of ASCII data containing 8-digit drive serial number.
Page 186 The drive responds to the Reset condition with the soft Reset alternative. TRMIOP (Terminate I/O Process) The disc drive does not support the Terminate I/O Process message. TrnDis (Transfer Disable) Not supported. Vendor Identification The ASCII data containing the vendor name (“SEAGATE”). Fibre Channel Interface Manual, Rev. D...
Page 187: Vital Product Data
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.
Page 188: Unit Serial Number Page (80H)
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) Byte Peripheral Qualifier Page Code (80h) Page Length (08h) Product Serial Number Field definitions (listed alphabetically) Table number Page Code...
Page 189: Implemented Operating Definition Page (81H)
12.6.3 Implemented Operating Definition page (81h) Table 109: Implemented Operating Definition page (81h) Byte Peripheral Qualifier Page Code (81h) Page Length (04h) SAVIMP SAVIMP SAVIMP Field definitions (listed alphabetically) Table number Current Operating Definition Returns the value of the present operating definition. The default operating definition field returns the value of the operating definition the disc drive uses when power is applied if no operating definition is saved.
Page 190: Device Identification Page (83H)
12.6.4 Device Identification page (83h) The device identification page provides the Node Name for the drive. Table 110: Device Identification page (83h) Byte Peripheral Qualifier Page Code (83h) Reserved Page Length (0Ch) Identification descriptor Field definitions (listed alphabetically) Table number Identification Descriptor Contains type information and a unique drive identification value.
Page 191 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. Peripheral Qualifier and Peripheral Device Type A direct-access device (magnetic disc) is connected to this logical unit. Each identification descriptor contains information identifying the logical unit.
Page 192 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. The Identifier field contains an IEEE Extended Unique Identifier, 64-bit (EUI-64). In this case, the Identifier Length field is set to 8.
Page 193: Firmware Numbers Page (C0H)
12.6.5 Firmware Numbers page (C0h) Table 113: Firmware Numbers page (C0h) Byte Peripheral Qualifier Page Code (C0h) Page Length (20h) Firmware Release Number Servo RAM Release Number Servo ROM Release Number Servo RAM Release Date in ASCII Servo ROM Release Date in ASCII Field definitions (listed alphabetically) Table number...
Page 194: Date Code Page (C1H)
12.6.6 Date Code page (C1h) Table 114: Date Code page (C1h) Byte Peripheral Qualifier Page Code (C1h) Page Length (0Ch) Product Date Code Compile Date Field definitions (listed alphabetically) Table number Compile Date The field contains 8 ASCII bytes of data for a date of the form MMDDYYYY. Page Code Provides the date code from the disc drive defect list.
Page 195: Jumper Settings Page (C2H)
12.6.7 Jumper Settings page (C2h) Table 115: Jumper Settings page (C2h) Byte Peripheral Qualifier Page Code (C2h) Page Length (02h) Rsvd Field definitions (listed alphabetically) Table number Page Code Provides the status of the option selections at the disc drive connector. Page Length The length (in bytes) of the Jumper Settings page.
Page 196 Table 116: AL_PA Select-ID mapping AL_PA Sel. ID (hex) (hex) AL_PA Sel. ID (hex) (hex) Fibre Channel Interface Manual, Rev. D AL_PA Sel. ID (hex) (hex)
Page 197: Device Behavior Page (C3H)
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. Table 117: Device Behavior page (C3h) Byte Peripheral Qualifier Page Code (C3h) Reserved Page Length Version Number...
Page 198: Lock-Unlock Cache (10) Command
12.7 Lock-Unlock Cache (10) command 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 algo- rithm. 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.
Page 199: Lock-Unlock Cache (16) Command
12.8 Lock-Unlock Cache (16) command 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 algo- rithm. 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.
Page 200 Operation Code The operation code for the Lock-Unlock Cache (16) command. RelAdr (Relative Addressing) This function is not supported by drives described in this manual. Fibre Channel Interface Manual, Rev. D...
Page 201: Log Select Command
12.9 Log Select command 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.
Page 202 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.
Page 203 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 Parameter List Length The Log Select and Log Sense commands use the same log page format. See Section 12.10. Fibre Channel Interface Manual, Rev.
Page 204: Log Sense Command
12.10 Log Sense command 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.
Page 205 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). •...
Page 206 Field definitions (listed alphabetically) Table number 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. Log Parameter Structures Most log pages contain one or more special data structures called Log Parameters.
Page 207 Since the drive uses volatile memory to hold cumulative values, they will be lost when a power cycle occurs. Unless the ini- tiator commands the drive to save them to nonvolatile memory using a Log Select or Log Sense command with the SP bit set to one.
Page 208 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 125: Threshold Met Criteria Basis for Comparison Code Notify of every update of cumulative value...
Page 209 Table 127: Supported log pages Byte Reserved Reserved (MSB) Supported Page List Field definitions (listed alphabetically) Table number Page Code 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.
Page 210: Error Counter Pages, Write, Read, Read Reverse, And Verify (Code 02, 03, 04, And 05H)
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. Table 128: Write, Read, Read Reverse, and Verify Error Parameter Code field Byte Parameter Code Field definitions (listed alphabetically)
Page 211: Non-Medium Error Page (Code 06H)
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) Byte Page Code (06h) Parameter Code Field definitions (listed alphabetically) Table number Page Code 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 sup- ported for this page).
Page 212: Temperature Page (Code 0Dh)
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) Byte Reserved Field definitions (listed alphabetically) Table number Page Code Temperature page.
Page 213 Table 132: Command Initiate Parameter Format Byte Reserved Field definitions (listed alphabetically) Table number 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.
Page 214 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.
Page 215: Device Self-Test Results Log Page (Code 10H)
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.
Page 216 Self-Test Results Log Parameter fields See Table 135 below. Table 135: Device Self-Test Results Log parameter data format Byte (MSB) Parameter Length (10h) Self-Test Code Self-Test Segment Number (MSB) (MSB) Additional Sense Code Additional Sense Code Qualifier Vendor Specific Field definitions (listed alphabetically) Table number Additional Sense Code...
Page 217 Parameter Control Bits Value provided by device server Device server supports saving of parameter Device server manages saving of parameter No threshold comparison is made on this value TMC xxx Ignored when ETC is 0 LBIN 1 The parameter is in binary format The parameter is a list parameter Parameter Length This value is always 10h.
Page 218: Cache Statistics Page (Code 37H)
12.10.5 Cache Statistics page (code 37h) Log Page code 37h specifies Cache Statistics page. Table 136: Cache Statistics page Byte Parameter Code Field definitions (listed alphabetically) Table number Parameter Code The number of logical blocks that have been sent to an initiator. The number of logical blocks that have been received from an initiator.
Page 219: Factory Log Page (Code 3Eh)
12.10.6 Factory Log page (code 3Eh) Log Page code 3Eh specifies factory status parameters. Table 137: Factory Log page Byte Parameter Code Field definitions (listed alphabetically) Table number 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.
Page 220: Mode Select (6) Command
12.11 Mode Select (6) command 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). Initia- tors should issue Mode Sense prior to Mode Select to determine supported pages, page lengths, and other parameters.
Page 221 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: •...
Page 222 Table 139: Mode Select (6) parameter list Byte Block Descriptor Length Either 00h or 08h Block Length (MSB) Block Length Block Length (LSB) Mode Select Page Headers And Their Parameters (see tables 140 and 145) 0–n Field definitions (listed alphabetically) Table number Block Descriptor Length...
Page 223 Mode Select Page Headers And Their Parameters See Mode Sense command (see Section 12.13) for detailed descriptions. 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.
Page 224: Mode Select (10) Command
12.12 Mode Select (10) command 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) Byte Reserved Reserved Reserved Reserved Reserved Reserved (MSB)
Page 225: Mode Sense (6) Command
The drive may return zero or more block descriptors in the returned Mode Sense data, at the drive’s discretion. Seagate FC-AL products return one block descriptor if the DBD bit is zero. The drive does not return any block descriptors in the returned Mode Sense data. The Block Descriptor Length field of the Mode Sense header contains 00h to indicate a block descriptor length of zero.
Page 226 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. 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.
Page 227 Table 143: Mode Sense (6) parameter list Byte Sense Data Length Block Length (MSB) Block Length Block Length (LSB) Mode Sense Page Headers and Their Parameters 0–n Field definitions (listed alphabetically) Table number Block Descriptor Length The length (in bytes) of the Block Descriptor. It is equal to the number of bytes in the Block Descriptor (8) and does not include the page headers and mode parameters, if any.
Page 228 Mode Sense Page Headers and Their Parameters See Table 144. Number of Blocks The number of logical blocks of the medium that meets the Block Length in the Block Descriptor. All of the remaining logical blocks of the logical unit have the medium characteristics specified by the Block Descrip- tor.
Page 229 Table 145: Mode sense page code section reference Page description Page code Unit Attention page Error Recovery Disconnect/Reconnect Control Format Parameters Rigid Disc Drive Geometry Verify Error Recovery page Caching page Control Mode page Notch and Partition page XOR Control Mode page Fibre Channel Interface Control page Power Condition page Informational Exceptions Control page...
Page 230: Unit Attention Page (00H)
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, Vol- ume 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.
Page 231 Check Condition is presented for all affected Initiators following a reset until Request Sense is issued by each Initia- tor (as per current operation). Byte 3 is reserved for future compatibility with Seagate host adapters. Though presently may be Note.
Page 232: Error Recovery Page (01H)
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;...
Page 233 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. Data Strobe Offset Count Zero is the default value and is not changeable.
Page 234 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. 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.
Page 235: Disconnect/Reconnect Control Page (02H)
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;...
Page 236 The buffer full ratio is taken to be a percentage of the smaller of: the buffer size 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.
Page 237: Format Parameters Page (03H)
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.
Page 238 Field definitions (listed alphabetically) Table number Alternate Sectors Per Zone The number of spare sectors to be reserved for the defined defect management zone. No sectors are to be reserved in each zone for defect management. This is to accommodate hosts that want to manage the defects themselves.
Page 239 Tracks Per Zone The number of tracks the disc drive allocates to each defect management zone. Seagate drives define a defect manage- ment zone as one track or one cylinder. A programmed value of 1 defines one track per zone (i.e. spare sectors per track).
Page 240: Rigid Disc Drive Geometry Parameters Page (04H)
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 summa- rizes the function and defines the default value. See the individual drive’s Product Manual, Volume 1, Mode Sense Data section, for changeable values. Table 150: Rigid Disc Drive Geometry Parameters page (04h) Byte Page Length (16h)
Page 241 Landing Zone Cylinder Not applicable. Medium Rotation Rate On Mode Sense commands, these bytes return drive nominal rotation rate in revolutions per minute for synchronous spin- dle operation. The bytes have no meaning for Mode Select. Number of Cylinders The number of physical cylinders used for data storage. This may or may not include spare cylinders set aside for flaw real- location.
Page 242: Verify Error Recovery Page (07H)
12.13.6 Verify Error Recovery page (07h) The Verify Error Recovery page specifies the error recovery parameters the target uses during the Verify com- mand and the verify operation of the Write and Verify command. Table 151: Verify Error Recovery page (07h) Byte Reserved Page Length (0Ah)
Page 243 EER (Enable Early Recovery) The disc drive applies on-the-fly T>1 ECC correction as soon as possible, before attempting other retry mecha- nisms, 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). The disc drive applies ECC correction before other retry mechanisms, but does not perform T>1 corrections on the fly;...
Page 244: Caching Parameters Page (08H) For Mode Sense/Mode Select
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. Table 152: Caching Parameters page (08h) Byte Reserved Page Length (12h) ABPF Demand Read Retention Priority (MSB) (MSB) (MSB) (MSB)
Page 245 Adaptive read look-ahead (ARLA) is disabled. Adaptive read look-ahead (ARLA) is enabled. Since Seagate drives covered by this manual never organize the cache according to size of segment, but rather by number of segments, this bit is used to enable or disable adaptive RLA.
Page 246 SCSI Read commands must access the media. Data cannot come from the cache. SIZE (Size Enable) For Seagate drives covered by this manual, this bit is always zero (0). The Cache Segment Size is to be used to control caching segmentation.
Page 247: Mode Sense/Mode Select Control Mode Page (0Ah)
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. Table 153: Control Mode page (0Ah) Byte Reserved...
Page 248 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. GLTSD (Global Logging Target Save Disable) The target provides a target-defined method for saving log parameters (Logged to disk). 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.
Page 249: Notch Page (0Ch)
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.
Page 250 LPN (Logical or Physical Notch) The notch boundaries are based on the physical parameters of the drive. The cylinder is considered most signifi- cant, the head least significant. The notch boundaries are based on logical blocks on the drive. Maximum Number of Notches The maximum number of notches supported by the drive.
Page 251: Xor Control Mode Page (10H)
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 oper- ating parameters. Table 155: XOR Control Mode page (10h) Byte Reserved Page Length (16h) Default Default 4–7 (MSB)
Page 252 PS (Parameter Savable) This bit is only used with the Mode Sense command. This bit is not used with the Mode Select command. 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. XORDis This bit enables and disables XOR operations within a device.
Page 253: Fibre Channel Interface Control Page (19H)
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 tech- niques defined for Fibre Channel.
Page 254 DLM (Disable Loop Master) 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. The target may participate in loop master arbitration in the normal manner and, if successful, may become loop master during the loop initialization process.
Page 255: Power Condition Page (1Ah)
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.
Page 256 Standby Condition Timer The inactivity time (in 100 millisecond increments) that the logical unit shall wait before entering the Standby condition. Fibre Channel Interface Manual, Rev. D...
Page 257: Informational Exceptions Control Page (1Ch)
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 infor- mational exceptions that report an additional sense code of Failure Prediction Threshold Exceeded to the application client.
Page 258 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 Description No reporting of informational exception condition.
Page 259 Perf (Performance) Informational exception operations that are the cause of delays are acceptable. 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 informa- tional exception conditions.
Page 260: Mode Sense (10) Command
12.14 Mode Sense (10) command 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 160: Mode Sense (10) command (5Ah) Byte Reserved Reserved...
Page 261 Table 161: Mode Sense (10) data Byte (MSB) Reserved Reserved (MSB) 0 0–7 Block Descriptor Data (see Table 143) 0–n Mode Sense Page Headers and Their Parameters Field definitions (listed alphabetically) Table number Block Descriptor Data See Table 143. Block Descriptor Length The length (in bytes) of the block descriptor.
Page 262: Move Medium Command
12.15 Move Medium command Not implemented. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev. D...
Page 263: Persistent Reserve In Command
12.16 Persistent Reserve In command 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). The actual length of the Persistent Reserve In parameter data is available in a parameter data Note.
Page 264: Persistent Reserve In Parameter Data For Read Keys
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 Byte (MSB) (MSB)
Page 265: Persistent Reserve In Parameter Data For Read Reservation
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 164: Persistent Reserve In parameter data for read reservation Byte (MSB) (MSB)
Page 266 Table 165: Persistent Reserve In Reservation Descriptor Byte (MSB) (MSB) Reserved (MSB) 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. Scope The value in this field specifies whether a persistent reservation applies to an entire logical unit or to an element.
Page 267 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. Type Code Name...
Page 268: Persistent Reserve Out Command
12.17 Persistent Reserve Out command 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.
Page 269 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). Register. Register a reservation key with the device server. Reserve. Create a persistent reservation with a specified scope and type. Release.
Page 270: Persistent Reserve Out Parameter List
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.
Page 271 Table 168: Persistent Reserve Out service actions and valid parameters Service action Allowed scope Register Ignored Reserve Logical Unit Element Release Logical Unit Element Clear Ignored Preempt Logical Unit Element Preempt and Clear Logical Unit Element Reservation Key This field contains an 8-byte value provided by the application client to the device server to identify the initiator that is the source of the Persistent Reserve Out command.
Page 272: Prefetch (10) Command
12.18 Prefetch (10) command 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. Table 169: PREFETCH (10) command (34h) Byte Operation Code (34h) (MSB) Reserved (MSB)
Page 273: Prefetch (16) Command
12.19 Prefetch (16) command 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. Table 170: PREFETCH (16) command (90h) Byte Operation Code (90h) (MSB) (MSB) Reserved...
Page 274 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. 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.
Page 275: Prevent/Allow Medium Removal Command
12.20 Prevent/Allow Medium Removal command 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. D...
Page 276: Read (6) Command
12.21 Read (6) command The Read (6) command requests the disc drive to transfer data to the initiator. Table 171: Read (6) command (08h) Byte Reserved Transfer Length Control Field definitions (listed alphabetically) Table number Control See Control Bytes in Section 11.2.1.6. Logical Block Address The logical block at which the read operation will begin.
Page 277 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.
Page 278: Read (10) Command
12.22 Read (10) command 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.
Page 279 RelAdr (Relative Address) This function is not supported by drives described in this manual. 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.
Page 280: Read (12) Command
12.23 Read (12) command The Read (12) command requests that the target transfer data to the initiator. Table 173: Read (12) command (A8h) Byte Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Transfer Length (MSB) Transfer Length Transfer Length Transfer Length (LSB)
Page 281 RelAdr (Relative Address) This function is not supported by drives described in this manual. 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.
Page 282: Read (16) Command (88H)
12.24 Read (16) command (88h) The Read (16) command requests that the target transfer data to the initiator. Table 174: Read (16) command (88h) Byte Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address Logical Block Address Logical Block Address Logical Block Address Logical Block Address (LSB)
Page 283 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). RelAdr (Relative Address) This function is not supported by drives described in this manual.
Page 284: Read Buffer Command
12.25 Read Buffer command 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.
Page 285: Read Combined Descriptor Header And Data Mode (000B)
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.
Page 286 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. Offset Boundary This field contains the boundary alignment with the selected buffer for subsequent Write Buffer and Read Buffer com- mands.
Page 287: Read Capacity (10) Command
12.26 Read Capacity (10) command The Read Capacity (10) command provides a means for the initiator to request the capacity of the disc drive information. Table 178: Read Capacity (10) command (25h) Byte Reserved Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB) Control...
Page 288 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 Description Logical Block Address (MSB) Logical Block Address Logical Block Address Logical Block Address (LSB)
Page 289: Read Capacity (16) Command
12.27 Read Capacity (16) command 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.
Page 290 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.
Page 291: Read Defect Data (10) Command
12.28 Read Defect Data (10) command 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.
Page 292 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, respec- tively, 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.
Page 293 Table 183: Defect List Header description Byte Reserved Defect List Length (MSB) (Value is 8 times the number of defects) Defect List Length (LSB) Defect Descriptor Bytes 4–n Field definitions (listed alphabetically) Table number 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: Bit P Bit G Interpretation Return Defect List header only.
Page 294: Read Defect Data (12) Command
12.29 Read Defect Data (12) command 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.
Page 295 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). Return all lists.
Page 296 Table 185: Defect List (12) Header description Byte Reserved Reserved Reserved (MSB) Defect Descriptor Bytes 0–n Field definitions (listed alphabetically) Table number 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: Bit P Bit G Interpretation Return Defect List header only.
Page 297: Read Element Status Command
12.30 Read Element Status command Not implemented. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev. D...
Page 298: Read Long Command
12.31 Read Long command 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.
Page 299: Reassign Blocks Command
12.32 Reassign Blocks command 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.
Page 300 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 termi- nates 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.
Page 301: Receive Diagnostic Results Command
12.33 Receive Diagnostic Results command The Receive Diagnostic Results command requests analysis data after completion of a Send Diagnostic com- mand 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. These additional pages have a page code that specifies to the disc drive the format of the data to be returned after it receives a Receive Diagnostic Results command.
Page 302 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 Page Code Description List of Supported Diagnostic Pages 01h - 0Fh SCSI Enclosure Services Pages Address Translation Page none...
Page 303 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.
Page 304 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.
Page 305 Translated Format The value from the Send Diagnostic command translate format field (see Table 209). The values are 000 (Logical block for- mat) or 101 (Physical sector address format). Table 195: Address field logical block address format Byte (MSB) Field definitions (listed alphabetically) Table number Logical Block Address...
Page 306 These bytes identify an assembly that may have failed. The codes will be listed in probability order, with the most probable assembly listed first and the least probable listed last. There is no FRU information. Seagate drives return this value in these bytes. The entire unit should be replaced.
Page 307: Release (6) Command
12.34 Release (6) command Obsolete. If the drive receives this command, a Check Condition status is sent. 12.35 Release (10) command Obsolete. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev. D...
Page 308: Report Device Identifier Command
12.36 Report Device Identifier command The Report Device Identifier command (see Table 198) requests that the drive send device identification infor- mation to the initiator. Table 198: Report Device Identifier command (A4h) Byte Operation Code (A3h) Reserved Reserved Reserved Reserved Reserved (MSB) Reserved...
Page 309 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.
Page 310: Report Luns Command
12.37 Report LUNs command 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.
Page 311 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 Byte (MSB) (MSB) LUN List (MSB) n–7 (MSB) Field definitions (listed alphabetically) Table number LUN List Length The LUN List Length field contains the length in bytes of the LUN list that is available to be transferred.
Page 312: Request Sense Command
12.38 Request Sense command 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.
Page 313: Reserve (6) Command
12.39 Reserve (6) command Obsolete. If the drive receives this command, a Check Condition status is sent. 12.40 Reserve (10) command Obsolete. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev. D...
Page 314: Logical Unit Reservation
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.
Page 315: Parameter List Format For Third-Party Addressing
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. Table 203: Parameter list format for third-party addressing Byte (MSB) (MSB)
Page 316: Rezero Unit Command
12.41 Rezero Unit command Obsolete. If the drive receives this command, a Check Condition status is sent. 12.42 Search Data Equal command Obsolete. If the drive receives this command, a Check Condition status is sent. 12.43 Search Data High command Obsolete.
Page 317: Seek (10) Command
12.46 Seek (10) command The Seek (10) command requests that the disc drive seek to the specified Logical Block Address. This com- mand is implemented with the disc drive specific parameters listed in Table 204. Table 204: Seek (10) command (2Bh) Byte Reserved Logical Block Address (MSB)
Page 318: Send Diagnostic Command
12.47 Send Diagnostic command This command requests that the disc drive perform diagnostic tests on itself, or perform other optional opera- tions. 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.
Page 319 Table 206: Supported Send Diagnostic pages Page Code Description Supported Diagnostic pages 01h - 0Fh SCSI Enclosure Services Information (ESI) pages Translate Address page Field definitions (listed alphabetically) Table number 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.
Page 320 - 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. Directs the device server to complete the target’s Default Self-Test.
Page 321: Supported Diagnostic Page-Send Diagnostic
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 com- mand includes only the first four bytes (Receive Diagnostic version given in Table 191).
Page 322: Translate Address Page-Send Diagnostic
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 fol- lowing the Receive Diagnostic Results command.
Page 323: Diagnostic Page-Send Diagnostic
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 Byte Page Code (A0h) Reserved (MSB) Reserved...
Page 324: Set Device Identifier Command
12.48 Set Device Identifier command The Report Device Identifier command (see Table 211) requests that the device identifier information in the log- ical 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.
Page 325 Set Device Identifier Parameter List Table 212: Report Device Identifier parameter list Byte Field definitions (listed alphabetically) Table number Identifier This field contains the vendor-specific value to be returned in Report Device Identifier commands. Fibre Channel Interface Manual, Rev. D Identifier...
Page 326: Set Limits Command
12.49 Set Limits command Not implemented. If the drive receives this command, a Check Condition status is sent. Fibre Channel Interface Manual, Rev. D...
Page 327: Start/Stop Unit Command
12.50 Start/Stop Unit command 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 simu- lated stopped condition.
Page 328: Synchronize Cache (10) Command
12.51 Synchronize Cache (10) command 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 logi- cal block from the cache memory is written to the physical medium.
Page 329: Synchronize Cache (16) Command
12.52 Synchronize Cache (16) command 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 logi- cal block from the cache memory is written to the physical medium.
Page 330: Test Unit Ready Command
12.53 Test Unit Ready command 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.
Page 331: Verify (10) Command
12.54 Verify (10) command 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 com- mand is being executed if the initiator supports disconnect/reconnect. Table 217: Verify (10) command (2Fh) Byte Reserved...
Page 332: Verify (12) Command
12.55 Verify (12) command 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 com- mand is being executed if the initiator supports disconnect/reconnect. Table 218: Verify (12) command (AFh) Byte Reserved...
Page 333 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.
Page 334: Verify (16) Command
12.56 Verify (16) command 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 com- mand is being executed if the initiator supports disconnect/reconnect. Table 219: Verify (16) command (8Fh) Byte Reserved...
Page 335 RelAdr (Relative Address) This function is not supported by drives described in this manual. 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.
Page 336: Write (6) Command
12.57 Write (6) command 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) Byte Reserved Transfer Length Control Field definitions (listed alphabetically) Table number Control See Control Bytes in Section 11.2.1.6.
Page 337 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 Invalid logical block address Target reset since last command from this initiator...
Page 338: Write (10) Command
12.58 Write (10) command 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 con- trol.
Page 339 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.
Page 340: Write (12) Command
12.59 Write (12) command 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 con- trol.
Page 341 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.
Page 342: Write (16) Command
12.60 Write (16) command 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 con- trol.
Page 343 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 num- ber of logical blocks that are transferred.
Page 344: Write And Verify (10) Command
12.61 Write and Verify (10) command 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.
Page 345: Write And Verify (12) Command
12.62 Write and Verify (12) command 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.
Page 346 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 num- ber of logical blocks that are transferred.
Page 347: Write And Verify (16) Command
12.63 Write and Verify (16) command 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.
Page 348 RelAdr (Relative Address) This function is not supported by drives described in this manual. 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 num- ber of logical blocks that are transferred.
Page 349: Write Buffer Command
12.64 Write Buffer command 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.
Page 350 Table 228: Mode definitions Write combined header and data (Section 12.64.1) Write data (Section 12.64.2) Download microcode Download microcode and save (Section 12.64.3) Download microcode with offsets Download microcode with offsets and save (Section 12.64.4) Mode Definition Fibre Channel Interface Manual, Rev. D...
Page 351: Combined Header And Data Mode (000B)
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 indi- cates that no data transfer takes place.
Page 352: Download Microcode With Offsets And Save Mode (111B)
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 condi- tion, the logical unit terminates each write buffer command with this mode (111b) with a Check Condition sta- tus, a sense key of Illegal Request, and sets the additional sense code to Command Sequence Error.
Page 353: Write Long Command
12.65 Write Long command 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 com- mand is usually issued before issuing a Write Long command.
Page 354: Write Same (10) Command
Control See Section 11.2.1.6. LBdata (Logical Block data) Seagate fibre channel drives do not support this bit. Logical Block Address The 32-bit address of the logical block affected by this command. Number of Blocks The number of contiguous logical blocks to be written.
Page 355: Write Same (16) Command
Control See Section 11.2.1.6. LBdata (Logical Block data) Seagate fibre channel drives do not support this bit. Logical Block Address The 32-bit address of the logical block affected by this command. Number of Blocks The number of contiguous logical blocks to be written.
Page 356: Xdread (10) Command
12.68 XDRead (10) command The XDRead (10) command requests that the target transfer the xor data generated by an XDWrite or Regen- erate command to the initiator. If the logical unit is reserved, a reservation conflict occurs when an XDRead command is received from an ini- tiator other than the one holding the logical unit reservation.
Page 357: Xdread (32) Command
12.69 XDRead (32) command The XDRead (32) command requests that the target transfer the xor data generated by an XDWrite or Regen- erate command to the initiator. If the logical unit is reserved, a reservation conflict occurs when an XDRead command is received from an ini- tiator other than the one holding the logical unit reservation.
Page 358 Field definitions (listed alphabetically) Table number 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 con- tain the number of bytes specified by the Additional CDB Length field, the command shall be terminated with a Check Con- dition status.
Page 359: Xdwrite (10) Command
12.70 XDWrite (10) command 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 com- mand.
Page 360 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. The device server accesses the media in performing the command prior to returning Good status.
Page 361: Xdwrite (32) Command
12.71 XDWrite (32) command 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 com- mand.
Page 362 Field definitions (listed alphabetically) Table number 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 con- tain the number of bytes specified by the Additional CDB Length field, the command shall be terminated with a Check Con- dition status.
Page 363: Xdwriteread (10) Command
12.72 XDWriteRead (10) command 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 fol- lowed by an XDRead (10) command with the same Logical Block Address and Transfer Length.
Page 364: Xdwriteread (32) Command
12.73 XDWriteRead (32) command 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 fol- lowed by an XDRead (32) command with the same Logical Block Address and Transfer Length.
Page 365 Control See Section 11.2.1.6. DPO (Disable Page Out) No data is cached. The DPO bit is only meaningful if the RCD bit of Mode Select Page 8 is set false (caching enabled). Disable Write The data transferred from the initiator is written to the medium after the xor operation is complete. The data is not written to the medium.
Page 366: Xpwrite (10) Command
12.74 XPWrite (10) command 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 initia- tor other than the one holding the logical unit reservation.
Page 367: Xpwrite (32) Command
12.75 XPWrite (32) command 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 initia- tor other than the one holding the logical unit reservation.
Page 368 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. The host expects that logical blocks accessed by this command are likely to be accessed again in the near future.
Page 369: Drive Features
13.2 Self-test operations Default Self-test (DST) technology is part of a system to recognize drive fault conditions that qualify it for return to Seagate. If the drive fails the test, remove it from service. 13.2.1 Default self-test The default self-test is mandatory for all device types that support the Send Diagnostics command. The response is simply a Good status if the test is successful or a Check Condition status if the test fails.
Page 370: Device Self-Test Modes
When a device server receives a Send Diagnostics command specifying a self-test to be performed in the fore- ground mode, the device server returns status for that command after the self-test has been completed. Not all Seagate drives support this mode. While performing a device self-test in foreground mode, the device server responds to all commands except Inquiry, Report LUNs, and Request Sense with a Check Condition status, a sense key of Not Ready and an additional sense code of Logical Unit Not Ready, Self-test In Progress.
Page 371: Elements Common To Foreground And Background Self-Test Modes
While the device server is performing a self-test in the background mode, it shall terminate with a Check Con- dition status any Send Diagnostics command it receives that meets one of the following criteria: a. The Self-test bit is one; or b.
Page 372 Table 241: Device Self-test mode summary When How to abort status is the Device Mode returned Self-test Fore- After the Abort Task task ground self-test is management complete function Back- After the Send Diagnos- ground CDB is tics command validated with Self-test Code field set to 100b...
Page 373: Seagate Technology Support Services
(1-800-SEAGATE) is the Seagate toll-free number (1-800-732-4283) to access our automated self-help and directory assistance for Seagate support services. Using a touch-tone phone, you can find ser- vice and support phone numbers, answers to commonly asked questions, troubleshooting tips and specifica- tions for disc drives 24 hours daily.
Page 374 Seagate service center representative for warranty-related issues. Resellers or end users of drive products should contact their place of purchase or one of the Seagate warranty service cen- ters for assistance. Have your drive’s “ST” model number and serial number available.
Page 375 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 11:45 . and 1:00 .
Page 376 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 ern time) Monday through Friday, except as noted. If your country is not listed here, direct dial one of our tech- nical support locations.
Page 377: Glossary
Appendix A. Glossary This section contains a glossary of terms used in this publication. ABTS Abort Sequence. ABTX Abort Exchange. Accept. 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.
Page 378 Arbitrated loop topology A topology where L_Ports use arbitration to establish a point-to-point circuit. A configuration that allows multi- ple 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 trans- mit frames, and if so, the allowable number of frames to transmit.
Page 379 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 ini- tiated.
Page 380 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.
Page 381 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.
Page 382 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 informa- tion category within a single Sequence.
Page 383 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.
Page 384 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. 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.
Page 385 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).
Page 386 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 Channel FC-4 Region A set of N_Ports connected either point-to-point or to a common fabric, such that any N_Port in the set can successfully complete the N_Port Login procedure with all other N_Ports in the set and successfully maintain...
Page 387 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.
Page 388 Hexadecimal notation. 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. Hertz = 1 cycle per second. Identifier.
Page 389 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.
Page 390 Jitter, deterministic (DJ) Timing distortions caused by normal circuit effects in the transmission system. Deterministic jitter is often sub- divided into duty cycle distortion (DCD) caused by propagation differences between the two transitions of a sig- nal and data dependent jitter (DDJ) caused by the interaction of the limited bandwidth of the transmission system components and the symbol sequence.
Page 391 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.
Page 392 Meter. Media Access Control. Mandatory A function which is required to be supported by a compliant implementation of FC-PH. Master of link. Mega bit. Mega byte. Mega baud. Meaningful A control field or bit shall be applicable and shall be interpreted by the receiver, wherever it is specified as meaningful.
Page 393 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.
Page 394 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 Initializa- tion. Nanosecond. Network Time Protocol. OESB Originator Exchange Status Block.
Page 395 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.
Page 396 Power on state In this state, any circuits or optical devices respond to controls resulting from higher levels. 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.
Page 397 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.
Page 398 Receiver sensitivity The minimum acceptable value of average received signal at point 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.
Page 399 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. Radio Frequency Interference. RIIN reflection induced intensity noise.
Page 400 RVC_ID Responder VC_ID. RVCS Read virtual circuit status. Receiver. RX_ID Responder_Exchange_Identifier. s or sec Second(s). signal-to-noise ratio. S_ID Source_Identifier. S_Length Security_Length. S_Type Security_Type. SBCCS Single byte command code sets. State change notification. Stacked connect request. SCSI Small Computer System Interface. SCSI device A device that originates or services SCSI commands.
Page 401 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. Sequence recipient The N_Port which receives data frames from the sequence initiator and, if applicable, transmits responses (Link_Control frames) to the sequence initiator.
Page 402 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.
Page 403 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.
Page 404 Upper layer protocol. 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 FC- Unsolicited control...
Page 405 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.
Page 406 Fibre Channel Interface Manual, Rev. D...
Page 407 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 Abort Prefetch Caching Parameters page 230 Abort Sequence 52 Abort Task Set FCP CMND Payload 128 Aborted Command disc drive sense keys 149...
Page 408 Allow Login Without Loop Initialization Fibre Channel Interface Control page 239 Alternate Credit Model F_Port Common Service Parameters 68 N_Port Common Service Parameters 60 Alternate Sector Translate Address page–Receive Diagnostic Alternate Sectors Per Zone Format Parameters page 223 Alternate Track Translate Address page–Receive Diagnostic Alternate Tracks Per Volume Format Parameters page 223...
Page 409 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...
Page 410 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 Continuous Increase SEQ_CNT F_Port Common Service Parameters 68 N_Port Common Service Parameters 60 Continuously Increasing Offset F_Port Common Service Parameters 68 N_Port Common Service Parameters 60 Control...
Page 411 FCP CMND header 126 FCP DATA frame header 137 FCP RSP header 140 FCP XFER RDY header 134 Frame header format 24 Data Length FCP CMND Payload 128 Data Overlay Allow PRLI Accept Payload 74 PRLI Payload 72 Data Protect disc drive sense keys 149 Data Strobe Offset Count Error Recovery page 218...
Page 412 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 XDWrite (32) command 347 XDWriteRead (10) command 349 XDWriteRead (32) command 350 XPWrite (10) command 352 XPWrite (32) command 353 Disable Page Out–Force Unit Access Mode Sense data 247...
Page 413 Enable Spin-Down Spin-Down Control Status page 123 Enable Threshold Comparison Log Parameter structure 192 Enable Vital Product Data Inquiry command 168 enclosure request 124 enclosure requested information 110 Enclosure Services disc drive inquiry data 170 enclosure services interface 101 command format 104 Enclosure Services Interface Page Device Address page 114 Device Identification page 117...
Page 414 FC Services Type Code RFT_ID Payload 99 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 FCP CMND. See Fibre Channel Protocol Command FCP DATA. See Fibre Channel Protocol Data FCP RSP.
Page 415 Persistent Reserve In parameter data for read reservations 251 Persistent Reserve In parameter data for ready keys 250 Global Logging Target Save Disable Control Mode page 233 Global Process Logout TPRLO Accept Payload 83 TPRLO Payload 81 GLTSD. See Global Logging Target Save Disable good status 258 Group Code 130 Hard Address of Originator...
Page 416 Interleave Format Parameters page 223 Format Unit command 161 intermediate status 258 intermediate–condition met status 258 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.
Page 417 LIP F8 Received Count Link Status page 120 LIP Loop A/B Initiate LIP Action Specific Bits 111 LIPA 42 LIRP 43 LISA 43 LISM 36 List Binary Log Parameter structure 192 List Parameter Log Parameter structure 192 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...
Page 418 Loss of Signal Count Link Status page 120 RLS Accept Payload 86 Loss of Synchronization Count Link Status page 120 RLS Accept Payload 86 Low Revision Capability Entries 94 LP. See List Binary LP. See List Parameter LPN. See Logical or Physical Notch LS Command Code.
Page 419 PLOGI Payload 58 Node Port End to End Credit Class Service Parameters 62 Node Port ID of Originator ADISC Payload 91 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...
Page 420 Firmware Numbers page 179 Format Parameters page 223 Implemented Operating Definition page 175 Informational Exceptions Control page 243 Inquiry command 168 Jumper Settings page 181 Log Page format 191 Log Sense command 190 Mode Select page descriptor header 209 Mode Sense command 211 Mode Sense page descriptor header 214 Non-Medium Error page 197 Notch page 235...
Page 421 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 Parameter Control Bits Device Self-test Results Log parameter data format 202 Parameter Length Device Self-test Results Log parameter data format 202 Enclosure Request 110 Log Parameter structure 192...
Page 422 PLPB. See Prevent Loop Port Bypass PM. See Performance Mode PMI. See Partial Medium Indicator point-to-point 10 service 33 Port disc drive inquiry data 170 Port A Device Address page 114 Port A Name Device Address page 114 Port A Port_Identifier Device Address page 114 Port A Position Device Address page 114...
Page 423 protocol 6 PS. See Parameter Savable QErr. See Queue Error Management Queue Algorithm Modifier Control Mode page 233 Queue Error Management Control Mode page 233 R_CTL. See Routing Control RAC. See Report A Check Random Relative Offset F_Port Common Service Parameters 68 N_Port Common Service Parameters 60 RAREA.
Page 424 Prefetch (16) command 259 Read (10) command 264 Read (12) command 266 Read (16) command 268 Read Capacity (10) command 273 Read Capacity (16) command 275 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...
Page 425 Rotational Offset Rigid Disc Drive Geometry Parameters page Round Unit Attention page 216 rounding 154 Routing Control basic link services header 52 common transport header 97 extended link services header 56 FCP CMND header 126 FCP DATA frame header 137 FCP RSP header 140 FCP XFER RDY header 134 Frame header format 24...
Page 426 Sense Key Specific Valid 147 Extended Sense Data 145 Field Pointer bytes 147 Format Indication bytes 148 Sense Length Valid FCP RSP Payload 142 SEQ_CNT. See Sequence Count SEQ_ID. See Sequence Identifier Sequence Count basic link services header 52 common transport header 97 extended link services header 56 FCP CMND header 126 FCP DATA frame header 137...
Page 427 Spin-Down Control Status 123 SSEC. See Soft Sectoring Stacked Connect Request Class 3 Service Parameters 70 Class Service Parameters 62 Service Option Class 3 fields 70 Service Option fields 64 standard inquiry data format 296 standards 5 Standby Power Condition page 241 Standby Condition Timer Power Condition page 241 Start...
Page 428 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...
Page 429 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 UnitOFL. See Logical Unit Off Line Unrecoverable read error Read (6) command 263 Unrecovered read error Read (10) command 265 Read (12) command 267 Read (16) command 269...
Page 430 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 XPWrite (10) command 352 XPWrite (32) command 353 Index-24 Fibre Channel Interface Manual, Rev.
Page 432 Seagate Technology LLC 920 Disc Drive, Scotts Valley, California 95066-4544, USA Publication Number: 77767496, Rev. D, Printed in USA...

Seagate 77767496 Product Manual

1 Publication Overview

2 Introduction to Fibre Channel

3 Fibre Channel Standards

4 Introduction to Topologies

5 Data Encoding (FC-1)

6 Framing Protocol (FC-2)

7 Classes of Service (FC-2)

8 FC Arbitrated Loop Concepts

9 Fibre Channel Link Services

10 Enclosure Services Interface (ESI)

11 SCSI Operations

12 Commands

13 Drive Features

14 Seagate Technology Support Services

Glossary

Quick Links

Related Manuals for Seagate 77767496

Summary of Contents for Seagate 77767496