X-Envelope-to: NOVELL@SUVM.BITNET
X-VMS-To: IN%"NOVELL@SUVM.BITNET"
X-VMS-Cc: JRD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.novell
Date:         Mon, 4 Jan 1993 22:44:22 -0600
Reply-To:     Novell LAN Interest Group <NOVELL@SUVM.BITNET>
From:         Joe Doupnik <JRD@USU.BITNET>
Subject:      Re: Netware 3.11/DEC MicroVAX interaction

>We are talking to one of our Health Insurance Vendors about a system that they
>have to allow us to do some cost analysis of our claims data. It is written
>for Oracle 6.0, which they have running on a DEC MicroVAX back-end.
>
>They are telling us they prefer to set this up as a stand-alone system,
>connected with Ethernet cable.  I already have a 70-node Netware 3.11 system
>installed here using Thin Ethernet, which everyone in the department uses for
>everything from word processing to e-mail.
>
>My question is - will the two systems pass data over the same wire without
>conflicts, so that I don't have to buy two computers for everyone who needs to
>use this new system? I have a mixture of 3Com and Cabletron NIC's on the net
>now.
>
>One of those great questions for you Systems Integrators out there!
>
>I would appreciate any information anyone can give me on making this work, if
>possible.  I can get more information from their techies if it will help. (Not
>being a Vaxen myself, I don't even know the model numbers of anything in this
>system)
>
>Thanks!
>
>Scott Smith
>Michigan State University
>Human Resource Information Systems
>PER12@MSU.EDU        PER12@MSU.BITNET
------------
Scott,
        As a networking person you left a gaping hole in your message, which
is: what protocol is required on the VAX?
        Here are some Answers In Advance, to coin a phrase.
        Supports TCP/IP Telnet. You are home free. The subject of simultaneous
NetWare IPX and Telnet TCP/IP packets is extremely familiar to readers of the
list and one which a great many sites do every day. There are several
approaches which I will only indicate here. Run a Packet Driver and build a
special IPX to run over it in parallel with the Telnet task. Use ODI drivers
and run either native mode Telnet programs over it (Novell's LWP/DOS, MS-DOS
Kermit) or install shim ODIPKT and run Ethernet Packet Driver apps over it.
        Supports only DECnet and/or LAT. Oh boy. Well that means running
DECnet/DOS (Pathworks, whatever today's name) on each client and that usually
means running the Lan Manager components over NDIS. Well, this can be done
too, but at a cost in memory which is shocking. Approach A is to use the
NDIS components from DEC down to the board, put shim DIS_PKT9 on the top
to form an Ethernet Packet Driver interface and go with PD style IPX and
Telnets. Approach B is use ODI drivers as above, and Novell's shim ODINSUP
to form an NDIS interface on the top of ODI. MS-DOS Kermit will talk over
DECnet to use both LAT and the CTERM pure DECnet parts of things.
        LAT is something to avoid if you can. It is not that fast, it breaks
very easily, and it can't be routed. Pure DECnet, being a wide area protocol,
is slower but it works. Straight TCP/IP to the wire is the fastest way, period.
        In terms of frames on the wire, there is no problem at all mixing
them. After all, that's what backbones are expected to carry. If the VAX
does not currently have TCP/IP support then run, do not walk, to your nearest
TGV distributor (eg TGV) and purchase a copy of Multinet; recommended.
        End of free advice.
        Joe D.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU