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

260 Chapter16
100VG-AnyLAN and HP-PB 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.
Check the system console; if the driver is shutting down or doing a
dump, wait until that completes. In these cases, several protocols may
experience this same error. If the driver is not shutting down or dying,
the protocol may be sending binds to the driver at the wrong time. See
Appendix A , “Submitting a CR,” and file an CR against the network
subsystem being started.
8210 CLAS0001 MESSAGE: One or more bad bind parms passed by upper level
protocol.
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.
8240 CLAS0001 MESSAGE: One or more bad bind parms passed by upper level
protocol.
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.