Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!ucbvax!KL.SRI.COM!info-vax-RELAY
From: info-vax-RELAY@KL.SRI.COM
Newsgroups: comp.os.vms
Subject: DEQNA timeouts
Message-ID: <8807271158.AA05174@ucbvax.berkeley.edu>
Date: 21 Jul 88 14:18:31 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: dragon@NSCVAX.PRINCETON.EDU
Organization: The Internet
Lines: 28

In article <2946@ci.sei.cmu.edu>sei!pdb@pt.cs.cmu.edu  (Patrick Barron)
writes:
>I'm trying to run the CMU/Tektronix TCP/IP package (V6.3) on MicroVAXen
>with DEQNAs.  On most of them it starts and runs fine.  However, on
>a couple of them, the IPACP starts, and then exits right away with
>"XE read error, RC=00000A00".

>Going through the sources reveals that return code to be equivalent
>to XM$M_STS_ACTIVE|XM$M_STS_TIMO.  The XM$M_STS_ACTIVE is OK; the
>XM$M_STS_TIMO is what it is objecting to.

>The I/O user's guide says that this return means something like "a
>DEUNA/DEQNA timeout has occurred".  I'm not sure what that means, and
>I can't find any further explaination.  What is timing out?  Is my
>hardware broken?

   In a word, probably!  Your problems with the DEQNA's are most likely
due to their not having a required FCO.  Without the FCO, DEQNA's are
brain dead, with the ECO they are merely brain damaged.  DEQNA's at
revision level D or earlier will need FCO DEQNA-R-001.

    DEQNA,s tend to fail under heavy load.  The FCO upgrades them
somewhat but does not correct the problem completely. 

   DEC's new Ethernet controller for the Q-BUS, the DELQA, is supposed
to work much better

   There is a mailing list for CMU/TEK TCP/IP users.  The list is
cmu-tek-tcp@c.cs.cmu.edu.  The request address is cmu-tek-tcp-request....