Dell Emulex Family of Adapters - Manual (Page 703)

Emulex Drivers for Windows User Manual P010077-01A Rev. A
Appendix A. Error and Event Log Information
FC/FCoE Error and Event Logs
703
Additional Notes on Selected Error Codes
These are error codes which may be seen more frequently than others or which indicate
conditions that you might be able to solve by investigation and correction of issues in
the SAN configuration.
Note: The nomenclature of “0x” is used as the prefix for the byte code fields because
those byte codes are actually hex values.
Node Timeout (Code 0xAA)
This event code indicates that a particular device has not been found (if the message is
logged during device discovery) or that a particular device has been removed from the
fabric. If this message is seen, determine if there is something wrong with the
connection of that device to the SAN (cables, switches or switch ports, status of the
target device itself).
SCSI Command Error (0x9A) and SCSI Check Condition (code 0x9B)
Code 0x9A indicates that the SCSI command to a particular device was responded to
with an error condition (the target and LUN information, along with the SCSI status,
are provided).
In the specific case of code 0x9B, this code indicates that the device responded with the
specific status of Check Condition – the ASC/ASCQ information provided in bytes
0x12 and 0x13 will allow you to find out what status is being reported by the target and
determine if there is an action that can be performed to return the device to functional
status.
Nameserver Response (Code 0x98)
This code is useful in determining if the expected number of targets in a SAN
configuration are being presented by the nameserver to the requesting adapter. The
number in byte 0x11 is the number of targets returned to the nameserver query made
by the adapter – if the number of targets does not match expectations, examine the SAN
configuration found in the switch tables and if that information shows targets or
devices still missing, check connections between the switch ports and those devices.
Context Allocation Failures
There are a number of event codes for which the interpretation contains the phrase
“context allocation failure” – these types of events are referring to the internal memory
constructs of the Emulex Storport Miniport driver and as such are intended for Emulex
design engineers’ information. If you encounter this type of code, contact Emulex
support for analysis and determination if that particular event may be an indicator of a
failed adapter or of some issue with interaction between the adapter, the Emulex
Storport Miniport driver, the host operating system, and the host memory.
Note: Context allocation failures are rare.