HP 3000 Manuals HP 3000 Manuals
LAN Error Messages (contd.)
187 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
188 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
189-197 MESSAGE Type 2 non-fatal software error.
CAUSE A non-fatal Type 2 driver software error
occurred.
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.
--------------------------------------------------------------------------
198 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
199 MESSAGE Type 2 non-fatal software error.
CAUSE A non-fatal Type 2 driver software error
occurred.
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.
--------------------------------------------------------------------------
200 MESSAGE Unable to send I/O Services message frame
LINKNAME
CAUSE A call to a system message send routine returned
in error.
ACTION Write down the error information displayed on
the console, submit an SR and call your
Hewlett-Packard support contact.
--------------------------------------------------------------------------
201 MESSAGE Unable to obtain a buffer manager buffer
LINKNAME
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 support contact.
--------------------------------------------------------------------------
202 MESSAGE Unable to obtain a system timer LINKNAME
CAUSE A call to obtain a timer resource returned an
error.
ACTION Take a system dump and call your Hewlett-Packard
support contact.
--------------------------------------------------------------------------
203 MESSAGE Unable to release a system timer LINKNAME
CAUSE The driver tried to free a timer that was not
recognized by the system as a valid timer.
ACTION Take a system dump and call your Hewlett-Packard
support contact.
--------------------------------------------------------------------------
204-206 MESSAGE Type 2 non-fatal software error.
CAUSE A non-fatal Type 2 driver software error
occurred.
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.
--------------------------------------------------------------------------
207 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
208 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
209-210 MESSAGE Type 2 non-fatal software error.
CAUSE A non-fatal Type 2 driver software error
occurred.
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.
--------------------------------------------------------------------------
211 MESSAGE Type 2 non-fatal protocol error.
CAUSE An unexpected packet format was 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.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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
support contact.
--------------------------------------------------------------------------
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 support contact.
--------------------------------------------------------------------------
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.
--------------------------------------------------------------------------