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

520 Chapter21
Logging Location Codes
Control Process Logging Location Codes
NETCP encountered an error trying to start the PXP protocol module
(PARM = 32-bit status returned by the call to tcp_module_config).
Always preceded by another error from a different entity (having a
different Entity number, such as 151–160), the configurator, logging the
reason for the original failure.
ACTION: This error in itself was not fatal, and general protocol startup
continued. However, dynamic name resolution will fail. 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 a
CR,” of this manual.
654 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While attempting to start all the general protocols because a
:NETCONTROL command was starting a new instance of Transport,
NETCP encountered an error trying to start the IPU (IP Update)
module (PARM = 32-bit status returned by the call to
tcp_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: The general protocols were started, but Transport will not
work. Older versions of Transport will improperly continue the startup
after this error, however path resolution will fail, and Transport may
also hang when stopped. Record the previous error and this error. Stop
the network. If there is no hang, then try restarting the network. If the
error still occurs, a common cause is that NMMGR “Unguided Confide”
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, 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 a CR,” of this manual.