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

370 Chapter19
Logging Location Codes
Control Process Logging Location Codes
mode was, at some time in the past, used to create the first NS
configuration ever put into the NMCONFIG file, and that a bug in the
Validation function of an earlier version of Transport then corrupted a
hidden record in that file, which specifies IPU startup information.
If you suspect “Unguided Config” mode was used, you can try to repair
the hidden record. First make a copy of the old NMCONFIG file. Then
one way to fix it is to purge and recreate the entire file using “Guided
Config” mode. If your file is complicated, you may first want to try
another way, which is to create a new dummy file named, say,
NMCONFGT, and using “Guided Config” mode, configure any network
NI (for instance, a dummy LAN network). Then reopen the original
NMCONFIG file and use the “Copy Subtree” utility function to copy the
NETXPORT.GPROT.IPU path, out of the dummy NMCONFGT file and
into NMCONFIG, overwriting the existing subtree. Then try restarting
the network. If the error goes away, you can purge NMCONFGT. But if
the same error still happens, there may be more corruption in the file
than just that one record; try recreating the entire file, but using
“Guided Config” mode wherever possible.
If, after recreating or attempting to repair the file, the problem still
persists, there is most likely a bug in Transport; see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
655 CLAS0002 CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP successfully started some modules, then encountered an error
trying to start the ICMP (PING) Server module (PARM = 32-bit escape
code returned by the call to pxp_module_config). Always preceded by
another error from another entity (having a different Entity number,
such as 151–160), logging the reason for the original failure.
ACTION: This error in itself was not fatal, and general protocol startup
continued. However, the PING service will not be available, and pings
from other nodes will go unanswered. To clear the problem, stop then
restart the network. If this problem persists, record the previous error
and this error, then see Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: INTERNAL ERROR; Internal resource error
656 CLAS0002 CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP successfully started some modules, then encountered an error
trying to start the Net Timers module (PARM = 32-bit status returned
by the call to nettmr_module_config). Always preceded by another
error from Net Timers, logging the reason for the original failure.
ACTION: TCP and ARP will not work without timers. Some versions of
Transport will erroneously continue the startup after this error. Record
the previous error and this error. Stop the network. Then try restarting