Commands Reference, Volume 5

tokstat Command

Purpose

Shows token-ring device driver and device statistics.

The tokstat command displays the statistics gathered by the specified Token-Ring device driver. The user can optionally specify that the device-specific statistics be displayed in addition to the device driver statistics. If no flags are specified, only the device driver statistics are displayed.

This command is also invoked when the netstat command is run with the -v flag. The netstat command does not issue any tokstat command flags.

If an invalid Device_Name is specified, the tokstat command produces an error message stating that it could not connect to the device.

Flags

-d	Displays all the device driver statistics, including the device-specific statistics.
-r	Resets all the statistics back to their initial values. This flag can only be issued by privileged users.
-t	Toggles debug trace in some device drivers.

Parameters

Device_Name

The name of the Token-Ring device, for example, tok0.

Statistic Fields

Note: Some adapters may not support a specific statistic. The value of non-supported statistic fields is always 0.

The statistic fields displayed in the output of the toktstat command and their descriptions are:

Title Fields

`Device Type`	Displays the description of the adapter type.
`Hardware Address`	Displays the Token-Ring network address currently used by the device.
`Elapsed Time`	Displays the real time period which has elapsed since the last time the statistics were reset. Part of the statistics may be reset by the device driver during error recovery when a hardware error is detected. There will be another Elapsed Time displayed in the middle of the output when this situation has occurred in order to reflect the time differences between the statistics.

Transmit Statistics Fields

`Packets`	The number of packets transmitted successfully by the device.
`Bytes`	The number of bytes transmitted successfully by the device.
`Interrupts`	The number of transmit interrupts received by the driver from the adapter.
`Transmit Errors`	The number of output errors encountered on this device. This is a counter for unsuccessful transmissions due to hardware/network errors.
`Packets Dropped`	The number of packets accepted by the device driver for transmission which were not (for any reason) given to the device.
`Max Packets on S/W Transmit Queue`	The maximum number of outgoing packets ever queued to the software transmit queue.
`S/W Transmit Queue Overflow`	The number of outgoing packets which have overflowed the software transmit queue.
`Current S/W+H/W Transmit Queue Length`	The number of pending outgoing packets on either the software transmit queue or the hardware transmit queue.
`Broadcast Packets`	The number of broadcast packets transmitted without any error.
`Multicast Packets`	The number of multicast packets transmitted without any error.
`Timeout Errors`	The number of unsuccessful transmissions due to adapter reported timeout errors.
`Current SW Transmit Queue Length`	The number of outgoing packets currently on the software transmit queue.
`Current HW Transmit Queue Length`	The number of outgoing packets currently on the hardware transmit queue.

Receive Statistics Fields

`Packets`	The number of packets received successfully by the device.
`Bytes`	The number of bytes received successfully by the device.
`Interrupts`	The number of receive interrupts received by the driver from the adapter.
`Receive Errors`	The number of input errors encountered on this device. This is a counter for unsuccessful reception due to hardware/network errors.
`Packets Dropped`	The number of packets received by the device driver from this device which were not (for any reason) given to a network demuxer.
`Bad Packets`	The number of bad packets received (saved) by the device driver.
`Broadcast Packets`	The number of broadcast packets received without error.
`Multicast Packets`	The number of multicast packets received without error.
`Receive Congestion Errors`	The number of incoming packets dropped by the hardware due to a no resource error.

General Statistics Fields

`No mbuf Errors`	The number of times mbufs were not available to the device driver. This usually occurs during receive operations when the driver must obtain mbuf buffers to process inbound packets. If the mbuf pool for the requested size is empty, the packet will be discarded. The netstat -m command can be used to confirm this.
`Lobe Wire Faults`	The number of times the adapter detected an open or short circuit in the lobe data path (for example, the cable is unplugged).
`Abort Errors`	The number of times the adapter had problems transmitting.
`AC Errors`	The number of times the adapter received more than one AMP (Active Monitor Present) or SMP (Standby Monitor Present) frame which had the address recognized and frame copied bits set to zero. This indicates a problem with neighbor notification. Every station learns and remembers who its Nearest Active Upstream Neighbor (NAUN) is from AMP and SMP frames. When a station reports a problem, it also reports who its NAUN is. This helps to define the fault domain.
`Burst Errors`	The number of times the adapter detected that the polarity of the signal did not switch when necessary.
`Frame Copy Errors`	The number of times the adapter detected that a frame with its specific address has been copied by another adapter.
`Frequency Errors`	The number of times the adapter detected that the frequency of the incoming signal differs from the expected frequency by more than that allowed by the IEEE 802.5 standard. Check the active monitor responsible for master clocking of the ring and compensating for frequency jitter.
`Hard Errors`	The number of times the adapter either transmitted or received a beacon MAC frame.
`Internal Errors`	The number of times the adapter had an internal error.
`Line Errors`	The number of times the adapter detected an invalid character in a frame or token.
`Lost Frame Errors`	The number of times the adapter transmitted a frame and failed to receive it back.
`Only Station`	The number of times the adapter sensed that it is the only adapter on the ring.
`Token Errors`	The number of times the adapter, acting as an active monitor, detected that the token got lost. This may be due to ring reconfiguration. If this occurs often, check to see if other soft errors indicate a specific problem.
`Remove Received`	The number of times the adapter received a Remove Ring Station MAC frame request.
`Ring Recovered`	The number of times the ring is purged and recovered back into a normal operating state.
`Signal Loss Errors`	The number of times the adapter detected the absence of a receive signal.
`Soft Errors`	The number of times the adapter detected a soft error (recoverable by the MAC layer protocols).
`Transmit Beacon Errors`	The number of times the adapter transmitted a beacon frame.
`Driver Flags`	The device driver internal status flags currently turned on.

Device Specific Statistics Fields

This part of the display may be different for each type of adapter. It may contain adapter-specific information and some extended statistics that were not included in the generic statistics. Some adapters may not have any device-specific statistics. Some fields that may be listed in this section are:

`ARI/FCI Errors`	ARI/FCI mismatch is also referred to as receiver congestion. If an adapter gets an address match on a frame going by on the ring, Address Recognized Indication(ARI), and has no place into which to copy the frame, Frame Copied Indication(FCI), an ARI/FCI mismatch has occurred. The adapter will turn on the ARI bits but will not turn on the FCI bits in the FS byte at the end of the frame as it goes by. In other words, the adapter saw a frame that was to be received but, could not receive it because the receive buffers have been depleted. Two seconds later the adapter will send a Report Soft Error MAC frame indicating a receiver congestion error.
`DMA Bus Errors`	The number of times the adapter completed a DMA transfer and detected a bus error.
`DMA Parity Errors`	The number of times the adapter completed a DMA transfer and detected a parity error.
`Receive Overruns`	The number of times the adapter receive FIFO was full when the adapter tried to receive a frame.
`Receive Underruns`	The number of times the adapter transmit FIFO was empty before the end of frame symbol was detected.
`Number of read log commands issued`	The number of times an adapter error counter overruns (reached 255) and the device driver issues a read log command to read (and reset) the error counters.

Examples

To display the device driver statistics for tok0, enter:

tokstat tok0

This produces the following output:

TOKEN-RING STATISTICS (tok0) :
Device Type: Token-Ring High-Performance Adapter (8fc8)
Hardware Address: 10:00:5a:4f:26:c1
Elapsed Time: 0 days 0 hours 8 minutes 33 seconds
Transmit Statistics:                  Receive Statistics:
--------------------                  -------------------
Packets: 191                          Packets: 8342
Bytes: 17081                          Bytes: 763227
Interrupts: 156                       Interrupts: 8159
Transmit Errors: 0                    Receive Errors: 0
Packets Dropped: 0                    Packets Dropped: 0
Max Packets on S/W Transmit Queue: 17 Bad Packets: 0
S/W Transmit Queue Overflow: 0
Current S/W+H/W Transmit Queue Length: 0

Broadcast Packets: 1                 Broadcast Packets: 8023
Multicast Packets: 0                 Multicast Packets: 0
Timeout Errors: 0                    Receive Congestion Errors: 0
Current SW Transmit Queue Length: 0
Current HW Transmit Queue Length: 0

General Statistics:
-------------------
No mbuf Errors: 0                    Lobe Wire Faults: 0
Abort Errors: 0                      AC Errors: 0
Burst Errors: 0                      Frame Copy Errors: 0
Frequency Errors: 0                  Hard Errors: 0
Internal Errors: 0                   Line Errors: 0
Lost Frame Errors: 0                 Only Station: 0
Token Errors: 0                      Remove Received: 0
Ring Recovered: 0                    Signal Loss Errors: 0
Soft Errors: 0                       Transmit Beacon Errors: 0
Driver Flags: Up Broadcast Running 
   AlternateAddress ReceiveFunctionalAddr

To display the token-ring device driver statistics and the Token-Ring device-specific statistics for tok0, enter:

tokstat -d tok0