Hi Alex,
Yup, that's true, but why then would we need the prefix list in the same
config if the route-map is good enough to do everything else. I've seen this
config on some SP routers, but fail to understand the logic of having both
inbound.
neighbor yadayada route-map CISCO in
neighbor yadayada prefix-list CISCO in
Does anyone know?
Cheers.
On Tue, Nov 2, 2010 at 6:52 PM, Alexei Monastyrnyi <alexeim73_at_gmail.com>wrote:
> Hi.
>
> With route-map you can match things other than prefixes, and also
> manipulate attributes. Also with route-maps you can impose more
> sophisticated logic upon your peers.
>
> HTH
> A.
>
> On 11/2/2010 9:45 AM, emir d souza wrote:
>
> Hi Guys,
>
> I'm a bit confused, from what I understand is that for filtering traffic,
> BGP will look at filtering in this order:-
>
> Inbound: route-map > filter-list > prefix-list
> Outbound: prefix-list > filter-list > route-map
>
> Question is: For example. why bother having both route-map and prefix-list
> filtering on the inbound when you can just use a single route-map to filter
> in traffic. I've seen this being done on some SP routers, and I'm wondering
> if there good explanation as to why they are doing this.
>
> Route-map will filter out community tags and prefix-list will filter out
> specific routes, can't we do both on route-maps alone??
>
> Cheers.
>
> Emir
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at: http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Wed Nov 03 2010 - 10:54:20 ART
This archive was generated by hypermail 2.2.0 : Sun Dec 05 2010 - 22:14:55 ART