HP 3000 Manuals HP 3000 Manuals
LAN Error Messages (contd)
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support
contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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.
--------------------------------------------------------------------------
176 MESSAGE Type 2 connection attempt failed.
CAUSE The remote system did not respond to a SABME
with a UA.
ACTION Check that the remote is activated, and make
sure the local and remote MAC addresses, and
SAPs are correctly configured.
--------------------------------------------------------------------------
177 MESSAGE Type 2 error during reset or disconnect.
CAUSE The remote system did not respond to a SABME or
DISC with a UA.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
178 MESSAGE Type 2 connection disconnected.
CAUSE The remote system transmitted a DISC, causing
the Type 2 connection to be dropped.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
179 MESSAGE Type 2 error during reset or disconnect.
CAUSE The remote system did not respond to a SABME or
DISC with a UA.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
180 MESSAGE Type 2 connection unexpectedly reset.
CAUSE A Type 2 protocol error occurred resulting in an
FRMR being transmitted or received.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
181 MESSAGE Type 2 connection unexpectedly reset.
CAUSE A Type 2 protocol error probably occurred,
resulting in a SABME being transmitted or
received.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
182 MESSAGE Type 2 connection unexpectedly reset.
CAUSE A Type 2 protocol error probably occurred
resulting in a SABME being transmitted or
received.
ACTION Disregard if the connection is working properly,
and no other errors occurred. If the connection
will not function or other errors have occurred,
write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
183 MESSAGE Type 2 Rendezvous ID invalid.
CAUSE A transport tried to established a connection on
a SAP which had not rendezvoused with the
driver.
ACTION Write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------
184 MESSAGE Type 2 connection already exists.
CAUSE Two transports are configured to use the same
MAC addresses and SAPs.
ACTION Correct the NMMGR configurations and restart the
driver.
--------------------------------------------------------------------------
185 MESSAGE Type 2 connection not available.
CAUSE The driver has reached the maximum number of
supported connections.
ACTION Shut down some connections to free up resources.
--------------------------------------------------------------------------
186 MESSAGE Type 2 Connection ID invalid.
CAUSE A transport tried to send a message to the
driver with an invalid connection identifier.
ACTION Write down the error information and contact
your Hewlett-Packard support contact.
--------------------------------------------------------------------------