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

Chapter 18 411
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
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 WAN
Sync MUX link (SDLCMUX, LAPBMUX) to enable tracing at startup.
1580 CLAS0001 MESSAGE: Subsystem is opening link.
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up (“Transport” = name of the
subsystem which is starting the link, or its subsystem number if the
configurator does not know the name).
ACTION: None. This is an informational event only. A similar event will
be logged when the link is closed.
1600 CLAS0001 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 (“Cause” = 32-bit status from the call to
sio_trace_req).
ACTION: This is an informational error that tracing was not disabled. If
this error occurs it is because some other error has already occurred.
The link open did not succeed.
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.”
1610 CLAS0001 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
(“Cause” = 32-bit status from the call to sio_trace_req).
ACTION: This is an informational error that tracing was not enabled.
The link came up, but the error was returned to the upper level
subsystem, which may decide to shut the link back down again.