Browse Prior Art Database

COMMANDS USED TO TUNNEL NON-SCSI TRANSACTIONS TO A FIBRE CHANNEL ATTACHED CONTROLLER

IP.com Disclosure Number: IPCOM000013421D
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 3 page(s) / 44K

Publishing Venue

IBM

Abstract

COMMANDS USED TO TUNNEL NON-SCSI TRANSACTIONS TO A FIBRE CHANNEL ATTACHED CONTROLLER

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 35% of the total text.

Page 1 of 3

COMMANDS USED TO TUNNEL NON-SCSI TRANSACTIONS TO A FIBRE

CHANNEL ATTACHED CONTROLLER

This disclosure describes a method of tunneling commands through the Fibre Channel interface. These commands are sent by specialized host applications that handle such functions as configuration, code download and debug. These tunneling Fibre/SCSI commands are needed because most of the commands contain more data than can fit in a SCSI CDB (Command Descriptor Block).

Two commands are defined for this purpose: Send Tunneling Transaction and Receive Tunneling Results. The following describes the fields in each command.

Timeout - Timeout value in milliseconds for the requested operation. If the operation does not complete within this timeframe, the operation will be canceled and the Status will be returned indicating Check Condition with sense information of "Operation Failed - Timeout (9x-DEADx)". This is an optional parameter, a value of zero indicates there is no timeout.

Parameter List Length - Number of bytes in the parameter list including Parameter Data. Note: This is not the total number of bytes to transfer for this CDB. If the Parameter List contains an operation which requires additional data, more data will be transferred. The FCP_DL indicates the maximum bytes to transfer for this CDB.

Debug - Indicates command should execute in debug mode.

There are two channels of communication associated with the Send Tunneling Transaction/Receive Tunneling Results command pair. The Debug flag in the CDB indicates which of these paths should be utilized within the controller. Normal configuration commands and transactions should not set the Debug flag. The Debug flag is provided as a means for development to execute commands through an alternate communications path if the normal path is not functioning due to a code bug.

Only one Receive Tunneling Results or Send Tunneling Transaction command can be executes at a time on each of these communications paths. If one of these commands is received prior to final status being presented to a previous Receive Tunneling Results or Send Tunneling Transaction command with the same setting of the Debug flag, Status will be returned indicating Check Condition with send information of "Aborted Command - Overlapped Commands Attempted".

Note: It is the initiator's responsibility to ensure that the transaction is not interfered with by another Initiator. These commands are for use by configuration tools and other utilities, not normal application programming.

Transaction Token - Token which must be sent with the corresponding Receive Tunneling Results

1

Page 2 of 3

command in order to retrieve any results data.

Destination Service - Transaction specific data.

Major Function - Transaction specific data.

Minor Function - Transaction specific data.

Parameter Data Length - Length of the Parameter Data contained in the Parameter List. This field must be equal to Parameter List Length - 28. Must be <= maximum buffer size -...