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

410 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
1520 CLAS0001 MESSAGE: Cannot validate configuration file.
CAUSE: After successfully reading configuration data for a link being
started, the link module configurator checked the data and found it was
not valid (“Cause” is not used here). For NS/3000, probably the link
type and NI type do not match.
ACTION: The module configurator cleaned up and returned an error to
the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the
NMCONFIG file and is LAPBMUX link type. If the subsystem being
started is NS, verify the link type matches the NI type for the network
being started.
If these are not the problem, an incorrect version of NMMGR may have
been used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=82 to check versions of NMMGR components.
The format of your NMCONFIG file may be incompatible with the link
driver version installed on your system. Run NMMGRVER.PUB.SYS to
update your NMCONFIG file to a newer version, or restore an older
version from a backup tape, whichever is appropriate.
If the problem still occurs, contact your Hewlett-Packard
Representative for assistance in using NMMGR to configure
LAPBMUX links.
1540 CLAS0001 MESSAGE: Bad hardware ID or path.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator did not find a valid hardware path specified in
NMCONFIG (“Cause” = 32-bit hex value from a system table which
holds the first 4 bytes of IODC information from the adapter card).
ACTION: The module configurator cleaned up and returned an error to
the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches
the path where a supported WAN ACC Sync MUX adapter card is
installed in the computer backplane. Contact your Hewlett-Packard
Representative for hardware assistance.
1560 CLAS0001 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
(“Cause” = 32-bit status from the call to nmopentrace).
ACTION: This is an informational error that tracing was not started.
The link came up, but the error was returned to the upper level
subsystem, which may decide to shut the link back down again.