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

402 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
Logging Sublocation Codes
The following are the logging sublocation codes reported by the WAN
ACC Sync MUX link drivers, including sublocation code, log class, log
message, and the appropriate cause of and action to take for each.
For meanings of 32-bit status values generated by the driver, refer to
the sections on status values.
1020 CLAS0001 MESSAGE: Cannot freeze a memory area.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator was preparing to send configuration data to
the driver, but encountered an error while trying to freeze that data
into memory (“Cause” = 32-bit status from the call to freeze).
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the operation. The open
did not succeed. The module configurator cleaned up and returned an
error to the subsystem.
1040 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator was preparing to send configuration data to
the driver, 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 start it. The
open did not succeed. The module configurator cleaned up and returned
an error to the subsystem.
Retry the operation. If this does not help, try stopping all networks
using the link, then retry. If the problem still persists, halt the system
and take a memory dump, then see Appendix A , “Submitting a CR.”
1060 CLAS0001 MESSAGE: An unexpected timeout occurred.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator sent configuration data to the driver, then
encountered a timeout while awaiting the correct reply message
(“Cause” = 32-bit status from the call to extend_receive, saying there
was a timeout).
ACTION: The link driver is probably hung because of a problem in the
driver, or the driver may have sent the wrong message back. The open
did not succeed. The module configurator cleaned up and returned an
error to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell