Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!acc.flint.umich.edu!jal
From: jal@acc.flint.umich.edu (John Lauro)
Newsgroups: comp.sys.apollo
Subject: Re: TCP/IP problems on DN10k
Message-ID: <1991Feb1.145429.11516@engin.umich.edu>
Date: 1 Feb 91 14:54:29 GMT
References: <1991Jan31.003842.14404@engin.umich.edu> <1991Jan31.161650.2117@alchemy.chem.utoronto.ca>
Sender: news@engin.umich.edu (CAEN Netnews)
Organization: University of Michigan - Flint
Lines: 15

In article <1991Jan31.161650.2117@alchemy.chem.utoronto.ca> system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:
>The last I heard, the problem is caused by a glitch in the VME Ethernet
>card, which causes it to lock up. The node then effectively disappears
>from the network. What relation this has to the dropped/delayed packets
>I'm not sure.

That sounds worse than what we are experiencing.  Right now all are
home directories are on the 10000, and that could really cause problems...
The only time it disappears from the net is with TCP/IP based
services such as ruptime.  It will sometimes drop a connection (tcpip)
for no reason too.

I'll take your suggestion and call the problem into Apollo.

    - John