THE DEVICE STATISTICS SCREEN
6-7
Rcvr Congestion Errors
This field displays the total number of Rcvr Congestion Errors. This
indicates a station is receiving/repeating a frame and recognizes a frame
addressed to it, but has no buffer space available for the frame.
This may indicate a poorly performing station, since it is receiving frames
faster than its adapter can copy information from the buffer. Although this
is counted as a non-isolating error (under the assumption that upstream
stations are transmitting data too quickly, rather than the receive station is
copying data too slowly), you can isolate the fault to the reporting station,
and may want to replace its network interface card (NIC) if this is a
frequent occurrence.
Token Errors
This field displays the total number of Token Errors. Token Errors occur
when an active monitor does not see a token circulating on the ring before
its TVX (Timer, Valid Transmission) time expires (e.g., a lost frame error
has occurred), or sees a recirculating frame or token. The active monitor is
then responsible for purging the ring and issuing a new token.
The major cause for token errors is the disruption of ring synchronization
as stations enter or leave the ring. Note that token errors are only reported
by an active monitor.
Frequency Errors
This field displays the total number of frequency errors. This indicates that
the frequency of the incoming signal deviates excessively from the
adapter’s onboard crystal oscillator (i.e., by more than .6%). This could
indicate an error in this node’s oscillator, the active monitor, or any node
in between. Note that it sometimes occurs when a network designed with
UTP cabling exceeds the standard of 72 stations. It also occurs more
frequently when your ring is operating at 16 Mbits/sec. When the node
detects a frequency error, it enters the monitor contention process.
Содержание TRMM
Страница 1: ...TRMM TRMMIM LOCAL MANAGEMENT USER S GUIDE ...
