On Saturday, March 03, 2012 06:55:14 AM [email protected] wrote: > I currently have prefix list filtering in place on my > core routers and I advertise a default route to my dsl > routers. My question is, what is the best practice for > advertising bgp routes in the core? I would like to > redistribute connected and static in bgp instead of > adding network statements under the bgp process. Just > trying to get some feedback on this before I start > changing my core network.
For static routes, assigning a tag to the routes and referencing that in a route-map which is attached to a BGP policy will get you what you want. The tag is useful to ensure you don't end up redistributing more routes into BGP than you should. For Connected routes, well, to ensure you don't redistribute interface routes that shouldn't be in BGP, you'd need to add another match condition such as a prefix list. You need to evaluate whether the efforts of both options above are more or less efficient than the 'network' statement option, in your particular environment. Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
