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

200 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
message (“Cause” = 32-bit status from the call to send_msg).
ACTION: There may be a system problem, or another subsystem has
already shut the driver down while this one was trying to start it. The
open did not succeed. The module configurator cleaned up and returned
an error to the subsystem.
Retry the operation. If this does not help, try stopping all networks
using the link, then retry. If the problem still persists, halt the system
and take a memory dump, then see Appendix A , “Submitting a CR.”
1060 CLAS0001 MESSAGE: An unexpected timeout occurred.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator sent configuration data to the driver, then
encountered a timeout while awaiting the correct reply message
(“Cause” = 32-bit status from the call to extend_receive, saying there
was a timeout).
ACTION: The link driver is probably hung because of a problem in the
driver, or the driver may have sent the wrong message back. The open
did not succeed. The module configurator cleaned up and returned an
error to the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See Appendix A ,
“Submitting a CR.”
1080 CLAS0001 MESSAGE: Did not receive an expected port message.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator sent configuration data to the driver, then
encountered an error while awaiting the correct reply message
(“Cause” = 32-bit status from the call to extend_receive).
ACTION: There may be a system problem with message ports, or the
link driver may have sent the wrong reply message. The open did not
succeed. The module configurator cleaned up and returned an error to
the subsystem.
Perform a :LINKCONTROL @ command to see if an entry exists for the
linkname being started. If so, then run the VBPBA diagnostic tool and
attempt to force a driver dump. If that works, save the resulting
NETDMP##.PUB.SYS file for analysis by Hewlett-Packard. Otherwise,
halt the system and take a memory dump. The dump should tell
Hewlett-Packard what actions the driver took. See Appendix A ,
“Submitting a CR.”