HP 3000 Manuals HP 3000 Manuals
Control Process Logging Location Codes (contd.)
412 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP received an unrecognized message
on port subqueue 2 or 4, which are only designed
for asynchronous event messages (PARM = first 16
bits of message, which should give the message
type.) NETCP was expecting either a DCLDM event
message (type 340) or an SDI async event message
(type 390).
Action: This error in itself was not fatal, and
NETCP continued operating. However, some other
modules on the system may still be waiting for a
message exchange that mistakenly went to NETCP,
and this could cause problems in those other
modules. If disc logging was enabled, NETCP
logged the entire received message to the
current NM logfile, which may aid in diagnosis.
It may not have been a Transport message at all.
If necessary, see "Submitting an SR" in appendix
A of this manual.
413 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While collecting configuration data for
startup of an X25 network, NETCP successfully
obtained a buffer to hold the data, but later on
was unable to write data into that buffer (PARM
= 32-bit status returned by the call to
bmgr_write_buffer).
Action: Not all the configuration data was
collected, and startup of that network failed.
Check the configuration file using NMMGR, to see
that the amount of X25 configuration data seems
to be within limits. Also verify your system
has any and all software patches that may be
needed to use the amount of X25 configuration
data you are specifying. If the problem still
cannot be isolated, see "Submitting an SR" in
appendix A of this manual.
414 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP received an asynchronous DCLDM
event message, but the device number in the
message did not correspond to any known device
in NETCP's tables (PARM = 16-bit internal ldev
number from the message).
Action: This error in itself was not fatal, and
NETCP continued operating. Some kind of timing
condition may have occurred. Another
possibility is NETCP or a DCLDM may be confused.
If the problem occurs repeatedly, see
"Submitting an SR" in appendix A of this manual.
416 CLAS0002 Message: INTERNAL ERROR; Async request from
link
Cause: NETCP received an asynchronous SDI event
message, but the specific type of event was
something other than an exception event, the
only message type NETCP was expecting (PARM =
32-bit SDI status field from the message).
Action: This error in itself was not fatal, and
NETCP continued operating. However, some other
modules on the system may still be waiting for
the event message that mistakenly went to NETCP,
and this could cause problems in those other
modules. If disc logging was enabled, NETCP
logged the entire received message to the
current NM logfile, which may aid in diagnosis.
If necessary, see "Submitting an SR" in appendix
A of this manual.
417 CLAS0003 Message: Level 3 Up on DTC
Cause: NETCP received an SDI asynchronous event
message from X25 informing it that a level 3
connection has been established on a DTC for an
X25 link already started by the Transport (PARM
= 32-bit SDI status field from the message).
Action: None. This is an informational message
only. NETCP has connected the device, and
Transport will now begin using this link.
418 CLAS0003 Message: INTERNAL ERROR; Async request from
link
Cause: NETCP received an SDI asynchronous event
message informing it that an X25 device reported
an error (PARM = 32-bit SDI status field from
the message).
Action: NETCP will bring down the X25 device
and its driver, then start a 2-minute automatic
restart timer. If the problem occurs
repeatedly, stop the network or use the
:NETCONTROL DELLINK=linkname; NET=niname command
to remove the DTC link from Transport use.
Verify that the DTC LAN link on the host is
functioning correctly (via LANDAD) then verify
that the link on the DTC is functioning
correctly (via the Openview DTC Manager). Once
the errors are corrected, restart the network or
use a :NETCONTROL ADDLINK=linkname; NET=niname
command to allow the Transport to use the DTC
link again.
419 CLAS0002 Message: INTERNAL ERROR; Device open
Cause: While starting an 802.3 LAN device prior
to opening its driver, NETCP encountered an
error attempting to add multicast addresses to
the driver's KSO (PARM = 32-bit status returned
by the call to ieee_multicast_add).
Action: The LAN network did not start. Use the
LANDAD tool to verify the LAN hardware is
functioning correctly. If it looks good, there
may be a problem with the LAN driver software or
a bug in NETCP; see "Submitting an SR" in
appendix A of this manual.
420 CLAS0002 Message: INTERNAL ERROR; Device close
Cause: While stopping an 802.3 LAN device prior
to closing its driver, NETCP encountered an
error attempting to delete multicast addresses
it supposedly added previously to the driver's
KSO (PARM = 32-bit status returned by the call
to ieee_multicast_delete).
Action: This error in itself was not fatal, and
device shutdown continued. After shutdown, use
the LANDAD tool to verify the LAN hardware is
functioning correctly. If it looks good but the
problem persists, then see "Submitting an SR" in
appendix A of this manual.
423 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While stopping an X25 network, NETCP
encountered an error attempting to delete the
X25 Flow Control Manager (PARM = 32-bit status
returned by the call to netfc_kill). The Flow
Control Manager dynamically allocates the flow
control buffer pools for X25.
Action: This error in itself was not fatal, and
shutdown of the X25 NI continued. If the error
occurs every time, see "Submitting an SR" in
appendix A of this manual.
428 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP was about to send a level 3
restart message to the X25 protocol, but the
NETCP tables showed a restart had already been
sent (PARM = 0).
Action: No restart message was sent this time,
but this situation should not have occurred. If
it occurs repeatedly, see "Submitting an SR" in
appendix A of this manual.
429 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP was about to send a level 3 stop
message to the X25 protocol, but the NETCP
tables showed a restart had already been sent
(PARM = 0).
Action: No stop message was sent this time, but
this situation should not have occurred. If it
occurs repeatedly, see "Submitting an SR" in
appendix A of this manual.
431 CLAS0003 Message: Level 3 Down on DTC
Cause: NETCP received an SDI async event
message informing it that the X25 RLM was not
ready, meaning that levels 3 and 2 have gone
down on the DTC for an X25 link already started
by Transport (PARM = 32-bit SDI status field
from the message).
Action: None. This is an informative message
only. In many cases the DTC will recover on its
own. If this does not happen, use the DTC
Manager to find the reason why levels 2/3 are
not up. Once the problem is corrected on the
DTC, the host will be informed and will start
using the device.
500 CLAS0005 Message: LOGGING; Log
Cause: NETCP has received a message instructing
it to process one of the general :NETCONTROL
commands (PARM = hex 330). Examples of these
are START, ADDLINK, DELLINK, STOP, and UPDATE
commands: anything except for STATUS.
Action: None. This is an informative message
only.
501 CLAS0005 Message: LOGGING; Log
Cause: NETCP has received a message instructing
it to process a :NETCONTROL STATUS command (PARM
= hex 332).
Action: None. This is an informative message
only.
600 CLAS0002 Message: Bad status
Cause: When NETCP attempted to send a reply
message back to NETUI to complete a blocked
:NETCONTROL command, or send a reply back to
NMMON to complete initial creation of NETCP
after either a successful or an unsuccessful
startup, an error occurred on the send (PARM =
32-bit status returned by the call to send_msg).
Action: If user session which issued the
command exists, it will now be hung. Since it
also owns resources, it cannot be aborted, and a
system restart will be needed to recover.
However, depending on the command that hung,
most other network operations should continue to
work normally. If not, you may try restarting
the network. If the command that hangs
attempted to mix several :NETCONTROL operations
in the same command, try avoiding this, issuing
separate commands instead. If the separate
commands are in a batch job or a UDC, try adding
some :PAUSE commands between the network
commands. If the problem still persists, see
"Submitting an SR" in appendix A of this manual.
601 CLAS0002 Message: Bad status
Cause: While attempting to send a request
message to the PROBE module to cause it to send
a packet to a network, NETCP encountered an
error on the send (PARM = 32-bit status returned
by the call to send_msg).
Action: Other systems on the network may be
unaware that this node is up. This, in itself,
will not prohibit connections into or out from
this node. If the desired connectivity cannot
be achieved, restart the network. If the
problem persists, then see "Submitting an SR" in
appendix A of this manual.
602 CLAS0002 Message: Bad status
Cause: While attempting to send an X25 restart
request message to the X25 protocol module,
NETCP encountered an error on the send (PARM =
32-bit status returned by the call to send_msg).
Action: X25 did not receive the restart
request. This will cause the X25 network to
enter a bad state. Stop and restart that
network. If this problem continues, see
"Submitting an SR" in appendix A of this manual.
603 CLAS0002 Message: Bad status
Cause: On an SNA network NI, while attempting
to send a bind message to the L2RESOLVE module
of SNA, NETCP encountered an error on the send
(PARM = 32-bit status returned by the call to
send_msg).
Action: This will prevent SNA from establishing
any connections. Stop and restart the network.
If this problem continues, see "Submitting an
SR" in appendix A of this manual.
604 CLAS0002 Message: Bad status
Cause: On an SNA network NI, while attempting
to send a device disconnect message to the
L2RESOLVE module of SNA for a device which had
previously established a level 1 connection,
NETCP encountered an error on the send (PARM =
32-bit status returned by the call to send_msg).
Action: The device was not disconnected.
Restart the network. If this problem continues,
then see "Submitting an SR" in appendix A of
this manual.
605 CLAS0003 Message: BUFFER MANAGER; Buffer manager error
Cause: In the last phases of stopping the last
device on an NI that was being shut down, NETCP
encountered an error while trying to delete that
NI inbound buffer pool (PARM = 32-bit status
returned by the call to bmgr_delete_pool).
Action: This error was not fatal, and network
shutdown continued. However, the amount of
system memory used by the pool may be
inaccessible until the next system restart.
Probably some buffers for the pool were lost, or
are still outstanding in protocol modules which
had previously encountered errors. If the
problem occurs repeatedly, see "Submitting an
SR" in appendix A of this manual.
606 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: In the last phases of stopping the last
device on an NI that was being shut down, NETCP
found the NI inbound buffer pool ID in its
device table, but not in its read pool table
(PARM = 16-bit buffer size for the missing pool
ID; this number was used internally in the NS
Registry to name that pool).
Action: This error was not fatal, and network
shutdown continued. However, since pool ID's
should always appear in both tables, NETCP is
confused. Even if the pool ID in the device
table was valid, NECP could not be sure, so to
be safe the buffer pool was not deleted, and the
NS Registry may still contain that pool ID. The
amount of system memory used by this buffer pool
may be inaccessible until the next system
restart. If the problem occurs again, see
"Submitting an SR" in appendix A of this manual.
607 CLAS0002 Message: Bad status
Cause: While attempting to disable tracing on
one of the Transport modules, in response to a
system shutdown or a user's :NETCONTROL command,
NETCP encountered an error trying to send a
trace disable message to that module (PARM =
32-bit status returned by the call to send_msg).
Action: This error was not fatal, and network
operation continued. Though it is not possible
to tell from console logging which module was
affected, disc logging will show the entire
message, including the interface code of the
entity being sent to. After this error, NETCP
disabled the affected module's tracing at the
NMS subsystem level, closing the trace file.
While this may result in additional module
specific errors if the module tries writing more
trace data later on, at least the file will be
available for analysis. If this problem occurs
repeatedly, see "Submitting an SR" in appendix A
of this manual.
608 CLAS0002 Message: Bad status
Cause: While attempting to enable tracing on
one of the Transport modules, in response to a
user's :NETCONTROL command, NETCP encountered an
error trying to send a trace enable message to
that module (PARM = 32-bit status returned by
the call to send_msg).
Action: This error was not fatal, and network
operation continued. Even though a new trace
file was created, the module will not record any
trace data in it, and more errors may occur when
tracing is disabled later on. The specified
module may have failed or may not exist. When
convenient, try restarting the network. If the
problem still persists, see "Submitting an SR"
in appendix A of this manual.
609 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: While stopping Transport due to a system
shutdown or a :NETCONTROL STOP command, NETCP
was unable to delete a CM Port Dictionary entry
named "NMCONFIG", into in which it had
previously stored the name of the NMCONFIG file
(PARM = 16-bit result code returned by the call
to dict_delete). The entry was used as a way to
partially lock the file, so NMMGR could tell
Transport was up and running. The CM Port
Dictionary is an operating system lookup service
used by, but not part of, Transport.
Action: This error in itself was not fatal, and
shutdown continued. However, the entry should
have been there. If the same error occurs
again, see "Submitting an SR" in appendix A of
this manual.
610 CLAS0002 Message: Bad status
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 Timers module (PARM = 32-bit
status returned by the call to sk_ti_stop).
Action: This error in itself was not fatal, and
shutdown continued. However, it may not be
possible to restart Transport without first
restarting the system. See "Submitting an SR"
in appendix A of this manual.
611 CLAS0002 Message: INTERNAL ERROR; Module Deconfig Failed
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error when trying to stop
one of the general protocols (PARM = 32-bit
escape code returned by the call to the module
deconfigurator that failed). Always preceded by
another error from another entity (having a
different Entity number, such as 151-160),
indicating the cause of the original failure.
Action: This error in itself was not fatal, and
shutdown continued. However, some system
resources may be lost until the next system
restart. Inspect the previous error, and if
necessary see "Submitting an SR" in appendix A
of this manual.
612 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error trying to delete the
NS Registry (PARM = 32-bit status returned by
the call to reg_del_register).
Action: This error in itself was not fatal, and
shutdown continued. However, it may not be
possible to restart Transport without first
restarting the system. If necessary, see
"Submitting an SR" in appendix A of this manual.
613 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error trying to delete its
utility buffer pool (PARM = 32-bit status
returned by the call to bmgr_delete_pool).
Action: This error was not fatal, and network
shutdown continued. However, the amount of
system memory used by the pool may be
inaccessible until the next system restart.
Probably some buffers for the pool were lost, or
are still outstanding in modules which remain in
the background after NETCP terminates. If the
problem occurs repeatedly, see "Submitting an
SR" in appendix A of this manual.
614 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: While shutting down Transport due to a
system shutdown or a :NETCONTROL STOP command,
NETCP encountered an error trying to delete a CM
Port Dictionary entry named "NetCP", into which
it had stored its own port number, for use by
various CM transport modules such as PROBE (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.
Action: This error in itself was not fatal, and
shutdown continued. However, it may not be
possible to restart Transport without first
restarting the system, since if the Dictionary
entry does still exist, future :NETCONTROL
commands may either hang or cause a system
abort. See "Submitting an SR" in appendix A of
this manual.
615 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: During the later phases of initial NETCP
startup, NETCP encountered an error trying to
add its port ID into the NMMON port table, so
that NETCP would receive a shutdown message if
the system or NMMON were later shut down (PARM =
32-bit status returned by the call to
nnmonaddid).
Action: This error was not fatal, and network
startup continued. However, shutting down the
system will not stop Transport, so to avoid
ungraceful connection losses, you should attempt
a :NETCONTROL STOP command before attempting
your next system shutdown. If you wish, you can
try restarting the network. If the problem
still occurs, NMMON may not be running, though
that would more likely cause a NETCP hang. Run
NMMAINT and check for version mismatches on
subsystem 0. If there is no mismatch, try
restarting the system. If the problem still
occurs, see "Submitting an SR" in appendix A of
this manual.
616 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: During the later phases of initial NETCP
startup, NETCP encountered an error trying to
add its own port number into a CM Port
Dictionary entry named "NetCP", for use by
various CM transport modules such as PROBE (PARM
= 16-bit result code returned by the call to
dict_add). The CM Port Dictionary is an
operating system lookup service used by, but not
part of, Transport.
Action: This error was not fatal, and network
startup continued. However, additional
problems, including system aborts, may occur
because other modules of Transport will not be
able to find NETCP. Also, additional errors will
occur later when NETCP tries to delete the
Dictionary entry (see error 614). If another
instance of Transport was just shut down, it is
possible a collision occurred. Stop and restart
the network. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
617 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: During the early phases of initial NETCP
startup, after successfully opening the
configuration file, NETCP encountered an error
trying to add the name of the file into a CM
Port Dictionary entry named "NMCONFIG" (PARM =
16-bit result code returned by the call to
dict_add). The entry was used as a way to
partially lock the file, so NMMGR could tell
Transport was up and running. The CM Port
Dictionary is an operating system lookup service
used by, but not part of, Transport.
Action: This error was not fatal, and network
startup continued. However, additional errors
will occur later when NETCP tries to delete the
Dictionary entry (see error 609). In addition,
assumptions made by Transport and NMMGR about
the partial lock on the file will not be valid;
all NMMGR access to the NMCONFIG file during the
time this instance of Transport is up should be
avoided. Restart the network. If the problem
persists, see "Submitting an SR" in appendix A
of this manual.
618 CLAS0002 Message: INTERNAL ERROR; Data dictionary error
Cause: While starting the X25 protocol module
for an X25 network that was being started, NETCP
encountered an error trying to add a linkname it
created for one of the X25 devices, into a CM
Port Dictionary entry (PARM = 16-bit result code
returned by the call to dict_add). 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 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
"Submitting an SR" in appendix A of this manual.
619 CLAS0002 Message: INTERNAL ERROR; Device open
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 "Submitting
an SR" in appendix A of this manual.
620 CLAS0002 Message: Bad status
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 "Submitting an SR" in appendix A of this
manual.
621 CLAS0002 Message: Bad status
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 "Submitting an SR" in
appendix A of this manual.
622 CLAS0002 Message: Bad status
Cause: While attempting to send a DCN start
message to IPU in response to an X25 automatic
restart or a user's :NETCONTROL START or
:NETCONTROL ADDLINK command, NETCP encountered
an error on the send (PARM = 32-bit status
returned by the call to send_msg). A DCN start
message is required for a Directly Connected
Network such as X25.
Action: IPU did not receive the message, so it
does not know the network is started. As a
result, path resolution for the NI will fail.
Restart the network. If this problem continues,
see "Submitting an SR" in appendix A of this
manual.
623 CLAS0002 Message: Bad status
Cause: After completing construction of a
GATEWAY update buffer in response to startup or
shutdown of some network, NETCP encountered an
error trying to send a message referencing that
buffer to the IPU module of Transport (PARM =
32-bit status returned by the call to send_msg).
Action: IPU did not receive the message, so
path resolution information for the network will
not be up to date, and attempts to establish
connections with it may fail. Restart the
network. If this problem persists, see
"Submitting an SR" in appendix A of this manual.
624 CLAS0002 Message: Bad status
Cause: While attempting to send a device stop
message to the DIAL module because protocols on
an existing ROUTER network are being shut down,
NETCP encountered an error on the send (PARM =
32-bit status returned by the call to send_msg).
Action: The error in itself was not fatal, and
shutdown of this network probably continued,
ending with deletion of this instance of the
DIAL module. However, DIAL was not notified the
device has stopped, which may have caused more
errors if it happened to run again before it was
deleted. In addition, some versions of
Transport may hang if this problem occurs,
requiring a system restart to recover. On a non
critical terminal, attempt a :NETCONTROL STATUS
command; if results are reported, then try
restarting the network. If the network restarts
but the problem returns, see "Submitting an SR"
in appendix A of this manual.
625 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While deconfiguring an NI for a network
that was being shut down and which also had IP
Store and Forward enabled, after first deleting
that Store and Forward buffer pool ID from the
NS Registry, NETCP encountered an error trying
to delete the buffer pool itself (PARM = 32-bit
status returned by the call to
bmgr_delete_pool).
Action: This error was not fatal, and network
shutdown continued. However, the amount of
system memory used by the pool may be
inaccessible until the next system restart.
Probably some buffers for the pool were lost, or
are still outstanding in link drivers or in
Transport modules which had previously
encountered errors. If the problem occurs
repeatedly, see "Submitting an SR" in appendix A
of this manual.
626 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While deconfiguring an NI for a network
that was being shut down, after first deleting
the outbound buffer pool ID from the NS
Registry, NETCP encountered an error trying to
delete the buffer pool itself (PARM = 32-bit
status returned by the call to
bmgr_delete_pool).
Action: This error was not fatal, and network
shutdown continued. However, the amount of
system memory used by the pool may be
inaccessible until the next system restart.
Probably some buffers for the pool were lost, or
are still outstanding in link drivers or in
Transport modules which had previously
encountered errors. If the problem occurs
repeatedly, see "Submitting an SR" in appendix A
of this manual.