Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!PSUORADM.CC.PDX.EDU!a2mp
From: a2mp@PSUORADM.CC.PDX.EDU (Michael Perrone)
Newsgroups: comp.protocols.appletalk
Subject: Administrative overhead of routing multiple protocols through cisco
Message-ID: <9105171831.AA22334@psuoradm.cc.pdx.edu>
Date: 17 May 91 18:31:07 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32


We are now creating a campus wide network at psu with a central router.
Lots of users would like to see multiple protocol routing, but our
Director is concerned with maintenance and support overhead, as well
as the possibility that the network might be less stable. 

I would like to hear from network administrators who route multiple
protocols (we have a cisco router): 

How much extra support and administration does multiple protocol routing
add? 

Does multiple protocol routing make either the net or router less
stable?

How much extra effort is needed to add just ipx bridging and
appletalk (phase 1 or 2) routing?

------------------On the FLIP SIDE-------------------------

Have any of you decided to limit routing to tcp/ip, and if so, why?

If you have limited routing to tcp/ip, are you using atalkad (ip tunneling)
to route appletalk? How much work is that?


Thanks for responses.

-----------------------------------------------------------
Michael Perrone                      PSU Computing Services
a2mp@psuoradm.cc.pdx.edu             (503) 725-3112
bitnet : a2mp@psuorvm.bitnet