NS3000/iX Error Messages Reference Manual (36923-90043)

310 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: All such errors are caused by bugs in the upper layer protocol
or mismatched software revisions. Attempt to determine which protocol
was trying to send, then see Appendix A , “Submitting a CR.”
239 ($EE) MESSAGE: Bad message for current state.
CAUSE: This is a generic error, reported when the driver received a
request from outside when the driver was not in a state where it could
process that type of request, or the when driver has already processed a
message of this type and was not expecting another. The driver may
have encountered a previous fatal error, may be in the middle of
startup, shutdown, or a recovery or dump operation, a message may
have arrived too late, or the sender may be confused.
ACTION: If the message has replies, the driver will attempt to send an
error reply back to the sender. If another error has already occurred,
this event may be ignored. Otherwise, if the problem happens
frequently, or if external subsystems are noticeably impacted after the
error, see Appendix A , “Submitting a CR.”
240 ($F0) MESSAGE: Unknown file record format.
CAUSE: The trace or log formatter attempted to decode a record header
to obtain basic information such as length and version, but on
inspection found that the record does not appear to be a 100Base-T
record supported by this formatter.
ACTION: The formatter will attempt to print this record in raw form.
You may be trying to format a trace or log file taken on a different
system that has newer software than the system you are formatting on.
Format the file on the system you took the trace or log on, or contact
your Hewlett-Packard Representative to check if patches are already
available to update the software on your current system.
242 ($F2) MESSAGE: Unknown data format.
CAUSE: The trace or log formatter attempted to decode a data entry
header. There was sufficient data to cover the entry’s stored length, and
the entry header looked OK, but when decoding was attempted, the
entry had an unknown tag, there wasn’t enough entry data for this
version of the entry, or a decoder routine was missing code to handle
this version of the entry.
ACTION: The formatter will attempt to print this record in the raw
form. You may be trying to format a trace or log file taken on a different
system that has newer software than the system you are formatting on.
Format the file on the system you took the trace or log on, or contact
your Hewlett-Packard Representative to check if patches are already
available to update the software on your current system.