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

Chapter 16 197
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: All such errors are caused by bugs in the upper layer protocol.
Attempt to determine what protocol was trying to bind, then see
Appendix A, “Submitting an SR.”
MESSAGE: A data buffer is too long.
224 ($E0) CAUSE: During diagnostic loopback testing, the driver was asked to
prepare a data block for transmission, but the block length or memory
allocation was beyond the driver’s DMA capabilities.
ACTION: This problem should only be seen in diagnostics, however it
should not be occurring at all. Specify a shorter loopback length, and
see Appendix A, “Submitting an SR.”
MESSAGE: One or more bad utility parms passed to driver.
225 ($E1) CAUSE: The driver received a utility register access request from an
upper level tool program such as PVGUTIL, but the register number
specified was out of the range of legal register values for the selected
register set.
ACTION: This is an informational error only. This problem most likely
occurred while diagnosing some previous problem. Retry the operation
using a legal register number for the register set you have selected.
MESSAGE: A data buffer is too short.
226 ($E2) CAUSE: A diagnostic status, loopback, or statistics operation did not
provide a buffer large enough for the link driver to return all the driver
information being requested.
ACTION: All such errors are caused by version mismatchesbetween the
link driver and the modules requesting the data, or bugs in the modules
requesting the data. Contact your Hewlett-Packard Representative to
determine if additional software patches are already available to
correct this problem.
MESSAGE: One or more bad unbind parms passed by upper level
protocol.
228 ($E4) CAUSE: The driver received an unbind (separate) from an upper layer
protocol module, but the specified rendezvous ID was out of range of
legal rendezvous ID values for this driver, or the corresponding
rendezvous table entry state indicated no bind had occurred or an
unbind had already occurred. The protocol was supposed to pass a
rendezvous ID value previously returned to it by the driver, when that
protocol did a bind. The protocol may be trying to unbind twice, or
unbind from the wrong link.
ACTION: This problem most likely occurred while stopping a running
network subsystem. Attempt to determine which subsystem was being
stopped when the error occurred and, if possible, which upper layer
protocol was unbinding. Future attempts to start that same protocol
will probably fail until the entire network is stopped or the system is