HP 3000 Manuals HP 3000 Manuals
Chapter 15 LAN, LAN/Console, Token Ring LAN Error Messages
Messages generated by the LAN, LAN/console, Token Ring LAN are the
following type:
Internal driver error in SYSLINK (LANWARN ###) or (LANERR ###)
where ### is an error number.
2 MESSAGE Bad LINK ID.
CAUSE An invalid LINK ID was passed to the link
driver's write initiator.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE An invalid LINK ID was specified in the
rendezvous request message.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
3 MESSAGE Bad OPEN ID.
CAUSE An invalid OPEN ID was specified in the
rendezvous request message.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
5 MESSAGE Unable to obtain a buffer manager buffer.
CAUSE The buffers are not freed.
ACTION Warmstart the system and correct the user
programs.
CAUSE Some other process has obtained buffers reserved
for the driver.
ACTION Write down the error information displayed on
the console, take a system dump, submit an SR,
and call your Hewlett-Packard representative.
6 MESSAGE Unable to obtain an I/O Services message frame.
CAUSE The driver could not obtain a message frame from
a user port for newly arrived LAN packet (or
from CAM's port, in the case of a CIO card) for
a new DMA request to the card.
ACTION Write down the error information displayed on
the console, take a system dump, submit an SR,
and call your Hewlett-Packard representative.
7 MESSAGE A call to IO_CONFIG_INT failed during driver
initialization.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
8 MESSAGE A call to IO_DECONFIG_INT failed during driver
shutdown.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
9 MESSAGE A call to IO_FLUSH_INT failed during power fail
recovery.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
10 MESSAGE Unable to obtain an I/O Services timer.
CAUSE A call to obtain a timer resource returned an
error. Too many timers may be in use.
ACTION If you suspect your system might be low on timer
resources because of heavy loading, try
restarting the link later. If repeated attempts
fail, try warmstarting your system. If the
problem persists, a system dump will be
required. Call your Hewlett-Packard
representative.
11 MESSAGE Unable to release an I/O Services timer.
CAUSE The driver tried to free a timer that was not
recognized by the system as valid. Memory data
corruption may have occurred.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
12 MESSAGE Unable to release an I/O Services message frame.
CAUSE A call to the system message freeing routine
returned an error. The port may belong to a
process that no longer exists or is not
operating with the required capabilities. Also,
the message frame may not have been recognized
by the system as a valid message frame.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
13 MESSAGE Unable to retrieve an I/O Services message
frame.
CAUSE A call to the system message retrieve routine
returned an error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
14 MESSAGE Unable to send I/O Services message frame to
another process.
CAUSE A call to a system message SEND routine returned
an error. The destination port may belong to a
process that no longer exists or is not
operating with required capabilities.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
16 MESSAGE LAN console is not supported.
CAUSE The console DM tries to bind with a driver as a
LAN Console DM.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
17 MESSAGE Unable to obtain a step data structure from
driver internal resources.
CAUSE All steps are in use and wait for DMA
completion. The driver may be low on steps
because of heavy LAN traffic.
ACTION Ignore this problem unless other problems are
occurring. If you are experiencing other
problems, write down the error information
displayed on the console and call your
Hewlett-Packard representative.
18 MESSAGE Unable to send I/O Services message frame to
another process.
CAUSE A call to a system message send routine returned
in error. The destination port may belong to a
process that no longer exists or is not
operating with required capabilities.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
19 MESSAGE NIO LAN/Console card reports internal fatal
hardware error.
CAUSE Indicates a problem caused by bad hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
20 MESSAGE Unable to release buffer manager buffer.
CAUSE The driver tried to free memory that the buffer
manager did not recognize as a valid buffer
because of a driver problem or memory data
corruption. Also, the driver may have tried to
free a buffer that is already freed.
ACTION System dump required. Call your Hewlett-Packard
representative.
32 MESSAGE Attempt to rendezvous with a link driver with
SAP or SAP+XSAP or Ethernet Type already being
used.
CAUSE The user is trying to rendezvous twice with a
link driver or two different users are using the
same SAP, SAP+XSAP or Ethernet Type.
ACTION Write down the error information displayed on
the console submit an SR and call your
Hewlett-Packard representative.
33 MESSAGE Attempt to separate from the driver failed.
CAUSE An attempt was made to separate from the driver
using console Link ID.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
34 MESSAGE Attempt to rendezvous with the driver or
separate from the driver when the Middle Plane
is in CLOSED state.
CAUSE The driver shuts itself down because of a fatal
hardware error or driver internal error and the
user tries to rendezvous with the driver or
separate from it.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
36 MESSAGE Bad Rendezvous ID.
CAUSE An attempt was made to use a bad rendezvous ID
in a process of separating from the driver or
changing its inbound buffer pool. This may be
caused by data corruption.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
37 MESSAGE Unable to rendezvous with the driver; the
rendezvous table is full.
CAUSE An attempt to rendezvous with the driver failed
due to running out of free entries in the
rendezvous table.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
38 MESSAGE Attempt to separate from the driver while not
having previously rendezvoused with it.
CAUSE An attempt is made to separate twice from the
link driver.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
39 MESSAGE Bad rendezvous info length.
CAUSE A bad length of rendezvous info was specified in
the rendezvous request.
ACTION Write down the error information displayed on
the console submit an SR and call your
Hewlett-Packard representative.
40 MESSAGE The Middle Plane is in wrong state.
CAUSE The Middle Plane state machine table is
corrupted.
ACTION Write down the error information displayed on
the console submit an SR, take a dump and call
your Hewlett-Packard representative.
41 MESSAGE Missing inbound pool in the rendezvous request
message.
CAUSE The rendezvous request message does not specify
inbound buffer pool.
ACTION Write down the error information displayed on
the console submit an SR, and call your
Hewlett-Packard representative.
42 MESSAGE Missing rendezvous info in the rendezvous
request message.
CAUSE The rendezvous request message does not have a
pointer to the rendezvous information buffer.
ACTION Write down the error information displayed on
the console submit an SR and call your
Hewlett-Packard representative.
48 MESSAGE Unsupported module type in IODC.
CAUSE The problem is caused by bad NIO LAN hardware,
the wrong path number, or the wrong type of
card.
ACTION Try these actions in this order:
1. Verify that the configured physical path
is correct by using NMMGR.
2. Verify that the card is a NIO LAN/console
card.
3. If you have tried both of the actions
above and are still experiencing
difficulties, your Hewlett-Packard
representative must run diagnostics on
the LAN/console card.
49 MESSAGE Unsupported software model in IODC.
CAUSE The problem is caused by bad NIO LAN hardware,
the wrong path number, or the wrong type of
card.
ACTION Try these actions in this order:
1. Verify that the configured physical path
is correct by using NMMGR.
2. Verify that the card is a NIO/LAN console
card.
3. If you have tried both of the actions
above and are still experiencing
difficulties, your Hewlett-Packard
representative must run diagnostics on
the LAN/console card.
50 MESSAGE The NIO LAN/console card did not return to a
ready state after a reset was issued.
CAUSE The problem is caused by bad NIO LAN/console
hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
52 MESSAGE The NIO LAN/console card register test failed
during LAN/console card initialization.
CAUSE The problem is caused by bad NIO LAN/console
hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
53 MESSAGE Unable to obtain IODC information from
IO_GET_MODULE_REC during initialization.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
55 MESSAGE An unknown interrupt type was received from
IO_Services.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
57 MESSAGE The NIO LAN/console card detects that bind
request for a given 802.2 SAP or 802.2 SAP +
XSAP or ETHERNET Type is already bound.
CAUSE The problem is caused by a link driver internal
problem.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
58 MESSAGE The NIO LAN/console card detects illegal bind
request.
CAUSE The problem is caused by a link driver internal
problem.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
59 MESSAGE The NIO LAN/console card detects a bad length of
the configuration data buffer.
CAUSE The problem is caused by data corruption in the
configuration quad.
ACTION Write down the error information displayed on
the console, submit an SR, take a dump and call
your Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
60 MESSAGE The NIO LAN/console card detects bad multicast
address in the configuration data.
CAUSE A bad multicast address was entered into the
Multicast Address Table.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
61 MESSAGE The NIO LAN/console card detects a bind request
to illegal register.
CAUSE The problem is caused by a link driver internal
error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
62 MESSAGE The NIO LAN/console card detects a bad Station
Address in CONFIG_SA.
CAUSE The problem is caused by configuring the wrong
Station Address in NMMGR.
ACTION Use NMMGR to verify that the configured Station
Address is correct.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
63 MESSAGE The NIO LAN/console card detects a bind request
to already bound register.
CAUSE The problem is caused by a link driver internal
error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
64 MESSAGE The NIO LAN/console card detects an unbind
request to an unbound register.
CAUSE The problem is caused by a link driver internal
error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
65 MESSAGE The NIO LAN/console card detects too many
multicast addresses in the configuration buffer.
CAUSE The problem is caused by a link driver internal
error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The problem is caused by a bad NIO LAN/console
backplane.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
66 MESSAGE The NIO LAN/console card reports that expected
CCMD_IN or CCMD_OUT was not found.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
67 MESSAGE The NIO LAN/console card reports that CCMD_OUT
was sent to an inbound only register set.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
68 MESSAGE The NIO LAN/console card reports that expected
CCMD_LINK was not found.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
69 MESSAGE The NIO LAN/console card reports that CCMD_IN
was sent to an outbound only register set.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
70 MESSAGE The NIO LAN/console card detects unknown CCMD.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
71 MESSAGE The NIO LAN/console card detects fatal backplane
error.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
72 MESSAGE The NIO LAN/console card detects fatal bus
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
73 MESSAGE The NIO LAN/console card detects fatal error,
dinmode.
CAUSE The problem is caused by bad NIO LAN/console
hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
74 MESSAGE The NIO LAN/console card detects parity error.
CAUSE The problem is caused by bad NIO LAN/console
hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
75 MESSAGE The NIO LAN/console card detects assertion of
the BUS_ERROR signal.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
76 MESSAGE The NIO LAN/console card detects a severe
hardware error.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
77 MESSAGE The NIO LAN/console card detects a severe
internal error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
78 MESSAGE The NIO LAN/console card detects a fatal error
in the bus protocol.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
79 MESSAGE The NIO LAN/console card reports that the
selftest failed.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the LAN/console card.
80 MESSAGE The NIO/LAN console card detected an internal
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
81 MESSAGE The NIO/LAN console card detected an internal
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
82 MESSAGE The NIO/LAN console card detected an internal
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
83 MESSAGE The BDMARS transferred less DMA data than the
host CCMD_IN or CCMD_OUT count requested.
CAUSE The NIO LAN/console card did not have enough
data bytes to completely fill the inbound
buffer. Or the NIO/LAN console card did not
accept all the data that the host tried to send;
for example, the number of bytes were bigger
than maximum LAN packet size.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
84 MESSAGE The BDMARS expected more DMA data to be
transferred than the host CCMD_IN or CCMD_OUT
count requested.
CAUSE The NIO LAN/console card was prepared to send
more data bytes to the host, but the host did
not provide enough buffers. Or the LAN/ console
card expected more data than the host provided.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
85 MESSAGE The NIO LAN/console card reported unknown
advisory error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
86 MESSAGE The NIO LAN/console card reported unknown apstat
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
87 MESSAGE The NIO LAN/console card reported unknown fatal
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
88 MESSAGE The NIO LAN/console card detects unknown CCMD.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
89 MESSAGE The NIO LAN/console card reports unknown hard
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
90 MESSAGE The NIO LAN/console card detects unknown I/O
command.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
91 MESSAGE The NIO LAN/console card reports unknown soft
error.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
112 MESSAGE The CIO bottom plane is unable to obtain buffer
manager buffer.
CAUSE Buffers have not been freed or some other
process has obtained buffers reserved for the
driver.
ACTION Warmstart the system and correct the user
programs. If you are still experiencing
problems, write down the error information
displayed on the console, take a system dump,
submit an SR, and call your Hewlett-Packard
representative.
114 MESSAGE The CIO bottom plane detects unknown reply
message from buffer manager.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
115 MESSAGE The bind request to CAM failed.
CAUSE The driver is already bound to CAM.
ACTION Write down the error information displayed on
the console, take a system dump, submit an SR,
and call your Hewlett-Packard representative.
CAUSE The value of CIO_META_TAG was not specified in
the bind request message.
ACTION Write down the error information displayed on
the console, take a system dump, submit an SR,
and call your Hewlett-Packard representative.
CAUSE The hardware address in the bind request was
invalid.
ACTION Write down the error information displayed on
the console, take a system dump, submit an SR,
and call your Hewlett-Packard representative.
116 MESSAGE The CIO LAN card selftest failed.
CAUSE The problem is caused by bad CIO LAN hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
117 MESSAGE The CIO LAN card detects a fatal backplane
error.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
118 MESSAGE The Identity Request to the CIO LAN card failed.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
119 MESSAGE The CIO LAN card reports an invalid hardware ID.
CAUSE The problem is caused by bad CIO LAN hardware,
the wrong path number, or the wrong type of
card.
ACTION Try these actions in this order:
1. Verify that the configured physical path
is correct by using NMMGR.
2. Verify that the card is a NIO/LAN console
card.
3. If you have verified that the physical
path and card type are correct and are
still experiencing problems, your
Hewlett-Packard representative must run
diagnostics on the LAN/console card.
120 MESSAGE The Status Request to the CIO LAN card failed.
CAUSE Unknown. Need more information.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
122 MESSAGE The CIO LAN card can not sense MAU heartbeat.
CAUSE The MAU is disconnected or bad.
ACTION Check your cables and if this error still
appears, your Hewlett-Packard representative
must run diagnostics on the CIO LAN card.
123 MESSAGE The unbind request to the CAM failed.
CAUSE The driver is not bound to the CAM.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
CAUSE The driver still has outstanding requests to the
CAM.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
125 MESSAGE The driver detects unknown option in the 802.2
control field of a test or xid packet.
CAUSE The problem is caused by a bad packet.
ACTION If this error appears repeatedly, write down the
error information displayed on the console and
call your Hewlett-Packard representative.
128 MESSAGE The CIO LAN configuration request failed.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
129 MESSAGE The CIO LAN statistics request failed.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR and call your
Hewlett-Packard representative.
130 MESSAGE The CIO LAN reset statistics request failed.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
131 MESSAGE The CIO LAN card reports Dead-or-Dying ARQ
status.
CAUSE The problem is caused by bad CIO LAN card
hardware.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
132 MESSAGE The CIO LAN card reports Protocol Error ARQ.
CAUSE Violation of the CIO LAN card backplane
protocol.
ACTION Your Hewlett-Packard representative must run
diagnostics on the CIO LAN card.
133 MESSAGE The CIO bottom plane received invalid request at
a given state.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
135 MESSAGE The CIO LAN card hard reset request failed.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
144 MESSAGE Dump request received when driver is dumping.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
145 MESSAGE Message received in invalid state.
CAUSE The link driver received an unexpected message.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
146 MESSAGE Driver detected unsupported command in received
SDI or WAN control message.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
147 MESSAGE Unknown driver problem.
CAUSE The driver detected an error, but did not say
what type of error was found.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
148 MESSAGE Unknown dump manager port number.
CAUSE The driver detects unrecoverable error and tries
to dump its PDA and the NIO LAN/console card but
the dump module is missing.
ACTION Run NMMAINT to verify that the dump module is
present.
149 MESSAGE Unable to obtain an I/O Services timer for a
dump process.
CAUSE A call to obtain a timer resource returned an
error. Too many timers may be in use.
ACTION If you suspect your system might be low on timer
resources be cause of heavy loading, try
restarting the link later. If repeated attempts
fail, try warmstarting your system. If the
problem persists, a system dump will be
required. Call your Hewlett-Packard
representative.
150 MESSAGE Unable to send dump request message to dump
manager.
CAUSE A call to a system message SEND routine returned
in error. The dump manager port is not
operating with required capabilities.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
151 MESSAGE Unexpected timer event message.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
152 MESSAGE Unimplemented message received.
CAUSE The message descriptor is not known to the
driver.
ACTION Call your Hewlett-Packard representative and
explain what you are trying to do.
160 MESSAGE Nil configuration pointer.
CAUSE A user passed a nil configuration pointer to the
driver.
ACTION Call your Hewlett-Packard representative and
explain what you are trying to do.
161 MESSAGE Trace manager overrun.
CAUSE The driver is generating trace entries faster
than the trace manager can process them. This
causes some trace entries to be lost.
ACTION This is only a warning and is indicative of a
very busy system. If not debugging a problem,
then tracing should be turned off. This will
improve system performance in general. If a
problem is being looked at, use partial tracing
whenever possible (when full data frames are not
needed) to ensure that no trace data is lost.
224 MESSAGE Could not read the link name from the LSS link
table.
CAUSE The link table does not exist.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
225 MESSAGE Could not add the link name to the LSS link
table.
CAUSE The link table does not exist.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
226 MESSAGE Could not delete the link name from the LSS link
table.
CAUSE The link name specified the LAN_KILL_MODULE call
is not in the LSS link table.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
227 MESSAGE Could not read multicast addresses table.
CAUSE The multicast addresses table does not exist.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
228 MESSAGE Could not open NMCONFIG.PUB.SYS file.
CAUSE The configuration file NMCONFIG.PUB.SYS was
purged or renamed or the NMCONFIG.PUB.SYS
configuration file may be opened with exclusive
access.
ACTION Type a LISTF NMCONFIG.PUB.SYS to determine if
the file has been opened with exclusive access.
If it has, wait for the program or process that
has this file opened exclusively to close it.
If the configuration file is missing, restore
the file from a backup tape and restart the link
again.
CAUSE The configuration file NMCONFIG.PUB.SYS may be
opened with exclusive access.
ACTION Wait for the program or process that has this
file opened exclusively to close it.
229 MESSAGE Link data not found in NMCONFIG.PUB.SYS.
CAUSE The link data is not found in the configuration
file NMCONFIG.PUB.SYS.
ACTION Use NMMGR to create the link data for the link
you are trying to start. Try to start the link
again.
230 MESSAGE The link data record is incorrect for this
driver.
CAUSE The link data record is corrupted in the
configuration file NMCONFIG.PUB.SYS.
ACTION Restore the file from a backup tape and restart
the link again.
CAUSE The configuration file NMCONFIG.PUB.SYS was not
converted to a version supported by the driver.
ACTION Run NMMGRVER on the configuration file
NMCONFIG.PUB.SYS.
233 MESSAGE A call to IO_GET_MGR_ENTRY failed during driver
configuration.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
234 MESSAGE A call to IO_CONFIG failed during driver
configuration.
CAUSE Wrong physical path is configured for the
installed LAN card.
ACTION Use NMMGR to correct the Physical Path for the
link.
CAUSE The card for the configured path is bad.
ACTION To determine whether the LAN card is good your
Hewlett-Packard representative must run
diagnostics on the LAN card.
235 MESSAGE A call to IO_UNCONFIG failed during driver
deconfiguration.
CAUSE Wrong physical path was specified in IO_UNCONFIG
call due to configuration data corruption in the
driver PDA.
ACTION Write down the error information displayed on
the console, submit an SR, take a system dump,
and call your Hewlett-Packard representative.
236 MESSAGE The LAN card is used by another link.
CAUSE The card was configured by another link.
ACTION Use NMMGR to correct the Physical Path for this
link or change the link name to point to a
different LAN card.
237 MESSAGE Could not create inbound buffer pool for the CIO
LAN card.
CAUSE The buffer manager cannot allocate a new logical
buffer pool entry or cannot allocate virtual
memory for the buffers.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
238 MESSAGE Could not delete the CIO LAN card inbound buffer
pool.
CAUSE Wrong pool ID was specified in the call to
delete inbound buffer pool due to configuration
data corruption in the driver's PDA.
ACTION Write down the error information displayed on
the console submit an SR, take a system dump,
and call your Hewlett-Packard representative.
239 MESSAGE Could not open trace file.
CAUSE The indicated trace file might be opened with
exclusive access.
ACTION Wait for the program or process that has the
trace file opened exclusively to close it.
240 MESSAGE Could not stop trace.
CAUSE Tracing might have been turned off with
LINKCONTROL TRACEOFF command, but the link
software information indicates that it was on.
ACTION Ignore this problem unless you are experiencing
other problems. If you are experiencing other
problems, write down the error information
displayed on the console and call your
Hewlett-Packard representative.
241 MESSAGE Could not start trace.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
242 MESSAGE Could not get Write Initiator label.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
243 MESSAGE Could not release Write Initiator label.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
244 MESSAGE Could not open NMLGxxxx.PUB.SYS file.
CAUSE The indicated log file may be opened with
exclusive access.
ACTION Wait for the program or process that has the log
file opened exclusively to close it.
CAUSE The driver subsystem is not configured in
logging configuration.
ACTION Use NMMGR to check logging configuration for
subsystem 25 or write down the error information
displayed on the console and call your
Hewlett-Packard representative.
245 MESSAGE Could not close the NMLGxxxx.PUB.SYS file.
CAUSE Invalid LOG ID due to configuration data
corruption in the driver's PDA.
ACTION Write down the error information displayed on
the console, submit an SR, take a system dump
and call your Hewlett-Packard representative.
246 MESSAGE Could not freeze the configuration record in
memory.
CAUSE Memory shortage problems are occurring.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
247 MESSAGE Could not unfreeze the configuration record in
memory.
CAUSE Memory problems are occurring.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
248 MESSAGE Could not send config request message.
CAUSE An internal system ports problem has occurred.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
249 MESSAGE Could not receive config reply message.
CAUSE An internal system ports problem has occurred.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
250 MESSAGE Timeout waiting for the config reply message.
CAUSE The link software or the card could not be
configured.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
251 MESSAGE Driver's PDA is corrupted.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console, submit an SR, take a dump and call
your Hewlett-Packard representative.
252 MESSAGE Configuration of the dump manager failed.
CAUSE Unknown. Need more information.
ACTION Write down the error information displayed on
the console and call your Hewlett-Packard
representative.
253 MESSAGE The link type is not LAN.
CAUSE The link name type in NMCONFIG.PUB.SYS is not
set to LAN.
ACTION Use NMMGR to correct the link name type.
254 MESSAGE The link driver failed to start.
CAUSE Incorrect physical path was specified in the
NMCONFIG file.
ACTION Correct the physical path in the NMCONFIG file
using NMMGR.