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

422 Chapter18
PCI LAPBMUX Link 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.
If upper level network subsystems appear hung, try shutting them
down manually, or shutting down and restarting the network link; if
the problem persists, see Appendix A , “Submitting a CR.”
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 HP Representative for assistance.
2720 CLAS0001 MESSAGE: Subsystem is binding to link driver.
CAUSE: An upper layer protocol has successfully bound (rendezvoused)
to the link driver (“Addr” = 32-bit encoded protocol address (SAP) value
for this protocol module). Being bound means the driver can now route
incoming data frames to this protocol.
ACTION: None. This is an informational message only. A similar
message is logged later, when the protocol unbinds. If this is the first
bind, the link driver will now attempt to reconnect the link.
2760 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While beginning a driver start or restart operation, the driver
tried to set the heartbeat timer, but encountered an error
(“Cause” = 32-bit status from the call to lnk_start_timer). This timer
was to be used to periodically awaken the driver so it could verify card
health; the driver cannot start if this timer cannot be started. If this
error is reported, it is because the driver has already encountered some
other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and
look it up also. The driver did not dump, but will still attempt to
auto-reset itself, up to a total of 12 times or more.
If the problem persists, the system may be low on timers; try stopping
some applications before retrying again.
2800 CLAS0001 MESSAGE: Subsystem is unbinding from link driver.
CAUSE: An upper layer protocol has begun to unbind (separate) from
the link driver (“Addr” = 32-bit encoded protocol address (SAP) value for
this protocol module). Once unbound, the driver can no longer route
incoming data frames to this protocol.
ACTION: None. This is an informational message only. A similar
message is logged earlier, when the protocol binds. If this is the last
bind, the link driver will now attempt to disconnect the link.