calling it a night after spending the weekend in a post mortem of an ASET practice lab taken a week ago.
the topic of filtering routes introduced into a domain via redistribution, and which are advertised back to the originating router through a different protocol. You all know the problem - the re-advertised routes come into the originating router via a protocol with a lower AD, thus wreaking havoc on routing tables, and causing flapping routes. Well, the ASET book answer for this particular problem on this particular router was to filter the particular routes using a distribute-list. This is all well and good, except that the protocol in question is OSPF, and as we all know from reading the documentation, distribute-list does not apply to IS-IS and OSPF. Well, except that distribute-list in appears to be quite effective in blocking unwanted routes from being received by an OSPF router distribute-list out appears to do what it is supposed to. checking Parkhurst. re-reading the documentation. If I were to hazard a guess, I would guess that the CCO documentation writers screwed up. It is distribute-list out that does not work in OSPF. ( haven't checked IS-IS yet ) Distribute-list in does indeed prevent ospf routes advertised by another ospf speaker from being installed in the routing table. the routes still appear in the ospf database, as expected. -- TANSTAAFL "there ain't no such thing as a free lunch" Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=63144&t=63144 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
