Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!NAZGUL.PHYSICS.MCGILL.CA!loki
From: loki@NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421)
Newsgroups: comp.sys.sgi
Subject: high collisions rates REVISITED
Message-ID: <9104250127.AA28210@nazgul.physics.mcgill.ca>
Date: 25 Apr 91 01:27:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 27


	OK... no one gave me any particularly useful info about what to
look for insofar as our net problem goes (recap: high collision rates
on 4D IRIS servers (2-10%) compared to SUNS (0.1% on servers and clients)
according to "netstat -i").  Examining net statistics shows that the
bulk of the problem lies with NFS to/from IRI.  SUN servers have no such
problem regardless of whether they are serving IRI or SUN.

	Besides the usual thinnet cabling limitations (max 185m of cable
segment before repeater is necessary, 50cm multiples in length, max 30 
machines), the only option suggested was to have a Sniffer or NetVisualizer
available, neither of which is financially feasible for us.  No one
mentioned a minimum cable length (other than 50cm).

	However.... at least two other sites noted the same problem and
have failed to come up with an explanation.  The Geometry hotline has yielded
nothing.  I was wondering if someone at SGI would like to comment.
Or at least propose a good reason why this should be acceptable from an IRIS.

		???

Regards,
                             _ _         _ _
Loki Jorgenson              / / _ _ _ _ _ \ \  node:  loki@Physics.McGill.CA
Grad/Systems Manager      _/_/_/_/_/ \_\_\_\_\_BITNET: PY29@MCGILLA
Physics, McGill University \ \ \_\_\_/_/_/ / / fax:   (514) 398-3733
Montreal Quebec CANADA      \_\_         _/_/  phone: (514) 398-7027