HP 3000 Manuals HP 3000 Manuals
Control Process Logging Location Codes
Control Process logging location codes are generated by the NETCP process
of Network Transport. For each of the logging explanations, any or all
of the following may be present:
PARM = Meaning of the parameter logged.
PORT = Transport port number of the Control Process.
NI = Network Interface Type against which the event was logged:
FDDI = Fiber Distributed Data Interface LAN.
GATEHALF = Gateway Half network over LAPB.
LAN = IEEE 802.3 or Ethernet LAN.
LOOP = Loopback network.
ROUTER = Point to Point network over DCLDM and LAPB.
SNA = NS over SNA/iX network (obsolete).
TOKEN = Token Ring LAN.
X.25 = Host-based or PC-based X.25 network.
Link = Link Type against which the event was logged:
DCLDM = Data Communications Logical Device Manager for LAPB.
DTC = Distributed Terminal Controller configured for X.25.
LAN = IEEE 802.3 or Ethernet LAN link.
LAPB = PSI (Programmable Serial Interface) link.
NS/SNA = NS over a specific SNA/iX LU (obsolete).
TOKEN = Token Ring LAN link.
FDDI = Fiber Distributed Data Interface LAN link.
X.25 = X.25 over a DTC link.
10 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While initially starting NETCP, or while
starting NI specific protocols on a LAN,
GATEHALF, or ROUTER network, NETCP could not get
node name information from the NODENAME path in
the NMCONFIG file (PARM = 32-bit status returned
by the call to nmconfgetdata).
Action: One or more network protocols were not
completely started. Stop the network and use
NMMGR to make sure a nodename is configured and
the NMCONFIG file is validated. If the file
looks good, try restarting the network. If the
problem persists, see "Submitting an SR" in
appendix A of this manual.
19 CLAS0002 Message: INTERNAL ERROR; Out of resources
Cause: While building the IP alias list, NETCP
discovered there are too many network NI's
configured in the NMCONFIG file (PARM = maximum
networks allowed).
Action: Check the configuration file, and if it
is not the problem see "Submitting an SR" in
appendix A of this manual.
20 CLAS0002 Message: INTERNAL ERROR; Bad/unknown port
message
Cause: NETCP received an unexpected message
that was not a reply, while waiting for a reply
message having a specific function code
(PARM.(0:16) = function code and PARM.(16:16) =
interface code of received message).
Action: It is not possible to tell from NETCP
logging what message it was expecting, however
if disc logging was enabled, the entire received
message was logged, which may aid debugging.
The flow of normal NETCP operations has been
interrupted, and a transport hang may be
imminent, especially if new :NETCONTROL commands
are issued. It may be necessary to restart the
system to clear this problem. See "Submitting
an SR" in appendix A of this manual.
21 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While initially starting NETCP, or while
starting NI specific protocols on a LAN,
GATEHALF, or ROUTER network, NETCP's attempt to
get a buffer for a nodal path report failed
(PARM = 32-bit status returned by the call to
bmgr_get_buffer).
Action: One or more network protocols were not
completely started. Stop transport and retry
the operation. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
22 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While initially starting NETCP, or while
starting NI specific protocols on a LAN,
GATEHALF, or ROUTER network, NETCP could not get
path report information from the
NETXPORT.GLOBAL.REPORT path in the NMCONFIG file
(PARM = 32-bit status returned by the call to
nmconfgetdata).
Action: One or more network protocols were not
completely started. Stop the network and use
NMMGR to check the NMCONFIG file and validate
it. If the file looks good, try restarting
transport. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
25 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While initially starting up, NETCP's
attempt to get the global information record
from the NETXPORT.GLOBAL path in the NMCONFIG
file failed (PARM = 32-bit status returned by
the call to nmconfgetdata).
Action: Transport did not start. Verify the
configuration file exists, and if this is not
the problem, see "Submitting an SR" in appendix
A of this manual.
27 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: An attempt to create NETCP's frozen
utility buffer pool failed during initial
startup (PARM = 32-bit status returned by the
call to bmgr_create_pool).
Action: Transport did not start. 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
"Submitting an SR" in appendix A of this manual.
29 CLAS0002 Message: IRRECOVERABLE ERROR; Bad CONFIG file
version
Cause 1: If PARM=0, during initial startup
NETCP discovered the version number in the
NMCONFIG file was not in the range expected by
Transport.
Action 1: Transport did not start. Run program
NMMGRVER to convert the configuration file to
the current version, then restart the network.
Cause 2: If PARM is nonzero, during initial
startup NETCP could not read the global
information record from the NETXPORT.GLOBAL path
in the NMCONFIG file (PARM = 32-bit status
returned by the call to nmconfgetdata).
Action 2: Transport did not start. Use NMMGR
to validate the NMCONFIG file, then retry the
operation again. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
30 CLAS0002 Message: PACKET DISCARD; Path resolve failure
Cause: During initial NETCP startup, an attempt
to initialize the Node/Address Path cache by
calling path_cache_init failed (PARM = maximum
cached node names).
Action: Transport did not start. It is not
possible to tell from NETCP logging what the
result code from path_cache_init was, but PATHS
may have logged additional errors. See
"Submitting an SR" in appendix A of this manual.
33 CLAS0002 Message: INTERNAL ERROR; Async request from
link
Cause: NETCP received an asynchronous event
message containing a negative error status, from
the DCLDM controlling one of the LAPB links on
the network (PARM = 32-bit status field from the
message).
Action: NETCP stopped the device associated
with the link, also stopping any attached
protocols and driver. Run the PSIDAD diagnostic
on the appropriate PSI card. If the PSI looks
good, it may be possible to restart the device
using :NETCONTROL ADDLINK=linkname; NET=niname.
If the problem persists, see "Submitting an SR"
in appendix A of this manual.
40 CLAS0002 Message: INTERNAL ERROR; A reads
Cause: While NETCP was rendezvousing a
particular protocol to a driver, an attempt to
connect a LAPB device failed for some reason
other than a close already being in progress
(PARM = 32-bit status returned by the call to
xp_connect_the_driver).
Action: Check the appropriate PSI card and its
cabling. If it looks good, another possibility
is that the DCLDM or LAPB driver are hung; see
"Submitting an SR" in appendix A of this manual.
42 CLAS0002 Message: INTERNAL ERROR; Device open
Cause: An attempt to physically start a device
failed with a nonzero status meaning an
unexpected error or warning occurred (PARM =
32-bit status returned by the call to
nslopenlink). Physical startup includes all
creation and startup of a link driver and its
dependent modules, selftest, startup,
downloading and configuration of link hardware,
plus optional creation of a DCLDM, so any error
along the way will be detected here by NETCP.
Action: Stop Transport and enable all available
logging for the link subsystem corresponding to
the NI type of the network reporting the error,
then restart Transport and reproduce the
problem, monitoring logged data for any
problems. If this does not reveal the cause,
link tracing can be used on the affected link to
collect even more data.
Check that the physical path specified in the
NMCONFIG file is correct for all link devices on
the network being started, and that a card is
installed in the slot for that path. You can
stop the system then use IOMAP to verify
physical path numbers.
For links other than X25, probably the link
driver failed to obtain a resource, the link
hardware was already in use by an IBM
communications subsystem such as NRJE, the link
hardware failed selftest or its firmware version
is not supported by the driver, the download
file was inaccessible, corrupt or has the wrong
version, or executing the download caused the
link hardware to hang and resulted in a driver
or module configurator timeout or other problem.
Use NMMGR to check the link configuration in
NMCONFIG and use SYSDIAG to check the link
hardware.
For X.25 links (and/or hardwired terminals), if
a DTC link is in use the DTC and network links
may have same physical path specified in NMMGR;
try specifying separate physical LAN cards.
Make sure the DTC configuration was validated
with NMMGR. Another common cause with X25
networks is that the NMCONFIG file may have
specified a DTC address or card which is
inoperative or does not exist, resulting in one
or more timeouts, some of which may have been
accidentally sent to NETCP. Using NMMGR, compare
the specified DTC configuration with the actual
DTC hardware, and delete any DTC cards that are
not physically present. Any DTC changes made,
or re-validation of the DTC configuration, may
require a system restart to take effect.
If the problem persists after investigating all
these causes, see "Submitting an SR" in appendix
A of this manual.
45 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While NETCP was starting a specific
network NI, an attempt to create a frozen
outbound buffer pool for that NI failed (PARM =
32-bit status returned by the call to
bmgr_create_pool).
Action: The NI did not start. Using NMMGR,
check the configured packet size for the
affected link. In particular, look for a packet
size of 8224, which may indicate the NMCONFIG
file has been corrupted, probably by an
incompatible version of NMMGR. If the packet
size is configured correctly, then 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.
50 CLAS0004 Message: Transport start
Cause: As one of the first things it does
during initial startup, NETCP logs that a new
instance of Transport is starting (PIN=0, and
PARM = PIN number of the NETCP system process).
Action: None. This is an informative message
only. It does not imply successful startup,
only that a startup is beginning. When starting
Transport after a previous instance of it has
just been stopped, it is possible for this
message to appear before the other instance's
Transport stop message appears.
51 CLAS0004 Message: Transport stop
Cause: As one of the last things NETCP does
during shutdown, it logs that that instance of
Transport has stopped. After this, NETCP will
close logging access, disconnect from NMMON,
release its message port, then terminate (PARM =
0).
Action: None. This is an informative message
only. It is only logged after all outstanding
replies have been received from the general
protocols. This message does not imply that
Transport is completely down, nor does it imply
successful shutdown, only that there is very
little cleanup left to do. It is possible that
another instance of Transport can be
successfully started before this message
appears.
54 CLAS0002 Message: INTERNAL ERROR; Device close
Cause: An attempt to physically stop a device
failed with a negative nonzero status meaning an
unexpected error (not a warning) occurred (PARM
= 32-bit status returned by the call to
nslcloselink). Physical stop includes all
shutdown and deletion of a link driver and its
dependent modules and any connections to the NMS
subsystem or the operating system, reset of link
hardware, plus optional deletion of a DCLDM, so
any error along the way will be detected here by
NETCP.
Action: This problem in itself was not fatal,
and link shutdown continued. However, there may
be a problem with the link driver software or
hardware.
Most shutdown problems are warnings, not errors
(see error 283). Usually the link driver failed
to release a resource, possibly due to a
previous error, or the link hardware failed to
stop in an orderly manner resulting in a driver
or module configurator timeout or other problem,
or an attempt to close logging resulted in a
warning which was incorrectly reported as an
error. If the link hardware is suspect, use
SYSDIAG to check it. For X25 networks, verify
the X25 switch has not failed.
If you wish to pursue the cause further, stop
Transport and enable all available logging for
the link subsystem corresponding to the NI type
of the network reporting the error, then restart
and stop the same network again to reproduce the
problem, monitoring logged data for any
problems. If this does not reveal the cause,
link tracing may be attempted on the affected
link to collect even more data, though because
the device is shutting down, keep in mind the
system may automatically stop the tracing before
the point at which the problem is detected.
If the problem persists after investigating all
these causes, see "Submitting an SR" in appendix
A of this manual.
58 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: At the beginning of NETCP shutdown due
to a system shutdown, a :NETCONTROL STOP
command, or an error during initial startup,
NETCP encountered an error trying to close the
NMCONFIG file it had previously opened (PARM =
32-bit status returned by the call to
nmconfclose).
Action: This error in itself was not fatal, and
shutdown continued. However, the NMCONFIG file
may be inaccessible. If the problem occurs
repeatedly, see "Submitting an SR" in appendix A
of this manual.
84 CLAS0002 Message: INTERNAL ERROR; Bad/unknown port
message
Cause: A message with an unrecognized function
code was received on the NETCP port while NETCP
was idle and waiting for new commands (PARM =
the 16-bit unknown message function code).
Action: The message was ignored and NETCP went
back to waiting for the next new command.
However, some other modules on the system are
still waiting for the 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.
101 CLAS0003 Message: INTERNAL ERROR; Write aborted by link
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that, in
addition to some other error, one or more queued
outbound write operations were aborted by the
LAPB PSI driver (PARM = 16-bit internal ldev
number of device whose writes were aborted).
This error is always preceded by another
asynchronous link error (for example, errors 257
and 259) indicating the original cause of the
failure that resulted in the aborts.
Action: None; this is an informative message
only, and only serves to indicate that queued
outbound data was not sent when the error
occurred. Additional information may be gained
by enabling logging classes 10 and 12 for link
subsystem 28 (LAPB) and class 0 for subsystem 4
(DCLDM), then reproducing the problem. If this
does not reveal the cause, see "Submitting an
SR" in appendix A of this manual.
106 CLAS0002 Message: INTERNAL ERROR; Trace
Cause: After successfully disabling tracing for
an entity at the Transport level, NETCP
encountered an error trying to stop it at the
NMS subsystem level (PARM = 32-bit status
returned by the call to nmclosetrace).
Action: This error was not fatal, and NETCP
continued running. However, the trace file may
not have been closed, and thus would not be
available for access until after the next system
restart. If the problem occurs every time, see
"Submitting an SR" in appendix A of this manual.
118 CLAS0002 Message: INTERNAL ERROR; Trace
Cause: While attempting to enable tracing for
an entity, NETCP encountered an error attempting
to get a trace ID from the NMS subsystem (PARM =
32-bit status returned by the call to
nmgettraceid).
Action: No message to enable tracing was sent
to the desired entity. Check that sufficient
discspace is available on the system, and that
trace filename specified in the link screen of
the NMCONFIG file, or in the :NETCONTROL TRACEON
command is legal and does not violate file
system security rules. If this does not reveal
the cause, see "Submitting an SR" in appendix A
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 "Submitting an SR" in appendix
A 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 "Submitting an SR"
in appendix A of this manual.
163 CLAS0005 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; see
below).
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 Verifys or any other requests
while awaiting previous replies, they are queued
for later execution if they are unique. If a
new Path Verify is a duplicate of one already
queued, the new one is counted and then
discarded. Later, after all replies arrive or a
timeout occurs, the oldest queued Path Verify is
executed (PARM = number of duplicates of this
Path Verify received and discarded while
awaiting replies; nonzero indicates a storm is
occurring, and larger numbers mean more severe
storms). This continues until no Path Verifys
arrive while awaiting replies. Other NETCP
requests such as :NETCONTROL STATUS, can then be
processed. If a new Path Verify arrives after
that point, even if it duplicates one already
processed it is treated as new and unique.
Action: None. This is an informative message
only.
167 CLAS0005 Message: STATIC UPDATE: Update
Cause: NETCP is about to send a GATEWAY update
message to IPU for a specific IP address,
because a network is starting (PARM = 32-bit IP
address being updated).
Action: None. This is an informative message
only. IPU will use information in the message
to update its tables.
168 CLAS0003 Message: Device restarting
Cause: NETCP is restarted a device either
because DIAL failed to make a connection (for
instance due to a bad security string), or
because idle device timeouts were enabled in the
configuration and a timeout occurred (PARM =
16-bit NETCP device index of affected device).
Action: If you suspect a security problem, you
may wish to address that issue. Otherwise, no
action is required; this is an informative error
message only. NETCP disconnected the device,
then cleaned up for the next device startup.
169 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While attempting to build GATEWAY update
information for IPU because a network was
starting, NETCP was unable to obtain a buffer
from its own pool to hold the information for a
specific NI (PARM = 32-bit status returned by
the call to bmgr_get_buffer).
Action: NETCP attempted to continue with the
next NI, possibly resulting in additional
errors. Probably all the NETCP buffers have
somehow been used up, though it should have
allowed for enough to support starting any
supported network configuration. Stop Transport
and use NMMGR to validate the NMCONFIG file and
check for obvious file corruption, then restart
the network. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
170 CLAS0005 Message: STATIC UPDATE: Update
Cause: NETCP is about to send a GATEWAY update
message to IPU for a specific IP address,
because a network is stopping (PARM = 32-bit IP
address being updated).
Action: None. This is an informative message
only. IPU will use information in the message
to update its tables.
171 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While attempting to collect current
address configuration data from NMCONFIG because
an X25 network was either starting or being
updated, NETCP was unable to obtain a logical
buffer from its own pool to hold all the X25
information (PARM = 32-bit status returned by
the call to bmgr_get_buffer).
Action: 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,
especially if you configuration contains more
than 1024 X.25 paths. If the problem still
cannot be isolated, the NMCONFIG file may be
corrupt, or there may be a bug in NETCP or the
NMS subsystem; see "Submitting an SR" in
appendix A of this manual.
222 CLAS0002 Message: PACKET DISCARD; Allowable max exceeded
Cause: While configuring a GATEHALF or a ROUTER
network mapping entry, NETCP was unable to find
free space in a global array to hold another new
phone number (PARM = maximum phone numbers per
system, in hex).
Action: Even after attempting to eliminate
duplicate phone numbers, no free cells were
available for an additional number; all entries
appear to be in use. If phone numbers have been
changed via :NETCONTROL UPDATE, stop and restart
the network, stop any started ROUTER or GATEHALF
networks that are not needed, or decrease the
number of unique phone numbers configured in the
NETXPORT.NI.niname.MAPPING.entryname paths of
your NMCONFIG file. Depending on the version of
Transport you are running, the maximum number of
unique phone numbers is either 1024 or 4096 for
the whole system, and the per-NI limit is either
256 or 1024 respectively.
232 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While attempting to build a DCN start
message for IPU because of a network start, a
:NETCONTROL ADDLINK command, or an X25 auto
restart, NETCP was unable to obtain a buffer
from its own pool to hold alias list information
(PARM = 32-bit status returned by the call to
bmgr_get_buffer).
Action: Though no DCN message was sent, network
startup probably continued to completion, but
connections over the affected network may not
work. Probably all the NETCP buffers have
somehow been used up, though it should have
allowed for enough to support starting any
supported network configuration. Stop Transport
and use NMMGR to validate the NMCONFIG file and
check for obvious file corruption, then restart
the network. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
238 CLAS0002 Message: INTERNAL ERROR: Configuration file
error
Cause: During NETCP processing of a network
start or update command, after an earlier
successful validation of the NMCONFIG file a
later validation of the file failed (PARM =
16-bit result code returned by the call to
validatenetxport).
Action: The specified network was not started.
Possibly the NMCONFIG file was being modified
while networks were running, and the changes
made were incomplete or incorrect. Stop
Transport and use NMMGR to open and validate the
NMCONFIG configuration file and find any errors.
Correct the errors and validate again. Then
restart the network.
241 CLAS0002 Message: INTERNAL ERROR; Port
Cause: During later phases of its initial
startup, NETCP was unable to create a process
port for itself (PARM = 32-bit status returned
by the call to create_port).
Action: The transport was not started. There
is a problem with the operating system or a bug
in NETCP; see "Submitting an SR" in appendix A
of this manual.
242 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: During later phases of its initial
startup, after NETCP was finished using the
NMCONFIG file, it encountered an error while
trying to close the file (PARM = 32-bit status
returned by the call to nmconfclose).
Action: This error in itself was not fatal, and
startup continued. However, the NMCONFIG file
may be inaccessible, and to be safe NETCP
assumed it still has the file open. If
Transport is later stopped, NETCP will again try
to close the file. Possibly an earlier run of
NMMGR left the file in a bad state. If the
problem occurs repeatedly, see "Submitting an
SR" in appendix A of this manual.
251 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While creating and initializing a
specific network NI because a :NETCONTROL START
command was issued, the NI module configurator
reported an error when trying to create the NI
port data area or port, or when sending an
initialization message to the new NI (PARM =
32-bit escape code returned by the call to
ni_module_config). Always preceded by another
error from the module configurator (having a
different Entity number, such as 151-160),
logging the reason for the original failure.
Action: Record the previous error and this
error. See "Submitting an SR" in appendix A of
this manual.
254 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: NETCP tried to search the NMCONFIG file
to determine if an NI having a specific name was
configured or not, but was unable to open the
file (PARM = 32-bit status returned by the call
to nmconfopen).
Action: Check that the NMCONFIG file exists and
is not already opened by some other user, such
as a STORE process or someone running NMMGR. If
this is not the problem, there may be a bug in
the NMS subsystem or in NETCP; see "Submitting
an SR" in appendix A of this manual.