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

418 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
shutting down or doing a dump, wait until that completes. Retry the
operation. If the driver still does not become usable after this, use
Control-B at the console to halt the system, take a memory dump, and
reboot, see Appendix A , “Submitting a CR.
2240 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a new open from an upper layer subsystem,
at a time the driver was not able to process these requests, such as
during shutdown or after a fatal software error (“Cause” = 16-bit
encoded value, giving driver input event code and current state:
Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if the driver is
shutting down or doing a dump, wait until that completes. Retry the
operation. If the driver still does not become usable after this, use
Control-B at the console to halt the system, take a memory dump, and
reboot see Appendix A , “Submitting a CR.
2250 CLAS0001 MESSAGE: Link disconnected.
CAUSE: The last upper layer subsystem has unbound itself from the
driver, triggering a link disconnect This event is also logged if the link
unexpectedly drops due to a cable disconnect, powerfail, severe line hit,
or other recoverable error (“Status” = 32-bit status giving the reason for
the disconnect, 0 = normal).
ACTION: This event is informational only. If the network is being shut
down, no action is required.
However, if the link was supposed to be up or the message appears
frequently while the link is up, this indicates possible cabling problems;
make sure cabling is securely connected.
2260 CLAS0001 MESSAGE: Link connected.
CAUSE: The first upper layer subsystem to bind to the driver triggered a
link connect, which was successful (“Mode” = the local mode: DTE or
DCE, “Protocol” = SDLC or LAPB). This event is also logged after the
link or cable has been successfully reconnected after being
disconnected, or on a link reconnect following severe line-hit, power
failure, or other recoverable error.
ACTION: This event is informational only.
No action is needed unless the message appears frequently while the
link is up, indicating possible cabling problems; make sure cabling is
securely connected and properly routed away from sources of
interference.
2280 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: While attempting to send a reset request to a lower manager
during startup, the driver encountered an error on the send
(“Cause” = 32-bit status returned by the call to send_msg).