Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!LLL-ICDC.ARPA!oberman
From: oberman@LLL-ICDC.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: DEQNAs on the uVAX
Message-ID: <8702210442.AA29407@ucbvax.Berkeley.EDU>
Date: Fri, 20-Feb-87 14:30:00 EST
Article-I.D.: ucbvax.8702210442.AA29407
Posted: Fri Feb 20 14:30:00 1987
Date-Received: Sat, 21-Feb-87 16:12:14 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "Oberman, Kevin" <oberman@lll-icdc.arpa>
Organization: The ARPA Internet
Lines: 24
Approved: info-vax@sri-kl.arpa

>I am hoping to use a microVAX with two DEQNA ethernet interfaces to connect two
>ethernets together; the microVAX will have full function routing DECNET and
>will pass decnet messages between the two LANs.  I cannot use a bridge in this
>case, because of incompatibilities between other protocols in use on the two
>seperate LANs. 
>
>DEC at Colorado claims this configuration should work; so far I've been
>unsuccessful.  The second DEQNA does not autoconfigure; when I manually connect
>it with SYSGEN, at the address and vector suggested by DEC at Colo, the system
>bugchecks with an "unexpected system service exception" in NETACP when I try to
>set the line state on in NCP.  All I've gotten from DEC is "Hm...should
>work..."  Am I missing something obvious???? 

We have done it successfully. So it can be made to work. I have no idea
why you are BUGCHECKing. We had to manually configure the unit with CSR,
ADAPTER, etc. But it worked. I suggest you check the DEQNA manual to confirm
the secondary DEQNA addressing information. And make sure 1 DEQNA is at
the primary address and the other is at the secondary.

					R. Kevin Oberman
					LLNL
					arpa: oberman@lll-icdc.arpa
					(415) 422-6955
------