[c-nsp] ME3600 BGP Route-Maps and IPv6 (WAS: Re: preference on bgp route advertisements)
Mark Tinka
mtinka at globaltransit.net
Thu Mar 8 09:06:33 EST 2012
On Thursday, March 08, 2012 12:30:16 PM Reuben Farrelly
wrote:
> 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 :)
Ah, now I understand.
I believe this would be expected behaviour, given that
you're applying the policy on an IPv6 session as well.
I can't confirm this as we run a different setup, but it
would theoretically make sense to be expected.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20120308/84a1c03d/attachment.sig>
More information about the cisco-nsp
mailing list