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

220 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
link (CAT-5 for HP-PB 100Base-T, CAT-3 or -5 for 100VG-AnyLAN).
3100 CLAS0002 MESSAGE: Link disconnected.
CAUSE: The last upper layer subsystem has unbound itself from the
driver, triggering a link disconnect This event is also logged if the link
unexpectedly drops due to a cable disconnect, hub retrain request,
powerfail, severe line hit, or other recoverable error (“Status” = 32-bit
status giving the reason for the disconnect, 0 = normal).
ACTION: This event is informational only. If the network is being shut
down, no action is required.
However, if the link was supposed to be up or the message appears
frequently while the link is up, this indicates possible cabling problems;
make sure cabling is securely connected and properly routed away from
sources of interference, and is of the proper UTP category or grade for
the type of link (CAT-5 for HP-PB 100Base-T, CAT-3 or -5 for
100VG-AnyLAN).
3130 CLAS0003 MESSAGE: Driver is starting adapter card.
CAUSE: The driver has completed initial startup of the adapter card, or
a restart following a reset, powerfail, dump, or other recoverable
condition (“Status” = 32-bit status giving the result of the startup
attempt, 0=successful).
ACTION: This event is informational. No action is required unless the
status is nonzero. Nonzero status indicates the startup failed; this may
be preceded by other specific errors.
3160 CLAS0001 MESSAGE: Configuration failed.
CAUSE: After successful or unsuccessful completion of initial hardware
startup, the driver attempted to reply to a pending configuration
request from its module configurator, but encountered an error on the
send (“Cause” = 32-bit status returned by the call to
vg_dvr_send_reply).
ACTION: This is a fatal software error. It might be caused by heavy CPU
load, or by attempting to operate the network subsystem or tool which
started the link at too low of a CPU process priority, causing a timeout.
Any condition, such as a timeout or abort, which causes the driver’s
module configurator to cease awaiting the reply and dispose of its reply
port, might also cause this error.
The module configurator did not receive the reply, therefore network
and/or link startup will fail. The driver now “dies” and awaits a
shutdown, which the module configurator should attempt
automatically.
3190 CLAS0001 MESSAGE: Configuration failed.
CAUSE: Following an unsuccessful initial startup of its adapter card, or
a restart because of a powerfail or reset, the driver sent a bad reply to