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

208 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
to send the port message (“Cause” = 32-bit status from the call to
send_msg).
ACTION: Theremay be a system problem, oranother subsystem has already
shut the driver down while this one was trying to close it. The driver did not
receive the updated configuration data. The module deconfigurator reported
an error, but attempted to continue with the close. If this happens every time,
see Appendix A , “Submitting a CR.”
1740 CLAS0001 MESSAGE: An unexpected timeout occurred.
CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator sent updated 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 isprobably hung because of aproblem in the driver,
the driver has already shut down, or the driver may have sent the wrong
message back. The module deconfigurator reported an error, but attempted to
continue with the close. If this happens every time, see Appendix A ,
“Submitting a CR.”
1760 CLAS0001 MESSAGE: Did not receive an expected port message.
CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator sent updated 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 module deconfigurator
reported an error, but attempted to continue with the close. If this happens
every time, see Appendix A , “Submitting a CR.”
1780 CLAS0001 MESSAGE:
(Varies)
CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator sent updated configuration data to the
driver, but the driver returned an error in the reply message (“Cause” is
not used here).
ACTION: If this error occurs, there may be additional driver-specific errors
logged, giving more information about the problem. Attempt to locate those
errors and look them up also. The module deconfigurator reported an error,
but attempted to continue with the close. If this happens every time, see
Appendix A , “Submitting a CR.”
1800 CLAS0001 MESSAGE: Subsystem is closing link.
CAUSE: An upper level subsystem has called the link module
deconfigurator, which has successfully located the link, and will now
proceed to close it.