Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!bu-it!kwe
From: kwe@bu-it.bu.edu (Kent England)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Serious Routing Problems
Message-ID: <61620@bu.edu.bu.edu>
Date: 30 Jul 90 18:50:50 GMT
References: <9007300339.aa00505@SPARK.BRL.MIL>
Sender: news@bu.edu.bu.edu
Reply-To: kwe@bu-it.bu.edu (Kent England)
Organization: Boston University
Lines: 23

In article <9007300339.aa00505@SPARK.BRL.MIL>, phil@BRL.MIL (Phil
Dykstra) writes:
> ... Given the number of hops, I have to wonder how well the Cisco
> routing protocol is doing, but then I don't know the net topology.

	Not too well in my opinion.  Chuck Hedrick from Rutgers posted some
very informative material in comp.dcom.sys.cisco about setting timers in IGRP
to speed convergence.  The timers are now settable in cisco configs.

	When lines flap for whatever reason, routes in IGRP go away and get
held down for many minutes, breaking TCP connections.  While caution must
be used, in many cases, shortening up the IGRP reaction times will prevent
line flaps from turning into big route lossage.  It all depends on how you have
your net set up.

	In my opinion, this will become a thing of the past with link
state protocols.  I'm anxious to see results from the OSPF early deployments
in NASA and SURAnet.

	Milo, Dave;  How does OPSF do when you have routes flapping?  Instant
convergence?

	--Kent