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

Chapter 16 225
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: A driver request failed.
3430 CLAS0001 CAUSE: While attempting to forward a diagnostic request to its ISR,
the driver encountered an error (“Cause”= 32-bit status returned by the
call to vg_dvr_copy_send_to_isr). Probably no comm frame was
available.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. Most likely the previous error
was fatal and the driver is about to “die”, then will either attempt an
auto-reset or else require a manual shutdown and restart.
MESSAGE: Driver encountered a software problem.
3460 CLAS0001 CAUSE: Before attempting to forward a diagnostic request to its ISR,
the driver discovered the ISR was already in a “dead” state and unable
to process requests (“Cause”= 32-bit status stating the driver is
“dying”).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored. The driver attempted to send an
error reply for the diagnostic request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
MESSAGE: Link tracing is already disabled.
3490 CLAS0001 CAUSE: The driver received a request to turn link tracing off when it
was already off. Typically this condition is caught at the C.I. level,
however in this case trace may be under the control of a different
mechanism.
ACTION: No action is required; this error is informational only. An
error reply was sent in response to the request. Trace was not stopped
by this request this time, but it remains off.
MESSAGE: A driver request failed.
3520 CLAS0001 CAUSE: While processing a request to turn link trace off, the driver was
unable to locate a free storage element in which to save reply
information (“Cause”= 32-bit status returned by the call to
vg_dvr_save_msg).
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. Most likely the previous error
was fatal and the driver is about to “die”, then will either attempt an
auto-reset or else require a manual shutdown and restart.