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

246 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
6020 CLAS0001 MESSAGE: Hub did not report link up within time allowed.
CAUSE: If this error occurs, it is because the link did not connect within
25 to 30 seconds after it was instructed to do so.
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.
6050 CLAS0001 MESSAGE: Timeout while awaiting link autonegotiation completion.
CAUSE: The link appears to be connected, but the driver thinks it is still
waiting for it to connect.
ACTION: This error should not occur. If it happens frequently, see
Appendix A , “Submitting a CR.”
6080 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a HP-PB 100Base-T connect sequence after the link
came up, the driver attempted to check the final connect settings, 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.”
6110 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a HP-PB 100Base-T connect sequence after the link
came up, the driver attempted to check the final connect settings, but
encountered an error trying to read from the autonegotiation
advertisement 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.”