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

Chapter 19 367
Logging Location Codes
Control Process Logging Location Codes
file may be corrupt, or there may be a bug in the NMS subsystem,
NMMGR, or NETCP; see Appendix A, “Submitting an SR,” of this
manual.
MESSAGE: INTERNAL ERROR; Internal resource error
645 CLAS0002 CAUSE: While stopping an NI because of a system shutdown or a
:NETCONTROL STOP command, NETCP was unable to delete the port
message pool it previously created for that NI and its attached protocols
(PARM = 32-bit status returned by the call to purge_pool).
ACTION: This error in itself was not fatal, and shutdown continued.
However, some amount of system memory that had been used by the
message pool may be inaccessible until after the next system restart. If
this problem happens repeatedly, there may be an operating system
problem or a bug in NETCP; see Appendix A, “Submitting an SR,” of
this manual.
MESSAGE: INTERNAL ERROR; NM Entry
646 CLAS0003 CAUSE: While initializing a new NI for a network that was being
started, NETCP successfully created a port message pool for use by that
NI and its attached protocols, but was unable to put the pool ID into a
new entity named “IP-NI” in the NS Registry (PARM = 32-bit status
returned by the call to reg_add_entity).
ACTION: This error was not fatal, and startup continued; use of the
Registry here is not critical. However, creation of the NS Registry by
NETCP may have failed (see error 285), or the Registry may be full. If
the message occurs every time, see Appendix A, “Submitting an SR,” of
this manual.
MESSAGE: INTERNAL ERROR; Module Deconfig Failed
647 CLAS0003 CAUSE: While shutting down an NI due to a system shutdown or a
:NETCONTROL STOP command, NETCP encountered an error while
trying to stop one of the NI specific protocols for that network (PARM =
32-bit escape code returned by the call to the module deconfigurator
that failed). Always preceded by another error from another entity
(having a different Entity number, such as 151–160), indicating the
cause of the original failure.
ACTION: This error in itself was not fatal, and shutdown continued.
However, some system resources may be lost until the next system
restart. Inspect the previous error, and if necessary see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: BUFFER MANAGER; Buffer manager error
648 CLAS0002 CAUSE: While reading the home node’s path report during initial
NETCP startup, or while starting some network specific protocols for a
LAN, GATEHALF or ROUTER network because a :NETCONTROL
command was issued, NETCP successfully read local node name data