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

Chapter 16 237
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape for
analysis by Hewlett-Packard and see Appendix A, “Submitting an SR.”
MESSAGE: General error trying to get a buffer.
4790 CLAS0001 CAUSE: While attempting to request action from its DVR module, the
driver’s ISR found that no available communication frames were
available on the referenced queue (“Cause” is not used here).
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, and see Appendix A, “Submitting an SR.” If the
problem persists, take a system memory dump immediately after the
problem has occurred.
MESSAGE: General error trying to get a buffer.
4820 CLAS0001 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 an SR.”
MESSAGE: Cannot send a port message.
4850 CLAS0001 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 an SR.”