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

Chapter 16 275
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: Replace the adapter card. If the problem continues, there may
be a driver startup bug; see Appendix A , “Submitting a CR.”
9710 (None) MESSAGE: (None)
CAUSE: 100VG-AnyLAN link training failed because, after the LAN
Controller chip reported a training frame was sent, the driver tried to
check if the frame was completely transferred out of 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 a CR.”
9740 (None) MESSAGE:
(None)
CAUSE: 100VG-AnyLAN link training failed because after the LAN
Controller chip reported a training frame was sent, it had still not
finished transferring frame data out of 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 a CR.”
9770 (None) MESSAGE:
(None)
CAUSE: 100VG-AnyLAN link training failed because after the LAN
Controller chip reported a training frame was sent, the driver’s ISR
module detected an unexpected connect state. A software 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: This probably indicates a driver bug. If the problem happens
frequently, 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 a CR.”