Hi, On Thu, Mar 08, 2012 at 09:08:11AM +0000, Phil Mayers wrote: > The occasion I ran into it was an attempt at laziness, to use the same > route-map for "redis connected" and "redis static". I wanted to use a > tag on static routes to signal "no-export" and wrote a route-map like this: > > route-map redis2bgp permit 10 > match tag 100 > set community no-export > route-map redis2bgp ... > > Of course, this fails for "connected" routes; because "match tag" is not > a "supported command" for connected, it's just ignored, meaning the 1st > statement matches for all connected routes.
Now *that* brings me to another favourite soapbox rant :-) - why oh why
is "tag" not supported on connected routes?
(Along with "why is there no way to make HSRP-slave interfaces really
passive, not showing up in the local FIB and in 'redist connected'
etc?"... none of this is "my network will stop working if I can't have
that!" critical, but it would save oh so many workarounds).
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgp1o79OLT4Xh.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
