- Integrated Systems
- About Us
- Integrated Systems
- About Us
03-29-2001 04:00 PM
Event Id 11
the driver detected a controller error on |device|scsi|cpqfcalm1
this error doesn't appear to effect the cluster at present which is working, but errors now appear once a minute..
can anyone issist as to what error relates to.
04-09-2001 04:00 PM
Event ID 11 [ CPQFCALM ]
- The driver detected a controller error on \Device\ScsiPort6
Event ID 15
- Device not ready for access
All event log entries generated by CPQFCALM which relate to Fibre Channel events WILL HAVE an event ID of 11. Although the system event log may contain other event IDs (such as 9 or 15) which list CPQFCALM as the source, the CPQFCALM driver DOES NOT generate these errors. Event log entries that list CPQFCALM as the source and have event IDs other than 11, are actually generated by the Windows NT SCSIPORT driver acting on behalf of CPQFCALM.
DECODING WINDOWS NT CPQFCALM EVENT ID 11 ENTRIES:
To help troubleshoot the cause of CPQFCALM event ID 11 errors, look at the first 32-bit value on the row labeled 0010. This information is located under "EVENT DETAIL" in the DATA box (refer to the bitmap attached to this IQ document for an example). Then, using the table below, look up this value to further define the cause of the error.
TABLE FOR DECODING CPQFCALM EVENT ID 11 ENTRIES:
An unknown Tachyon status value was received.
An unexpected SCSI frame was received.
A fatal error was detected by Tachyon, or a request for memory failed. The controller is taken offline.
A fatal hardware error occurred. The controller is taken offline.
Fibre Manager warning
Count of loop initialization primitives received.
Count of elastic store errors detected.
The port lost synchronization with the incoming data or the port is not receiving a signal from a node.
A laser fault was detected.
A loop timeout occurred because the loop was in a particular state for too long.
A laser fault, loss of synchronization, loss of signal or an elastic store error occurred.
The Tachyon is in an offline state.
Count of node logins received from remote nodes.
An unknown single frame sequence was received.
SCSI Command received.
SCSI Data received.
An unknown multiple frame sequence was received.
Count of sequences aborted by a remote node.
Controller ALPA has changed.
Count of loop down conditions that caused all previous node logins to be invalid.
Target Reset complete
Target Reset failed.
Count of node logouts
A recoverable PCI bus error occurred.
An unrecoverable PCI bus error occurred. The controller is taken offline.
A loop problem has occurred that has prevented the host controller from reinitializing the loop.
The link went down during the transmission of a frame.
The driver failed to obtain an arbitrated loop physical address for the controller. This indicates a fibre channel loop problem. The controller is taken offline.
The driver failed to initialize the controller due to a hardware or configuration error.
One or more elastic stores were detected in 60 seconds prior to the event log entry being generated. The 3 bytes nnnnnn contain the hexadecimal count that occurred.
Also, the information provided by the third and fourth values on row 0020 and 0030 can further assist in troubleshooting the error. If the event is associated with a particular device on the Fiber Channel Loop, these values will provide the Windows NT SCSI address (Bus number, Target ID, and logical Unit number) of that device. If these values each contain 000000ff, then the event is not a
07-17-2001 04:00 PM
Please email any info at email@example.com