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

196 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Cannot stop tracing.
209 ($D1) CAUSE: After a link-open operation by an upper level subsystem failed,
the link module configurator tried to clean up, but encountered an error
trying to disable driver tracing.
ACTION: Probably the link driver returned an error reply when asked
to disable tracing. The driver may have a problem, or may already have
shut down. Check for other, driver-specific error messages which may
give more information about the problem, and look them up also. If no
other errors are found, see Appendix A, “Submitting an SR.
MESSAGE: Cannot send a trace request.
210 ($D2) CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator found that the link was configured to enable
tracing at startup. After successfully opened a trace file, the
configurator encountered an error trying to enable driver tracing.
ACTION: Probably the link driver returned an error reply when asked
to enable tracing. The driver may have a problem. Check for other,
driver-specific error messages which may give more information about
the problem, and look them up also. If no other errors are found, see
Appendix A, “Submitting an SR.
MESSAGE: Unimplemented operation attempted.
218 ($DA) CAUSE: The driver was asked to, or attempted to perform an operation
which it is not currently designed to handle.
ACTION: If possible, the driver will attempt to send an error reply in
response to the request. However, depending on the operation, the
driver may not know how to do this, and will not attempt it. Determine
what you were trying to do, then contact your Hewlett-Packard
Representative for assistance.
MESSAGE: Buffer chaining is not supported.
220 ($DC) CAUSE: An upper layer protocol attempted to send data to the driver
using a buffer containing chained data. No link subsystems support
this data format.
ACTION: There is a problem in the upper-layer protocol. Attempt to
determine which application produced the error, then see Appendix A,
“Submitting an SR.
MESSAGE: One or more bad bind parms passed by upper level
protocol.
223 ($DF) CAUSE: This is a generic error, reported when the driver received a
bind (rendezvous) from an upper layer protocol, but the parameters in
the request were not satisfactory to the driver. There are a number of
separate causes; look up the specific sublocation code that was logged,
for more information.