Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!BOOLE.ECE.CMU.EDU!Gene.Hastings
From: Gene.Hastings@BOOLE.ECE.CMU.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: VaxCluster and rdump don't mix?
Message-ID: <1989.11.20.5.31.38.Gene.Hastings@boole>
Date: 20 Nov 89 05:51:34 GMT
References: <710@sce.carleton.ca>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

There are a number of simple (I hope!) ideas to pursue:
(Most of them require some sort of Ethernet monitor, like PC Netwatch, FTP
Software Lanwatch, TCPdump on a Sun, or a special purpose monitor like an
Excelan Lanlyser, or a Network General Sniffer.)

Is your Retix bridge really filtering? If it is, the Physics people should
not see any non-broadcast traffic. Check the Physics cable for existence of
the rdump traffic or destination addresses that aren't on it. 

There are two things that can be affecting the VMS hosts - inordinate
amounts of broadcast traffic (which would affect any host), or VERY high
traffic on the cable, this last because of features of the way DECNET
routing updates are done.

Chances are, iff the Vax subnet is seeing your traffic (and it can't be
avoided), some help can be gained by lengthening (in NCP) the DECNET routing
period. Have them check the DECNET manuals for ranges of settings for the
announce and listen parameters.

Gene