[comp.dcom.lans] LAN hardware & software advice

wyatt@cfa.harvard.EDU (Bill Wyatt) (03/31/88)

>Q:	I would like to run Ethernet between the microVAX and the
>	11/750. Which ethernet controller should i buy for the uVAX?
>	I already have a DEUNA on the 750 but might trade it in for
>	a DELUA.
>A:	GO with the DELUA, there was a bug with DEUNA's in 750's that
>	they sunk so much power when they energized the transciever that
>	DCLO would occur on the UNIBUS crashing the machine.

While I agree DELUAs are better, we've never had a problem with our 
DEUNA on an 11/750. I suggest keeping the DEUNA (if it's working), and
spending your money elsewhere.

>Q:	How can I set things up so that folks on the uVAX logon to the
>	UNIX machine and vice-versa? I think I would like to get TCP/IP
>	and all the rlogin/telnet/ftp,etc. stuff for the uVAX. Which is the
>	best (or recommended) options to buy?
>	Will the uVAX-II be able to support all this? Will VMS block
>	ethernet logins?
>A:	Answer, best bet in a mixed environment is to run TCP/IP (of
>	course, I'm a IP bigot).  You can get TCP/IP for the VAX from
>	a couple of commercial sources.  We deal with Wollengong.  The
>	price is around $6000 list for a multiuser VMS uVAX, but you
>	may be able to convince them to give them a discount.  They have
>	a very liberal discount for Universities now.   This will allow
>	full connectivity for login/telnet between the two machines.

There are also TCP processor boards to plug in, but be careful if you
want to attach TCP/IP terminal servers to them. There can be some gotchas.
Wollengong software is known to have gotchas, also.

>	You could get DECNET for the UNIX machine, but this is not such
>	a good solution.

I don't necessarily agree. The Ultrix/DECnet gatewaying capability is
wonderful. Users can (nearly) transparently telnet and ftp through
the Ultrix machine in either direction, without even having an account
on the Ultrix Vax. Also, you don't have to have TCP on each VMS machine;
users can log in to the Ultrix machine and login directly to any DECnet 
host. I agree some TCP/IP capabililty on the VMS machines is required,
though.
-- 

Bill    UUCP:  {husc6,ihnp4,cmcl2,mit-eddie}!harvard!cfa!wyatt
Wyatt   ARPA:  wyatt@cfa.harvard.edu
         (or)  wyatt%cfa@harvard.harvard.edu
      BITNET:  wyatt@cfa2
        SPAN:  cfairt::wyatt 

ron@topaz.rutgers.edu (Ron Natalie) (03/31/88)

One of the reasons I didn't recommend DECNET is that the requestor
didn't indicate that he was running ULTRIX, nor did he indicate
that the UNIX machine was a VAX at all.  While you can have DECNET
for SUNs, it isn't very nice.  Second, why bother to mix protocols
at all with a gateway, reasonable non-proprietary protocols like
TCP/IP exist for VMS, something that DEC seems to be continually
unaware of.

Second, the smart Ethernet cards are generally not a very satisfactory
solution except for terminal traffic.  The new 3.0 release on Wollongong
seems to work extermely well with our terminal servers, even the BRIDGE
ones which have yet to get the protocols straight.

The DEUNA/DCLO problem occurs when you put the DEUNA in the small
UNIBUS backplane in the CPU cabinet.  Having a expansion box for
the DEUNA is likely to solve the problem.

-Ron

shan@mcf.UUCP (Sharan Kalwani) (04/01/88)

>>	You could get DECNET for the UNIX machine, but this is not such
>>	a good solution.

Really ? I thought one needed to buy Ultrix from DEC in order to get
DECNET on UNIX. We run 4.3bsd+nfs (mt.xinu) and would like to stick to
them. In that case, who are the vendors who will sell me DECNET?


-- 
sharan "alf" kalwani		     internet:  shan%mcf.uucp@umix.cc.umich.edu
usenet:     ...!{ihnp4!mibte, uunet!umix, pur-ee!iuvax, ucbvax!mtxinu}!mcf!shan
dec enet: decwrl::"umix.cc.umich.edu!mcf!shan" bitnet: mcf!shan@psuvax1.psu.edu
% setenv DISCLAIMER "`cat /your/favorite/disclaimer.h`"