Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!pasteur!agate!ucbvax!decwrl!decvax!tektronix!gvgpsa!davew
From: davew@gvgpsa.GVG.TEK.COM (David C. White)
Newsgroups: comp.dcom.lans
Subject: Re: Some nodes can't reach others - is this a LanBridge problem?
Message-ID: <1083@gvgpsa.GVG.TEK.COM>
Date: 9 Feb 89 16:43:37 GMT
References: <17850@vax5.CIT.CORNELL.EDU> <13818@bellcore.bellcore.com>
Reply-To: davew@gvgpsa.GVG.TEK.COM (David C. White)
Followup-To: comp.docm.lans
Organization: Grass Valley Group, Inc., Grass Valley, CA
Lines: 21
Distribution:

In article <13818@bellcore.bellcore.com> karn@thumper.bellcore.com (Phil R. Karn) writes:
>
>When a bridge learns the broadcast address, it will refuse to pass
>broadcasts. This breaks ARP.  We had this problem occasionally on our
>(rather large) bridged network until DEC finally sent us a new batch of ROMs
>that fixed the problem.

Right.  We had the same problem.  Lean on your DEC service people to
replace the ROMs with the new version and the problem will go away.
This was hashed over fairly thoroughly a while back in this group and
at that time the ROMs were not released but you could get them if you
applied some real pressure.  They should be readily available now.

If you want to really hose the bridges, ping to your broadcast
address.  If you don't have the new ROMS this will lock out systems on
the other side of the bridge from reaching you.  The only way to
fix the problem is to initialize the bridge if you have access to
RBMS or power cycle the bridge.
-- 
Dave White	Grass Valley Group, Inc.   PHONE: +1 916.478.3052
P.O. Box 1114  	Grass Valley, CA  95945    davew@gvgpsa.gvg.tek.com