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

Chapter 17 337
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
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 100Base-T).
4260 CLAS0003 MESSAGE: Driver is starting adapter card.
CAUSE: The driver has completed initial startup of the adapter card, or
a restart following a reset, 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.
4290 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
pbt_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.
4320 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
the pending config request message, if any, logged this error, then died
(“Cause” = 32-bit status giving the reason startup failed).
ACTION: This event indicates a fatal driver software condition. May be
preceded by other errors giving more information about the original
failure, which may help you determine whether it was a hardware or
software problem.
If this occurred on initial startup, the driver’s module configurator
should shut the driver down automatically. If not, it may mean the
adapter card has failed because of a hardware problem, or that a
software reset attempt has failed. The driver may need to be manually
shut down and restarted, using an appropriate network subsystem
command (such as :NETCONTROL STOP). If you wish, you may first try
running the VGPBA diagnostic; execute the Reset function to see if that