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

Chapter 16 245
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
5930 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a HP-PB 100Base-T connect sequence, the driver
attempted to check for presence of a link signal, but encountered an
error trying to read from the generic status register on the PHY chip
(“Cause” = 32-bit status from the call to vg_mii_read16). Most likely a
powerfail has occurred.
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. Otherwise, the MII
bus may have failed; replace the adapter card. If the same problem
persists, see Appendix A , “Submitting a CR.”
5960 CLAS0001 MESSAGE: Autonegotiation reports link settings are incompatible
with hub.
CAUSE: If this error occurs, it is probably because the link has reported
a remote fault. Usually this means the adapter card and the hub or
switch to which it is connected, have failed to agree on a link speed and
duplex setting acceptable to both.
ACTION: Verify that the cable is securely connected to the adapter card
at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3
or 4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired, and
that you have software version A00550B0 or later.
Check the configuration of the hub or switch port to which the adapter
card is connected. Adjust that configuration and, if necessary, use
NMMGR to adjust the configuration of the link, so that something will
match. If necessary, specify a forced speed and duplex setting, and
disable autonegotiation, at both ends.
5990 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a HP-PB 100Base-T connect sequence, the driver found
the link was not connected yet, but encountered an error while trying to
get or reset a timer (“Cause” = 32-bit status from the call to
vg_start_timer). This timer was to be used to wait again for the link
connect to finish; the driver cannot connect the link if a PHY 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.