Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!sdcsvax!ucsdhub!hp-sdd!ncr-sd!crash!jeh
From: jeh@crash.CTS.COM (Jamie Hanrahan)
Newsgroups: comp.os.vms
Subject: Re: DECNET dies and users are disconnected
Message-ID: <1785@crash.CTS.COM>
Date: Mon, 28-Sep-87 16:51:37 EDT
Article-I.D.: crash.1785
Posted: Mon Sep 28 16:51:37 1987
Date-Received: Wed, 30-Sep-87 04:47:39 EDT
References: <8709272318.AA21530@ucbvax.Berkeley.EDU>
Reply-To: jeh@crash.CTS.COM (Jamie Hanrahan)
Organization: Simpact Associates, San Diego CA
Lines: 19
Summary: check power to Unibus adapter

In article <8709272318.AA21530@ucbvax.Berkeley.EDU> "NTVAXA::BILLY" <billy%ntvaxa.decnet@utadnx.cc.utexas.edu> writes:
>I keep getting the above messages [DECnet circuit bounce reports]
> on the console once or twice a day.  At the
>same time, all users are disconnected from that node.  Some of the users are on
>a DZ11 and some are over ETHERNET.  The node doing this is a part of a two node
>homogenous cluster.  This problem does not occur on the other node at all.
>However, the node causing the problem is an area router for DECnet.  
> ...

You didn't say what kind of VAX this was.  Many of the larger VAXes with
Unibus adapters can tolerate a power failure in the Unibus expansion box;
in fact, field service can power off the BA11, swap a card, and power it
on, and VMS keeps going... but users are thrown off of terminal lines 
that go to boards in that box, and of course DECnet circuits get dropped.
Which sounds a lot like what's happening to you.  

SO, if it's not a 730 or 750, I'd look for intermittent power problems (or
perhaps grounding problems) in the BA11.  You might also check the 
error log for Unibus adapter power failure reports.