From: Omer Ansari (omer@xxxxxxxxxx)
Date: Fri Aug 23 2002 - 22:42:59 GMT-3
Mike,
but the igrp or rip process is a recipient, the donor is ospf/eigrp.
thus
OSPF[tagged]route ----->{route-map TagBoy}----> IGRP
I think you should be able to block tagged routes. the redistribute engine
from its usage seems to be modular and not part of a routing protocol, as
it exhibits the same options/behavior under each RP configuration.
I'll verify in lab sometime and confirm. chwarren confirmed that tagged
OSPF routes can be denied while redist'ing into RIP.
> -----Original Message-----
> From: Michael Snyder [mailto:msnyder@ldd.net]
> Sent: Friday, August 23, 2002 1:22 AM
> To: 'Omer Ansari'
> Cc: ccielab@groupstudy.com
> Subject: RE: denying tagged routes when redist'ing into RIP/IGRP
>
>
> No. My experience is that route maps and tags do not work into rip or
> igrp.
>
> An sometimes it doesn't work as expected from rip or igrp.
>
> If it is just a few routes, a distribute list might be a better general
> choice from a rip or igrp route donor.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Omer Ansari
> Sent: Thursday, August 22, 2002 6:14 PM
> To: ccielab@groupstudy.com
> Subject: denying tagged routes when redist'ing into RIP/IGRP
>
> All,
>
> knowing the IGRP/RIP engine doesnt know how to handle tags, is this
> allowed or do have to stick with ACLs?
>
> router igrp 100 (or rip)
> redistribute ospf 10 route-map TagBoy metric ......
> !
> route-map TagBoy deny 10
> match tag 90
> route-map TagBoy permit 20
> !
>
> regards,
> Omer
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:36 GMT-3