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

Chapter 18 397
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
207 ($CF) MESSAGE: Cannot update to link table.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator successfully started the driver, but
encountered an error trying to update the link to the link table
(“Cause” = 32-bit status from the call to lsslktbladd).
ACTION: The module configurator cleaned up and returned an error to
the subsystem. Possibly too many links are started. Try starting a
different link, tosee if that works.If not, first try doinga :LINKCONTROL
@ command to see if any LSS errors occur. If they do, you may need to
reinstall MPE software; contact your Hewlett-Packard Representative
for assistance. Otherwise try restarting the system to see if it corrects
the problem or LINKCONTROL errors. If none of these suggestions
helps, see Appendix A , “Submitting a CR.”
208 ($D0) MESSAGE: Cannot open tracing.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator found that the link was configured to enable
tracing at startup, but encountered an error trying to open the trace
file.
ACTION: Using NMMGR, check if a filename was configured. If so,
verify it is a legal MPE filename. A group and account may need to be
specified. Make sure the user starting the link has the necessary
capabilities to create that file in the group and account specified. Check
whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks. Make sure the
version of the NMCONFIG file matches the rest of the system software,
by running NMMGRVER.PUB.SYS. If none of these suggestions solves the
problem, contact your Hewlett-Packard Representative for assistance
with configuring a LAPBMUX link to enable tracing at startup.
209 ($D1) MESSAGE: Cannot stop tracing.
CAUSE: After a link-open operation by an upper level subsystem failed,
the link module configurator tried to clean up, but encountered an error
trying to disable driver tracing.
ACTION: Probably the link driver returned an error reply when asked to
disable tracing. The driver may have a problem, or may already have
shut down. Check for other, driver-specific error messages which may
give more information about the problem, and look them up also. If no
other errors are found, see Appendix A , “Submitting a CR.”
210 ($D2) MESSAGE: Cannot send a trace request.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator found that the link was configured to enable
tracing at startup. After successfully opened a trace file, the
configurator encountered an error trying to enable driver tracing.