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

Chapter 18 421
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
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 a CR against the network
subsystem being started.
2600 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 SDI address family was not one of the
values supported by the driver (“Cause” = 32-bit value giving the bad
address family 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.
2640 CLAS0001 MESSAGE: Link common reported a protocol bind problem.
CAUSE: While attempting to setup a rendezvous entry (by calling
lnk_rendez), an error was returned to the ISR. (“Cause” = 32-bit
integer specifying the SAP that was trying to rendezvous).
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.
2680 CLAS0001 MESSAGE: Link common reported an inbound buffering problem.
CAUSE: After completing a read and delivering a data buffer to an
upper layer protocol, the ISR encountered an error when trying to setup
inbound buffer pool. (“Cause” = 32-bit status from Lnk_buf_initl).