From: CCIE Study Group (bs.ccie@xxxxxxxx)
Date: Sat Mar 04 2000 - 22:54:18 GMT-3
Because EIGRP acts similar to a LINK state protocol, updates are only sent
periodically, I think every 2hrs a full update is sent(I am not sure), and
also when an event occurs. The route was already in the database and just
adding a list will not have it removed. When David caused an event, this
created route updates to be sent to R4. The route would then be filtered
from R4. RTMP updates every 10 seconds so the route would be filtered that
much sooner with out having to delete the route or bounce the interface.
Any time you want to filter routes think about the routing protocol you are
using and how it behaves in respect to when route updates are sent.
----- Original Message -----
From: David Russell <drussell@tns-inc.com>
To: GRIZZUTI Javier <jgrizzut@softnet.com.ar>; <ccielab@groupstudy.com>
Sent: Saturday, March 04, 2000 5:12 PM
Subject: Re: APPLETALK Access list
> I tried the same thing and found that I had to do two things to make the
> access-list work:
>
> 1. Bounce the interface that the cable range was on (shut/no shut)
>
> 2. Clear the routing entry on the router with the access-list.
>
> After that, the EIGRP database was cleared and the routing table was
> cleared. My thought was that once the route makes it into EIGRP it will
not
> be cleared out just by installing a filter to block future updates.
>
> RTMP does not seem to have this problem.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:03 GMT-3