NS3000/iX Error Messages Reference Manual (36923-90043)

394 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
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.
154 ($9A) MESSAGE: Configuration failed.
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.
160 ($A0) MESSAGE: Heartbeat timeout. Adapter card appears to be hung.
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.”
162 ($A2) MESSAGE: Adapter card did not finish reset in the time allowed.
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.”
198 ($C6) MESSAGE: Cannot open configuration file.
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