Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!SUVM.BITNET!JMWOBUS
From: JMWOBUS@SUVM.BITNET ("John M. Wobus")
Newsgroups: comp.sys.proteon
Subject: P4200 problems.
Message-ID: <8906021509.AA21099@devvax.TN.CORNELL.EDU>
Date: 2 Jun 89 15:08:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22

We've had trouble with our P4200s dropping routes, presumably because they
are discarding incoming RIP information.  Proteon suggested we spend more
money replacing what they just sold us with their newer equipment, which
we have done to some extent.  We have also eliminated all RIP information
about networks other than or own subnets from our network (using static
default routes instead).

Has anyone else had this sort of problem with P4200s?  If so, how did you
solve it?  It has bothered us to no end that we bought into this stuff,
then had to spend additional money buying new versions before we got a
working network (by "working network", I mean a network which would not
spontaneously disconnect telnet users several times a day).

Also, it strikes me that software can be written to do other things
besides drop routes when things get busy--we've never had such a problem
with our non-Proteon routers.  It seems to me that each of our remaining
P4200-10s is a time-bomb ready to start killing routes again when things
get busy, and that our P4200-31s would do the same at some busier level,
given the priorities of the software.

John Wobus
Syracuse University