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

Chapter 18 419
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
ACTION: This error is sometimes fatal, causing the remainder of the
driver's processing to be skipped. May be followed by another error
giving more information about what kind of reply the driver was trying
to send; check log data for that error and look it up also. If the link does
not seem to be responding, attempt to shut down and restart the
network and/or link. If the problem persists, wait until it occurs again,
then use Control-B at the console to halt the system, take a memory
dump, and reboot, see Appendix A , “Submitting a CR.”
2320 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During a shutdown operation by an upper level subsystem, the
driver was preparing to send a reply to the unbind_request, but
encountered an error while trying to send the port message
(“Cause” = 32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem has
already shut the driver down while this one was trying to close it. If this
happens every time, see Appendix A , “Submitting a CR.”
2360 CLAS0001 MESSAGE: No adapter card found on specified PCI bus.
CAUSE: During initial driver startup, a PCI bus was not found at the
hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Use NMMGR to verify the path in
NMCONFIG is correct and complete, and matches the path where a
WAN ACC Sync MUX adapter card is installed in your computer
backplane. A diagram of the backplane slot paths, often found in the
rear of your system near the backplane, may help you. You can also try
an offline diagnostic utility such as MAPPER, or an online utility such
as SYSMAP, to precisely determine your hardware configuration. If
necessary, change the NMCONFIG configurations or contact your
Hewlett-Packard Representative for assistance in determining paths or
correcting bus hardware problems.
2400 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: While attempting to send a bind 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).
ACTION: This error is sometimes fatal, causing the remainder of the
driver's processing to be skipped. May be followed by another error
giving more information about what kind of reply the driver was trying
to send; check log data for that error and look it up also. If the link does
not seem to be responding, attempt to shut down and restart the
network and/or link. If the problem persists, wait until it occurs again,
then use Control-B at the console to halt the system, take a memory
dump, and reboot, see Appendix A , “Submitting a CR.”