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

Chapter 16 265
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding. The bind failed. The driver logged the error, then
attempted to send an error reply message back to the protocol module
and continue.
Either there is a bug in the driver or upper layer protocol software, or
there is a system software mismatch. You may require additional
software patches; contact your Hewlett-Packard Representative for
assistance.
MESSAGE: (Varies)
8390 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but when it attempted to save information about that
protocol’s inbound buffer pool, a lower level routine reported an error,
as described by the Message (“Cause” is not used here). Most likely the
either the table is full, there is an internal problem with the Buffer
Manager, or the size of physical buffers in the pool is smaller than the
minimum supported by the driver.
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding.
The bind failed. The driver logged the error, then attempted to send an
error reply message back to the protocol module and continue.
If the table is full, too many protocols are started; close some
unnecessary subsystems and try again. Otherwise there may be
something wrong with the buffer pool or Buffer Manager, system
memory may be low, or there may be a driver bug. Shut down the
network and restart it. If the problem happens every time, see
Appendix A, “Submitting an SR.”
MESSAGE: (Varies)
8420 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but when it attempted to save information about that
protocol's address (SAP), a lower-level routine reported an error, as
described by the Message (“Cause”= 32-bit encoded value of the SAP
being bound). Most likely either the address is already in the driver’s
table, or the table is full.
ACTION: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding.
The bind failed. The driver logged the error, then attempted to send an
error reply message back to the protocol module and continue.