• ATTO Celerity FC-161E
• ATTO Celerity FC-162E
• ATTO Celerity FC-164E

 The following operating systems are supported and tested.

• Windows 7
• Windows 8
• Windows 8.1
• Windows 10
• Windows Server 2008 R2
• Windows Server 2012
• Windows Server 2012 R2

 The following operating systems have not been tested but may work.

• Windows XP
• Windows Vista
• Windows Server 2003
• Windows Server 2008

To create installation media from the Celerity FC Installation CD:

1. Insert the Celerity FC Installation CD into a CD or DVD drive and the CD will automatically start. If the CD does not start, navigate to the root of the CD and run 'autorun.bat'.
2. Select "Windows Drivers" from the items on the left side of the screen.
3. Select the appropriate CPU based operating system from operating system choices.
4. Select "Create Driver Installation Media" for the desired operating system.
5. Follow the instructions for creating the installation media.

To create installation media from a Celerity FC driver download from the ATTO Technology website:

1. Go to the Downloads section of www.attotech.com and locate the driver download for your product and operating system.
2. Click on the link to download the file. Internet Explorer users may select 'Run' to automatically run the downloaded self-extracting executable. Otherwise, select a download destination and run the self-extracting executable when the download is complete.
3. Uncheck 'When done unzipping open .\Setup.exe'.
4. Select a different destination folder if desired and click 'Unzip' to extract the driver files.
5. The expanded software package may contain a scsiport subdirectory for Windows XP x86. Otherwise, use the driver in the base directory. Navigate to the folder with the desired driver.
6. Run 'makedisk.exe' and follow the instructions for creating the installation media.

• Modifying your registry incorrectly may result in making your machine unbootable. Please use care in editing the registry.
• All registry settings are DWORD values.
• The following settings can be found in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Clry16FC\Parameters\Device.

Event Type	Value (hexadecimal)	Description
Fatal	0x00000001	Fatal errors, always reported
Link	0x00000002	FC link events
SCSI	0x00000004	SCSI command errors
Protocol	0x00000008	FC protocol errors
Login	0x00000010	Device login/logout events
RSCN	0x00000020	RSCN events
Resource	0x00000040	Resource usage failures
Info	0x00000080	Informational messages
Underflow	0x00000800	Data underflow errors

In general, only errors that are output for event type 'Fatal' are significant; all others are mostly for informational or diagnostic purposes. When turning on event logging, be aware that certain events reported as errors are expected. For example, a SCSI Check Condition error will be reported for the first command sent to a device after power on or a reset condition. Also, certain data underrun errors are expected by the software and are normal.

All events report the adapter number on which the event occurred. The adapter number is simply the order in which Windows initialized the adapter channels and has no relevance to what slot the adapter is in or which channel of the adapter is being reported.

In the descriptions below, the ID is the Event ID reported in Event Viewer, and Severity is the Type reported in Event Viewer.

The following events are classified as 'Fatal' and are always reported.

ID	Severity	Event Message	Description
8192	Error	Error doing Bus Reset	An error occurred while the system was attempting to reset link attached to the adapter channel.
8195	Error	Invalid SCSI Request Block.	The operating system sent an unrecognized SCSI request block.
8198	Error	No PCI I/O Base Address	The operating system was not able to map the device registers.
8199	Error	Can't Get Uncached Extension	The operating system was unable to allocate the memory required for the uncached data required by the driver.
8200	Error	LunMask Allocation Error.	The operating system was unable to allocate the memory required for the LUN mask array.
8201	Error	LunMask Registry Error - Total Value.	The number of LUN mask records masking all LUNs on targets is greater than the number that the driver can handle, which is 256. This can happen if LUN mask records are created for new devices, then some of those devices are removed from the system and new records are added for the new devices but not removed for the old ones. Use the LUN mask utility to clean up records no longer needed.
8202	Error	LunMask Registry Error - Partial Value.	The number of LUN mask records masking specific LUNs on targets is greater than the number that the driver can handle, which is 256. This can happen if LUN mask records are created for new devices, then some of those devices are removed from the system and new records are added for the new devices but not removed for the old ones. Use the LUN mask utility to clean up records no longer needed.
8203	Error	Maximum number of adapters exceeded.	More than 64 adapter channels discovered. The driver can handle at most 64 adapter channels.
32770	Error	Unrecoverable FC layer error	The FC layer encountered an unrecoverable error. The driver will attempt to reinitialize the FC layer
32777	Error	Stuck Frame Manager interrupt	The Frame Manager interrupt could not be cleared in 100 iterations through the Frame Manager Interrupt procedure. The error is not fatal in that the FC layer may recover from the situation. It sometimes occurs during loop disturbances. If it is persistent, it may indicate a bad Fibre Channel cable or a misbehaving device.
32778	Error	SEST Programming Error. {Reason} Additional info: {Value}	This error indicates that invalid parameters were used to program the SCSI Exchange State Table (SEST). The {Reason} can be one of: # of SEST entries out of range SEST length not a power of 2 SEST Logical or Physical Address is 0 Invalid SEST address alignment The Additional Info is either the SEST length or the SEST address. This error should never be seen in a released driver.
32779	Warning	ABTS received for Exchange OX_ID (OX_ID) Port ID: {PortID}	An ABTS (Abort Sequence) Basic Link Service request has been received. An ABTS is typically sent by a SCSI Initiator (HBA) when a request has timed out. If Target Mode is disabled or if the Initiator is current- ly not logged in, this warning will always be reported regardless of the setting of EventLogMask. In these cases, the reported {PortID} will be 0. If Target Mode is enabled and the Initiator is logged in, this warning is reported only if the EVENT_TYPE_SCSI bit is set in EventLogMask.
32785	Error	PCI Bus Error, channel being reset PCI Status: {Status} Function Status: {Fstat} PCI-X Received Split Completion: (0/1) PCI-X Unexpected Split Completion: (0/1) PCI-X Split Completion Discarded: (0/1)	A PCI Bus error has occurred. An attempt to reset and restart the adapter channel will be performed. Any I/O requests that are outstanding will be terminated with an error status (the OS may retry them). The additional information provided should be forwarded to Technical Support for analysis if the error persists.
32788	Error	Target Command received, Target Mode disabled! OX_ID {OX_ID} Frame Type {n}	A SCSI command was received when Target Mode is not enabled on the adapter channel. This error indicates that something is wrong with the Initiator sending the command - it is not legal to send a SCSI command unless properly logged in at both the FC2 and FC4 levels and the TGT bit was set in the PRLI (Process Login) response.
32789	Error	Unexpected Primitive Send completion.	The FC layer reported that a Primitive Send operation has completed. Since the OS and HW layers never send primitives, this completion is unexpected. This error should never occur in released drivers.
32790	Error	Unknown Event passed to {Function} Event {Event} Parameter {Parameter}	An unknown event was sent from the FC layer to the indicated function. The Event Code and associated Parameter are displayed. This error should never occur in released drivers.
32795	Error	Unknown frame type received. OX_ID {Originator Exchange ID} Frame Type {FrameType}.	An unknown frame type was received by the FC layer. This error indicates that some device sent an FC frame with an invalid or illegal FC Frame Type. The additional information should be reported to a Technical Support representative.
32798	Error	Multiple adapters with same Port Name {PortName}. Reflash and update WWNs of offending adapters.	Two or more adapter channels in the computer have the same Port Name. Only the last 12 digits of the Port Name are displayed. No two ports in the world should ever have the same Port Name. Adapters are shipped from the factory with unique Port Names. Each adapter has a WWN sticker on it. The user should use the NODENAM3.BAT batch file in the DOS\UTILITIES directory on the driver diskette to re- program the offending adapters' Port Names using the WWN indicated on the sticker.
32799	Error	More than 3 attempts to recover from PCI errors in the last minute. Channel is now inoperative.	After 3 attampts to recover from PCI errors within a one- minute period, the driver gives up and renders the adapter channel inoperative to avoid affecting the operation of the rest of the system. This error typically indicates that either the adapter or the slot into which it is plugged has a serious problem.
61456	Error	Initiator Not Logged In (Target Mode). OX_ID {Originator Exchange ID} Frame Type {Frame Type}.	A SCSI command has been received from an Initiator who is not currently logged in.
61468	Informational	Bus Reset Request Completed. Status: {n} ({Desc}).	This event indicates that a requested Bus Reset has completed. If there was no error during the reset procedure, this event will only be reported if the EVENT_TYPE_INFO bit is set in EventLogMask, otherwise it will be reported regardless of the EventLogMask.
61469	Error	Configuration parameters not found or corrupt. Please reflash card.	This event indicates that the driver could not read the configuration parameters for the indicated adapter. Default configuration values will be used. The adapter needs to have its flash memory rewritten.
61593	Error	Unknown Event Code. Code is {Code}. Least Significant Word is {Info}.	This event indicates that an unknown event code was generated by the driver code that the decoder does not know about. This event should never occur in a released driver.
61696	Error	Event Buffer Overflow. Number of Events Lost is {Count}.	This event indicates that events occurred faster than the OS could get them dumped to the event log on disk. This doesn't happen very often.
61969	Error	Unexpected Exchange Event {Event} (XID {n}).	This event indicates that an unexpected event code was passed internally to the driver's exchange callback function.
62013	Error	Chip error detected. Sliport Status:{n} Sliport Error1:{n} Sliport Error2:{n}	This event indicates that a chip error has occurred.
62014	Error	Chip error detected. Semaphore Post Error. Semaphore Status Register:{n}	This event indicates that the power on self test has errored.

The following events are classified as 'Link'.

ID	Severity	Event Message	Description
32769	Informational	Bus Reset started Status: # (meaning).	The link connected to the adapter channel is being reset. This can occur if the OS requests a bus reset to recover from some error situation or when a topology change is needed, for eaample when the channel is cur- rently in loop mode and needs to switch to point-to- point.
32772	Informational	FC Link Up.	The FC link is in the operational state - synchronization has occurred, and speed and topology have been determined.
32773	Informational	FC Link Down.	Synchronization has been lost.
32780	Informational	Login qualifier recovery complete Port ID {PortID}, Port Speed {Speed}, Topology {Topology}	Link speed and topology have been established and the FC link has received a Port ID.
32796	Informational	Hub port change detected. Int Status {IntStat}, Port Status {PortStat} Change detected on hub port(s) {Ports}.	A loop disturbance was detected on one of the hub ports on the 22XH card. The hub Interrupt and Port status are shown in hex.
32800	Informational	LIP occurred {count} time(s).	The indicated number of LIP (Loop Initialize) primitives have occurred. The link is attempting to initialize in Loop mode.
32801	Informational	NOS/OLS occurred {count} time(s).	The indicated number of NOS (Not Operational State) or OLS (Off Line State) primitives have occurred. The link is attempting to initialize in Point-to-Point mode.

The following events are classified as 'SCSI'.

ID	Severity	Event Message	Description
32779	Warning	ABTS received for Exchange OX_ID (OX_ID) Port ID: {PortID}	An ABTS (Abort Sequence) Basic Link Service request has been received. An ABTS is typically sent by a SCSI Initiator (HBA) when a request has timed out. If Target Mode is disabled or if the Initiator is current- ly not logged in, this warning will always be reported regardless of the setting of EventLogMask. In these cases, the reported {PortID} will be 0. If Target Mode is enabled and the Initiator is logged in, this warning is reported only if the EVENT_TYPE_SCSI bit is set in EventLogMask.
61440	Error	SCSI Error. Error Code {Code}, Sense Key {Key}, Add'l Sense Code {ASC}, Command Code {Cmd}, Path ID {Path}, Target ID {TargetID}, LUN {Lun}.	An error has been reported by the target device. The Error Code is usually 0x02 (Check Condition), in which case the Sense Key and Additional Sense Code displayed are valid. It is normal for the first command sent to a SCSI device after power on or reset to report a SCSI error, in which case the Sense Key would be 0x06 (Unit Attention) and the Additional Sense Code would be 0x29 (Power-On/Reset).
61446	Informational	SCSI Bus Reset Requested.	The OS is requesting that a bus reset be performed. This may happen in cases where a request times out and the Abort that the driver attempts is not successful. The Bus Reset will cause the FC layer to send Target Reset Task Management requests to every logged in target. Any requests outstanding at the time will be completed with a status of Aborted due to Bus Reset.
61470	Informational	Task Mgt Code {n} ({Desc}) LUN {n}, Initiator Port ID {n}	A task management command has been received.
61479	Informational	Task Mgt Sent, Code {n} ({Desc}) Target {n}, LUN {n}.	A task management command has been sent in initiator mode.
61482	Informational	Task Mgt Complete, Code {n} ({Desc}) Target {n}, LUN {n}.	A task management command has been successfully completed.
61483	Informational	Task Mgt Complete, Code {n} ({Desc}) Target {n}, LUN {n} Response Code {n} ({Desc}).	A task management command has been rejected.
61484	Informational	IOC Error (Initiator). IOC Status is {n} ({Desc}) Task Mgt Code {n} ({Desc}) Target {n}, LUN {n}	A task management request failed before being transmitted.

The following events are classified as 'Protocol'.

ID	Severity	Event Message	Description
61441	Error	IOC Error (Initiator). IOC Status is {n} {Desc}. Command Code {Cmd}, Path ID {Path}, Target ID {Targ}, LUN {Lun} LBA {Logical Block Address}.	A transport or other error has been detected on an Initiator mode request. Common errors reported might include 0x06, Aborted due to Bus Reset, or 0x0E, Lost Frame. Note that the Logical Block Address is only valid if the command is a read (0x28) or write (0x2A).
61442	Error	IOC Error (Target). IOC Status is {n} {Desc}.	A transport or other error has been detected on a Target Mode assist. These errors are very rare.

The following events are classified as 'Underflow'.

ID	Severity	Event Message	Description
61441	Error	IOC Error (Initiator). IOC Status is 21 (Data Underrun). Command Code {Cmd}, Path ID {Path}, Target ID {Targ}, LUN {Lun} LBA {Logical Block Address}.	A Data Underrun has occurred. Data Underruns may occur quite expectedly on certain commands, such as Inquiry, due to the OS or application program specifying a larger buffer than required to execute the command, hence this particular error has its own enabling bit in the Event- LogMask. Note that the Logical Block Address is only valid if the command is a read (0x28) or write (0x2A). In the specific case of an Inquiry command, the Inquiry Page number can be found in one of the bytes of the reported "LBA."

The following events are classified as 'Login'.

ID	Severity	Event Message	Description
32775	Informational	Port Database Update requested.	The Port Database is being updated. This happens whenever a change to the LUN masks has been made by the LUN mask application.
61443	Informational	Port Logged In. Port Name is {PortName}.	The indicated port has logged in. Note that only the last 12 digits of the Port Name are displayed.
61444	Informational	Port Logged Out. Port Name is {PortName}.	The indicated port has logged out. Note that only the last 12 digits of the Port Name are displayed. The logout may be explicit (requested by the device) or it may be implicit (it has gone offline without issuing a logout, its cable may have been pulled, etc.)

The following events are classified as 'Resource'.

ID	Severity	Event Message	Description
61445	Warning	Resource Failure. {ResourceType}. Unavailable Count is {count}.	The driver encountered a situation where not enough of the indicated resource is available. The ResourceType will be one of the following. (The Registry entry controlling the number of each resource is indicated in parentheses.) SEST Entries (NumSest) Exchange CB's (NumXcb) Sequence CB's (NumScb) S/G Lists (NumSgLists, SglPageSize) Exchange CB's and Sequence CB's are only used for Target Mode. When running out of SEST Entries, Sequence CB's, or S/G Lists, nothing bad will happen; the driver will retry the operation when the resources become available. If running Target Mode, however, and there are not enough Exchange CB's, the incoming command(s) will be dropped and the Initiator will time these requests out and issue Aborts. If this happens, the NumXcb registry entry should be adjusted to a higher value. Refer to the registry.txt file for a complete description of the resource entries.

The following events are classified as 'Info'.