HP 3000 Manuals HP 3000 Manuals
Control Process Logging Location Codes (contd)
256 CLAS0002 Message: INBOUND; Device disconnected
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link was disconnected (PARM = 32-bit NETCP
device state bitmask for the device). NETCP
will not attempt to reconnect the device because
it appears neither level 1 nor level 2
connections were established when this event
occurred. May be followed by informative error
101 if outbound data was queued when the error
occurred.
Action: This error may follow a previous
asynchronous link error, which may indicate an
earlier problem. Additional information may be
gained by enabling logging classes 3 for
Transport subsystem 3, 10 and 12 for link
subsystem 28 (LAPB) and class 0 for subsystem 4
(DCLDM), then reproducing the problem. It may
be possible to manually restart the device using
a :NETCONTROL ADDLINK=linkname; NET=niname
command. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
257 CLAS0003 Message: INBOUND; Device disconnected
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link was closed (PARM = 16-bit internal ldev
number of the device). NETCP will attempt to
reconnect the device because it appears either
level 1 or level 2 connections, or both, were
established when the event occurred. May be
followed by informative error 101 if outbound
data was queued when the error occurred.
Action: None. This is an informative error
message only. The link will reconnect
automatically unless error 256 appears. This
event may follow a previous asynchronous link
error, which may indicate an earlier problem.
If the situation continues, there may be a
problem with the phone system; additional
information may be gained by enabling logging
classes 10 and 12 for link subsystem 28 (LAPB)
and class 0 for subsystem 4 (DCLDM).
258 CLAS0003 Message: INBOUND; Device connected
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link has established a level 2 connection
(PARM = 16-bit internal ldev number of the
device).
Action: None. This is an informative message
only. The LAPB link is now successfully engaged
in protocol handshaking, and will stay up unless
an error, disconnect, or idle timeout occurs, or
the network is stopped.
259 CLAS0003 Message: INBOUND; Device disconnected
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link was disconnected by its remote side
(PARM = 0). May be followed by informative
error 101 if outbound data was queued when the
error occurred.
Action: None. This is an informative error
message only. NETCP will now tell the driver on
the local side to disconnect, so informative
error 257 should follow.
260 CLAS0002 Message: PACKET DISCARD; Illegal phone number
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
driver had some problem handling a phone number
change request (PARM = 32-bit NETCP device state
bitmask for the device).
Action: This error may be related to the syntax
or length of the phone number, but could also be
caused by some internal problem. Use NMMGR to
check the syntax of the telephone number in the
NMCONFIG file for the affected link. Then
attempt a :NETCONTROL ADDLINK=linkname;
NET=niname command. If the error persists, see
"Submitting an SR" in appendix A of this manual.
261 CLAS0002 Message: INBOUND; Device disconnected
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that closing
its LAPB PSI link failed (PARM = 16-bit internal
ldev number of the device). NETCP will attempt
to bring down the device and its driver. May be
followed by informative error 101 if outbound
data was queued when the error occurred.
Action: See "Submitting an SR" in appendix A of
this manual.
262 CLAS0005 Message: INTERNAL ERROR; Async request from
link
Cause: NETCP received an asynchronous event
message from the DCLDM indicating its LAPB PSI
link reported some sort of miscellaneous warning
(PARM = 16-bit internal ldev number of the
device).
Action: None. This is an informative message
only.
265 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While creating an NI because a specific
network was starting, NETCP encountered an error
trying to create a message pool for the new NI
port (PARM = 32-bit status returned by the call
to create_pool).
Action: The network was not started. See
"Submitting an SR" in appendix A of this manual.
266 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 after successfully
opening the file it was unable to close it (PARM
= 32-bit status returned by the call to
nmconfclose).
Action: This error in itself was not fatal, and
NETCP continued. However, the NMCONFIG file may
be inaccessible. Check that the NMCONFIG file
exists and is not already opened by some other
user, such as someone running NMMGR. If this is
not the problem and the message persists, see
"Submitting an SR" in appendix A of this manual.
267 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While creating an NI because a network
was starting, NETCP encountered an error trying
to create a new mapping table for the NI (PARM =
32-bit status returned by the call to
map_create_table).
Action: The network was not started. 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.
268 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: While creating an NI because a network
was starting, NETCP successfully created a new
mapping table for the NI, but then encountered
an error trying to add the NETCP entity into the
table (PARM = 32-bit status returned by the call
to map_add_entity).
Action: The network was not started. See
"Submitting an SR" in appendix A of this manual.
278 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While processing a :NETCONTROL command
to start or update a network or add a link,
NETCP successfully opened the NMCONFIG file, but
was unable to lock it (PARM = 32-bit status
returned by the call to nmconflockfile).
Action: The command did not execute, and NETCP
closed the open file. Check that the NMCONFIG
file exists and is not already opened by some
other user, such as someone running NMMGR. If
this is not the problem and the message
persists, see "Submitting an SR" in appendix A
of this manual.
280 CLAS0002 Message: INTERNAL ERROR; Configuration file
error
Cause: While processing a :NETCONTROL command
to start or update a network or add a link,
NETCP was unable to open the NMCONFIG file (PARM
= 32-bit status returned by the call to
nmconfopen).
Action: The command did not execute. Check
that the NMCONFIG file exists and is not already
opened by some other user, such as someone
running NMMGR. If this is not the problem and
the message persists, see "Submitting an SR" in
appendix A of this manual.
281 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: NETCP received a dial request message
but the entity whose reply port was in the
message was not one of the network specific
protocols known to NETCP for this NI (PARM = 0).
Action: Some entity other than DIAL may be
attempting dial requests. See "Submitting an
SR" in appendix A of this manual.
282 CLAS0003 Message: Device Startup Warning
Cause: An attempt to physically start a device
was successful, but returned a positive status
meaning some sort of unexpected warning occurred
(PARM = 32-bit status returned by the call to
nslopenlink).
Action: None. This is an informative error
message, and exists for pre-5.0 systems only.
If you want more information, try enabling
additional logging for the link subsystem
corresponding to the type of NI for the network
reporting the warning, then reproduce the
message. If this still does not reveal the
cause, see "Submitting an SR" in appendix A of
this manual.
283 CLAS0003 Message: Device Shutdown Warning
Cause: An attempt to physically stop a device
failed with a positive nonzero status meaning an
unexpected warning (not an error) 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 54). 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.
284 CLAS0003 Message: Device restarting
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link received a second SABM frame after a
connection was already established, meaning the
link has connected again (PARM = 0).
Action: None. This is an informative error
message only, of interest to operators who wish
to know when new connections occur. Handling a
second SABM is a normal part of the LAPB
protocol.
285 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: During NETCP's early initial startup,
immediately after attempting to create the NS
Registry, NETCP was unable to add Transport's
subsystem number to it (PARM = 32-bit status
returned by the call to reg_add_subsys).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed, in which case all
subsequent calls to it will also result in
errors being logged. If this message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
286 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: Near the end of NETCP's early initial
startup, it was unable to put its port number
into a new entity named "NetCP" in the NS
Registry (PARM = 32-bit status returned by the
call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
289 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: While creating a network NI for which IP
Store and Forward was enabled, NETCP was unable
to put the new Store and Forward buffer pool ID
into a new entity, having the same name as the
NI, in the NS Registry (PARM = 32-bit status
returned by the call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
290 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: During NETCP's early initial startup, it
was unable to put the NETCP utility buffer pool
ID into a new entity named "CP POOL" in the NS
Registry (PARM = 32-bit status returned by the
call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
291 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: While creating an NI because a network
was being started, NETCP was unable to put that
NI outbound buffer pool ID into a new entity,
having the same name as the NI, in the NS
Registry (PARM = 32-bit status returned by the
call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
292 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: While building a buffer containing all
X25 configuration data for a network, NETCP
successfully obtained a buffer of the supposedly
correct size, but later encountered an error
attempting to write a block of Network Directory
address information to the buffer (PARM = 32-bit
status returned by the call to
bmgr_write_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. If
the problem still cannot be isolated, see
"Submitting an SR" in appendix A of this manual.
293 CLAS0002 Message: INTERNAL ERROR; Auto dial failure
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI's autodial operation failed due to an
internal autodialer problem (PARM = 16-bit
internal ldev number of the device).
Action: Check the autodialer cabling and
strapping or configuration, and diagnose the
autodialer hardware. Then retry the operation.
294 CLAS0003 Message: PACKET DISCARD; Illegal phone number
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI card was passed a bad autodial telephone
number (PARM = 16-bit internal ldev number of
the device).
Action: Use NMMGR to check the syntax of the
telephone number in the NMCONFIG file for the
affected link. Then retry the dialing
operation. If the problem persists, see
"Submitting an SR" in appendix A of this manual.
295 CLAS0003 Message: PACKET DISCARD; Auto dial not
completed
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that a LAPB
PSI's autodial operation was not completed,
possibly because the site being dialed is either
busy or not picking up (PARM = 16-bit internal
ldev number of the device).
Action: Attempt to dial out again at a later
time, or reconfigure the remote site and the
local NMCONFIG mappings to provide additional
phone connections into that site.
296 CLAS0003 Message: INTERNAL ERROR; No auto dialer power
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI autodial operation was attempted while the
autodialer hardware was not powered up (PARM =
16-bit internal ldev number of the device).
Action: Turn on the autodial unit and check for
power and correct cabling. Then attempt to dial
out again.
303 CLAS0003 Message: OUTBOUND; Data line occupied
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI autodial failed because the line was busy or
a phone line was not available (PARM = 16-bit
internal ldev number of the device). (Some
pre-5.0 versions of Transport also incorrectly
reported wrong autodialer cables under this
location; now see error 674).
Action: Attempt to dial out again later when a
phone line is free.
304 CLAS0003 Message: Device restarting
Cause: NETCP received an asynchronous event
message from the DCLDM indicating that its LAPB
PSI link experienced a power failure, resulting
in a disconnect of the phone line (PARM = 16-bit
internal ldev number of the device). May be
followed by informative error 101 if outbound
data was queued when the error occurred.
Action: None. This is an informative error
message only. NETCP will now automatically
attempt to bring the device driver down and then
back up.
305 CLAS0002 Message: INTERNAL ERROR; Internal resource
error
Cause: During later stages of NETCP's initial
startup, NETCP was unable to create a message
pool for its own process port (PARM = 32-bit
status returned by the call to create_pool).
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.
306 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: During later stages of NETCP's initial
startup, NETCP was unable to add its own port
message pool ID to the NS Registry (PARM =
32-bit status returned by the call to
reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
311 CLAS0003 Message: INTERNAL ERROR; Dial
Cause: While restarting a link requiring
autodial, because an unexpected error occurred
while connected (see error 257), NETCP
instructed the local side to establish a level 2
connection. This failed because NETCP received
an asynchronous DCLDM event message indicating
its LAPB PSI link reported that the remote side
was establishing or had already established a
connection (PARM = 16-bit connect event code
from LAPB).
Action: None. This is an informative error
message only. The connection was successfully
established, but through the initiative of the
remote side, not the local. NETCP then
disconnected the device at the local side.
312 CLAS0003 Message: INTERNAL ERROR; Dial
Cause: While restarting a link requiring
autodial, because an unexpected error occurred
while connected (see error 257), NETCP
instructed the local side to establish a level 2
connection. A connection was established, but
then failed because NETCP received an
asynchronous DCLDM event message indicating its
LAPB PSI link reported another failure (PARM =
upper 16 bits of status from the call to
xp_connect_the_driver: usually the connect
event code from LAPB).
Action: NETCP disconnected the device and
notified protocols that the link went down.
This is most likely a link level problem.
Consult the link diagnostics and check the
modems. Confirm that the link connection is
working for the affected link. If the link is
connection is working, then see "Submitting an
SR" in appendix A of this manual.
313 CLAS0003 Message: INTERNAL ERROR; Dial
Cause: While restarting a LAPB PSI link because
an unexpected error occurred while connected
(see error 257), NETCP encountered an error when
it instructed the local side to reestablish a
level 1 connection so that a level 2 connection
can be established later (PARM = 32-bit status
returned by the call to xp_connect_the_driver).
Action: NETCP brought the device and its driver
down, and notified protocols that the link went
down. This is most likely a link level problem.
Another possibility is that the DCLDM or LAPB
driver are hung. Consult the link diagnostics
and check the modems. Confirm that the link
connection is working for the affected link. If
the link is connection is working, then see
"Submitting an SR" in appendix A of this manual.
315 CLAS0003 Message: INTERNAL ERROR; Dial
Cause: While processing a legal dial request
message, NETCP found that the link appeared to
already be connected, so dialing was not
possible (PARM = adjusted LAPB status).
Action: None. This is an informative error
message only. Another class-3 logging message
may have preceded this, indicating that the link
just connected.
316 CLAS0003 Message: INTERNAL ERROR; Dial
Cause 1: NETCP received a legal dial request
message but encountered an error while
downloading the phone number to the link (PARM =
32-bit status returned by the call to
xp_driver_config_dial).
Action 1: This event may follow a previous
asynchronous link error, which may indicate the
original problem. Another possibility is that
the DCLDM or LAPB driver are hung. Also check
the validity of the phone number in the
configuration. If the situation continues,
additional information may be gained by enabling
logging classes 10 and 12 for link subsystem 28
(LAPB), and class 0 for subsystem 4 (DCLDM). If
this still does not reveal the problem, see
"Submitting an SR" in appendix A of this manual.
Cause 2: NETCP received a legal dial request
message but encountered an error while trying to
establish a level 2 connection at the LAPB
driver, through the DCLDM (PARM = 32-bit
adjusted status returned by the call to
xp_connect_the_driver: add decimal 256 to get
the actual status).
Action 2: Perform the same actions as above.
322 CLAS0003 Message: INTERNAL ERROR; Dial
Cause: While processing a legal dial request
message, NETCP found that the link was already
closed, due to system timing conditions (PARM =
adjusted LAPB status).
Action: This is an informative error message
only. Attempt to dial out again if necessary.
401 CLAS0003 Message: 2 IP adr for 1 adr key
Cause: While collecting configuration data for
startup of an X25 network, NETCP found two IP
addresses mapping to the same X25 address key
(PARM = 0).
Action: This error in itself was not fatal, and
collection of the X25 data continued. The
logging does not tell which address was
involved. You may wish to run NMMGR and inspect
the X25 configuration data for mistakes.
404 CLAS0002 Message: BUFFER MANAGER; Buffer manager error
Cause: An attempt to create a frozen inbound
buffer pool for a particular NI device failed
(PARM = 32-bit status returned by the call to
bmgr_create_pool). Always followed by another
error indicating whether LAPB (see error 407) or
non-LAPB (see error 619) pool creation was being
attempted.
Action: The NI did not start. Check the packet
size configured in the NMCONFIG file. For LAPB
links, pool creation parameters are obtained
from this file, but other link types have a more
complex process for determining packet size.
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.
406 CLAS0003 Message: INTERNAL ERROR; NM Entry
Cause: While creating a frozen inbound buffer
pool for a particular NI device because its
network was being started, NETCP was unable to
put that pool ID into a new entity, having a
name that is the Ascii version of the decimal
buffer size, in the NS Registry (PARM = 32-bit
status returned by the call to reg_add_entity).
Action: This error was not fatal, and startup
continued; use of the Registry here is not
critical. However, creation of the NS Registry
by NETCP may have failed (see error 285), or the
Registry may be full. If the message occurs
every time, see "Submitting an SR" in appendix A
of this manual.
407 CLAS0002 Message: INTERNAL ERROR; Device open
Cause: While attempting to start a LAPB PSI
device on an existing NI, NETCP was unable 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
LAPB links, pool creation parameters are
obtained from 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.
410 CLAS0002 Message: INTERNAL ERROR; Device close
Cause: While shutting down a specific protocol
on a network, NETCP encountered an error
attempting to unbind that protocol from a device
driver (PARM = 32-bit status returned by the
call to ns_separate_from_driver). NETCP did not
expect any error since it supposedly bound that
protocol to the driver during network startup.
(Some pre-5.0 versions of Transport also
reported unbind errors for shutdown of specific
devices under this location; now see error 673).
Action: This error in itself was not failed,
and protocol shutdown continued. If this error
occurs every time, see "Submitting an SR" in
appendix A of this manual.
411 CLAS0003 Message: Overwrote X25 Addr/DDN
Cause: While collecting configuration data for
startup of an X25 network, NETCP found that a
user had specified an X25 address for a remote
node was on a DDN Network, but had also supplied
the actual address. Instead, the X25 address
should be derived from the IP address by the
Transport code (PARM = 0).
Action: Verify that the network interface
started is actually for a DDN Network. If the
network is DDN, no action is required, since all
configured X25 addresses will be ignored. If
not, reconfigure the DTC (using the DTC
manager), then stop and restart the network NI
on the host. This error message is only printed
once per startup, even if multiple X25 addresses
have this problem.