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

482 Chapter21
Logging Location Codes
Control Process Logging Location Codes
33 CLAS0002 MESSAGE: INTERNAL ERROR; Async request from link
CAUSE: NETCP received an asynchronous event message containing a
negative error status, from the DCLDM controlling one of the LAPB
links on the network (PARM = 32-bit status field from the message).
ACTION: NETCP stopped the device associated with the link, also
stopping any attached protocols and driver. Run the PSIDAD diagnostic
on the appropriate PSI card. If the PSI looks good, it may be possible to
restart the device using :NETCONTROL ADDLINK=linkname;
NET=niname. If the problem persists, see Appendix A , “Submitting a
CR,” of this manual.
40 CLAS0002 MESSAGE: INTERNAL ERROR; A reads
CAUSE: While NETCP was rendezvousing a particular protocol to a
driver, an attempt to connect a LAPB device failed for some reason
other than a close already being in progress (PARM = 32-bit status
returned by the call to xp_connect_the_driver).
ACTION: Check the appropriate PSI card and its cabling. If it looks
good, another possibility is that the DCLDM or LAPB driver are hung;
see Appendix A , “Submitting a CR,” of this manual.
42 CLAS0002 MESSAGE: INTERNAL ERROR; Device open
CAUSE: An attempt to physically start a device failed with a nonzero
status meaning an unexpected error or warning occurred (PARM =
32-bit status returned by the call to nslopenlink). Physical startup
includes all creation and startup of a link driver and its dependent
modules, selftest, startup, downloading and configuration of link
hardware, plus optional creation of a DCLDM, so any error along the
way will be detected here by NETCP.
ACTION: Stop Transport and enable all available logging for the link
subsystem corresponding to the NI type of the network reporting the
error, then restart Transport and reproduce the problem, monitoring
logged data for any problems. If this does not reveal the cause, link
tracing can be used on the affected link to collect even more data.
Check that the physical path specified in the NMCONFIG file is correct
for all link devices on the network being started, and that a card is
installed in the slot for that path. You can stop the system then use
IOMAP to verify physical path numbers.
For links other than X25, probably the link driver failed to obtain a
resource, the link hardware was already in use by an IBM
communications subsystem such as NRJE, the link hardware failed
selftest or its firmware version is not supported by the driver, the
download file was inaccessible, corrupt or has the wrong version, or
executing the download caused the link hardware to hang and resulted
in a driver or module configurator timeout or other problem. Use
NMMGR to check the link configuration in NMCONFIG and use
SYSDIAG to check the link hardware.