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

Chapter 16 235
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
buffer manager or its data structures, or with the way the system is
configured. Note all log messages, especially the “Cause” status for this
error, and see Appendix A , “Submitting a CR.” If the problem persists,
take a system memory dump immediately after the problem has
occurred.
4820 CLAS0001 MESSAGE: General error trying to get a buffer.
CAUSE: When attempting to post a queued request for a new buffer
manager buffer from a read pool, to replenish the inbound buffer cache
for one of its bound protocols, the driver’s ISR encountered an error that
was not one of the few legal errors it expected, or was able to handle
(“Cause” = 32-bit status returned by the call to bmgr_get_buffer).
ACTION: The driver logs this error, then attempts to continue. However,
the problem could indicate some serious internal problems within the
buffer manager or its data structures, or with the way the system is
configured. Note all log messages, especially the “Cause” status for this
error. If the problem persists, wait until it occurs again, then use
Control-B at the console to halt the system, take a memory dump, and
reboot. See Appendix A , “Submitting a CR.”
4850 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: While attempting to send a reply to an earlier request message
forwarded by the driver from an upper level subsystem or tool, the
driver’s ISR encountered an error on the send (“Cause” = 32-bit status
returned by the call to send_msg).
ACTION: This error is sometimes fatal, causing the remainder of the
driver’s processing to be skipped. May be followed by another error
giving more information about what kind of reply the ISR was trying to
send; check log data for that error and look it up also. If the link does
not seem to be responding, attempt to shut down and restart the
network and/or link. If the problem persists, wait until it occurs again,
then use Control-B at the console to halt the system, take a memory
dump, and reboot. See Appendix A , “Submitting a CR.”
4880 CLAS0001 MESSAGE: Driver could not identify the expected PHY on card.
CAUSE: After verifying the PHY chip on the adapter card had been
successfully reset, the driver checked the ID of the PHY, but found it
did not match any ID expected for this kind of adapter card
(“Cause” = 32-bit PHY ID obtained from the card).
ACTION: Replace the adapter card. The motherboard and PMC board
may be mismatched, the PHY chip may have gone bad, or your software
may be out of date. Only the upper 12 bits of the ID need to match the
expected value, which varies depending on adapter card type.
The link did not connect. Following this error, the driver may “die” and
require a manual shutdown of the network. If the same problem
persists even after replacement with a known good card, see Appendix
A , “Submitting a CR.”