Re: ACL vs Prefix-list

 On Thu, 8 Sep 2011 11:26:35 +0530, Amit Kumar Lohumi wrote:
> While performing redistribution from RIP to OSPF, i was trying to
> set-up the
> route-type for certain routes to E1 using a route-map.
>
>
> First, i used an access-list inside the route-map to identify those
> routes.
> Although the ACL was filtering routes, the 'set' action was not being
> performed by the route-map.
>
>
> The problem was resolved after replacing the ACL with a prefix-list.
>
> Is there a ready explanation for this observation ... ??
>
> *ACL*
>
> ip access-list standard summary
> permit 30.0.0.0 0.252.255.255
> permit 31.0.0.0 0.252.255.255
> *Prefix-List*
>
> ip prefix-list summary seq 5 permit 30.0.0.0/8 ge 14
> ip prefix-list summary seq 10 permit 31.0.0.0/8 ge 14
> *Route-map with ACL*
>
> route-map assign-metrics permit 10
> match ip address summary
> set metric-type type-1
> !
> route-map assign-metrics permit 20
> *Route-map with Prefix-list*
>
> route-map assign-metrics permit 10
> match ip address prefix-list summary
> set metric-type type-1
> !
> route-map assign-metrics permit 20
>

 Hi,

 You are using INEs topology right? Your ACL looks a bit off. You are
 using a wildcard of 0.252.255.255 which will match 30.0.0.0, 30.4.0.0,
 30.8.0.0 and so on. I think the WC you were after is 0.3.255.255. If you
 also want to match the network mask you need to use an extended ACL.

 /Daniel

Blogs and organic groups at http://www.ccie.net
Received on Thu Sep 08 2011 - 09:35:10 ART