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

336 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
with the system software installation; the software may need to be
reinstalled, or additional software patches may be required, see
Appendix A , “Submitting a CR,” or contact your Hewlett-Packard
Representative to verify you have the required level of software
installed.
4170 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While attempting to reply to a change multicast list request
(most likely from upper level subsystem DLPI), the driver encountered
an error sending the reply message (“Cause” = 32-bit status returned
from pbt_dvr_send_reply).
ACTION: The process which sent the multicast list request message
(likely DLPI) may be hung waiting for the reply message that the driver
was unable to send.
If that is the case, try stopping the link to see if that allows the DLPI
process to terminate. Additional errors may have been logged which
give more information about why the send failed.
If the problem persists, collect all available information logged by this
link (driver) from the log file; also check for driver-generated dump files
(NETDMP##.PUB.SYS), see Appendix A , “Submitting a CR.”
4200 CLAS0002 MESSAGE: Link connected.
CAUSE: The first upper layer subsystem to bind to the driver triggered a
link connect, which was successful (“Mode” = the connection mode:
100BT, 10BT, etc.; “Duplex” = Full or Half). This event is also logged
after the link or cable has been successfully reconnected after being
disconnected, or on a link reconnect following a severe line hit or other
recoverable error.
ACTION: This event is informational only.
No action is needed unless the message appears frequently while the
link is up, indicating possible cabling problems; make sure cabling is
securely connected and properly routed away from sources of
interference, and is of the proper UTP category or grade for the type of
link (CAT-5 for 100Base-T).
4230 CLAS0002 MESSAGE: Link disconnected.
CAUSE: The last upper layer subsystem has unbound itself from the
driver, triggering a link disconnect This event is also logged if the link
unexpectedly drops due to a cable disconnect, hub retrain request,
powerfail, severe line hit, or other recoverable error (“Status” = 32-bit
status giving the reason for the disconnect, 0 = normal).
ACTION: This event is informational only. If the network is being shut
down, no action is required.
However, if the link was supposed to be up or the message appears
frequently while the link is up, this indicates possible cabling problems;