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

480 Chapter21
Logging Location Codes
Control Process Logging Location Codes
ACTION: One or more network protocols were not completely started.
Stop the network and use NMMGR to make sure a nodename is
configured and the NMCONFIG file is validated. If the file looks good,
try restarting the network. If the problem persists, see Appendix A ,
“Submitting a CR,” of this manual.
19 CLAS0002 MESSAGE: INTERNAL ERROR; Out of resources
CAUSE: While building the IP alias list, NETCP discovered there are too
many network NI’s configured in the NMCONFIG file (PARM =
maximum networks allowed).
ACTION: Check the configuration file, and if it is not the problem see
Appendix A , “Submitting a CR,” of this manual.
20 CLAS0002 MESSAGE: INTERNAL ERROR; Bad/unknown port message
CAUSE: NETCP received an unexpected message that was not a reply,
while waiting for a reply message having a specific function code
(PARM.(0:16) = function code and PARM.(16:16) = interface code of
received message).
ACTION: It is not possible to tell from NETCP logging what message it
was expecting, however if disk logging was enabled, the entire received
message was logged, which may aid debugging. The flow of normal
NETCP operations has been interrupted, and a transport hang may be
imminent, especially if new :NETCONTROL commands are issued. It may
be necessary to restart the system to clear this problem. See Appendix
A , “Submitting a CR,” of this manual.
21 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While initially starting NETCP, or while starting NI specific
protocols on a LAN, GATEHALF, or ROUTER network, NETCP’s
attempt to get a buffer for a nodal path report failed (PARM = 32-bit
status returned by the call to bmgr_get_buffer).
ACTION: One or more network protocols were not completely started.
Stop transport and retry the operation. If the problem persists, see
Appendix A , “Submitting a CR,” of this manual.
22 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: While initially starting NETCP, or while starting NI specific
protocols on a LAN, GATEHALF, or ROUTER network, NETCP could
not get path report information from the NETXPORT.GLOBAL.REPORT
path in the NMCONFIG file (PARM = 32-bit status returned by the call
to nmconfgetdata).
ACTION: One or more network protocols were not completely started.
Stop the network and use NMMGR to check the NMCONFIG file and
validate it. If the file looks good, try restarting transport. If the problem
persists, see Appendix A , “Submitting a CR,” of this manual.