Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!pyramid!hplabs!ucbvax!USC-ISIF.ARPA!dolson
From: dolson@USC-ISIF.ARPA.UUCP
Newsgroups: mod.computers.vax
Subject: Re: microVMS 4.4, DECnet 4.4 and DEQNA's
Message-ID: <8606121119.AA10175@ucbvax.Berkeley.EDU>
Date: Wed, 11-Jun-86 14:47:16 EDT
Article-I.D.: ucbvax.8606121119.AA10175
Posted: Wed Jun 11 14:47:16 1986
Date-Received: Thu, 12-Jun-86 19:27:35 EDT
References: <8606101651.AA18211@utah-cbd.ARPA>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@sri-kl.arpa

ed-

I had a similar problem with circuit drop/reappearances when I first
set up our ethernet just a few months ago.  I was taking a single
11/785 to a two-node (both 11/785s) VAXCluster.  With no ether
experience we were trying to bring up DECSA terminal servers (which
get their load software from any host-designated VAX on the ether),
the DEUNAs on the VAXen, and interconnecting these boxes with a DELNI.
As you experienced, we saw circuit yo-yos which made absolutely no
sense.  At times things were so confused that the DEUNA on the first
785 looked like it had completely died; NCP> was reporting hard
controller errors, etc, which didn't go away until rebooting.

What was getting us was the DELNI.  It has 8 ports, right?  logically
equivalent, right?  Evidently not electrically.  If you aren't using
all 8 ports, start your connections at port 1 (nearest the special
DELNI-DELNI port) and use them sequentially.  I only counted 7
connections in your message so if your vacant DELNI port isn't number
8, maybe it should be.  That cleared our problems up.  And trying it
should only take a minute or two.

Doug (dolson @ Ada20.arpa)
-------