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

Chapter 16 263
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: One or more bad bind parms passed by upper level
protocol.
8210 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but the pointer to the information block was not
specified (“Cause” is not used here).
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: One or more bad bind parms passed by upper level
protocol.
8240 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but the specified length of the information block
header was not the length expected (“Cause”= 32-bit value giving the
bad length which was specified).
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: One or more bad bind parms passed by upper level
protocol.
8270 CLAS0001 CAUSE: The driver received a bind (rendezvous) from an upper layer
protocol module, but the specified length of the information block body
was not the length expected (“Cause”= 32-bit value giving the bad
length which was specified).
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.