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

Chapter 21 527
Logging Location Codes
Control Process Logging Location Codes
message content was logged in the NM logfile along with this error,
which may aid in debugging any hung modules. If the received message
looks like a Path Verify reply, there is a message length bug in the
general protocol module which sent it; this is not serious though it may
result in error 629 later. If the problem occurs repeatedly or a general
protocol bug is suspected, update to the latest Transport patches, and if
this does not solve the problem either, see Appendix A , “Submitting a
CR,” of this manual.
679 CLAS0002 MESSAGE: INTERNAL ERROR; Bad/unknown port message
CAUSE: While awaiting Path Verify replies from all general protocols in
response to multiple requests it sent previously, NETCP received a
message that was indeed a reply, but the function code in the message
was not the expected value (PARM.(0:16) = the function code that was
expected and PARM.(16:16) = interface code of received message).
ACTION: This error may be followed by a timeout of up to 15 seconds,
which is normal. Possibly some other module on the system sent a
message to the wrong place, and because whatever module sent it could
be expecting a reply which will never come, that module may now be
hung. Possibly one of NETCP’s previous reply waits timed out, but the
offending module has now decided to reply. For debugging purposes the
message content was logged in the NM logfile along with this error,
which may aid in debugging any hung modules. If the problem occurs
repeatedly or a general protocol bug is suspected, see Appendix A ,
“Submitting a CR,” of this manual.
680 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
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 encountered error when trying to
compute the total length of some NMCONFIG file data, prior to getting
a buffer large enough to hold all that data (PARM = 32-bit status
returned by the call to nmconfdatalength).
ACTION: You may have attempted to configure a larger network than is
currently supported by Transport; save a copy of your current
NMCONFIG file, then reduce the size of your configuration and try the
operation again. If your network is small and you therefore do not
suspect size as the cause, there may be some problem with the NMS
subsystem, NMMGR, or NETCP, so see Appendix A , “Submitting a
CR,” of this manual.
681 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
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 path report data from
the NMCONFIG file, then encountered an error trying to write that