ITEM: H9357L

What is the source of errors on my tr0 Interface? netstat -I tr0 5...

Question:

shows 25-40% errs on the tr0 interface.

 

Response:

Here is a scenario to investigate these errs.  Open two windows, and run in them

netstat -I tr0 60
iptrace -d \ -i tr0 /tmp/nettrace

The first command will give me a rough count of errs and frames in one minute,
and the second command I want to run over approximately the same minute (as
close as fingers and mice will allow) to trace all frames comming into the tr0
interface.

At the end of the minute, kill the pid for the iptrace command, and run

ipreport -r -n -s /tmp/nettrace >/tmp/netreport

First command gave me 8 errs in 127 packets, and interestingly enough, I see
8 unknown protocol frames in the report from iptrace.  All frames are to all-
stations address ffff ffff ffff and they show the following LLC header info:

TOK: dsap aa, ssap aa, ctrl 3, proto 0:0:0, type 600 (unknown)

Network General Sniffer on PS/2 Portable 70 was used to trace broadcast frames
from particular addresses with type=600 protocol.  Type 600 is an XNS protocol,
which INET family TCP/IP interfaces will not recognize, and count as errors.
But these errors are not necessarily detrimental to LAN performance.  Lots of
frames that ARE recognized are broadcast, e.g. ARP protocol.  As you add more
RISC System/6000s to your network, the 25-40% XNS protocol errs will probably
decrease to a less "alarming" percentage of network traffic.




Support Line: What is the source of errors on my tr0 Interface?  netstat -I tr0 5... ITEM: H9357L

Dated: April 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:46

Comments or suggestions?
Contact us