HP 3000 Manuals HP 3000 Manuals
Control Process Logging Location Codes (contd.)
661 CLAS0002 Message: Bad status
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 "Submitting an SR" in
appendix A of this manual.
664 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
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.
Action: This error in itself was not fatal, and
network startup continued. However, X25 may not
operate correctly. If X25 connections are not
working, stop then restart the network. If the
problem persists, see "Submitting an SR" in
appendix A of this manual.
665 CLAS0002 Message: Bad status
Cause: After successfully starting a TOKEN 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
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 TOKEN link again. If the
same problem persists, see "Submitting an SR" in
appendix A of this manual.
666 CLAS0002 Message: Bad status
Cause: While processing a :NETCONTROL STATUS
command, NETCP encountered an error trying to
send a reply message back to the NETUI module
(PARM = 32-bit status returned by the call to
send_msg).
Action: This error in itself was not fatal, and
Transport should continue to run. However, if
the session which issued the :NETCONTROL STATUS
command still exists, that session will now be
hung. If the session does not exist, this also
indicates a bug since supported HP commands to
abort the session should have been disabled by
NETUI. A system restart will be required to
clear the session's hang. If the session is on
the system console, a :CONSOLE command may be
attempted to temporarily move the logical
console to another terminal until a system
restart is convenient. If the problem persists,
issue a :NETCONTROL TRACEON=MHDSBN command
beforehand, to enable NETCP tracing which may
capture the problem. When the problem occurs,
issue a :NETCONTROL TRACEOFF command from
another terminal, then take a system dump and
send in the dump and the resulting trace file;
see "Submitting an SR" in appendix A of this
manual.
668 CLAS0002 Message: Bad status
Cause: While processing a :NETCONTROL STATUS
command which reported an error because a
requested module was not active, or because no
buffer was available to hold excess error
information, NETCP then encountered another
error while trying to send a reply message about
the first error, back to the NETUI module (PARM
= 32-bit status returned by the call to
send_msg). The cause of the first error cannot
be determined, except if NETCP message tracing
was enabled, the message was traced.
Action: The second error in itself was not
fatal, and Transport should continue to run.
However, if the session which issued the
:NETCONTROL STATUS command still exists, that
session will now be hung. If the session does
not exist, this also indicates a bug since
supported HP commands to abort the session
should have been disabled by NETUI. A system
restart will be required to clear the session's
hang. If the session is on the system console,
a :CONSOLE command may be attempted to
temporarily move the logical console to another
terminal until a system restart is convenient.
If the problem persists, issue a :NETCONTROL
TRACEON=MHDSBN command beforehand, to enable
NETCP tracing which may capture the problem.
When the problem occurs, issue a :NETCONTROL
TRACEOFF command from another terminal, then
take a system dump and send in the dump and the
resulting trace file; see "Submitting an SR" in
appendix A of this manual.
669 CLAS0002 Message: Bad status
Cause: While processing a request sent by the
DIAL protocol module because a LAPB autodial
link is being connected, NETCP encountered some
kind of error (such as errors 315, 316, 322),
then encountered a second error trying to send
the bad reply message back to DIAL to report the
first error (PARM = 32-bit status returned by
the call to send_msg).
Action: Since DIAL never received its reply, it
may take up to 30 minutes for DIAL to time out
and reset itself, and during this delay, new
autodial connections cannot be established, and
sessions which attempt it may hang. To clear
this condition, first try a :NETCONTROL
DELLINK=linkname; NET=niname command against the
affected link, followed by a :NETCONTROL
ADDLINK=linkname; NET=niname. If this does not
help, a system restart will probably be required
to clear the hang. If the problem occurs again,
take a dump when the first error 669 is reported
and before any attempts to recover, and see
"submitting an SR" in appendix A of this manual.
670 CLAS0002 Message: Bad status
Cause: While bringing down a device because of
a serious asynchronous error, powerfail, or a
:NETCONTROL DELLINK command, NETCP encountered
an error trying to send a Path Verify message to
the UDP protocol module (PARM = 32-bit status
returned by the call to send_msg). The message
was to have told UDP to discard cached paths.
Action: In this case UDP will continue to
function, but may be unable to reach some
destinations. If you cannot reach needed UDP
destinations then you will need to restart
Transport. This is not generally a fatal error,
however some versions of Transport may
accidentally hang if this error appears. If the
problem occurs repeatedly, see "Submitting an
SR" in appendix A of this manual.
671 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: During startup of the SNMP module, the
configuration file was unlocked. But
afterwards, NETCP tried for up to 2 minutes to
lock the file again without success (PARM =
status from NMConflockfile). The 2-minute
timeout is not configurable.
Action: Network startup was incomplete. Stop
the network. Use :LISTF NMCONFIG.PUB.SYS,3 to
verify the NMCONFIG file exists and is not
opened. If any users are currently running
NMMGR, ask them to exit. Then restart the
network. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
673 CLAS0003 Message: INTERNAL ERROR; Device close
Cause: While bringing down a device because of
a serious asynchronous error, powerfail, or a
:NETCONTROL DELLINK command, NETCP encountered
an error when attempting to separate one of the
active protocols from the link driver (PARM =
32-bit status returned by the call to
ns_separate_from_driver).
Action: This in itself was not a fatal error,
and other device stop actions continued.
However, either the DCLDM or the link driver may
have failed, which indicates a problem. No
additional NETCP logging or tracing information
is available, though if problems continue, DCLDM
tracing and link tracing can be used to either
follow the separate request downward and locate
the point where errors occur. If the problem
persists, see "submitting an SR" in appendix A
of this manual.
674 CLAS0002 Message: INTERNAL ERROR; Wrong autodial cable
OUTBOUND; occupied
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI's autodial operation was not completed,
because the cable attached to the PSI card is
not the proper cable required for autodial
operations (PARM = 16-bit internal ldev number
of the device). Older versions of Transport may
print different messages for this error, such as
"OUTBOUND; occupied" or "INTERNAL ERROR; Auto
dial failure", though the actual problem is the
cable.
Action: Install the correct cable and retry the
operation. If the problem persists then see
"Submitting an SR" in appendix A of this manual.
677 CLAS0002 Message: Bad status
Cause: While awaiting Path Verify replies from
all general protocols in response to requests
sent previously, NETCP received a new message on
the control or reply subqueues of its port,
which was not one of the expected replies.
NETCP then encountered an error while trying to
requeue that request for later processing, by
resending it to itself (PARM = 32-bit status
returned by the call to send_msg).
Action: The new request message has probably
been lost, and depending on the purpose of
message, whatever module sent it may be
expecting a reply which will never come, so that
module or session may now be hung. For
debugging purposes the message content was
logged in the NM logfile along with this error,
which may aid in debugging any hung modules.
Check for other errors, and also check for Path
Verify storms by first enabling Class-5
Transport console logging in NMCONFIG, then
restarting Transport and retrying the
operations. Depending on the meaning of the
error status PARM, the NETCP port may have run
out of message frames, in which case a system
failure may occur soon, though stopping and
restarting Transport may be possible, and may
clear the problem until next time. See
"Submitting an SR" in appendix A of this manual.
678 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
new message on the reply subqueue of its port
that either was not a reply or whose length was
not right for a reply (PARM.(0:16) = function
code 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 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 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 "Submitting an SR"
in appendix A 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 "Submitting an SR" in appendix A
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
"Submitting an SR" in appendix A 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 data into a buffer it obtained a
short time earlier (PARM = 32-bit status
returned by the call to bmgr_write_buffer).
Action: NETCP was unable to write all the
required data, and attempted to recover and free
the buffer. The network operation that was
being performed will not work correctly.
Because the buffer given to NETCP by the buffer
manager should have been large enough to contain
all data that was to be written, there may be a
problem in either NETCP, the buffer manager, the
NMS subsystem, or NMMGR, or the NMCONFIG file
may be corrupt. Stop the network and retry the
operation. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
682 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While reading X25 configuration data
because a :NETCONTROL command was issued, NETCP
successfully read X25 data from the NMCONFIG
file, then encountered an error trying to write
that data into a buffer it obtained a short time
earlier (PARM = 32-bit status returned by the
call to bmgr_write_buffer).
Action: NETCP stopped trying to load additional
X25 data; some required data may not have been
loaded, but startup of that network probably
continued. Some or all X25 nodes may not be
accessible. Because the buffer given to NETCP
by the buffer manager should have been large
enough to contain all data that was to be
written, there may be a problem in either NETCP,
the buffer manager, the NMS subsystem, NMMGR, or
the NMCONFIG file may be corrupt. Use NMMGR to
check the X25 configuration in the file. Stop
the network and retry the operation. If the
problem persists, see "Submitting an SR" in
appendix A of this manual.
683 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While reading X25 configuration data
because a :NETCONTROL command was issued, NETCP
successfully computed the size of all applicable
X25 data in the NMCONFIG file, then encountered
an error trying to write a small descriptive
header onto the start of a a buffer it obtained
a short time earlier to hold all the X25
configuration data (PARM = 32-bit status
returned by the call to bmgr_write_buffer).
Action: No X25 data was actually buffered, and
NETCP attempted to recover and free the buffer.
Though startup of that X25 network probably
continued, the network will not operate
correctly. Because the buffer given to NETCP by
the buffer manager should have been large enough
to contain all data that was to be written,
there may be a problem in either NETCP, the
buffer manager, the NMS subsystem, NMMGR, or the
NMCONFIG file may be corrupt. Stop the network
and retry the operation. If the problem
persists, see "Submitting an SR" in appendix A
of this manual.
684 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: After NETCP successfully wrote
configuration data for an X25 network into a
buffer it obtained earlier, because a
:NETCONTROL command was issued, while trying to
crossmatch the X25 mappings NETCP encountered an
error trying to read a data entry out of that
same buffer (PARM = 32-bit status returned by
the call to bmgr_read_buffer).
Action: The current matching operation stopped,
then more merging of X25 mappings may have
continued, possibly causing more errors, then
the bad configuration data was passed to the X25
protocol module. The X25 network will probably
not operate correctly now. Because NETCP
already wrote to the buffer, it should have also
been able to read from it; probable causes are a
bug in NETCP or in the buffer manager. Stop the
network and retry the operation. If the problem
persists, see "Submitting an SR" in appendix A
of this manual.
685 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: After NETCP successfully wrote
configuration data for an X25 network into a
buffer it obtained earlier, because a
:NETCONTROL command was issued, while trying to
crossmatch the X25 mappings NETCP successfully
read one data entry out of that buffer, then
encountered an error trying to read other data
entries to match up to the first one (PARM =
32-bit status returned by the call to
bmgr_read_buffer).
Action: The current matching operation stopped,
then more merging of X25 mappings may have
continued, possibly causing more errors, then
the bad configuration data was passed to the X25
protocol module. The X25 network will probably
not operate correctly now. Because NETCP
already wrote to the buffer, it should have also
been able to read from it; since it already read
once, this indicates a probable bug in NETCP.
Stop the network and retry the operation. If
the problem persists, see "Submitting an SR" in
appendix A of this manual.
686 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: After successfully opening the NSDIR
network directory file, while preparing to read
X25 network directory information from the file,
NETCP was unable to obtain a buffer from its own
buffer pool large enough to hold the maximum
possible number of X25 mapping entries (PARM =
32-bit status returned by the call to
bmgr_get_buffer). The size of the buffer NETCP
tried to obtain was based on the size of the
mapping table, a value which was obtained from a
hidden field in the NI record of the NMCONFIG
file.
Action: No network directory data was read, and
NETCP attempted to recover and close the opened
file. Some versions of transport may then
attempt to build X25 mappings, even though no
buffer was obtained, and send a restart message
to X25. After the error, network startup may
continue to completion, but the resulting
network will probably not operate correctly.
Verify you have all the required patches,
especially a coherent set of patches required to
support 2048 X25 SVC paths under NMMGR and NS
Transport. Also verify that the number of X25
paths configured in the NMCONFIG file is within
the supported limits. If the problem still
cannot be found, see "Submitting an SR" in
appendix A of this manual.
688 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While starting or updating a ROUTER
network, because a :NETCONTROL command was
issued, NETCP successfully started a LAPB link
device, then encountered an error trying to read
information from the NMCONFIG file about the
number of mappings in that NI, prior to actually
loading the mappings (PARM = 32-bit status
returned by the call to nmconf3soninfo).
Action: No mapping entries were read, and
though network startup probably continued to
completion without a command error, you will not
be able to connect to any remote nodes
configured in the mapping entries. Verify you
have a coherent set of patches installed,
especially between Transport and NMMGR, and
especially if your NMCONFIG file contains a
large number of ROUTER mappings. Try stopping
and restarting the network. If the problem
persists, you may have a software installation
problem, a bug in the NMS subsystem, or a
corrupt NMCONFIG file; if necessary, see
"Submitting an SR" in appendix A of this manual.
689 CLAS0002 Message: Module Deconfig Failed
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error trying to delete the
NETIPC Socket Registry module (PARM. (0:16) =
error location within SOCKREG.NET.SYS and PARM.
(16:16) = error status from SOCKREG).
Action: This error in itself was not fatal, and
shutdown continued. However, depending on the
error it may not be possible to restart
Transport without first restarting the system.
See "Submitting an SR" in appendix A of this
manual.
690 CLAS0002 Message: Data dictionary error
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
after attempting to delete the NETIPC Socket
Registry module, NETCP discovered a CM Port
Dictionary entry named "SOCKREGISTRY" had not
been deleted (PARM = 32-bit port number of the
SOCKREG.NET.SYS process which failed to delete
the entry).
Action: This error in itself was not fatal, and
shutdown continued. However, the entry should
have been deleted, and now it will not be
possible to restart Transport without first
restarting the system. See "Submitting an SR"
in appendix A of this manual.
691 CLAS0002 Message: INTERNAL ERROR; No DEVS
Cause: While starting an X.25 network due to a
:NETCONTROL START command, or while updating it
due to a :NETCONTROL UPDATE command, NETCP found
that none of the X.25 address keys in the
Network Directory file matched any keys in the
NMCONFIG file's SVC or PVC configurations for
that X.25 network (PARM = 0).
Action: This error in itself was not fatal, and
startup continued. However, outbound
connections cannot be initiated using this X.25
network. Stop the network and use NMMGR to
ensure the address keys in the "Additional
Address" field of X.25 Network Directory entries
match "X.25 Address Key" fields in the
NETXPORT.NI.name.PROTOCOL.X25.SVCPATH (or
PVCPATH) screens of the NMCONFIG file. If this
does not solve the problem, see "Submitting an
SR" in appendix A of this manual.