HP 3000 Manuals HP 3000 Manuals
LAN Error Messages (contd)
237 MESSAGE Could not create driver buffer pool.
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
support contact.
--------------------------------------------------------------------------
238 MESSAGE Could not delete the driver 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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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.
--------------------------------------------------------------------------
2100 MESSAGE Token Ring adapter detected a network error on
LINKNAME
CAUSE The Token Ring adapter detected an error.
ACTION Write down the Cause Status and call your
Hewlett-Packard support contact.
--------------------------------------------------------------------------
2101 MESSAGE Token Ring adapter detected signal loss on
LINKNAME
CAUSE This station has detected a loss of signal on
the ring.
ACTION Verify that this station is properly attached to
the network. Check network components
(adapters, cables, MSAUs, etc.). Have your
network provider examine the network.
--------------------------------------------------------------------------
2102 MESSAGE Token Ring adapter detected a hard error on
LINKNAME
CAUSE A station has stopped receiving data and is
transmitting beacon frames.
ACTION If this error persists, check network components
(adapters, cables, MSAUs, etc.). Have your
network provider examine the network.
--------------------------------------------------------------------------
2103 MESSAGE Token Ring adapter detected a soft error on
LINKNAME
CAUSE This station has detected an error and notified
the Ring Error Monitor.
ACTION If this error persists, query your Ring Error
Monitor to determine the type of error. Check
network components (adapters, cables, MSAUs,
etc.). Have your network provider examine the
network.
--------------------------------------------------------------------------
2104 MESSAGE Token Ring adapter beaconing on LINKNAME
CAUSE This station has stopped receiving data.
ACTION If this error persists, then verify that all
stations are configured to the proper data rate.
Check network components (adapters, cables,
MSAUs, etc.). Have your network provider
examine the network.
--------------------------------------------------------------------------
2105 MESSAGE Token Ring adapter detected lobe cable fault on
LINKNAME
CAUSE An open or short circuit was detected in the
lobe cable.
ACTION Verify that this station is properly attached to
the network. Check network components
(adapters, cables, MSAUs, etc.). Have your
network provider examine the network.
--------------------------------------------------------------------------