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

Chapter 16 189
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Configuration failed.
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.
160 ($A0) CAUSE: The LAN controller chip on the adapter card has failed to
produce any interrupt from normal activity for over 5 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 you wish you may try running the VGPBA diagnostic and
attempt a reset. If the problem persists with a known good card, see
Appendix A, “Submitting an SR.”
MESSAGE: Card did not go ready after hard reset.
161 ($A1) CAUSE: After performing a hard reset of the adapter card during
startup, the HP-PB interface chip did not report “ready” status, or
reported an error.
ACTION: Replace the adapter card. If the same problem persists even
after replacement with a known good card, contact Hewlett-Packard:
your software could be out of date, but a patch may be available. It is
unlikely this would be caused by a system HP-PB bus hardware
problem.
MESSAGE: An expected PHY interrupt did not arrive.
162 ($A2) CAUSE: During a link connect sequence, the driver requested a test
interrupt from the PHY chip on the adapter card, but received a
timeout. The driver cannot connect the link if PHY interrupts do not
work.
ACTION: Replace the adapter card. The link did not connect. If the
problem persists with a known good card, see Appendix A, “Submitting
an SR.”