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

486 Chapter21
Logging Location Codes
Control Process Logging Location Codes
the :NETCONTROL TRACEON command is legal and does not violate file
system security rules. If this does not reveal the cause, see Appendix A ,
“Submitting a CR,” of this manual.
136 CLAS0002 MESSAGE: INTERNAL ERROR; Device open
CAUSE: While attempting to rendezvous a specific protocol to the link
driver, NETCP encountered an error (PARM = 32-bit status returned by
the call to ns_rendezvous_to_driver).
ACTION: NETCP assumed the rendezvous failed. If this was a LAPB
device, it was also not told to connect. See Appendix A , “Submitting a
CR,” of this manual.
138 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: During early initialization of NETCP during startup, validation
of the NMCONFIG file failed (PARM = 16-bit result code returned by
the call to validatenetxport).
ACTION: The transport did not start. Using NMMGR, open and validate
the NMCONFIG configuration file to find any errors. Correct the errors
and validate again. Then restart the network.
143 CLAS0002 MESSAGE: BUFFER MANAGER; Buffer manager error
CAUSE: While starting a network NI having a nonzero number of
buffers configured for IP Store/Forward, NETCP was unable to create a
frozen buffer pool to provide those buffers (PARM = 32-bit status
returned by the call to bmgr_create_pool).
ACTION: The NI was not started. Using NMMGR, check total
Store/Forward buffers for each NI configured. Depending on the error, it
is possible too much frozen memory is being used by the system, but
this can change with time. Use GLANCEXL or a similar utility to check
memory usage by the system. If memory is not the cause and the
problem persists even if retried after a suitable waiting period, see
Appendix A , “Submitting a CR,” of this manual.
163 CLAS0002 MESSAGE: Path verify
CAUSE: NETCP is about to execute a Path Verify operation because of a
possible path change detected by the Transport software, such as
excessive retransmissions or a redirect message from a GATEWAY.
NETCP logs this event, then forwards Path Verify messages to all
general protocols and to the ICMP server, if any, then waits up to 15
seconds for replies to all those messages. General protocols which fail to
respond will cause logging of error 629 after the timeout (PARM =
number of duplicates).
Path Verify storms (a large number of Path Verify operations during a
short time period) can occur if a heavily used high speed link suddenly
fails. During storms, if NETCP receives new Path Verifies or any other
requests while awaiting previous replies, they are queued for later