Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!nrl-cmf!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!decwrl!sun!pitstop!sundc!seismo!uunet!munnari!otc!uqcspe!miw
From: miw@uqcspe.OZ (Mark Williams)
Newsgroups: comp.os.vms
Subject: Re: LAVC help/info request
Message-ID: <1707@uqcspe.OZ>
Date: 14 Jan 88 04:47:11 GMT
References: <8801041936.AA01332@ucbvax.Berkeley.EDU>
Reply-To: miw@uqcspe.oz (Mark Williams)
Organization: Prentice Computer Centre, University of Queensland
Lines: 27

In article <8801041936.AA01332@ucbvax.Berkeley.EDU> SYSMGR@IPG.PH.KCL.AC.UK writes:
>We have a 4-node LAVC connected via a DELNI, which in turn is connected to
>thick wire Ethernet for comms. to other systems (not LAVC nodes). Recently,
>we had to extend the thickwire. I was most surprised that the fairly brief
>interruption to the thickwire caused all LAVC satellite nodes to perform a
>CLUEXIT bugcheck!
>                 [stuff deleted]
>3 - Why does a DELNI cause communication through itself to fail when the only
>    fault is on the thickwire to which it is connected? Is there any way to
>    prevent this action?

The communication through the DELNI fails, because it is repeating all the
junk reflections ,bogus collisions, and stuff that are happening out on
the Co-axial cable. Being on the DELNI is almost the same as being attached
to the cable directly.
	However, if you KNOW you are going to be disturbing the CO-AX, 
you can isolate the DELNI from the cable by switching the little black
switch to the right of the co-ax connector to the    [\] position.

Mark Williams
ccwilliams%wombat.decnet.uq.oz@uunet.uu.net

-- 
The views expressed above are not necessarily those of my employer. In a
couple of hours they may not even be my own.

Pound for pound, the amoeba is the most vicious creature on Earth.