🚀 go-pugleaf

In article <lafo7rINNqp1@skat.usc.edu> tli@skat.usc.edu (Tony Li) writes:
>In article <184ee4INNimp@moe.ksu.ksu.edu> bav@hobbes.ksu.ksu.edu (Brick Verser) writes:
>    We've got an AGS+ running Version 8.2(7) which seems to pause every 30 
>    seconds.  Seems likely this is RIP updates, but it seems unlikely that 
>    the router should do absolutely nothing else for that period.  Is there 
>    a simple configuration change that we've overlooked which will make this 
>    all better?
>    
>Responding to Ping packets is a relatively low priority process within
>the router and is not really a good measure of what the router is
>doing.  You should try pinging through the router to see what it is
>really doing.

That is, in fact, what I was doing.  NO packets go through the router, as 
best I can tell, when this is happening.

I've partially solved the problem by turning off the advertising of MIDnet
routes on campus, which reduces the number of nets being RIPped from 300
to about 30.  So now the router pauses only 80ms every 30 seconds.  Much
better, but still bothersome.  I would prefer to fix the Ciscos' scheduler.
Guess a phone call to them is in order.

--Brick