Path: utzoo!mnetor!uunet!husc6!rutgers!ucla-cs!zen!ucbvax!IPG.PH.KCL.AC.UK!SYSMGR
From: SYSMGR@IPG.PH.KCL.AC.UK
Newsgroups: comp.os.vms
Subject: LAVC help/info request
Message-ID: <8801041936.AA01332@ucbvax.Berkeley.EDU>
Date: 4 Jan 88 15:30:39 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 32

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!

I think this may be because the LAVC installation procedure reduces the
SYSGEN parameter RECNXINTERVAL to 20 seconds, so that after the Ethernet is
u/s for longer than that the cluster falls apart. What I would like to ask
any LAVC experts out there is:

1 - Is my diagnosis right?

2 - Is there any way to prevent a cluster crash for this reason? Assuming my
    diagnosis is right, setting RECNXINTERVAL to something sensible like 300
    should work - but why do DEC reduce it from the default 60 to 20 in the
    first place? Has anyone out there actually tried this fix?

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?

    A merry new year to all, and thanks in advance for any help offered.


Nigel Arnot (Dept. of Physics, Kings College, the Strand, London WC2R 2LS, UK)

                 Janet: SYSMGR@UK.AC.KCL.PH.IPG
                 Arpa:  SYSMGR%UK.AC.KCL.PH.IPG@UKACRL.BITNET
                 UUCP:  SYSMGR%UK.AC.STRATH.VAXA@UKC
 Bitnet/NetNorth/Earn:  SYSMGR@IPG.PH.KCL.AC.UK (OR) SYSMGR%IPG.PH.KCL@AC.UK
                 Phone: +44 1 836 6192