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

Chapter 18 383
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
SDI Driver Specific Status Values
The following error messages gives the meaning of the second 8 bits of
32-bit status values produced by the WAN ACC Sync MUX link driver
and its supporting modules. This is the so-called “driver status” portion.
All values are driver-specific, and are intended to provide additional
detail beyond the generic indication provided by the first 8 bits of
status.
For information about the generic portion of the status, you must look
at the first 8 bits, described in the previous section.
The final (rightmost) 16 bits gives the subsystem number of the module
generating the status, or 0 if there was no error or warning.
0 ($00) MESSAGE: No error.
CAUSE: The operation was successful. No error occurred.
ACTION: None
1 ($01) MESSAGE: Subsystem is opening link.
CAUSE: An upper level subsystem has called the link module
configurator, which has successfully located configuration for the link,
and will now proceed to start it up.
ACTION: This event is informational. No action is required.
2 ($02) MESSAGE: Driver is starting up.
CAUSE: The driver has just completed initial configuration and is now
starting up.
ACTION: This event is informational. No action is required.
3 ($03) 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.
ACTION: This event is informational. No action is required.
4 ($04) MESSAGE: Driver is re-starting adapter card.
CAUSE: The driver has completed a restart of the adapter card,
following a reset, powerfail, dump, or other recoverable condition.
ACTION: This event is informational. No action is required.
5 ($04) MESSAGE: Link connected.
CAUSE: The first upper layer subsystem to bind to the driver triggered a
link connect, which was successful. This event is also logged after the
link or cable has been successfully reconnected after being