Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!hellgate.utah.edu!basset.utah.edu!haas
From: haas%basset.utah.edu@cs.utah.edu (Walt Haas)
Newsgroups: comp.dcom.lans
Subject: Re: Novell: fear and loathing...
Keywords: novell ethernet
Message-ID: <1990Nov3.185439.6425@hellgate.utah.edu>
Date: 4 Nov 90 01:54:39 GMT
References: <15581@cbmvax.commodore.com>
Organization: University of Utah CS Dept
Lines: 19

In article <15581@cbmvax.commodore.com> grr@cbmvax.commodore.com (George Robbins) writes:
>We've traditionally run an Engineering LAN based on TCP/IP and DECnet over
>a combination of thick and thin Ethernet and recently a T1 link.  Loading
>is a mixture of LAT and Telnet "terminal" connections, with X-window server/
>client stuff starting to take off and an ever growing NFS load.
>
>Now our MIS department has recently obtained approval of a plan to implement
>"corporate" networking and E-mail services based on Novell software, and
>twisted pair ethernet.

No big deal, we run Novell along with everything else on our campus network.
I recommend that you require all Novell devices to have the ECONFIG option
to give real Blue Book framing, otherwise you get a botched version of
802.3 framing.  The routing protocol is pretty much straight RIP, which
works out all right if there is only one path between two points (as our
network is configured) but is likely to become stupid in the face of multiple
paths between two machines.

-- Walt Haas    haas@ski.utah.edu