HP 3000 Manuals HP 3000 Manuals
LAP-B Link Driver Error Messages
This section describes error messages generated by the LAP-B Link Driver.
They are displayed on the HP 3000 Series 900 operator's console in the
following format:
LAPB (linkname) Message text
LAPB (linkname) Error ErrorNum, Status = Status, Path: PhysPath
1000 MESSAGE The download file is too small.
CAUSE Possible causes for this problem are as follows:
1. The download file is corrupt.
2. There is an incorrect version of the
download file.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Check the version of the download file
with NMMAINT and call your
Hewlett-Packard representative if
incorrect.
1001 MESSAGE The download file is too large.
CAUSE Possible causes for this problem are as follows:
1. The download file is too large.
2. There is an incorrect version of the
download file.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Check the version of the download file
with NMMAINT and call your
Hewlett-Packard representative if
incorrect.
1002 MESSAGE No STEPs data structures are available.
CAUSE A catastrophic internal resource error was
detected.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1003 MESSAGE An unknown interrupt type was received from
IO_Services.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1004 MESSAGE PSI fatal error, dinmode.
CAUSE Possible causes for this problem are as follows:
1. The download file is corrupt.
2. Bad PSI hardware.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Run the Sherlock diagnostics on the PSI
and call your Hewlett-Packard
representative if a failure is detected.
1005 MESSAGE PSI fatal bus error.
CAUSE Either the download file is corrupt, or the PSI
hardware has failed.
ACTION Replace the download file from your latest
system update tape, and run the Sherlock
diagnostics on the PSI. Call your
Hewlett-Packard representative if a failure is
detected.
1006 MESSAGE PSI fatal internal error.
CAUSE Either the download file is corrupt, or the PSI
hardware has failed.
ACTION Replace the download file from your latest
system update tape and run the Sherlock
diagnostics on the PSI and call your
Hewlett-Packard representative if a failure is
detected.
1007 MESSAGE Unknown PSI fatal error.
CAUSE Either the download file is corrupt, or the PSI
hardware has failed.
ACTION Replace the download file from your latest
system update tape and run the Sherlock
diagnostics on the PSI and call your
Hewlett-Packard representative if a failure is
detected.
1008 MESSAGE The PSI received less data from your
Hewlett-Packard system than it expected.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1009 MESSAGE The PSI received more data from your
Hewlett-Packard system than its internal buffers
could handle.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1010 MESSAGE The PSI Received a bad command from the driver.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1011 MESSAGE PSI received a bad DMA command from the driver.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1012 MESSAGE Unknown PSI module dependent hard error
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1013 MESSAGE The PSI detected a bad length count during
download.
CAUSE Either the download file is corrupt, or there is
an incorrect version of the download file.
ACTION Replace the download file from your latest
system update tape. You should also check the
version of the download file with NMMAINT and
call your Hewlett-Packard representative if
incorrect.
1014 MESSAGE PSI detected a bad checksum during download.
CAUSE Possible causes for this problem are as follows:
1. The download file is corrupt.
2. There is an incorrect version of the
download file.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Check the version of the download file
with NMMAINT and call your
Hewlett-Packard representative if
incorrect.
1015 MESSAGE PSI received download blocks out of sequence.
CAUSE Possible causes for this problem are as follows:
1. The download file is corrupt.
2. There is an incorrect version of the
download file.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Check the version of the download file
with NMMAINT and call your
Hewlett-Packard representative if
incorrect.
1016 MESSAGE Attempt to download to a bad card address.
CAUSE Possible causes for this problem are as follows:
1. The download file is corrupt.
2. There is an incorrect version of the
download file.
ACTION Possible actions for this problem are as
follows:
1. Replace the download file from your
latest system update tape.
2. Check the version of the download file
with NMMAINT and call your
Hewlett-Packard representative if
incorrect.
1017 MESSAGE PSI reported an undefined error during download.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1018 MESSAGE PSI detected a severe internal error.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1019 MESSAGE PSI detected a severe error on the backplane.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1020 MESSAGE PSI reported an unknown severe error type.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1023 MESSAGE Unable to obtain IODC information from
IO_GET_MODULE_REC during initialization.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1024 MESSAGE Unsupported module type in IODC.
CAUSE Possible causes for this problem are as follows:
1. Bad PSI hardware.
2. Wrong path name is NMMGR.
3. Wrong card type.
ACTION Possible actions for this problem are as
follows:
1. Run the Sherlock diagnostics on the PSI
and call your Hewlett-Packard
representative if there is an error.
2. Verify the configured path name is
correct in NMMGR.
3. Verify that the target card is a PSI
card.
1025 MESSAGE Unsupported software model in IODC.
CAUSE Possible causes for this problem are as follows:
1. Bad PSI hardware.
2. Wrong path name in NMMGR.
3. Wrong card type.
ACTION Possible actions for this problem are as
follows:
1. Run the Sherlock diagnostics on the PSI
and call your Hewlett-Packard
representative if there is an error.
2. Verify the configured path name is
correct in NMMGR.
3. Verify that the target card is a PSI
card.
1026 MESSAGE Incompatible software version in IODC.
CAUSE The version of the PSI is not compatible with
this driver.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1027 MESSAGE PSI did not return to a ready state after a
reset was issued.
CAUSE Bad PSI hardware.
ACTION Run the Sherlock diagnostics on the PSI hardware
and call your Hewlett-Packard representative if
an error is detected.
1028 MESSAGE A call to IO_CONFIG_INT failed during driver
initialization.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1029 MESSAGE A call to IO_INIT_PFHANDLER failed during driver
initialization.
CAUSE Internal error.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1030 MESSAGE PSI register test failed during PSI
initialization.
CAUSE Bad PSI hardware.
ACTION Run the Sherlock diagnostics on the PSI and call
your Hewlett-Packard representative if a failure
is detected.
1032 MESSAGE User invoked dump caused the driver to fail.
CAUSE A user manually instructed the driver to dump
via diagnostic utilities when the driver had not
encountered previous errors.
ACTION If the dump was taken as a snapshot of a
problem, call your Hewlett-Packard
representative, and save the raw dump file to
show to the HP person.
1033 MESSAGE Dump-sequence failure.
CAUSE Possible causes for this problem are as follows:
1. The dump module is missing.
2. The driver encountered an error while
attempting to produce a dump. The driver
has unlocked itself and reported to upper
levels the error which originally caused
the dump attempt; these levels will now
destroy the driver. Any dump file
produced is probably incomplete.
ACTION Possible actions for this problem are as
follows:
1. Run NMMAINT.PUB.SYS to verify the dump
module is present.
2. Write down the error information
displayed on the console, submit an SR,
and call your Hewlett-Packard
representative.
1034 MESSAGE An input message is being ignored.
CAUSE A message received by the driver was not
recognized or processing of it could not begin.
It is also possible the source port is not
operating with the required capabilities. The
message was logged and dropped.
ACTION The diagnostic system logfile should contain a
partial image of the ignored message. Write
down the information from this logfile as well
as the error information displayed on the
console, submit an SR, and call your
Hewlett-Packard representative.
1035 MESSAGE No TAB data structures available.
CAUSE TAB data structures are used whenever the driver
attempts to start new hardware activity. There
is a limited number of these data structures
available. Unexpected use of incorrect port and
subqueues may have created excessive pending
hardware activity. This problem may also be
reported if a buffer-manager buffer could not be
obtained.
ACTION Unsupported programs should not contact the
driver through incorrect subqueues. This
problem should produce a dump; keep the raw dump
file along with the error information displayed
on the console, call your Hewlett-Packard
representative, and submit an SR.
1036 MESSAGE Download file is incorrect for this driver.
CAUSE Hardware was successfully downloaded, but the
downloaded code turned out to be for a different
driver. Someone may have incorrectly renamed a
download file to have the name of the file
expected by the driver, or your download file or
installed driver may be extremely old and not
matched.
ACTION Run NMMAINT.PUB.SYS to verify the version of the
download file and driver. If the file is
incorrect, attempt to restore a copy from a
system backup tape. If this does not solve the
problem, you may need to update your system and
download file; call your Hewlett-Packard
representative.
1037 MESSAGE Download file is too old for this driver.
CAUSE Hardware was successfully downloaded but the
revision of the download file cannot be used
with the version of the corresponding installed
driver because their interfaces are
incompatible.
ACTION Check to see if operators forgot to restore the
latest download file during a recent system
update. If not, try restoring the file from a
system backup tape. If this does not solve the
problem, you may need to update your system and
download file; call your Hewlett-Packard
representative.
1038 MESSAGE Unable to obtain a buffer manager buffer.
CAUSE Possible causes for this problem are as follows:
1. Terminating user programs have not freed
buffers and/or buffer pools they were
using.
2. Some other process had obtained buffers
reserved for use by the driver while the
driver was trying to initialize itself.
ACTION Possible actions for this problem are as
follows:
1. Warmstart the system and correct the user
programs.
2. Try restarting the driver. If repeated
link-restarts fail, a system dump will be
required; call your Hewlett-Packard
representative.
1039 MESSAGE Unable to release a buffer manager buffer.
CAUSE The driver attempted to free memory which the
buffer manager did not recognize as a valid
buffer, due to a driver problem or memory data
corruption. Also, a problem somewhere may have
caused the driver to attempt to free a buffer
which was not in use.
ACTION A system dump will probably be required; call
your Hewlett-Packard representative.
1040 MESSAGE Unable to obtain an I/O Services timer.
CAUSE A call to obtain a timer resource returned in
error. Too many timers may be in use.
ACTION If you suspect your system may be low on timer
resources due to heavy loading, try restarting
the link later. If repeated attempts fail,
warmstart your system. If the problem persists,
a system dump will be required; call your
Hewlett-Packard representative.
1041 MESSAGE Unable to reset an I/O Services timer.
CAUSE The system rejected an attempt by the driver to
reset a timer supposedly owned by the driver.
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.
1042 MESSAGE Unable to release an I/O Services timer.
CAUSE The driver tried to free a timer which was not
recognized by the system as a valid timer.
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.
1043 MESSAGE Unable to obtain an I/O Services message frame.
CAUSE The driver could not obtain a reply-message
frame from the source port of a newly arrived
request message, or from a transport port in the
case of a driver-detected asynchronous event.
If the system is otherwise operating well,
modules attempting to communicate with the
driver may not be operating with the required
capabilities.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1044 MESSAGE Unable to send an I/O Services message to
another process.
CAUSE A call to the system message-send routine
returned in error. The destination port may
belong to a process which no longer exists or is
not operating with the required capabilities.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1045 MESSAGE Unable to release an I/O Services message frame.
CAUSE A call to the system message-freeing routine
returned in error. The port may belong to a
process which no longer exists or is not
operating with the required capabilities, or the
message frame was not 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.
1046 MESSAGE Attempting to find I/O Services message on port
failed.
CAUSE The system rejected an attempt by the driver to
locate message frames on its own port. 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.
1047 MESSAGE Attempted impossible state after a request or
completion.
CAUSE The driver attempted to enter a state which it
should never be able to get into, and ceased
operations instead. Memory data corruption, a
driver bug, or a problem with the execution
priorities of the driver and/or its hardware may
exist.
ACTION This problem should produce a dump. Keep the
raw dump along with the error information
displayed on the console, call your
Hewlett-Packard representative, and submit an
SR.
1048 MESSAGE Driver notified of powerfail by system.
CAUSE The driver was notified that power returned
after a power failure of any duration.
ACTION The driver is not capable of recovering from
power failures, and modem connections were
probably lost. Restart the link.
1049 MESSAGE Request received when driver broken.
CAUSE The driver had to reject a request message
because it had previously become broken for
another reason. The rejected request could not
be processed while the driver was broken.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1050 MESSAGE Request received when driver dead.
CAUSE The driver received a request message during a
short time interval after shutdown completed,
but before the driver's port had been destroyed
by the system. The driver should not be
receiving new requests after shutdown, and it
cannot successfully complete them.
ACTION If this problem occurs repeatedly, call your
Hewlett-Packard representative.
1051 MESSAGE Request received when hardware in bad state.
CAUSE Hardware was not ready to process a request
message which required hardware participation.
ACTION Retry the request at a later time. If the
problem persists, call your Hewlett-Packard
representative.
1052 MESSAGE Not enough TARs available to process request.
CAUSE The driver could not obtain enough context
storage to begin processing a request, so the
request was rejected. Unexpected use of
incorrect port subqueues may have created
excessive pending hardware activity.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1053 MESSAGE Request received in invalid state.
CAUSE The driver received a sequencing message at the
wrong time. This was a startup, shutdown, or
dump-control message which arrived
out-of-sequence.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
1054 MESSAGE Unimplemented request received.
CAUSE The driver recognized a request message but the
feature it requested is not applicable to that
driver. The message descriptor was known but
the message and/or its subfunction code(s) are
unimplemented.
ACTION Call your Hewlett-Packard representative and
explain what you were trying to do.
1055 MESSAGE One or more do_bind config addresses is zero
(0).
CAUSE Possible causes for this problem are as follows:
1. The path to the hardware may not be
configured correctly.
2. The physical path to the hardware may be
faulty, or a previously undetected
hardware failure may have occurred since
system startup.
ACTION Possible actions for this problem are as
follows:
1. Check to be sure the configured pathname
is correct for the cardslot the PSI is
in.
2. Write down the error information
displayed on the console, submit an SR,
and call your Hewlett-Packard
representative.
1056 MESSAGE Critical configuration message data is
incorrect.
CAUSE The configuration buffer passed to the driver
during startup was not correctly formatted for
the driver it was sent to. That driver did not
find its own subsystem number in the expected
buffer field.
ACTION Run NMMAINT.PUB.SYS to verify the software
versions are correct between the driver and
module-configurator. Also check your
configuration screens and if necessary restore
NMCONFIG.PUB.SYS from a system backup tape. If
the problem does not go away, call your
Hewlett-Packard representative.
1057 MESSAGE Input buffer passed in a message is too small.
CAUSE Data was requested from the driver but the
length of the buffer specified in the request
was too small to accept all the data. The
driver is not capable of returning partial data.
The driver also imposes a minimum-size limit on
trace buffers.
ACTION If the problem occurred when starting trace, try
specifying a larger trace-buffer size. There
may be a version-mismatch between your driver
and other supporting software; call your
Hewlett-Packard representative.
1058 MESSAGE Driver tracing is already off.
CAUSE The driver received a trace-disable request when
trace was already off. The trace-manager module
should not have passed the request to the driver
when trace was off.
ACTION This is intended as a warning. You do not need
to turn trace off when it is not on.
1059 MESSAGE Driver tracing is already on.
CAUSE The driver received a trace-enable request when
trace was already on. The trace-manager module
should not have passed the request to the driver
when trace was on. The driver does not support
altering the active trace-level in this manner.
ACTION This is intended as a warning. You cannot turn
trace on when it is already on.
1060 MESSAGE Bad download file address in configuration data.
CAUSE The driver requires the valid memory address of
an open download file to appear in a
configuration buffer passed during startup, but
the address it found was zero. The module
configurator should not have sent the configure
message if it could not open the download file.
Alternately, configuration buffer formats may be
mismatched.
ACTION Run NMMAINT.PUB.SYS to verify the versions of
the driver, module configurator, and download
file. If the problem cannot be solved from this
information, call your Hewlett-Packard
representative.
1061 MESSAGE Bad middle plane buffer pool in configuration
data.
CAUSE The driver requires the valid buffer-pool ID of
a pool to be used for read/write datacomm line
frames, to appear in a configuration buffer
passed during startup, but the ID it found was
zero. The transport should not have invoked the
module configurator if the buffer pool could not
be opened. Alternately, configuration buffer
formats may be mismatched.
ACTION Check to see if the transport reported any
initialization errors. Run NMMAINT.PUB.SYS to
verify the versions of the driver, module
configurator, and download file. If the problem
cannot be solved from this information, call
your Hewlett-Packard representative.
1062 MESSAGE Bad top plane buffer pool in configuration data.
CAUSE The driver requires the valid buffer-pool ID of
a pool to be used for card trace and other
internal I/O, to appear in a configuration
buffer passed during startup, but the ID it
found was zero. The module configurator should
not have sent the configure message if the
buffer pool could not be opened. Alternately,
configuration buffer formats may be mismatched.
ACTION Run NMMAINT.PUB.SYS to verify the versions of
the driver, module configurator, and download
file. If the problem cannot be solved from this
information, call your Hewlett-Packard
representative.
1063 MESSAGE Timeout during startup.
CAUSE The driver startup timer expired between the
time the driver received its configure message
and the time it completed all hardware and
software startup. Probably the PSI hung due to
a hardware failure, download bug, or corrupt
download data not otherwise detected. Though
unlikely, it is also possible that completions
for driver requests were excessively delayed due
to heavy system loading.
ACTION The driver normally allows about 30 seconds for
all of startup. In a heavily loaded system,
this problem might appear intermittently; try
restarting the link. If the problem persists,
call your Hewlett-Packard representative.
1064 MESSAGE Timeout during selftest.
CAUSE The driver selftest timer expired between the
time the driver received its do_bind message and
the time the hardware completed selftest.
Probably the PSI failed selftest so badly it was
unable to report the selftest error.
ACTION The driver normally allows about 30 seconds for
selftest to complete. Your PSI hardware is
probably dead; write down the error information
displayed on the console, submit an SR, and call
your Hewlett-Packard representative.
1065 MESSAGE Local timer popped.
CAUSE This timeout should only occur if the PSI
hardware hangs due to a hardware failure or a
bug in the downloaded code. The driver
solicited activity from the hardware local
timeout seconds ago, and that activity has still
not completed. The driver has stopped the
hardware and requested a dump.
ACTION This problem should produce a dump; file an SR,
keep the raw dump, and call your Hewlett-Packard
representative.
1066 MESSAGE Unknown driver problem.
CAUSE The driver detected an error, but did not say
what type of error was detected.
ACTION Write down the error information displayed on
the console, submit an SR, and call your
Hewlett-Packard representative.
2013 MESSAGE Unknown error while attempting to autodial.
CAUSE Before attempting to autodial, the PSI detected
something wrong. Specifically, the PSI detected
an active ACR line before attempting to
autodial.
ACTION Check your autodialer and the modem.
2014 MESSAGE Autodial phone number configured incorrectly.
CAUSE The autodial phone number was entered into your
configuration screen incorrectly.
ACTION Check autodial phone number entry in your
configuration screen for this link.
2015 MESSAGE Autodial not completed.
CAUSE The autodial was not completed. This may happen
when the remote system's modem is not turned on
or not functional.
ACTION Check with your remote system to ensure that its
modems are turned on and functional.
2016 MESSAGE Local autodial modem not powered on.
CAUSE Your local autodial modem has not been turned
on.
ACTION Turn on your local autodial modem.
2017 MESSAGE Local autodial modem is busy.
CAUSE Possible causes for this problem are as follows:
1. Someone else is using your autodial
modem.
2. A previous user of the modem failed to
disconnect from it.
ACTION Possible actions for this problem are as
follows:
1. Check with other users of your system to
see if they are using the modem. If the
modem is not in use, turn the modem off,
wait a few seconds, and turn the modem on
and try again.
2. Powercycle the modem and try again. If
you try again and get the same error
message, your autodial modem may be
broken.
2018 MESSAGE Cannot autodial because of cabling problems.
CAUSE Either no cable is attached, a non-autodial
cable is attached, or a bad autodial cable is
attached.
ACTION Check to see if the cable is properly attached.
If it is, try another cable. If you still get
this error, write down the error information
displayed on the console, submit an SR, and call
you local Hewlett-Packard representative.
2500 MESSAGE There was a read from the PSI which completed
with a error.
CAUSE Possible causes for this problem are as follows:
1. The link is down.
2. You have a faulty PSI.
3. Internal driver, firmware or system
error.
ACTION Possible actions for this problem are as
follows:
1. Check the cabling and modem on the PSI.
2. Run Sherlock Diagnostics on the PSI.
3. Write down the console error message,
file an SR and call your Hewlett-Packard
representative.
2501 MESSAGE The driver does not have any more storage for
commands to the PSI.
CAUSE Unexpected use of driver subqueues may create
this problem.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2502 MESSAGE The PSI has completed a bad command.
CAUSE Bad Asynchronous event quad completed by the
PSI.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2503 MESSAGE The driver is unable to continue operation.
CAUSE The driver received a command or is in a state
where it cannot continue operation.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2504 MESSAGE An unexpected command was received by the
driver.
CAUSE A completion by the PSI was received in an
invalid state.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2505 MESSAGE PSI cannot send a frame across the line.
CAUSE Possible causes for this problem are as follows:
1. Link could be down.
2. Bad PSI hardware
3. Internal PSI or driver error.
ACTION Possible actions for this problem are as
follows:
1. Check the cabling and modem.
2. Run Sherlock diagnostics to determine the
cause.
3. Write down the console error messages,
submit an SR and call your
Hewlett-Packard representative.
2506 MESSAGE Bad message parameter passed to the driver.
CAUSE The driver received a bad meta language tag
while binding with NS.
ACTION Write down the console error message, submit an
SR and call your Hewlett-Packard representative.
2507 MESSAGE Bad message received from NS.
CAUSE The driver received a bind message while it was
already bound.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2508 MESSAGE The PSI card is not ready for operation.
CAUSE The driver was requested to perform a command
when the PSI card was not ready.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2509 MESSAGE Bad completion from the PSI.
CAUSE The module dependent field returned by the PSI
does not make any sense.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.
2510 MESSAGE Bad message received from NS.
CAUSE The driver was asked to execute a command
without being bound to upper layer.
ACTION Write down the error information displayed on
the console, submit an SR and contact your
Hewlett-Packard representative.