Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!zaphod.mps.ohio-state.edu!ncar!csn!boulder!daemon
From: ARCHERB@VAX1.UMKC.EDU (Barry Archer)
Newsgroups: comp.dcom.sys.cisco
Subject: campus network configuration
Message-ID: <31735@boulder.Colorado.EDU>
Date: 23 Jan 91 21:18:05 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 30


  We're looking into finally expanding our network throughout the campus.  UMKC
is an urban campus with a number of buildings to cover and ancient, meandering
conduit.

  Once we get off the backbone, we've been looking at using a combination of
ethernet concentrators (such as Chipcom's, which allows an ethernet star
config) and cisco IGS routers.  So the route to a building might look like:

  Backbone -- Big_Router -- ethernet_concentrator		! building A 
			      |
			     IGS -- ethernet_concentrator	! building B
					|
					IGS -- ether_concentrator ! building C

  The links between concentrators & routers would be ethernet over fiber, with
the max distance between the two less than 1km.  The concnetrators would give 
us a wiring hub within each building.

  Does this appear reasonable?  How deep can I go with the routers?  I'd like 
to keep any one host from having more than 4 hops before getting off campus,
since it takes another 4 hops to get to the NFSnet.  Is there a good rule of
thumb?

  Any comments welcomed ( I think? :-) ).

Barry Archer, UMKC NOC
archerb@gawain.umkc.edu
archerb@vax1.umkc.edu
archerb@umkcvax1.bitnet