Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!sun-barr!rutgers!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.dcom.lans
Subject: Novell: fear and loathing...
Keywords: novell ethernet
Message-ID: <15581@cbmvax.commodore.com>
Date: 3 Nov 90 18:40:49 GMT
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 44

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.

I guess the real question is how the Novell protocols rate as good network
neighbors and what kind of loading Novell clients represent to the network?

I know that the Ethernet can be universal, but I'm interested in the pragmatic
issues of maintaining adequate service levels in a mixed environment where
administrative control might no longer completely in our hands.

How should one approach the intermingling of the two networks?  I see several
obvious alternatives:

1) Maintain two completely separate networks, with some kind of mail gateway
   being the only common ground.

2) Use our existing bridge/router (Wellfleet) to provide traffic isolation
   between the networks, but allow various systems on either side to talk to
   each other.

3) Try to isolate the Novell traffic via the router, but permit connection of
   Novell nodes in areas served only by our backbones or where the business
   reporting areas overlap.
   
4) Allow indiscriminate attachment of Novell and other nodes, and hope that
   departmental clustering and creative bridging will minimize handle loading.

Can anyone suggest which approaches seem to work well, and which are an
invitation to disaster?

Finally, can anyone suggest some references which deal with Novell protocols
and services at a reasonably sophisticated level?  So far, I haven't seen
much beyond babytalk or Novell-centric administrator manuals.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)