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

216 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
reproduce the problem, and save the resulting trace file
(NMTC####.PUB.SYS) for analysis by Hewlett-Packard. See Appendix
A, “Submitting an SR.”
MESSAGE: Illegal access to saved port message area.
2620 CLAS0001 CAUSE: While completing an old blocking request (requiring a driver
exit and later reply), the driver found that the index specified for an
entry in the pending message save area, where the request was
supposedly saved, was not within the range of legal table indexes
(“Cause”= the bad table entry number specified).
ACTION: This fatal software error is only caused by memory
corruption or a bug, because the driver should never passing an illegal
index. After reporting this error, the driver will die, then will either
attempt an auto-reset or else require a manual shutdown and restart. If
the problem persists, try to determine which program, networking
subsystem, or operator command causes it; then activate link tracing,
reproduce the problem, and save the resulting trace file
(NMTC####.PUB.SYS) for analysis by Hewlett-Packard. See Appendix
A, “Submitting an SR.”
MESSAGE: Out of internal comm frame resources.
2650 CLAS0001 CAUSE: While attempting to request action from its ISR module, the
driver found that no available communication frames were available on
the referenced queue (“Cause” is not used here). The number of
available comm frames is not configurable, and the driver cannot
operate if frames run out.
ACTION: This is a fatal software error. After reporting this error, the
driver will attempt a driver dump, then will auto-reset and attempt to
continue. Typically followed by another error giving more information
about what kind of comm the driver was trying to send; check log data
for that error and look it up also.
Collect binary copies of all NETDMP##.PUB.SYS dump files on tape for
analysis by Hewlett-Packard and see Appendix A, “Submitting an SR.”
MESSAGE: Cannot send a port message.
2680 CLAS0001 CAUSE: While attempting to send a reply to an earlier request message
from an upper level subsystem or tool, the driver 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 driver 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.”