No - as opposed to having no route-map matching IPv6 at all.
So, if I have a route-map that (after my correction) actually matches an
IPv6 route at the top of the route-map sequence and sets the community
value of that IPv6 matched route, then it works as expected.
If I have a route-map that parses IPv6 routes, but does not match any
IPv6 routes (no match ipv6 ... defined anywhere in any of the route-map
sequence entries) then it matches on the first _IPv4_ route map entry
and sets the community of that IPv6 route to the IPv4 match instead.
That's the bug :)
Reuben
On 8/03/2012 2:48 PM, Mark Tinka wrote:
On Wednesday, March 07, 2012 06:01:41 AM Reuben Farrelly
wrote:
Correction. I made a mistake in my testing there...
If I have:
ipv6 prefix-list PERMIT-IPV6-ANY seq 10 permit ::/0 le 64
Then yes the IPv6 specific route-map matches first and
the correct community is set.
You mean as opposed to "... le 48"?
Cheers,
Mark.
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
