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

372 Chapter19
Logging Location Codes
Control Process Logging Location Codes
ACTION: This secondary error is not the main concern, though it may
indicate additional problems. The general protocols were started, but
the specified network failed to start because of the first error. Retry the
operation. If the problem persists, see Appendix A, “Submitting an SR,”
of this manual.
MESSAGE: INTERNAL ERROR; Data dictionary error
660 CLAS0002 CAUSE: While stopping an X25 network because of a system shutdown,
or a :NETCONTROL STOP command for one or all networks, NETCP
first stopped all devices before stopping any protocols, then encountered
an error trying to delete a CM Port Dictionary entry it had previously
added to keep track of one of the X25 device ports (PARM = 16-bit result
code returned by the call to dict_delete). The CM Port Dictionary is
an operating system lookup service used by, but not part of, Transport.
There should be one entry per X25 device, named “X25.linkid”, where
“linkid” consists of 4 unprintable bytes defining the binary SDI link
ID for that link, dynamically assigned by the Link Support Services
subsystem.
ACTION: This error in itself was not fatal, and network shutdown
continued. No resources were lost. If the problem happens every time,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: Bad status
661 CLAS0002 CAUSE: After successfully starting a LAN 802.3 or Ethernet link and
all its network specific protocols because a :NETCONTROL 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 network 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 LAN link again.
If the same problem persists, see Appendix A, “Submitting an SR,” of
this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
664 CLAS0002 CAUSE: While starting Transport’s first active X25 NI because a
:NETCONTROL command was issued, NETCP encountered an error
trying to start the X25 Flow Control Manager (PARM = 32-bit status
returned by the call to netfc_config). NETCP keeps track of the
number of X25 networks started, and only makes this call then starting
the first one. The Flow Control Manager dynamically allocates the flow
control buffer pools for X25.