Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!decvax!crltrx!jg
From: jg@crltrx.crl.dec.com (Jim Gettys)
Newsgroups: comp.bugs.4bsd
Subject: Re: DEQNA woes
Message-ID: <118@crltrx.crl.dec.com>
Date: 27 Mar 89 14:06:26 GMT
References: <7705@pyr.gatech.EDU> <7615@batcomputer.tn.cornell.edu>
Reply-To: jg@crltrx.crl.dec.com.UUCP (Jim Gettys)
Organization: DEC Cambridge Research Lab
Lines: 21

In article <7615@batcomputer.tn.cornell.edu> jch@tcgould.tn.cornell.edu (Jeffrey C Honig) writes:
>In article <7705@pyr.gatech.EDU> don@pyr.gatech.edu (Don Deal) writes:
>>A Vaxstation II running 4.3 that we are using as a dedicated name server has
>>recently begun spurting a rash of:
>>
>>	qerestart: restart qe0 <n>
>>
>
>Older DEQNA's locked up under load, check with DEC to be sure your DEQNA
>is up to rev level.  Sorry, but I don't remember what rev level it
>should be up to.

Also note that this may be a symptom of broadcast woes, as the problem was
triggered by collisions in particular.  A badly configured network with
a bunch of hosts running old network code can cause real grief.  This
is generally caused by some machines believing one IP broad cast address
and others believing a different one, often caused by machines not knowing
how to do subnet routing or misconfigured broadcast addresses.  4.3BSD
is much less eager to be "helpful" and much less likely to forward broadcast 
packets to a gateway, but other machines on your net may not be so kind.
			- Jim