Compaq ProLiant 1000 LAN Driver Statistics for Novell Drivers - Page 14

ECG043/1097 INTEGRATION NOTE (cont.) 1...4 Frame Copied Errors See AC error for more information. AC errors AC errors are also referred to as Address Recognized Indication/Frame Copied Indicator (ARI/FCI) errors and occurs when a station detects that an upstream station did not correctly set the bits on a frame. If an AC error occurs, perform the following steps during your next planned maintenance: 1. Ensure that the NIC is compliant with the protocol in use. The NIC that did not set the bit (the station directly upstream of the station that reported the problem) is not participating in the low level protocol and may not be completely compliant with 802.5 protocol. 2. Replace the NIC to see if the problem still occurs. Token Errors Token Errors are reported by the active monitor due to one of the following reasons: 1. The active monitor detects that a frame has gone around the ring more than once, either because the sender de-asserted from the ring before stripping the frame, or because there are two active monitors present on the network. The active monitor will purge the network and clear the condition in either case. 2. A station reserved a token at a high priority and then de-asserted itself from the network. The active monitor will detect the token traversing the ring more than once as it searches for the station that requested the high priority. The active monitor will purge the ring. 3. The active monitor detects that no token or frame is received for 10 milliseconds. This usually occurs when a station asserts or de-asserts from the ring. If this counter escalates rapidly, it is usually caused by several stations asserting themselves onto the ring, or deasserting themselves at the same time. For example, this condition could occur when the power is off temporarily and then returned. In this example, several stations would try to assert themselves onto the ring all at the same time, disrupting the signal. If this condition appears to occur for no known reason, however, you may need to check your Multi-Access Unit (MAU). Use a network analyzer to isolate the problem area. 4. The active monitor detected a token that was returned to it containing a token violation. You will also see line errors along the ring. The active monitor will purge the ring, but you should also check for the following: Failing cable: Packet data traveling through shorted or damaged cabling may become corrupt before reaching the destination station and cause line errors and token errors. Segment not grounded properly: Improper grounding of a segment may allow ground-induced noise to corrupt data flow and cause line errors and token errors. Noisy cable: Interference or noise produced by motors or other devices can distort the signals and cause CRC/Alignment errors, which will increment the line error count and may cause token errors. If you cannot find the problem after checking the above conditions, use a network analyzer to isolate the station corrupting the frame. The analyzer should indicate which station is causing the problem, and let you know if the NIC should be replaced.