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

Chapter 16 277
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
This code would only appear in the formatted PHY chip trace from a
100VG-AnyLAN link connect failure. It would not appear in a log event.
Seeing this error implies you are already using link tracing to try to
debug a problem, or are analyzing driver context data directly.
ACTION: The driver cleared statistics already, so none should overflow
during link training unless there is a problem.
There could be a hardware or configuration problem with the
100VG-AnyLAN hub or switch. Check the wiring. Try plugging the card
into a different port on the 100VG-AnyLAN hub or switch. Replace the
transceiver module in the switch if it has one. If this does not solve the
problem, replace the adapter card.
If the problem remains, use NMMGR to modify the LINK configuration
for this link, to enable link tracing at startup. Reproduce the problem,
then shut down the link and save the resulting NMTCnnnn.PUB.SYS
trace data file for analysis by Hewlett-Packard. See Appendix A,
“Submitting an SR.”
MESSAGE: (None)
9590 (None) CAUSE: 100VG-AnyLAN link training failed because, after the LAN
Controller chip reported receiving a training frame, the driver tried to
check if the frame was completely transferred into adapter card
memory, but detected a powerfail instead. A power failure state was
then signaled.
This code would only appear in the formatted PHY chip trace from a
100VG-AnyLAN link connect failure. It would not appear in a log event.
Seeing this error implies you are already using link tracing to try to
debug a problem, or are analyzing driver context data directly.
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. If the problem
happens every time, see Appendix A, “Submitting an SR.”
MESSAGE: (None)
9620 (None) CAUSE: 100VG-AnyLAN link training failed because after the LAN
Controller chip reported receiving a training frame, it had still not
finished transferring frame data into adapter card memory even after
the driver waited 64 microseconds. A hardware failure state was then
signaled.
This code would only appear in the formatted PHY chip trace from a
100VG-AnyLAN link connect failure. It would not appear in a log event.
Seeing this error implies you are already using link tracing to try to
debug a problem, or are analyzing driver context data directly.
ACTION: Replace the adapter card. If the problem continues, see
Appendix A, “Submitting an SR.”