On Tuesday, November 29, 2011 12:41:08 AM Keegan Holley wrote: > You can also apply attributes directly to the aggregate. > So you can set origin code, local pref etc. directly on > the route.
Yes, but you can also do that with a regular route-map for your outbound BGP policy toward the route reflectors. Moreover, you can apply attributes directly to 'network' statements too, so the 'aggregate' feature isn't the only one that brings this. > Also, from the non-technical side it's > cleaner to know it's an aggregate as opposed to a static > route doing something else. Well, I hardly find it useful to use the 'aggregate' command as documentation, just because it's originating an aggregate :-). Some other networks might call it something else. But to each his own. > That wasn't centered around aggregates and no. Some of > us don't run gigantic intercontinental ISP's :) So yes > us lowly Tier-II and Tier-III AS's may on occasion learn > our own routes from an external connection. Hmmh, risky - certainly something I wouldn't advise even for small ISP's. > > Actually I was. 6509/Nexus vs. EX8200, Cisco ME vs. > > EX4200, ASR vs. M/MX > > and CRS vs. T/TX are all different conversations. I > thought you were alluding to something like that which I > would have agreed with. No, I wasn't alluding to that at all. 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/
