Thanks for the info. That clears that up.
Jeff On Sep 16, 2011, at 10:26 , Kevin Epperson wrote: > Typically the route-map is used to do attribute manipulation (i.e. match > these prefixes and change this attribute) and the prefix-list applied to a > neighbor is used for permit/deny of prefixes. You could however embed the > prefix-list in the route-map -- completely up to you. > > Another reason to keep the prefix-list direct on the neighbor is that you > might reuse a route-map across multiple neighbors but the prefix-list might > be common to only one neighbor. > > It should work either way though :) Let me know if you have some specific > examples and I can take a looksie at it. > > -Kevin > > On Fri, 16 Sep 2011, Jeffrey G. Fitzwater wrote: > >> I have been using the ( neighbor xxx.xxx.xxx.xxx prefix-lit myPrefix out ) >> to control what prefixes we announce to our ISPs. >> >> I now have a need to do a little more prefix filter control using ( neighbor >> xxx.xxx.xxx.xxx route-map myRouteMap out ) . >> >> >> Can I just do all the PREFIX filtering using the ( neighbor xxx.xxx.xxx.xxx >> route-map myRouteMap out ) and remove the ( neighbor xxx.xxx.xxx.xxx >> prefix-lit myPrefix out )? >> >> >> Is there any reason to keep the ( neighbor xxx.xxx.xxx.xxx prefix-lit >> myPrefix out ) bgp command or is it just redundant with the route-map >> command? >> >> >> I just need to do more control on what PREFIXES get advertised to our peers. >> >> >> >> >> >> Thanks for any help. >> >> >> >> Jeff Fitzwater >> OIT Network Systems >> Princeton University >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
