Novell NETWARE 6-DOCUMENTATION Manual page 2742

Statistic
DMA Parity Errors Count
Command Reject Count
Tx Timeout Count
Transmit Late Count
Transmit Defragment Count
304 Utilities Reference
Description
(TOKENDMA) This counter is incremented when a DMA transfer
completes with a parity error.
If this is incremented, it could indicate a hardware problem.
(TOKENDMA) This counter is incremented when the driver sends
a command to the board and the command is either invalid or the
board is still busy processing the previous command.
This number should be zero or a low number.
(TOKENDMA) This counter is incremented and the adapter is
reset if two seconds elapse before the driver learns from the
firmware that the transmit was or wasn't successful.
This counter shows the driver is successfully recovering from the
lost hardware transmit.
It isn't a problem if this number is incremented.
(TOKENDMA) This counter is incremented when the firmware
reports that the board transmitted more than it actually did.
After this event occurs, the data that wasn't transmitted will be
sent in the next packet.
This problem is more likely to occur on busier networks.
(TOKENDMA) This counter tracks how many ECBs are
redirected to the buffer below 16 MB.
The IBM Token-Ring DMA LAN boards are not able to access
memory above 16 MB. Therefore, if the operating system issues
an Event Control Block (ECB) with a memory address above 16
MB, the board uses some of the reserved buffers below 16 MB to
double buffer the ECB.
These are not errors. In many cases, this counter can be as high
as the total packets sent and received. However, this double
buffering decreases performance.
If the system has more than 16 MB of RAM and a board that is
bus-mastering or using DMA that is not a 32-bit adapter,
performance may decrease.