Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!BU-IT.BU.EDU!kwe
From: kwe@BU-IT.BU.EDU
Newsgroups: comp.sys.proteon
Subject: Re: P4200 problems.
Message-ID: <8906022150.AA25429@buit13.bu.edu>
Date: 2 Jun 89 21:50:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 31


	The problem is most likely between the unm p4200 and
the westnet cisco.
	The unm p4200 is hitting the westnet cisco with 500
routes (500 + 20 from behind unm-p4200) most of which are
poison reverse (metric 16) routes.
	The cisco could be losing some of the 20 routes from
behind unm-p4200 in the mass of poison-routes.

	The p4200 should not be losing updates from the westnet
cisco.

	You should have a look at the RIP exchanges going on
on UNMnet.  You could use the PPRG Sun GW and tcpdump.

	Then you should have a look at the debugging console
data on the westnet-cisco and watch your 20 local nets behind
unm-p4200 come and go.  Do the same on the unm-p4200 and
see if any interesting routes are coming and going.

	Also, the unm-p4200 and the PPRG-Sun-GW could be
sync'ed on RIP updates leading to ~1000 routes hitting
the cisco at the same time.  Tough on the old bird.  Likewise
the Sun and cisco could be pounding the p4200.  See what
tcpdump says.  You may have to turn off routing on the Sun-GW
to make sure that tcpdump gets enough cpu and all the packets
it can.

	Good luck.

	Kent England, Boston University