|
|
|
The following error messages gives the meaning of the second 8 bits of 32-bit
status values produced by the WAN ACC Sync MUX link driver and its supporting
modules. This is the so-called "driver status" portion. All values are
driver-specific, and are intended to provide additional detail beyond the
generic indication provided by the first 8 bits of status.
For information about the generic portion of the status, you must look at the
first 8 bits, described in the previous section.
The final (rightmost) 16 bits gives the subsystem number of the module
generating the status, or 0 if there was no error or warning.
| MESSAGE: No error. |
| Level: 0 ($00)
CAUSE: The operation was successful. No error occurred.
ACTION: None |
| MESSAGE: Subsystem is opening link. |
| Level: 1 ($01)
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up.
ACTION: This event is informational. No action is
required. |
| MESSAGE: Driver is starting up. |
| Level: 2 ($02)
CAUSE: The driver has just completed initial configuration
and is now starting up.
ACTION: This event is informational.
No action is required. |
| MESSAGE: Driver is starting adapter card. |
| Level: 3 ($03)
CAUSE: The driver has completed initial startup of the
adapter card, or a restart following a reset, powerfail, dump, or
other recoverable condition.
ACTION: This event is informational.
No action is required. |
| MESSAGE: Driver is re-starting adapter card. |
| Level: 4 ($04)
CAUSE: The driver has completed a restart of the adapter
card, following a reset, powerfail, dump, or other recoverable condition.
ACTION: This event is informational.
No action is required. |
| MESSAGE: Link connected. |
| Level: 5 ($04)
CAUSE: The first upper layer subsystem to bind to the
driver triggered a link connect, which was successful. This event
is also logged after the link or cable has been successfully reconnected
after being disconnected, or on a link reconnect following a hub
retrain, severe line hit, power failure, or other recoverable error.
ACTION: This event is informational. No action is needed
unless the message appears frequently while the link is up, indicating
possible cabling problems; make sure cabling is securely connected
and properly routed away from sources of interference. |
| MESSAGE: Link disconnected. |
| Level: 7 ($07)
CAUSE: The last upper layer subsystem has unbound itself from the
driver, triggering a link disconnect. This event is also logged if the link
unexpectedly drops due to a cable disconnect, hub retrain request,
powerfail, severe line hit, or other recoverable error.
ACTION: This event is informational. No action is required if the
network is being shut down. However, if the link was supposed to be up or
the message appears frequently while the link is up, this indicates
possible cabling problems; make sure cabling is securely connected and
properly routed away from sources of interference. |
| MESSAGE: Driver is shutting down. |
| Level: 8 ($08)
CAUSE: The driver is being shut down. The last subsystem
that was using the driver is now closing it.
ACTION: This event is informational.
No action is required. |
| MESSAGE: Subsystem is binding to link driver. |
| Level: 9 ($09)
CAUSE: An upper-layer protocol has successfully bound
(rendezvoused) to the link driver. Being bound means the driver
can now route incoming data frames to this protocol.
ACTION: This event is informational. No action is required.
If this is the first bind, the link driver will now attempt to reconnect
the link. |
| MESSAGE: Subsystem is unbinding from link driver. |
| Level: 10 ($0A)
CAUSE: An upper-layer protocol has begun to unbind (separate)
from the link driver. Once unbound, the driver can no longer route
incoming data frames to this protocol.
ACTION: This event is informational. No action is required.
If this is the last bind, the link driver will now attempt to disconnect
the link. |
| MESSAGE: Subsystem is closing link. |
| Level: 11 ($0B)
CAUSE: An upper level subsystem has called the link module
deconfigurator, which has successfully located the link, and will now
proceed to close it.
ACTION: This event is informational.
No action is required. |
| MESSAGE: Cannot release ADA memory object. |
| Level: 14 ($0E)
CAUSE: During shutdown, the driver requested the I/O
system to release a memory object, but received an error reply in response.
ACTION: This error should not occur. The driver may be confused,
or there is a system problem. However, the driver will ignore the error and
attempt to continue with the shutdown. If this happens frequently, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot get ADA memory object. |
| Level: 15 ($0F)
CAUSE: During initial startup, the driver attempted to
obtain a memory object via the I/O system, but received a bad status
in the reply in response.
ACTION: Probably the amount of frozen memory on the system
is very high; if you have the GLANCE tool you can try to check memory
usage. Try retrying the operation again later, or first terminate
some applications and then retry. |
| MESSAGE: Cannot close NM logging. |
| Level: 18 ($12)
CAUSE: The link module configurator or deconfigurator attempted to
close access to the NM logging facility, but encountered an error.
ACTION: This is an informational warning that the logfile may
still be open. Use of the :SWITCHNMLOG command should not be
affected, however there may be a delay at system shutdown time. If this
happens every time, see Appendix
A "Submitting a CR" |
| MESSAGE: Cannot unfreeze a memory area. |
| Level: 19 ($13)
CAUSE: After previously freezing a data structure into
system memory, software encountered an error trying to unfreeze
the same memory.
ACTION: This is an informational warning that some system
memory resources may have been lost. Software probably continued,
ignoring the error. Software may be confused, or the pointer to
the memory area may have been changed. If this happens every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Powerfail detected. |
| Level: 22 ($16)
CAUSE: The driver was notified of a power failure by
the I/O system, or detected all 1's on a hardware register
read, and, upon checking further, saw that its hardware I/O address
space was disabled, indicating a powerfail had already occurred.
ACTION: This event is informational. No action is required.
Power failures can occur at any moment. If the driver was executing
at the moment power failed, power then returned, and the driver
ran to completion, noticing this error along the way. Upon exit,
the driver was then officially notified of a powerfail by MPE. The
driver then attempted powerfail recovery, and should now be operating
the same as before. |
| MESSAGE: Cannot release a system plabel. |
| Level: 25 ($19)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator encountered an error
while trying to release the link's write initiator procedure.
ACTION: This is an informational warning that some system memory
resources may have been lost. The module deconfigurator reported an error,
but attempted to continue with the close. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Late dump-done message received. Dump took too long. |
| Level: 27 ($1B)
CAUSE: The driver received a driver-dump completion message
when it was not working on a dump.
ACTION: This error is informational only. Probably the
Network Dump Process was delayed by other system processing, such
that it exceeded the time limit set by the driver. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, after which the driver will now attempt to
auto-reset and continue. If you are trying to reproduce a specific
problem but this error occurs every time, reduce the CPU or disc
activity load before the next attempt. If load is not the problem,
see Appendix A "Submitting a CR" |
| MESSAGE: A driver dump is starting. |
| Level: 28 ($1C)
CAUSE: During driver dumping, Dump Surrogate tried to
open the dump file.
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR" |
| MESSAGE: A driver dump was suppressed. Too many dumps already. |
| Level: 32 ($20)
CAUSE: During processing of some other fatal driver error,
the driver attempted a driver dump, but encountered an error.
ACTION: This error is mainly informational, since the driver did
not dump, but may be indicative of other, possibly-related problems. The
driver will still attempt to auto-reset itself, up to a total of 12
times or more. |
| MESSAGE: Driver is out of DMA resources. |
| Level: 33 ($21)
CAUSE: During processing of a fatal driver error, the
driver attempted a driver dump, but determined it had already dumped
too many times since it was initially started.
ACTION: By design, the driver attempts to auto-reset itself after
any driver dump. But after 3 dumps, to avoid uncontrollably filling disk
space with driver dumps, additional dumps are automatically suppressed.
No attempt is made to determine whether the dumps are duplicates of the
same problem. The driver did not dump, but will still attempt to auto-reset
itself, up to a total of 12 times or more. There is apparently something
wrong, since many driver dumps are occurring. Collect binary copies of all
dump files (NETDMP##.PUB.SYS) on tape for analysis by
Hewlett-Packard and see
Appendix A "Submitting a CR" |
| MESSAGE: Driver dump was forced. |
| Level: 34 ($22)
CAUSE: A user is forcing a driver dump to occur, typically
via the CI prompt.
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR" |
| MESSAGE: A received frame could not be delivered. |
| Level: 43 ($2B)
CAUSE: Just before delivering a received data frame to
an upper layer protocol, the driver found that the rendezvous table
entry specified in the buffer was not in the proper state.
ACTION: This is an internal error which detects a normal race
condition. Probably the protocol separated from the driver while a frame
destined for it was in motion. The frame was not delivered, and the buffer
was silently released. No action is required. |
| MESSAGE: Link tracing is already enabled. |
| Level: 46 ($2E)
CAUSE: The driver received a request to turn link tracing
on when it was already on.
ACTION: This event is informational. No action is required.
An error reply was sent in response to the request. Trace was not
started by this request this time, but it remains on. |
| MESSAGE: Link tracing is already disabled. |
| Level: 47 ($2F)
CAUSE: The driver received a request to turn link tracing
off when it was already off.
ACTION: This event is informational. No action is required.
An error reply was sent in response to the request. Trace was not
stopped by this request this time, but it remains off. |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 60 ($3C)
CAUSE: This is a generic hardware error, reported when any of the
driver's hardware access routines reports an error. By itself it is not
descriptive of the problem. This error is often seen as a result of
firmware crash.
ACTION: When this problem happens, driver will dump the card and itself.
If this problems happens repeatedly, then halt the system, take a memory
dump, and reboot. see
Appendix A "Submitting a CR" |
| MESSAGE: Bad hardware ID or path. |
| Level: 61 ($3D)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a supported
WAN ACC Sync MUX adapter card at the hardware path specified in NMCONFIG.
ACTION: Verify the path in NMCONFIG is correct and complete, and
matches the path where a WAN ACC Sync MUX adapter card is installed in the
computer backplane. Verify the Power LED is lit on that adapter. If
necessary, reseat the board or contact your Hewlett-Packard Representative
for hardware assistance. |
| MESSAGE: No adapter card found on specified PCI bus. |
| Level: 62 ($3E)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find an HP-PB bus
at the hardware path specified in NMCONFIG.
ACTION: Verify the path in NMCONFIG is correct and complete,
and matches the path where a WAN ACC Sync MUX adapter card is installed
in your computer backplane. If necessary, change NMCONFIG or contact
your Hewlett-Packard Representative for assistance in determining
paths or correcting bus hardware problems. |
| MESSAGE: Adapter card found does not match software configuration. |
| Level: 63 ($3F)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found a supported adapter
card at the path specified in NMCONFIG, but it was not the right
type of card for the link being started.
ACTION: Correct the network configuration or plug in the
correct type of adapter card, and retry the operation. |
| MESSAGE: Memory test failed: memory data miscompare. |
| Level: 64 ($40)
CAUSE: Upon reaching the end of a diagnostic test of
adapter card memory or LAN controller chip memory, the driver had
accumulated at least one data pattern mismatch.
ACTION: One or more data patterns written by the driver
did not match the data read back from those same memory locations.
Depending on which test was being performed, either the adapter card or LAN
controller chip is faulty. Replace the adapter card. |
| MESSAGE: Cannot install interrupt handler. |
| Level: 73 ($49)
CAUSE: During initial driver startup, the driver was
unable to add its TLIH into the MPE I/O system, as an interrupt
handler routine for any adapter card interrupts on that EIR bit.
ACTION: The driver did not start up. There is probably an MPE
software installation problem, with incomplete or incompatible O/S software.
Verify the system is running an MPE release which supports WAN ACC Sync MUX
link drivers. The only other cause is a software bug; see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 77 ($4D)
CAUSE: This is a generic error saying that the link driver,
module configurator or deconfigurator, or other module of the link
subsystem encountered an error when trying to send a port message.
This error could be caused by the target module having been already
shut down. It could also be an indication of a more serious system
software problem, and may be followed by a system abort; probably
all message frames have been exhausted by some module running on the system.
ACTION: Severity and side effects of this error are dependent upon
the purpose of the message that was not sent. Attempt to determine the
conditions that led to the error. If it occurred during a shutdown,
possibly this error can be ignored. Otherwise, if the same problem happens
repeatedly, or if a system abort occurs, take a memory dump and.
See Appendix A "Submitting a CR" |
| MESSAGE: Cannot reset a system timer. |
| Level: 78 ($4E)
CAUSE: The driver attempted to reset a system timer previously
obtained from I/O Services but encountered an error. This is likely caused
by a bug in system software, or by corruption of the driver's
PDA context memory.
ACTION: This is a fatal software error. The driver cannot operate
without all necessary timers. If the problem persists, halt the system,
take a memory dump, and reboot. See
Appendix A "Submitting a CR" |
| MESSAGE: Cannot free a system timer. |
| Level: 79 ($4F)
CAUSE: The driver attempted to release a system timer
previously obtained from I/O Services but encountered an error.
This is likely caused by a bug in system software, or by corruption
of the driver's PDA context memory.
ACTION: This is a warning that some timer resources may have been
lost. Possibly followed by another error giving more information about what
kind of timer the driver was releasing; check log data for that error and
look it up also. If the problem happens every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 80 ($50)
CAUSE: This is a generic error saying that the link driver, module
configurator or deconfigurator, or other module of the link subsystem
encountered an error when trying to send a port message. This error could
be caused by the target module having been already shut down. It could also
be an indication of a more serious system software problem, and may be
followed by a system abort; probably all message frames have been exhausted
by some module running on the system.
ACTION: Severity and side effects of this error are dependent upon
the purpose of the message that was not sent. Attempt to determine the
conditions that led to the error. If it occurred during a shutdown,
possibly this error can be ignored. Otherwise, if the same problem happens
repeatedly, or if a system abort occurs, take a memory dump and
see Appendix A "Submitting a CR" |
| MESSAGE: Error from upper layer protocol read completor. |
| Level: 81 ($51)
CAUSE: The driver finished transferring a data frame
and passed it to an upper layer protocol, but the protocol's
read completor returned an error which was not one of the expected,
legal errors the driver was able to handle.
ACTION: This is an informational error only. The driver
incremented a statistic then attempted to continue. However, the
protocol may not have received the inbound frame, therefore some
applications could be hung. There may be a problem in the upper
layer protocol. If the problem occurs frequently, take a link trace
showing the problem, then see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot load driver plabel. |
| Level: 84 ($54)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load the code for the driver.
ACTION: Probably not all software required to operate this type of
link is installed. The software was incorrectly installed, or you may need
to purchase additional link or MPE software or install newer patches.
Reinstall the link software or contact your Hewlett-Packard Representative
for assistance. |
| MESSAGE: Cannot add driver to I/O system. |
| Level: 85 ($55)
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator attempted to create a new instance of the link
driver, but encountered an error which was not one of the legal errors the
configurator was able to handle.
ACTION: Verify the path in NMCONFIG is correct and complete, and matches
the path where a WAN ACC Sync MUX adapter card is installed in your
computer backplane. If necessary, change NMCONFIG or contact
your Hewlett-Packard Representative for assistance in determining
paths or correcting bus hardware problems. |
| MESSAGE: Cannot remove driver from I/O system. |
| Level: 86 ($56)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
an instance of the link driver, but encountered an I/O system error.
ACTION: Not all resources were released. The driver may
already have been shut down by some other means, or the system I/O
configuration may have been altered. If this happens frequently,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot load a system routine. |
| Level: 87 ($57)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load code for the write initiator procedure needed for
the link type configured in NMCONFIG.
ACTION: Probably not all software required to operate
this type of link is installed. Software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance. |
| MESSAGE: Cannot open NM logging. |
| Level: 88 ($58)
CAUSE: During a link open attempt by an upper-level subsystem,
the link module configurator encountered a positive (error) status
when trying to open NM logging against the link's subsystem ID.
ACTION: This event is informational. No action is required.
The module configurator cleared the error and will attempt to continue.
However, NM logging may not be available to the link. You may need
to install new NM logging patches. If the problem occurs every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot freeze a memory area. |
| Level: 89 ($59)
CAUSE: This is a generic error that during a link-open
or some other operation by an upper level subsystem, link software
encountered an error while trying to freeze some data into memory
before passing the driver a pointer to that data.
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the
operation. |
| MESSAGE: Did not receive an expected port message. |
| Level: 90 ($5A)
CAUSE: This is a generic error that during a link-open
or some other operation by an upper level subsystem, link software
sent a port message to the driver, then encountered an error while
awaiting the correct reply message.
ACTION: Severity and side effects of this error are dependent
upon the purpose of the message that was not received. There may
be a system problem with message ports, or the link driver may have
sent the wrong reply message. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot create a buffer pool. |
| Level: 107 ($6B)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to create an outbound buffer pool or control buffer pool.
ACTION: The system may be low on available memory. Try
stopping some applications or sessions and retry the operation.
If the problem persists, stop all networking and restart it, or
restart the system. The buffer size and pool size are not configurable.
If the problem still occurs, there could be a problem with the buffer
manager. See
Appendix A "Submitting a CR" |
| MESSAGE: Cannot delete a buffer pool. |
| Level: 108 ($6C)
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to delete an outbound buffer pool or control buffer pool.
ACTION: This is an informational warning that some system
memory resources may have been lost. Probably not all buffers were
freed before the pool was deleted. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: General error trying to get a buffer. |
| Level: 109 ($6D)
CAUSE: When attempting to directly obtain a new buffer
manager buffer from a read pool, to replenish the inbound buffer
cache for one of its bound protocols, the driver encountered an
error that was not one of the few legal errors it expected, or was
able to handle.
ACTION: The problem could indicate some serious internal problems
within the buffer manager or its data structures, or with the way the
system is configured. Note all log messages, especially the "Cause" status
for this error, and see Appendix A "Submitting a CR".
If the problem persists, take a system memory dump immediately after the
problem has occurred. see Appendix A "Submitting a
CR" |
| MESSAGE: Driver encountered a software problem. |
| Level: 116 ($74)
CAUSE: This is a generic software error, reported when
any of the driver's non-hardware routines reports an error. By itself
it is not descriptive of the problem. This error is often seen as a result
of previous errors from intrinsics, reply messages, or validity checks.
ACTION: When this error occurs as a result of previous errors, it
mainly serves as a way to track the sequence of the failure back to what
was happening at the time. Check for those errors and look them up for an
additional explanation of the problem. |
| MESSAGE: A driver request failed. |
| Level: 117 ($75)
CAUSE: This is a generic software error, used when the
driver receives a new request but cannot process it because of an
earlier failure. It is used in the reply to the outside module which
requested the operation, to indicate it could not be processed.
ACTION: If this status is reported, it is because of some earlier
failure. Check log files and locate any previous errors for this link, to
try to find the reason this error is now occurring. |
| MESSAGE: Module Configurator cannot access its context area. |
| Level: 120 ($78)
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator checked its context memory
area for validity, but did not find the expected data.
ACTION: The module deconfigurator's context memory area is being
overwritten, or is not working properly. The deconfigurator did not perform
the close. If this happens every time, wait until the next time the link is
to be closed; instead of closing the link, halt the system and take a
memory dump, and see
Appendix A "Submitting a CR" |
| MESSAGE: Error in configuring Download Surrogate. |
| Level: 121 ($79)
CAUSE: During the link start up process, the module configurator
tries to configure the Download Surrogate and encountered an error
where it got the surrogate's port number as Nil.
ACTION: This is a error. Try to restart the link again If the
problem persists with a known good card, see
Appendix A "Submitting a CR" |
| MESSAGE: The subsys link products are not installed. |
| Level: 122 ($7A)
CAUSE: Probably not all software required to operate
this type of link is installed. Software was incorrectly Installed,
or you may need to purchase additional software or install new patches.
ACTION: If this status is reported during a startup operation,
Reinstall the link software or contact your HP Representative for
assistance. |
| MESSAGE: Bind table full. Too many upper level protocols. |
| Level: 150 ($94)
CAUSE: When a new upper-layer protocol attempted to bind
(rendezvous) to the link driver, the driver determined all available
rendezvous table entries were already in use. Too many different protocols
are trying to use the driver.
ACTION: Shut down any networking subsystems that are not
currently needed and try again. |
| MESSAGE: Open table full. Too many driver users. |
| Level: 151 ($93)
CAUSE: Too many subsystems are attempting to open the
driver at the same time, or subsystems are shutting down without
closing the driver.
ACTION: Shut down any networking subsystems that are not
currently needed and try again. A side-effect of this error may
be that the driver becomes unusable. |
| MESSAGE: Driver initialization failed. |
| Level: 152 ($98)
CAUSE: While processing its very first startup message,
the driver encountered a problem. Probably the configured hardware
is not present, is not the correct kind of adapter card, or there
was a problem configuring the ISR into the I/O system.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log data for that error and look it up also, for more actions to
take. The driver will attempt to send an error reply for the startup
request. It then enters a "broken" state and awaits a shutdown, which the
module configurator should attempt automatically. |
| MESSAGE: Configuration failed. |
| Level: 154 ($9A)
CAUSE: This is a generic error, reported after successful
or unsuccessful completion of initial hardware startup, if the driver
encountered an error bringing up the adapter card, or when opening
the link, or while attempting to send the reply to a pending configuration
request from its module configurator.
ACTION: This is a fatal software error. It might be caused
by a bad adapter card, by having too many driver users, by a heavy
CPU load, or by attempting to operate the network subsystem or tool
which started the link at too low of a CPU process priority, causing
a timeout. Any condition, such as a timeout or abort, which causes
the driver's module configurator to cease awaiting the
reply and dispose of its reply port, might also cause this error.
The driver now "dies" and awaits a shutdown, which
the module configurator should attempt automatically. |
| MESSAGE: Heartbeat timeout. Adapter card appears to be hung. |
| Level: 160 ($A0)
CAUSE: The firmware on the adapter card has failed to
produce any interrupt from normal activity for over 10 seconds.
It has also failed, for an additional 5 seconds, to respond to the
driver's inquiry by producing a test interrupt. The driver has decided
the card is dead or hung.
ACTION: This is a fatal hardware error. Replace the adapter card.
The driver will enter a "broken" state and await a manual shutdown by the
operator. If the problem persists with a known good card, see
Appendix A "Submitting a CR" |
| MESSAGE: Adapter card did not finish reset in the time allowed. |
| Level: 162 ($A2)
CAUSE: During a link startup sequence, the driver to reset the
adapter card, but it still did not go "ready" after the reset.
ACTION: This is a fatal hardware error. Replace the adapter
card. The driver cannot start the link if the card will not reset.
If the problem persists with a known good card, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot open configuration file. |
| Level: 198 ($C6)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to open the configuration file.
ACTION: Verify an NMCONFIG.PUB.SYS file exists. If so,
try to verify its format matches rest of the operating system. If the
system was updated, you may need to run NMMGRVER.PUB.SYS to
convert the file to a newer format. If the system was backdated, you may
need to restore an older copy of NMCONFIG from a backup tape. Perform a
:LISTF,3 command and make sure the file is not protected by a
lockword, and that the user starting the link has the necessary access
rights to open the file. Perform a :DSTAT ALL command and make sure
the disk drive the file resides on is present and mounted. Make sure the
file resides on Ldev 1. If not, use Fcopy and a file equation with a
";DEV=1" option to force a copy of the file onto Ldev 1. Perform
a :SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE process
exists. If not, shut down and restart the system, and retry the operation.
If the problem persists, contact your Hewlett-Packard Representative for
assistance with NMCONFIG file open problems. |
| MESSAGE: Cannot read from configuration file. |
| Level: 199 ($C7)
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator was able to open the configuration file, but
encountered an error while trying to data for the link being started.
ACTION: Using NMMGR, verify the path LINK.linkname exists
in the NMCONFIG file and is the exact same linkname which is now being
started. Verify the "Data=Y" flag is set at the top of that LINK
screen (meaning that ENTER has been pressed to save the configuration data
there). If the link is being used with NS or DTS, use the VALIDATE function
to validate the network configuration. Correct any configuration
errors and retry the operation. |
| MESSAGE: Cannot validate configuration file. |
| Level: 200 ($C8)
CAUSE: After successfully reading configuration data
for a link being started, the link module configurator checked the
data and found it was not valid. For NS/3000, probably the link
type and NI type do not match.
ACTION: Using NMMGR, verify the path LINK.linkname exists in the
NMCONFIG file and is either a LAPBMUX link type. If the subsystem being
started is NS, verify the link type matches the NI type for the network
being started. If these are not the problem, an incorrect version of NMMGR
may have been used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=82 to check versions of NMMGR components. The
format of your NMCONFIG file may be incompatible with the link driver
version installed on your system. Run NMMGRVER.PUB.SYS to update
your NMCONFIG file to a newer version, or restore an older version from a
backup tape, whichever is appropriate. If the problem still occurs, contact
your Hewlett-Packard Representative for assistance in using NMMGR to
configure WAN Sync MUX links. |
| MESSAGE: Cannot determine link type. |
| Level: 203 ($CB)
CAUSE: Early in a link open operation by an upper level
subsystem, the link module configurator encountered an error while
attempting to use Link Support Services to determine the type of
link being started. Probably the link is not completely configured.
ACTION: If the link is already started, LSS tries to read the link
type from its own link table. Otherwise, it tries to read it from the
NMCONFIG file. Using NMMGR, verify the path LINK.linkname exists
in the NMCONFIG file and is the exact same linkname which is now being
started. Verify the "Data=Y" flag is set at the top of that LINK screen
(meaning that ENTER has been pressed to save the configuration data there).
Correct any configuration errors and retry the operation. |
| MESSAGE: Cannot read from link table. |
| Level: 204 ($CC)
CAUSE: Early in a link open operation by an upper level
subsystem, the link module configurator attempted to determine if
the link was already running, by trying to read from the link table,
but an error occurred which was not one of the expected, legal errors
the configurator was designed to handle.
ACTION: If the linkname being started is a valid linkname,
then there may be a problem with Link Support Services. Halt the
system, take a system memory dump, then restart the system. If the
problem still occurs, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot add to link table. |
| Level: 205 ($CD)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to add the link to the link table.
ACTION: Possibly too many links are started. If not, try starting
a different link, to see if that works. If not, first try doing a
:LINKCONTROL @ command to see if any LSS errors occur. If they do,
you may need to reinstall MPE software; contact your Hewlett-Packard
Representative for assistance. Otherwise try restarting the system to see
if it corrects the problem or LINKCONTROL errors. If none
of these suggestions helps, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot delete from link table. |
| Level: 206 ($CE)
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
the link from the link table, but encountered an error.
ACTION: The module deconfigurator reported an error, but
attempted to continue with the close. Network management services
may have been shut down. Otherwise, if this happens every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot update to link table. |
| Level: 207 ($CF)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to update the link to the
link table ("Cause" = 32-bit status from
the call to lsslktbladd).
ACTION: The module configurator cleaned up and returned an error
to the subsystem. Possibly too many links are started. Try starting a
different link, to see if that works. If not, first try doing a
:LINKCONTROL @ command to see if any LSS errors occur. If they do,
you may need to reinstall MPE software; contact your Hewlett-Packard
Representative for assistance. Otherwise try restarting the system to see
if it corrects the problem or LINKCONTROL errors. If none of these
suggestions helps, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot open tracing. |
| Level: 208 ($D0)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup, but encountered an error
trying to open the trace file.
ACTION: Using NMMGR, check if a filename was configured. If so,
verify it is a legal MPE filename. A group and account may need to be
specified. Make sure the user starting the link has the necessary
capabilities to create that file in the group and account specified. Check
whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks. Make sure the version
of the NMCONFIG file matches the rest of the system software, by running
NMMGRVER.PUB.SYS. If none of these suggestions solves the problem,
contact your Hewlett-Packard Representative for assistance with configuring
a LAPBMUX link to enable tracing at startup. |
| MESSAGE: Cannot stop tracing. |
| Level: 209 ($D1)
CAUSE: After a link-open operation by an upper level
subsystem failed, the link module configurator tried to clean up,
but encountered an error trying to disable driver tracing.
ACTION: Probably the link driver returned an error reply when
asked to disable tracing. The driver may have a problem, or may already
have shut down. Check for other, driver-specific error messages which may
give more information about the problem, and look them up also. If no other
errors are found, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a trace request. |
| Level: 210 ($D2)
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator found that the link was configured to enable
tracing at startup. After successfully opened a trace file, the
configurator encountered an error trying to enable driver tracing.
ACTION: Probably the link driver returned an error reply when
asked to enable tracing. The driver may have a problem. Check for other,
driver-specific error messages which may give more information about the
problem, and look them up also. If no other errors are found, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver received an unknown port message. |
| Level: 216 ($D8)
CAUSE: The driver received a port message which it does
not implement, or containing a function code which it does not implement.
ACTION: This is an informational error only. If this error
occurred as part of a driver reset operation, it may be ignored. The driver
did not attempt to return an error reply to the message sender. That
sender may now be hung, awaiting a reply. Attempt to determine what action
caused the error. Activate link tracing, reproduce the problem, then stop
link tracing and save the resulting NMTCnnnn.PUB.SYS trace data
file, see
Appendix A "Submitting a CR" |
| MESSAGE: One or more bad bind parms passed by upper level protocol. |
| Level: 223 ($DF)
CAUSE: This is a generic error, reported when the driver
received a bind (rendezvous) from an upper layer protocol, but the
parameters in the request were not satisfactory to the driver. There
are a number of separate causes; look up the specific sublocation
code that was logged, for more information.
ACTION: All such errors are caused by bugs in the upper
layer protocol. Attempt to determine what protocol was trying to
bind, then see
Appendix A "Submitting a CR" |
| MESSAGE: A data buffer is too long. |
| Level: 224 ($E0)
CAUSE: During the receive, the driver was asked to prepare
a data block for receive, but the block length or memory allocation
was beyond the driver's configured length.
ACTION: This is an informational error only. If this problem
happens repeatedly and impacts the normal operation, then try configuring
the buffer length to the next higher value and see
Appendix A "Submitting a CR" |
| MESSAGE: One or more bad utility parms passed to driver. |
| Level: 225 ($E1)
CAUSE: The driver received a utility register access
request from an upper level tool program such as PLNKUTIL, but the
register number specified was out of the range of legal register
values for the selected register set.
ACTION: This is an informational error only. This problem
most likely occurred while diagnosing some previous problem. Retry
the operation using a legal register number for the register set
you have selected. |
| MESSAGE: One or more bad unbind parms passed by upper level protocol. |
| Level: 228 ($E4)
CAUSE: The driver received an unbind (separate) from
an upper layer protocol module, but the specified rendezvous ID
was out of range of legal rendezvous ID values for this driver,
or the corresponding rendezvous table entry state indicated no bind
had occurred or an unbind had already occurred. The protocol was
supposed to pass a rendezvous ID value previously returned to it
by the driver, when that protocol did a bind. The protocol may be
trying to unbind twice, or unbind from the wrong link.
ACTION: This problem most likely occurred while stopping
a running network subsystem. Attempt to determine which subsystem
was being stopped when the error occurred and, if possible, which
upper layer protocol was unbinding. Future attempts to start that
same protocol will probably fail until the entire network is stopped
or the system is rebooted. Either there is a bug in the driver or
upper layer protocol software, memory data corruption has occurred,
or there is a system software mismatch. You may require additional
software patches; contact your Hewlett-Packard Representative for
assistance. |
| MESSAGE: Module Configurator cannot get its context area. |
| Level: 230 ($E6)
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator tries to get the context
memory area for validity, but found as invalid pointer. ("Cause" =
32-bit status saying the context was not accessed).
ACTION: The module configurator's context memory
area is being overwritten, or is not working properly. If this happens
every time, wait until the next time the link is to be closed; instead
of closing the link, halt the system and take a memory dump, and
see Appendix A "Submitting a CR" |
| MESSAGE: The same upper level protocol attempted to bind twice. |
| Level: 235 ($EB)
CAUSE: The driver received a bind (rendezvous) from an
upper layer protocol module, but when it attempted to save information
about that protocol's address (SAP), a lower-level routine reported
an error because the address is already in the driver's rendezvous table.
ACTION: Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding. If a duplicate address is in the table already,
either an attempt has been made to start the same subsystem twice,
or a previous instance of that subsystem did not properly shut down;
a system reboot may be required to shut it. Otherwise there could
be a driver bug, if two protocols are truly different but the driver
thinks they are the same. Shut down the network and restart it.
If the problem happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Bad message for current state. |
| Level: 239 ($EE)
CAUSE: This is a generic error, reported when the driver
received a request from outside when the driver was not in a state
where it could process that type of request, or the when driver
has already processed a message of this type and was not expecting
another. The driver may have encountered a previous fatal error,
may be in the middle of startup, shutdown, or a recovery or dump
operation, a message may have arrived too late, or the sender may
be confused.
ACTION: If the message has replies, the driver will attempt
to send an error reply back to the sender. If another error has
already occurred, this event may be ignored. Otherwise, if the problem
happens frequently, or if external subsystems are noticeably impacted
after the error, see
Appendix A "Submitting a CR" |
| MESSAGE: Unknown file record format. |
| Level: 240 ($F0)
CAUSE: The trace or log formatter attempted to decode
a record header to obtain basic information such as length and version,
but on inspection found that the record does not appear to be a
WAN ACC record supported by this formatter.
ACTION: The formatter will attempt to print this record
in raw form. You may be trying to format a trace or log file taken
on a different system that has newer software than the system you
are formatting on. Format the file on the system you took the trace or log
on, or contact your Hewlett-Packard Representative. |
| MESSAGE: Unknown data version. |
| Level: 243 ($F3)
CAUSE: The trace or log formatter attempted to decode a record
header to obtain general information such as link type and link name, but
on inspection found that the version of that data was not supported by this
formatter, thus no other fields could be decoded.
ACTION: The formatter will attempt to print this record in raw
form. You may be trying to format a trace or log file taken on a different
system that has newer software than the system you are formatting on.
Format the file on the system you took the trace or log on, or contact your
Hewlett-Packard Representative. |
| MESSAGE: Error encountered while decoding an entry. |
| Level: 244 ($F4)
CAUSE: The trace or log formatter encountered an entry
having an unrecognized entry tag value. The formatter cannot decode
entries of this type.
ACTION: The formatter will attempt to print this entry in raw
form. You may be trying to format a trace or log file taken on a different
system that has newer software than the system you are formatting on.
Format the file on the system you took the trace or log on, or contact
your Hewlett-Packard Representative. |
| MESSAGE: Incomplete data was encountered. |
| Level: 245 ($F5)
CAUSE: The trace or log formatter attempted to decode
an entry, but on inspection found that the entry did not contain
at least the minimum length of data required for this version of the data.
ACTION: The trace or log file may be corrupted, or you may be
trying to format a trace or log file taken on a different system that has
newer software than the system you are formatting on. The formatter will
attempt to print this entry in raw form. Format the file on the system you
took the trace or log on, or contact your Hewlett-Packard Representative to
check if VGFOS patches are already available to correct this
problem. |
The following are the logging sublocation codes reported by the WAN ACC Sync
MUX link drivers, including sublocation code, log class, log message, and the
appropriate cause of and action to take for each.
For meanings of 32-bit status values generated by the driver,
refer to the sections on status values.
| MESSAGE: Cannot freeze a memory area. |
| Level: 1020 CLAS0001
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator was preparing to send configuration data to
the driver, but encountered an error while trying to freeze
that data into memory ("Cause" = 32-bit
status from the call to freeze).
ACTION: The system may be low on available memory. Try
closing any unnecessary applications or sessions and retry the operation.
The open did not succeed. The module configurator cleaned up and
returned an error to the subsystem. |
| MESSAGE: Cannot send a port message. |
| Level: 1040 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was preparing to send configuration
data to the driver, but encountered an error while trying to send
the port message ("Cause" = 32-bit status
from the call to send_msg).
ACTION: There may be a system problem, or another subsystem
has already shut the driver down while this one was trying to start
it. The open did not succeed. The module configurator cleaned up
and returned an error to the subsystem.
Retry the operation. If this does not help, try stopping all
networks using the link, then retry. If the problem still persists,
halt the system and take a memory dump, then see
Appendix A "Submitting a CR" |
| MESSAGE: An unexpected timeout occurred. |
| Level: 1060 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered a timeout while awaiting the correct
reply message ("Cause" = 32-bit status
from the call to extend_receive, saying there was a timeout).
ACTION: The link driver is probably hung because of a
problem in the driver, or the driver may have sent the wrong message
back. The open did not succeed. The module configurator cleaned
up and returned an error to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See
Appendix A "Submitting a CR" |
| MESSAGE: Did not receive an expected port message. |
| Level: 1080 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered a timeout while awaiting the correct
reply message ("Cause" = 32-bit status
from the call to extend_receive).
ACTION: There may be a system problem with message ports,
or the link driver may have sent the wrong reply message. The open
did not succeed. The module configurator cleaned up and returned
an error to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See
Appendix A "Submitting a CR" |
| MESSAGE: (Varies) |
| Level: 1100 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, but the driver returned an error in the reply message
("Cause" is not used here).
ACTION: If this error occurs, there may be additional
driver-specific errors logged, giving more information about the
problem. Attempt to locate those errors and look them up also. The
open did not succeed. The module configurator cleaned up and returned
an error to the subsystem. |
| MESSAGE: Cannot freeze a memory area |
| Level: 1120 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was preparing to send configuration
data to the driver, but encountered an error while trying to freeze
that data into memory ("Cause" = 32-bit
status from the call to freeze).
ACTION: The system may be low on available memory. Try
closing any unnecessary applications or sessions and retry the operation.
The open did not succeed. The module configurator cleaned up and
returned an error to the subsystem. |
| MESSAGE: Cannot send a port message. |
| Level: 1140 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was preparing to send configuration
data to the driver, but encountered an error while trying to send
the port message ("Cause" = 32-bit status from
the call to send_msg).
ACTION: There may be a system problem, or another subsystem
has already shut the driver down while this one was trying to start
it. The open did not succeed. The module configurator cleaned up
and returned an error to the subsystem.
Retry the operation. If this does not help, try stopping all
networks using the link, then retry. If the problem still persists,
halt the system and take a memory dump, then see
Appendix A "Submitting a CR" |
| MESSAGE: An unexpected timeout occurred. |
| Level: 1160 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered a timeout while awaiting the correct
reply message ("Cause" = 32-bit status from the
call to extend_receive, saying there was a timeout).
ACTION: The link driver is probably hung because of a
problem in the driver, or the driver may have sent the wrong message
back. The open did not succeed. The module configurator cleaned
up and returned an error to the subsystem.Perform a :LINKCONTROL @
command to see if an entry exists for the linkname being
started. If so, halt the system and take a memory dump. The dump
should tell Hewlett-Packard what actions the driver took, see
Appendix A "Submitting a CR" |
| MESSAGE: Did not receive an expected port message. |
| Level: 1180 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator sent configuration data
to the driver, then encountered an error while awaiting the correct
reply message ("Cause" = 32-bit
status from the call to extend_receive).
ACTION: There may be a system problem with message ports,
or the link driver may have sent the wrong reply message. The open
did not succeed. The module configurator cleaned up and returned
an error to the subsystem.Perform a :LINKCONTROL @ command to see
if an entry exists for the linkname being
started. If so, halt the system and take a memory dump. The dump
should tell Hewlett-Packard what actions the driver took, see
Appendix A "Submitting a CR" |
| MESSAGE: (Varies) |
| Level: 1200 CLAS0001
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator did not find an PCI bus at the hardware path
specified in NMCONFIG ("Cause" is not used here).
ACTION: If this error occurs, there may be additional
driver-specific errors logged, giving more information about the
problem. Attempt to locate those errors and look them up also. The
open did not succeed. The module configurator cleaned up and returned
an error to the subsystem. |
| MESSAGE: No adapter card found on specified PCI bus. |
| Level: 1220 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but encountered an error which was
not one of the legal errors the configurator was able to handle
("Cause" = 32-bit status from the call to io_configure).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.Verify the path in NMCONFIG is correct
and complete, and matches the path where a supported WAN ACC Sync
MUX adapter card is installed in your computer backplane. A diagram
of the backplane slot paths, often found in the rear of your system
near the backplane, may help you. You can also try an offline diagnostic
utility such as MAPPER, or an online utility such as SYSMAP, to
precisely determine your hardware configuration. If necessary, change
NMCONFIG or contact your Hewlett-Packard Representative for assistance
in determining paths or correcting bus hardware problems. |
| MESSAGE: No adapter card found on specified PCI bus. |
| Level: 1240 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find an PCI bus
at the hardware path specified in NMCONFIG ("Cause" is not used here).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.Verify the path in NMCONFIG is correct
and complete, and matches the path where a supported WAN ACC Sync
MUX adapter card is installed in your computer backplane. A diagram
of the backplane slot paths, often found in the rear of your system
near the backplane, may help you. You can also try an offline diagnostic
utility such as MAPPER, or an online utility such as SYSMAP, to
precisely determine your hardware configuration. If necessary, change
NMCONFIG or contact your Hewlett-Packard Representative for assistance
in determining paths or correcting bus hardware problems. |
| MESSAGE: Bad hardware ID or path. |
| Level: 1260 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a supported
WAN ACC Sync MUX adapter card at the hardware path specified in
NMCONFIG ("Cause" = 32-bit hex
value from a system table which holds the first 4 bytes
of IODC information from the adapter card).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.Verify the path in NMCONFIG is correct
and complete, and matches the path where a supported WAN ACC Sync
MUX adapter card is installed in the computer backplane. Verify
the Power LED is lit on that adapter. If necessary, reseat the board
or contact your Hewlett-Packard Representative for hardware
assistance. |
| MESSAGE: No adapter card found on specified PCI bus. |
| Level: 1280 CLAS0001
CAUSE: During a link-open operation by an upper level subsystem,
the link module configurator did not find an PCI bus at the hardware path
specified in NMCONFIG ("Cause" is not used here).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported WAN ACC Sync MUX adapter card is installed in your
computer backplane. A diagram of the backplane slot paths, often found in
the rear of your system near the backplane, may help you. You can also try
an offline diagnostic utility such as MAPPER, or an online utility such as
SYSMAP, to precisely determine your hardware configuration. If necessary,
change NMCONFIG or contact your Hewlett-Packard Representative for
assistance in determining paths or correcting
bus hardware problems. |
| MESSAGE: Bad hardware ID or path. |
| Level: 1300 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a supported
WAN ACC Sync MUX adapter card at the hardware path specified in
NMCONFIG ("Cause" = 32-bit hex
value from a system table which holds the first 4 bytes
of IODC information from the adapter card).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported WAN ACC Sync MUX adapter card is installed in the
computer backplane. Verify the Power LED is lit on that adapter. If
necessary, reseat the board or contact your Hewlett-Packard Representative
for hardware assistance. |
| MESSAGE: Adapter card found does not match software configuration. |
| Level: 1320 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found a supported adapter
card at the path specified in NMCONFIG, but it was not the right
type of card for the link being started.
ACTION: Correct the network configuration or plug in the
correct type of adapter card, and retry the operation. The module
configurator cleaned up and returned an error to the
subsystem. |
| MESSAGE: Cannot create a buffer pool. |
| Level: 1340 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to create an outbound buffer pool ("Cause" =
32-bit status from the call to bmgr_create_pool).
ACTION: The system may be low on available memory. The
module configurator cleaned up and returned an error to the subsystem.
Try stopping some applications or sessions and retry the operation. If the
problem persists, stop all networking and restart it, or restart the system.
The buffer size and pool size are not configurable. If the problem still
occurs, there could be a problem with the buffer manager,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot load a system routine. |
| Level: 1360 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load code for the write initiator procedure needed for
the link type configured in NMCONFIG ("Cause" =
32-bit status from the call to hpgetsysplabel).
ACTION: Probably not all software required to operate
this type of link is installed. Software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance. |
| MESSAGE: Cannot load driver plabel. |
| Level: 1380 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load the code for the driver ("Cause" =
32-bit status from the call to io_get_mgr_entry).
ACTION: Probably not all software required to operate
this type of link is installed. The software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance. |
| MESSAGE: Unable to auto-configure underlying IO paths. |
| Level: 1400 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was attempting to create
a new instance of the link driver, but encountered an error when
configuring the underlying I/O paths ("Cause" =
32-bit status from the call to io_configure_path).
ACTION: Probably not all software required to operate
this type of link is installed. The software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance. |
| MESSAGE: Cannot add driver to I/O system. |
| Level: 1420 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the link driver, but encountered an error which was
not one of the legal errors the configurator was able to handle
("Cause" = 32-bit status from the call to io_configure).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the
path where a supported WAN ACC Sync MUX adapter card is installed
in your computer backplane. A diagram of the backplane slot paths,
often found in the rear of your system near the backplane, may help
you. You can also try an offline diagnostic utility such as MAPPER, or
an online utility such as SYSMAP, to precisely determine your hardware
configuration. If necessary, change NMCONFIG or contact your Hewlett-Packard
Representative for assistance in determining paths or correcting
bus hardware problems. |
| MESSAGE: Cannot load Driver plabel. |
| Level: 1440 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to load the code for the DM (Device Manager) ("Cause" =
32-bit status from the call to io_get_mgr_entry).
ACTION: Probably not all software required to operate
this type of link is installed. The software was incorrectly installed,
or you may need to purchase additional software or install newer
patches. Reinstall the link software or contact your Hewlett-Packard
Representative for assistance. |
| MESSAGE: Cannot add driver to I/O system. |
| Level: 1460 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator attempted to create a new
instance of the DM (Device Manager) for link driver, but encountered
an error which was not one of the legal errors the configurator
was able to handle ("Cause" = 32-bit
status from the call to io_configure).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the path
where a supported WAN ACC Sync MUX adapter card is installed in your
computer backplane. A diagram of the backplane slot paths, often found in
the rear of your system near the backplane, may help you. You can also try
an offline diagnostic utility such as MAPPER, or an online utility such as
SYSMAP, to precisely determine your hardware configuration. If necessary,
change NMCONFIG or contact your Hewlett-Packard Representative for
assistance in determining paths or correcting
bus hardware problems. |
| MESSAGE: Cannot open configuration file. |
| Level: 1480 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator encountered an error while
trying to open the configuration file ("Cause" =
32-bit status from the call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.Verify an NMCONFIG.PUB.SYS file exists. If so,
try to verify its format matches rest of the operating system. If the
system was updated, you may need to run NMMGRVER.PUB.SYS to
convert the file to a newer format. If the system was backdated, you may
need to restore an older copy of NMCONFIG from a backup tape.
Perform a :LISTF,3 command and make sure the file is not protected
by a lockword, and that the user starting the link has the necessary access
rights to open the file.
Perform a :DSTAT ALL command and make sure the disk drive the file
resides on is present and mounted. Make sure the file resides on Ldev 1. If
not, use Fcopy and a file equation with a ";DEV=1" option to force a copy
of the file onto Ldev 1.
Perform a :SHOWPROC 1;TREE;SYSTEM command and verify an NMFILE
process exists. If not, shut down and restart the system, and retry the
operation. If the problem persists, contact your Hewlett-Packard
Representative for assistance with NMCONFIG file open
problems. |
| MESSAGE: Cannot read from configuration file. |
| Level: 1500 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator was able to open the configuration
file, but encountered an error while trying to data for the link
being started ("Cause" = 32-bit status from the
call to nmconfopen).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Using NMMGR, verify the path LINK.linkname exists in the NMCONFIG file and
is the exact same linkname which is now being started. Verify the "Data=Y"
flag is set at the top of that LINK screen (meaning that ENTER has been
pressed to save the configuration data there). If the link is being used
with NS, use the VALIDATE function to validate the network configuration.
Correct any configuration errors and retry the operation. |
| MESSAGE: Cannot validate configuration file. |
| Level: 1520 CLAS0001
CAUSE: After successfully reading configuration data
for a link being started, the link module configurator checked the
data and found it was not valid ("Cause" is not
used here). For NS/3000, probably the link type and NI type do not match.
ACTION: The module configurator cleaned up and returned
an error to the subsystem.Using NMMGR, verify the path LINK.linkname
exists in the NMCONFIG file and is LAPBMUX link type. If the subsystem
being started is NS, verify the link type matches the NI type for
the network being started.
If these are not the problem, an incorrect version of NMMGR may have been
used to create the NMCONFIG file on your system. Run
NMMAINT.PUB.SYS;PARM=82 to check versions of NMMGR components.
The format of your NMCONFIG file may be incompatible with the link driver
version installed on your system. Run NMMGRVER.PUB.SYS to update
your NMCONFIG file to a newer version, or restore an older version from a
backup tape, whichever is appropriate.
If the problem still occurs, contact your Hewlett-Packard Representative
for assistance in using NMMGR to configure LAPBMUX links. |
| MESSAGE: Bad hardware ID or path. |
| Level: 1540 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator did not find a valid hardware
path specified in NMCONFIG ("Cause" = 32-bit hex
value from a system table which holds the first 4 bytes of IODC
information from the adapter card).
ACTION: The module configurator cleaned up and returned an error
to the subsystem.
Verify the path in NMCONFIG is correct and complete, and matches the
path where a supported WAN ACC Sync MUX adapter card is installed
in the computer backplane. Contact your Hewlett-Packard Representative
for hardware assistance. |
| MESSAGE: Cannot open tracing. |
| Level: 1560 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup, but encountered an error
trying to open the trace file ("Cause" = 32-bit
status from the call to nmopentrace).
ACTION: This is an informational error that tracing was
not started. The link came up, but the error was returned to the
upper level subsystem, which may decide to shut the link back down again.
Using NMMGR, check if a filename was configured. If so, verify it is a
legal MPE filename. A group and account may need to be specified. Make
sure the user starting the link has the necessary capabilities to create
that file in the group and account specified.
Check whether the system is low on disk space. Check whether too many
NMTCnnnn.PUB.SYS trace data files already exist. Purge files as
necessary to free up disk space, or add more disks.
Make sure the version of the NMCONFIG file matches the rest of the system
software, by running NMMGRVER.PUB.SYS.
If none of these suggestions solves the problem, contact your
Hewlett-Packard Representative for assistance with configuring a WAN Sync
MUX link (SDLCMUX, LAPBMUX) to enable tracing at startup. |
| MESSAGE: Subsystem is opening link. |
| Level: 1580 CLAS0001
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up ("Transport" = name of the subsystem
which is starting the link, or its subsystem number
if the configurator does not know the name).
ACTION: None. This is an informational event only. A similar
event will be logged when the link is closed. |
| MESSAGE: Cannot stop tracing. |
| Level: 1600 CLAS0001
CAUSE: After a link-open operation by an upper level
subsystem failed, the link module configurator tried to clean up,
but encountered an error trying to disable driver tracing ("Cause" =
32-bit status from the call to sio_trace_req).
ACTION: This is an informational error that tracing was not
disabled. If this error occurs it is because some other error has already
occurred. The link open did not succeed.
Probably the link driver returned an error reply when asked to disable
tracing. The driver may have a problem, or may already have shut down.
Check for other, driver-specific error messages which may give more
information about the problem, and look them up also. If no other errors
are found, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a trace request. |
| Level: 1610 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator found that the link was
configured to enable tracing at startup. After successfully opened
a trace file, the configurator encountered an error trying to enable
driver tracing ("Cause" = 32-bit status from the
call to sio_trace_req).
ACTION: This is an informational error that tracing was
not enabled. The link came up, but the error was returned to the
upper level subsystem, which may decide to shut the link back down again.
Probably the link driver returned an error reply when asked to enable
tracing. The driver may have a problem. Check for other, driver-specific
error messages which may give more information about the problem, and look
them up also. If no other errors are found, see
Appendix A "Submitting a CR" |
| MESSAGE: The subsys link products are not installed. |
| Level: 1620 CLAS0001
CAUSE: Probably not all software required to operate
this type of link is installed. Software was incorrectly Installed,
or you may need to purchase additional software or install new patches.
ACTION: If this status is reported during a startup operation,
Reinstall the link software or contact your HP Representative for
assistance. |
| MESSAGE: Cannot release a system plabel. |
| Level: 1640 CLAS0001
CAUSE: During the link startup operation by an upper
level subsystem, the link module configurator encountered an error
while trying to release the link's key routine procedure
("Cause" = 32-bit status from the call to hprelsysplabel).
ACTION: This is an informational warning that some system
memory resources may have been lost. The module configurator reported
an error, but attempted to continue with the open. If this happens
every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Module Configurator cannot get its context area. |
| Level: 1660 CLAS0001
CAUSE: During the link start up process, the module configurator
tries to configure the Download Surrogate and encountered an error
where it got the surrogate's port number as Nil.
ACTION: This is an error. Try to restart the link again. If the
problem persists with a know good card, see
Appendix A "Submitting a CR" |
| MESSAGE: The link is already started. |
| Level: 1680 CLAS0001
CAUSE: During the first link-open operation by an upper level
subsystem, the link module configurator attempted to create a new instance
of the link driver, but discovered the driver was already created and has
been opened at least once ("Cause" = 32-bit status from the call to
io_configure, saying the link is already started).
ACTION: This is an informational warning only. The module
configurator will leave the link driver up and stop trying to start it
again. Usually preceded by another error. |
| MESSAGE: Error in configuring download surrogate. |
| Level: 1700 CLAS0001
CAUSE: During the first link-open operation by an upper
level subsystem, the link module configurator attempted to create
a new instance of the link driver, but discovered the driver was already
created and has been opened at least once ("Cause" = 32-bit status from the
call to io_configure, saying the link is already started).
ACTION: This is an informational warning only. The module
configurator will leave the link driver up and stop trying to start it
again. Usually preceded by another error. |
| MESSAGE: Cannot add to link table. |
| Level: 1720 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to add the link to the link
table ("Cause" = 32-bit status from the call to lsslktbladd).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.
Possibly too many links are started.
If not. try starting a different link, to see if that works. If not, first
try doing a :LINKCONTROL @ command to see if any LSS errors occur.
If they do, you may need to reinstall MPE software; contact your
Hewlett-Packard Representative for assistance. Otherwise try restarting the
system to see if it corrects the problem or LINKCONTROL errors. If none
of these suggestions helps, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot update to link table. |
| Level: 1740 CLAS0001
CAUSE: During a link-open operation by an upper level
subsystem, the link module configurator successfully started the
driver, but encountered an error trying to update the link to the
link table ("Cause" = 32-bit status from the call to lsslktbladd).
ACTION: The module configurator cleaned up and returned
an error to the subsystem.Possibly too many links are started.
If not. try starting a different link, to see if that works. If not, first
try doing a :LINKCONTROL @ command to see if any LSS errors occur.
If they do, you may need to reinstall MPE software; contact your
Hewlett-Packard Representative for assistance. Otherwise try restarting the
system to see if it corrects the problem or LINKCONTROL errors. If none
of these suggestions helps, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot freeze a memory area. |
| Level: 1760 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator was preparing to send
new configuration data to the driver, but encountered an error while
trying to freeze that data into memory ("Cause" =
32-bit status from the call to freeze).
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the operation. The driver
did not receive the updated configuration data. The module deconfigurator
attempted to continue with the close. If this happens every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 1780 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator was preparing to send
updated configuration data to the driver, but encountered an error
while trying to send the port message ("Cause" =
32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem
has already shut the driver down while this one was trying to close
it. The driver did not receive the updated configuration data. The
module deconfigurator reported an error, but attempted to continue
with the close. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: An unexpected timeout occurred. |
| Level: 1800 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, then encountered a timeout while awaiting the
correct reply message ("Cause" = 32-bit status
from the call to extend_receive, saying there was a timeout).
ACTION: The link driver is probably hung because of a
problem in the driver, the driver has already shut down, or the
driver may have sent the wrong message back. The module deconfigurator
reported an error, but attempted to continue with the close. If
this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Did not receive an expected port message. |
| Level: 1820 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, then encountered an error while awaiting the
correct reply message ("Cause" = 32-bit status
from the call to extend_receive).
ACTION: There may be a system problem with message ports, or the
link driver may have sent the wrong reply message. The module
deconfigurator reported an error, but attempted to continue with the close.
If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: (Varies) |
| Level: 1840 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator sent updated configuration
data to the driver, but the driver returned an error in the reply
message ("Cause" is not used here).
ACTION: If this error occurs, there may be additional
driver-specific errors logged, giving more information about the
problem. Attempt to locate those errors and look them up also. The
module deconfigurator reported an error, but attempted to continue
with the close. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Subsystem is closing link. |
| Level: 1860 CLAS0001
CAUSE: An upper level subsystem has called the link module
deconfigurator, which has successfully located the link, and will now
proceed to close it.
ACTION: None. This is an informational event only. A similar
event was logged when the link was opened. |
| MESSAGE: Module Configurator cannot access its context area. |
| Level: 1880 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator checked its context memory
area for validity, but did not find the expected data ("Cause" =
32-bit status saying the context was not accessed).
ACTION: The module deconfigurator's context memory
area is being overwritten, or is not working properly. The deconfigurator
did not perform the close. If this happens every time, wait until
the next time the link is to be closed; instead of closing the link,
halt the system and take a memory dump, and see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot delete from link table. |
| Level: 1900 CLAS0001
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
the link from the link table, but encountered an error ("Cause" =
32-bit status from the call to lsslktbldelete).
ACTION: The module deconfigurator reported an error, but
attempted to continue with the close. Network management services
may have been shut down. Otherwise, if this happens every time,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot delete a buffer pool. |
| Level: 1920 CLAS0001
CAUSE: During a link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to delete a control buffer pool ("Cause" =
32-bit status from the call to bmgr_delete_pool).
ACTION: This is an informational warning that some system
memory resources may have been lost. Probably not all buffers were
freed before the pool was deleted. The module deconfigurator reported
an error, but attempted to continue with the close. If this happens
every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot release a system plabel. |
| Level: 1940 CLAS0001
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator encountered an error
while trying to release the link's write initiator procedure
("Cause" = 32-bit status from the call to hprelsysplabel).
ACTION: This is an informational warning that some system
memory resources may have been lost. The module deconfigurator reported
an error, but attempted to continue with the close. If this happens
every time, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot remove driver from I/O system. |
| Level: 1960 CLAS0001
CAUSE: During the final link-close operation by an upper
level subsystem, the link module deconfigurator attempted to delete
an instance of the DM of link driver, but encountered an I/O system
error ("Cause" = 32-bit status from the call to io_unconfigure).
ACTION: The deconfigurator stopped trying to close the
link. However, the driver already received updated configuration
data removing the subsystem's multicast information, but
other resources, such as link table, were not updated. The driver
may already have been shut down by some other means, or the system
I/O configuration may have been altered. If this happens frequently,
see Appendix A "Submitting a CR" |
| MESSAGE: Cannot remove driver from I/O system. |
| Level: 1980 CLAS0001
CAUSE: During the final link-close operation by an upper level
subsystem, the link module deconfigurator attempted to delete an instance
of the link driver, but encountered an I/O system error ("Cause" = 32-bit
status from the call to io_unconfigured).
ACTION: The deconfigurator stopped trying to close the
link. Hiowever, the driver already receivedf updated configuration
data removing the subsystem's multicast information, but
other resources, such as link table, were not updated. The driver
may already have been shut down by some other means, or the system
I/O configuration may have been altered. If this happens frequently,
see Appendix A "Submitting a CR" |
| MESSAGE: Unable to write to adapter card PCI configuration space. |
| Level: 2000 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Unable to read from adapter card PCI configuration space. |
| Level: 2040 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Unable to write to adapter card PCI configuration space. |
| Level: 2080 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Unable to read from adapter card PCI configuration space. |
| Level: 2120 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Unable to write to adapter card PCI configuration space. |
| Level: 2160 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Bad message for current state. |
| Level: 2200 CLAS0001
CAUSE: The driver received a new open from an upper layer
subsystem, at a time the driver was not able to process these requests,
such as during shutdown or after a fatal software error ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if
the driver is shutting down or doing a dump, wait until that completes.
Retry the operation. If the driver still does not become usable
after this, use Control-B at the console to halt the system, take
a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Bad message for current state. |
| Level: 2240 CLAS0001
CAUSE: The driver received a new open from an upper layer
subsystem, at a time the driver was not able to process these requests,
such as during shutdown or after a fatal software error ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if
the driver is shutting down or doing a dump, wait until that completes.
Retry the operation. If the driver still does not become usable
after this, use Control-B at the console to halt the system, take
a memory dump, and reboot see
Appendix A "Submitting a CR" |
| MESSAGE: Link disconnected. |
| Level: 2250 CLAS0001
CAUSE: The last upper layer subsystem has unbound itself
from the driver, triggering a link disconnect This event is also
logged if the link unexpectedly drops due to a cable disconnect,
powerfail, severe line hit, or other recoverable error ("Status" =
32-bit status giving the reason for the disconnect, 0 = normal).
ACTION: This event is informational only. If the network
is being shut down, no action is required.
However, if the link was supposed to be up or the message appears
frequently while the link is up, this indicates possible cabling problems;
make sure cabling is securely connected. |
| MESSAGE: Link connected. |
| Level: 2260 CLAS0001
CAUSE: The first upper layer subsystem to bind to the
driver triggered a link connect, which was successful ("Mode" =
the local mode: DTE or DCE, "Protocol" = SDLC
or LAPB). This event is also logged after the link or cable has
been successfully reconnected after being disconnected, or on a
link reconnect following severe line-hit, power failure, or other
recoverable error.
ACTION: This event is informational only.
No action is needed unless the message appears frequently while the link is
up, indicating possible cabling problems; make sure cabling is securely
connected and properly routed away from sources of
interference. |
| MESSAGE: Cannot send a port message. |
| Level: 2280 CLAS0001
CAUSE: While attempting to send a reset request to a
lower manager during startup, the driver encountered an error on
the send ("Cause" = 32-bit status
returned by the call to send_msg).
ACTION: This error is sometimes fatal, causing the remainder
of the driver's processing to be skipped. May be followed by another
error giving more information about what kind of reply the driver
was trying to send; check log data for that error and look it up
also. If the link does not seem to be responding, attempt to shut
down and restart the network and/or link. If the problem persists,
wait until it occurs again, then use Control-B at the console to
halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 2320 CLAS0001
CAUSE: During a shutdown operation by an upper level subsystem,
the driver was preparing to send a reply to the unbind_request,
but encountered an error while trying to send the port message ("Cause"
= 32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem
has already shut the driver down while this one was trying to close
it. If this happens every time, see
Appendix A "Submitting a CR" |
| MESSAGE: No adapter card found on specified PCI bus. |
| Level: 2360 CLAS0001
CAUSE: During initial driver startup, a PCI bus was not
found at the hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Use NMMGR to verify the path
in NMCONFIG is correct and complete, and matches the path where a WAN ACC
Sync MUX adapter card is installed in your computer backplane. A diagram of
the backplane slot paths, often found in the rear of your system near the
backplane, may help you. You can also try an offline diagnostic utility
such as MAPPER, or an online utility such as SYSMAP, to precisely determine
your hardware configuration. If necessary, change the NMCONFIG
configurations or contact your Hewlett-Packard Representative for
assistance in determining paths or correcting bus hardware
problems. |
| MESSAGE: Cannot send a port message. |
| Level: 2400 CLAS0001
CAUSE: While attempting to send a bind request to a lower manager
during startup, the driver encountered an error on the send ("Cause" =
32-bit status returned by the call to send_msg).
ACTION: This error is sometimes fatal, causing the remainder
of the driver's processing to be skipped. May be followed by another
error giving more information about what kind of reply the driver
was trying to send; check log data for that error and look it up
also. If the link does not seem to be responding, attempt to shut
down and restart the network and/or link. If the problem persists,
wait until it occurs again, then use Control-B at the console to
halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 2440 CLAS0001
CAUSE: While shutting down the link, the driver attempted
to free ADA memory previously obtained from the MPE I/O system,
but encountered an error trying to send a memory request message
to the I/O Memory Port ("Cause" = 32-bit status
from the call to send_msg).
ACTION: This is a warning that some memory resources may
have been lost. The driver will attempt to continue. Unless this
happens frequently, the system should continue to run.
If the problem happens every time, enable link tracing via
:LINKCONTROL then reproduce the link shutdown problem (the trace
file will close automatically). Save the resulting trace file
(NMTC####.PUB.SYS) on tape for Hewlett-Packard analysis, and see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 2480 CLAS0001
CAUSE: While starting up the link, the driver attempted
to request ADA memory from the MPE I/O system, but encountered an
error trying to send a memory request message to the I/O Memory
Port ("Cause" = 32-bit status
from the call to send_msg).
ACTION: This is a fatal software error. The driver cannot
operate the adapter card without ADA memory. After reporting this
error, the driver will return a configuration error, then die and
wait to be shut down; the configuration routine should shut it down
automatically.The problem can be caused either by lack of memory
or by a bug. If you suspect high memory usage and have the GLANCE
tool, run it and check system memory usage. If usage is high, try
closing some applications or subsystems, then retry link startup.
If the problem persists, shut down the system to clear memory, then
reboot but try starting the link earlier, before too many other
applications get going.If still low on memory, you may need to add
more memory hardware. First, however, Hewlett-Packard can try to
determine if more memory would help, or if instead there is a bug.
Use NMMGR to make sure all logging classes are enabled for the link
type, for disk logging. Reproduce the problem, then collect all
NM log files (NMLG####.PUB.SYS) and see
Appendix A "Submitting a CR" |
| MESSAGE: Bad message for current state. |
| Level: 2560 CLAS0001
CAUSE: The driver received a new bind (rendezvous) from
an upper layer protocol, at a time when the driver was not able
to process these requests, such as before receiving its initial
configuration data, during shutdown, or after a fatal software error
("Cause" = 16-bit encoded value, giving driver
input event code and current state: HP use only).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.Check the system console; if the driver
is shutting down or doing a dump, wait until that completes. In
these cases, several protocols may experience this same error. If
the driver is not shutting down or dying, the protocol may be sending
binds to the driver at the wrong time. See
Appendix A "Submitting a CR" and
file a CR against the network subsystem being started. |
| MESSAGE: One or more bad bind parms passed by upper level protocol. |
| Level: 2600 CLAS0001
CAUSE: The driver received a bind (rendezvous) from an
upper layer protocol module, but the specified SDI address family
was not one of the values supported by the driver ("Cause" =
32-bit value giving the bad address family which was specified).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Either there is a bug in the driver or upper layer protocol software, or
there is a system software mismatch. You may require additional software
patches; contact your Hewlett-Packard Representative for
assistance. |
| MESSAGE: Link common reported a protocol bind problem. |
| Level: 2640 CLAS0001
CAUSE: While attempting to setup a rendezvous entry (by
calling lnk_rendez), an error was returned to the ISR. ("Cause" =
32-bit integer specifying the SAP that was trying to rendezvous).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
Either there is a bug in the driver or upper layer protocol
software, or there is a system software mismatch. You may require
additional software patches; contact your Hewlett-Packard Representative
for assistance. |
| MESSAGE: Link common reported an inbound buffering problem. |
| Level: 2680 CLAS0001
CAUSE: After completing a read and delivering a data
buffer to an upper layer protocol, the ISR encountered an error
when trying to setup inbound buffer pool. ("Cause" =
32-bit status from Lnk_buf_initl).
ACTION: This problem most likely occurred while starting
a new network subsystem. Attempt to determine which subsystem was
being started when the error occurred and, if possible, which upper
layer protocol was binding. The bind failed. The driver logged the
error, then attempted to send an error reply message back to the
protocol module and continue.
If upper level network subsystems appear hung, try shutting
them down manually, or shutting down and restarting the network
link; if the problem persists, see
Appendix A "Submitting a CR"
Either there is a bug in the driver or upper layer protocol
software, or there is a system software mismatch. You may require
additional software patches; contact your HP Representative for
assistance. |
| MESSAGE: Subsystem is binding to link driver. |
| Level: 2720 CLAS0001
CAUSE: An upper layer protocol has successfully bound
(rendezvoused) to the link driver ("Addr" = 32-bit
encoded protocol address (SAP) value for this protocol module).
Being bound means the driver can now route incoming data frames
to this protocol.
ACTION: None. This is an informational message only. A
similar message is logged later, when the protocol unbinds. If this
is the first bind, the link driver will now attempt to reconnect
the link. |
| MESSAGE: Driver encountered a software problem. |
| Level: 2760 CLAS0001
CAUSE: While beginning a driver start or restart operation,
the driver tried to set the heartbeat timer, but encountered an
error ("Cause" = 32-bit status from the call to lnk_start_timer).
This timer was to be used to periodically awaken the
driver so it could verify card health; the driver cannot start if
this timer cannot be started. If this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or more.
If the problem persists, the system may be low on timers; try stopping some
applications before retrying again. |
| MESSAGE: Subsystem is unbinding from link driver. |
| Level: 2800 CLAS0001
CAUSE: An upper layer protocol has begun to unbind (separate)
from the link driver ("Addr" = 32-bit encoded
protocol address (SAP) value for this protocol module). Once unbound,
the driver can no longer route incoming data frames to this protocol.
ACTION: None. This is an informational message only. A
similar message is logged earlier, when the protocol binds. If this
is the last bind, the link driver will now attempt to disconnect the link.
If any errors occur as a result of the unbind, they will appear
after, not before, this log event; the unbind will still complete,
and the protocol will be successfully unbound. |
| MESSAGE: Driver encountered a software problem. |
| Level: 2840 CLAS0001
CAUSE: When attempting to separate during a protocol separate
(unbind), the driver gets an error from its state machine ("Cause" = 32-bit
status stating the driver is "dying").
ACTION: If the operator already knows the driver is in
the process of being closed, this error can be ignored. |
| MESSAGE: Bad hardware ID or path. |
| Level: 2860 CLAS0001
CAUSE: During initial driver startup, a supported Sync
MUX adapter card was not found at the hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Verify the path in
NMCONFIG is correct and complete, and matches the path where a Sync
MUX adapter card is installed in the computer backplane. Verify
the Power LED is lit on that adapter. If necessary, contact your
Hewlett-Packard Representative for hardware assistance. |
| MESSAGE: Driver is starting adapter card. |
| Level: 2880 CLAS0001
CAUSE: The driver has completed initial startup of the
adapter card, or a restart following a reset, powerfail, dump, or
other recoverable condition ("Status" = 32-bit
status giving the result of the startup attempt, 0 = successful).
ACTION: This event is informational. No action is required
unless the status is nonzero. Nonzero status indicates the startup
failed; this may be preceded by other specific errors. |
| MESSAGE: Cannot install interrupt handler. |
| Level: 2890 CLAS0001
CAUSE: During initial driver startup, the driver was
unable to add its ISR into the MPE I/O system, as an interrupt handler
routine for any adapter card interrupts on that EIR bit ("Cause" =
32-bit status returned by the call to io_config_pci_int).
ACTION: The driver did not start up. There is probably
an MPE software installation problem, with incomplete or incompatible
O/S software. Verify the system is running an MPE release which
supports WAN Sync MUX link drivers. The only other cause is a software bug;
see Appendix A "Submitting a CR" |
| MESSAGE: Powerfail detected. |
| Level: 2920 CLAS0001
CAUSE: During a LAPBMUX link connect attempt, the driver
detected all 1's on a hardware register read, and, upon checking
further, saw that its hardware I/O address space was disabled, indicating
a powerfail had already occurred.
ACTION: None. This error can be ignored. Power failures
can occur at any moment. The driver was executing at the moment
power failed. Power then returned, and the driver ran to completion,
noticing this error along the way. Upon exit, the driver was then
officially notified of a powerfail by MPE. The driver then attempted
powerfail recovery, and should now be operating the same as
before. |
| MESSAGE: One or more bad utility parms passed to driver. |
| Level: 2960 CLAS0001
CAUSE: The driver received a utility register access
request from an upper level tool program such as PLNKUTIL, but the
register number specified was out of the range of legal register
values for the selected register set.
ACTION: This is an informational error only. This problem
most likely occurred while diagnosing some previous problem. Retry
the operation using a legal register number for the register set
you have selected. |
| MESSAGE: Unable to read from adapter card PCI configuration space. |
| Level: 3000 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to read data from an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Unable to write to the adapter card PCI configuration space. |
| Level: 3040 CLAS0001
CAUSE: During driver startup, during a restart following
a reset operation, or during processing of a utility register read
request, the driver called the I/O System to write data to an adapter
register in PCI Configuration Space, but the I/O System reported an error.
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI backplane,
or may not be responding. If the I/O slot has a power indicator,
verify it is on. Re-seat the board, and if necessary, contact your
HP Representative for hardware assistance. |
| MESSAGE: Error from upper layer protocol read completor. |
| Level: 3080 CLAS0001
CAUSE: The driver finished transferring a data frame
and passed it to an upper layer protocol, but the protocol's
read completor returned an error which was not one of the expected,
legal errors the driver was able to handle ("Cause" =
32-bit status returned from the read completor).
ACTION: This is an informational error only. The driver
incremented a statistic, logged the error, then attempted to free
the read buffer and continue. However, the protocol may not have
received the inbound frame, therefore some applications could be
hung. There may be a problem in the upper layer protocol. Also,
if the protocol had already freed the buffer, this may have resulted
in a SysAbort from the Buffer Manager. If the problem occurs frequently,
start link tracing, reproduce the problem, then stop link tracing
and save the resulting NMTC####.PUB.SYS file for analysis by
Hewlett-Packard, and see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 3120 CLAS0001
CAUSE: The driver finished transferring a data frame,
but encountered an error while trying to send the frame to an upper
layer protocol via a port message ("Cause" = 32-bit
status returned by the call to send_msg).
ACTION: This error is reported at a low level, where the
actual send fails. It should be followed by a another error giving
more information. Locate that error and look it up also. The driver
will now attempt to clean up and continue. |
| MESSAGE: Error from upper layer protocol read completor. |
| Level: 3160 CLAS0001
CAUSE: The driver finished transferring a data frame,
but encountered an error while trying to send the frame to an upper
layer protocol via a port message ("Cause" = 32-bit
status returned by the call to Acc_send_msg).
ACTION: This is an informational error only. The driver
has incremented a statistic, logged the error, and will now attempt
to free the receive buffer and continue. However, the protocol may
not have received the inbound frame, therefore some applications
could be hung.
There is probably a problem in the upper layer protocol. Also, if the
protocol had already freed the buffer, this may have resulted in a SysAbort
from the Buffer Manager. If the problem occurs frequently, start
link tracing, reproduce the problem, then stop link tracing and save
the resulting NMTC####.PUB.SYS file for analysis by
Hewlett-Packard, and see
Appendix A "Submitting a CR" |
| MESSAGE: Link common reported an inbound buffering problem. |
| Level: 3200 CLAS0001
CAUSE: After completing a read and delivering a data
buffer to an upper layer protocol, the ISR encountered an error
when trying to refill the SAP's buffer cache. ("Cause" =
32-bit status from Lnk_buf_refill).
ACTION: This message is informational; this might be because of
contention on the system for buffers. However, if the underlying contention
or problem persists, the SAP may run out of buffers and no longer be able
to receive data over the network.
If upper level network subsystems appear hung, try shutting them down
manually, or shutting down and restarting the network link; if the problem
persists, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 3240 CLAS0001
CAUSE: This is a generic hardware error, reported when
any of the driver's hardware access routines reports an
error. By itself it is not descriptive of the problem. This error
is often seen as a result of firmware crash.
ACTION: When this problem happens, driver will dump the card and
itself. If this problems happens repeatedly, then halt the system, take a
memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver received an unknown port message. |
| Level: 3280 CLAS0001
CAUSE: Some module on the system has sent the driver
a message having an unknown message descriptor. The driver does
not implement any messages having that descriptor ("Cause" =
32-bit value of the message descriptor field).
ACTION: The driver took no action on the message, and
dropped it. However, if the problem occurs frequently, your system
may not be set up properly. The driver traces the message which
it received. If you can repeat the problem, first enable link tracing.
Then reproduce the problem, stop tracing, and save the resulting
trace data file for analysis by Hewlett-Packard, see
Appendix A "Submitting a CR" |
| MESSAGE: Bad message for current state. |
| Level: 3400 CLAS0001
CAUSE: The driver received a new open from an upper layer
subsystem, at a time the driver was not able to process these requests,
such as during shutdown or after a fatal software error ("Cause" =
16-bit encoded value, giving driver input event code and current
state; Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if
the driver is shutting down or doing a dump, wait until that completes.
Retry the operation. If the problem persists, the driver may be
broken. If the driver still does not become usable after this, use
Control-B at the console to halt the system, take a memory dump,
and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver initialization failed. |
| Level: 3580 CLAS0001
CAUSE: While processing its very first startup message, the driver
encountered a problem ("Cause" = 32-bit status returned by the call to
acc_initialize). Probably the configured hardware is not present,
is not the correct kind of adapter card, or there was a problem configuring
the ISR into the I/O system.
ACTION: This informational error should be preceded by
another error giving a more specific reason for the failure; check
log for that error and look it up also, for more actions to take.
The driver will attempt to send an error reply for the startup request.
It then enters a "broken" state and awaits a shutdown, which the module
configurator should attempt automatically. |
| MESSAGE: Bad message for current state. |
| Level: 3640 CLAS0001
CAUSE: The driver received a second copy of the first
initialization message it would ever get, indicating a second attempt
to start the driver ("Cause" = 16-bit encoded value, giving driver input
event code and current state: HP use only).
ACTION: The driver sent an error reply in response to
the message. Further action may not be required. If the problem
occurs frequently, try to determine what operator commands or actions
trigger the error, then see
Appendix A "Submitting a CR" |
| MESSAGE: Late dump-done message received. Dump took too long. |
| Level: 3670 CLAS0001
CAUSE: The driver received a driver-dump completion message
when it was not working on a dump ("Cause" = 32-bit
status saying there was a bad message for the current state).
ACTION: This error is informational only. Probably the
Network Dump Process was delayed by other system processing, such
that it exceeded the time limit set by the driver. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, after which the driver will now attempt to
auto-reset and continue. If you are trying to reproduce a specific
problem but this error occurs every time, reduce the CPU or disk
activity load before the next attempt.
If load is not the problem, see
Appendix A "Submitting a CR" |
| MESSAGE: Internal error while initiating a dump. Dump failed. |
| Level: 3700 CLAS0001
CAUSE: The driver's dump timer popped while
performing a dump operation ("Cause" = 32-bit
status indicating a timeout has occurred). Probably a heavy CPU
or disk activity load caused the Network Dump Process to take longer
than the time allowed by the driver.
ACTION: This error is informational only. The resulting
dump file may or may not be incomplete. A more serious driver problem
has already occurred, and by the time this error is logged, the
driver is already attempting to auto-reset and continue. If you
are trying to reproduce a specific problem but this error occurs
every time, reduce the CPU or disk activity load before the next
attempt. |
| MESSAGE: Link tracing is already disabled. |
| Level: 3840 CLAS0001
CAUSE: The driver received a request to turn link tracing
off when it was already off. Typically this condition is caught
at the C.I. level, however in this case trace may be under the control
of a different mechanism.
ACTION: No action is required; this error is informational
only. An error reply was sent in response to the request. Trace was not
stopped by this request this time, but it remains off. |
| MESSAGE: Cannot initiate a dump. Already dumping. |
| Level: 3850 CLAS0001
CAUSE: A user attempted to force a driver dump while
a previous driver dump was still occurring ("Cause" =
32-bit status saying a driver dump is starting).
ACTION: A dump of your problem is already being produced. Wait a
minute or two for the dump to finish. Forward the resulting
NETDMP##.PUB.SYS to Hewlett-Packard for analysis if necessary, and
see Appendix A "Submitting a CR" |
| MESSAGE: A driver dump is starting. |
| Level: 3880 CLAS0001
CAUSE: A user is forcing a driver dump to occur, typically via CI
("Cause" = 32-bit status saying the driver dump was forced).
ACTION: This error is informational only. The dump is probably
being forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot get ADA memory object. |
| Level: 3910 CLAS0001
CAUSE: During initial startup, the driver attempted to
obtain a memory object via the I/O system, but received a bad status
in the reply for that request ("Cause" = 32-bit
status from the reply message).
ACTION: The link did not start, and the driver attempted
to send back an error reply in response the configuration request
from the module configurator. Probably the amount of frozen memory
on the system is very high; if you have the GLANCE tool you can
try to check memory usage. Try retrying the operation again later,
or first terminate some applications and then retry. |
| MESSAGE: Cannot release ADA memory object. |
| Level: 4000 CLAS0001
CAUSE: During shutdown, the driver requested the I/O
system to release a memory object, but received an error reply in
response ("Cause" = 32-bit status from the mem_reply message).
ACTION: This error should not occur. The driver may be
confused, or there is a system problem. However, the driver will
ignore the error and attempt to continue with the shutdown. If this
problem happens frequently when the driver is shutting down, see
Appendix A "Submitting a CR" |
| MESSAGE: Link tracing is already enabled. |
| Level: 4000 CLAS0001
CAUSE: The driver received a request to turn link tracing
off when it was already off. Typically this condition is caught
at the C.I. level, however in this case trace may be under the control
of a different mechanism.
ACTION: No action is required; this error is informational only.
An error reply was sent in response to the request. Trace was not stopped
by this request this time, but it remains off. |
| MESSAGE: Bad message for current state. |
| Level: 4040 CLAS0001
CAUSE: The driver received a trace enable request, at
a time the driver was not able to process these requests. ("Cause" =
16-bit encoded value, giving driver input event code and current
state: Hewlett-Packard use only).
ACTION: Try this operation later. If the problem still persists.
If the driver still does not become usable after this, use Control-B at
the console to halt the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Bad message for current state. |
| Level: 4270 CLAS0001
CAUSE: The driver received an unconfigure request message
before it received its first configure request ("Cause" =
16-bit encoded value, giving driver input event code and current
state: HP use only).
ACTION: This error is informational only. The driver attempted to
return an error reply to the sending subsystem. If this problem happens
frequently, try to determine what actions lead to the problem, then see
Appendix A "Submitting a CR" |
| MESSAGE: Powerfail detected. |
| Level: 4970 CLAS0001
CAUSE: A power failure appears to have occurred during a hard
reset of the adapter card during startup ("Cause" is not used here).
ACTION: This is an informational error only. The driver
should have then attempted to recover from the powerfail. If you
suspect a powerfail has not occurred, and the same problem occurs
on every restart, the adapter card or system HP-PB hardware may
have failed. Replace the adapter card. Then, if the problem still
persists, contact your Hewlett-Packard Service Representative for
help in diagnosing your system hardware. |
| MESSAGE: Level-2 connection not happened within time allowed. |
| Level: 5000 CLAS0001
CAUSE: During a WAN link connect attempt, the driver
requested a level-2 connection from the remote host, but no connection
happened within the connect time allowed.
ACTION: This error is informational only. The driver will
retry the connect. If the problem happens every time, first check
that the cable is good, If the cable is good, then check the NMMGR
configuration like clock setting, interface type, Local mode (DTE
or DCE) etc. |
| MESSAGE: A data buffer is too long. |
| Level: 5040 CLAS0001
CAUSE: During the receive, the driver got a receive buffer
of length greater than the configured value in NMMGR. ("Cause" =
32-bit total length of the requested transmission).
ACTION: Try to check the NMMGR configuration. Try to set
the buffer size greater than 2048 for SDLCMUX link. If the problem
persists, first activate link tracing, reproduce the problem, stop
tracing, and save the resulting link trace file. Then see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5080 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to start the protocol firmware. By itself it is not descriptive
of the problem. This error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt
the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5120 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to configure the ports on the card. By itself it is not descriptive
of the problem. This error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt
the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5160 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to configure the port with the protocol configurations on
the card. By itself it is not descriptive of the problem. This error
is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5200 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to start the protocol (level-1)on the ports. By itself it
is not descriptive of the problem. This error is often seen as a
result of firmware crash.
ACTION: If this problems happens repeatedly, then halt
the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5240 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to stop the protocol (bring level-1 down) on the ports. By
itself it is not descriptive of the problem. This error is often
seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5280 CLAS0001
CAUSE: This is a generic hardware error, reported by firmware when
any of the driver's hardware interface routines tries to bring down the
ports on the card. By itself it is not descriptive of the problem. This
error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5320 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to start the protocol (level-2) on the ports. By itself it
is not descriptive of the problem. This error is often seen as a
result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Driver encountered a hardware problem. |
| Level: 5360 CLAS0001
CAUSE: This is a generic hardware error, reported by
firmware when any of the driver's hardware interface routines
tries to stop the protocol (bring level-2 down) on the ports. By
itself it is not descriptive of the problem. This error is often
seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt
the system, take a memory dump, and reboot, see
Appendix A "Submitting a CR" |
| MESSAGE: Cannot send a port message. |
| Level: 6000 CLAS0001
CAUSE: During final processing of a fatal driver error,
the driver attempted a standard auto-reset instead of dying. However,
its attempt to send a reset message to itself failed ("Cause" =
32-bit status returned by the call to send_msg). If this error is
reported, it is because the driver has already encountered some other error.
ACTION: This error is likely an indication of a more serious
system software problem, and may be followed by a system abort.
Probably all message frames have been exhausted by some module running
on the system. Further recovery actions may not be possible; if
the system fails, take a memory dump and reboot.
Otherwise, since the auto-reset failed, the driver dies instead,
notifying upper layer software via an asynchronous event message
if possible. The network and/or link must now be stopped and restarted.
Some upper layers may stop the link on their own in response to
an event message. If not, manually stop the network and/or link
via the appropriate operator command (for example, :NETCONTROL STOP)
and then restart it. |
| MESSAGE: A driver dump was suppressed. Too many dumps already. |
| Level: 6040 CLAS0001
CAUSE: During processing of a fatal driver error, the
driver attempted a driver dump, but determined it had already dumped
too many times since it was initially started ("Cause" is
not used here). If this error is reported, it is because the driver
has already encountered some other error.
ACTION: By design, the driver attempts to auto-reset itself after
any driver dump. But after 3 dumps, to avoid uncontrollably filling disk
space with driver dumps, additional dumps are automatically suppressed.
No attempt is made to determine whether the dumps are duplicates
of the same problem. The driver did not dump, but will still attempt
to auto-reset itself, up to a total of 12 times or more.
There is apparently something wrong, since many driver dumps are occurring.
Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape
for analysis by Hewlett-Packard and see
Appendix A "Submitting a CR" |
| MESSAGE: Internal error while initiating a dump. Dump failed. |
| Level: 6080 CLAS0001
CAUSE: During processing of a fatal driver error, the driver
attempted a driver dump, but encountered an error while trying to get or
reset a timer ("Cause" = 32-bit status returned by the call to
lnk_timer_start). This timer was to be used to avoid deadlock in
case the dump process did not respond; the driver cannot attempt a dump if
a dump timer cannot be started. If this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving
better information about the original cause; check log data for
that error and look it up also. The driver did not dump, but will
still attempt to auto-reset itself, up to a total of 12 times or
more. |
| MESSAGE: Cannot send a port message. |
| Level: 6120 CLAS0001
CAUSE: During final processing of a fatal driver error, the driver
attempted a driver dump, but was unable to send a dump event to the dump
process ("Cause" = 32-bit status returned by the call to send_msg).
If this error is reported, it is because the driver has already
encountered some other error.
ACTION: The driver did not dump, but will still attempt
to auto-reset itself, up to a total of 12 times or more. |
| MESSAGE: Internal error while initiating a dump. Dump failed. |
| Level: 6160 CLAS0001
CAUSE: During processing of some other fatal driver error, the
driver attempted a driver dump, but encountered an error. It then
encountered this second error while trying to clean up, when attempting
to release a dump timer it had obtained ("Cause" =
32-bit status returned by the call to lnk_stop_timer).
ACTION: Typically preceded by another error giving better
information about the original cause; check log data for that error
and look it up also. This error is mainly informational, since the
driver did not dump, but may be indicative of other, possibly-related
problems. The driver will still attempt to auto-reset itself, up
to a total of 12 times or more. |
| MESSAGE: Cannot send a port message. |
| Level: 6200 CLAS0001
CAUSE: During the normal operation, the driver encountered
a problem trying to send a reply to that message ("Cause" =
32-bit status returned by the call to Acc_send_reply) in
Acc_reply. Probably an underlying call to send_msg
has failed.
ACTION: This informational error should be preceded by
other errors giving a more specific reason for the failure; check
log data and look up that error also, for more actions to take.
Possibly the process which was to receive the reply no longer exists.
The error occurred on the reply, so if the caller, typically the
I/O system does exist, it will not receive the reply, and may time
out. The hardware path may or may not be usable after this error,
so a system reboot may be needed before the next retry, however
you may attempt a retry anyway. |
|
Complete PDF