[bit.listserv.novell] The silver bullet . . .

SYSDEH@SUVM.BITNET (Donald E. Hanley) (01/11/90)

Has anybody out there experienced anything similar to the
following on their networks:

We have seven file servers on an Arcnet backbone.

Five additional servers are connected to the backbone via internal bridges
in the backbone servers.  Almost all of the servers have at least two
network cards; i. e., each has one or more "local", plus one "global" network
connections.

Now for the problem:  During the last few months we have experienced
simultaneous "hits" on the backbone servers which causes
just these machines to go incommunicado on all of the networks to
which they are connected.  They aren't crashed; they just aren't
talking or listening anymore.

No error messages are displayed on the console or entered in the error log.

You can continue to use the console; in particular, you can turn
TRACK ON and see that the server thinks that it is still sending routing
information on networks to which it is connected.  However, a network
sniffer program shows no data traffic at all, just the token being
passed around.

The other file servers, i. e., those not directly connected to the
backbone are not affected; they march merrily along, oblivious to the
disaster that has befallen their brethern.

We are running Advanced and SFT 2.15a and 2.11.

Any insights?  Ideas?  Suggestions?  Sympathy?

SYPETER@CUGSBVM.BITNET (peter bombace) (01/11/90)

>Now for the problem:  During the last few months we have experienced
>simultaneous "hits" on the backbone servers which causes
>just these machines to go incommunicado on all of the networks to
>which they are connected.  They aren't crashed; they just aren't
>talking or listening anymore.

We've had the same (or what looks like the same) problem in a server
we use in one of our computer labs. I noticed that the server
is using up it's routing buffers before it crashes. I still haven't
found the solution, but since the machine that is hanging is an
HP Vectra (20mhz 386) the next thing I am going to try is changing
the server it a 16mhz 386, figuring maybe the Arcnet cards can't
hack 20mhz. I've tried everything else I can think of. I'll let you
know what happens.
-pb