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

Chapter 19 359
Logging Location Codes
Control Process Logging Location Codes
ACTION: This error was not fatal, and network startup continued.
However, additional errors will occur later when NETCP tries to delete
the linkname (see error 660). In addition, certain X25 operations may
not work correctly. Restart the network. If this problem continues, see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Device open
619 CLAS0002 CAUSE: While attempting to start a device on an existing NI type other
than a ROUTER, NETCP encountered an error trying to create a frozen
inbound buffer pool for that device’s reads (PARM = 32-bit status
returned by the call to cp_get_read_pool). Always preceded by
another error indicating the original failure (see error 404).
ACTION: The device did not start. Check the packet size configured in
the NMCONFIG file; for non LAPB links, pool creation parameters are
computed from the base figures found in this file. 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 these are not the causes
and the problem persists even if retried after a suitable waiting period,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
620 CLAS0002 CAUSE: While attempting to send a device start message to an existing
NI in response to a :NETCONTROL command, NETCP encountered an
error on the send (PARM = 32-bit status returned by the call to
send_msg).
ACTION: The device was started at the NETCP and MAP layers, but
not at the NI layer. As a result, no packets can be successfully sent or
received over that device, and other errors, especially NI errors, may
occur if attempted. Restart the network. If the problem persists, see
Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
621 CLAS0002 CAUSE: After successfully starting an FDDI link and all its network
specific protocols because a :NETCONTROL START command was
issued, NETCP encountered an error trying to send a broadcast
information message to the UDP protocol module (PARM = 32-bit
status returned by the call to send_msg).
ACTION: This error in itself was not fatal, and NETCP startup
continued. After this failure, most of Transport, with the exception of
UDP, will probably run correctly. However, certain actions, such as Path
Verifies, can indirectly result in more sends to UDP, which may cause
more errors. When convenient, try stopping Transport using
:NETCONTROL STOP, then restart it and bring up the FDDI link again.
If the same problem persists, see Appendix A, “Submitting an SR,” of
this manual.
MESSAGE: Bad status