<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Sep 5, 2012, at 3:33 AM, Youssef Bengelloun-Zahr wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="jive-rendered-content"><p>Hello community,</p><p>I have been struggling with a nice IPv6 BGP problem.</p><p>I
am using my route reflectors (CER-RT, v5.3.0b) to generate the BGP
prefixes we will be announcing to our upstreams via our edge routers
(MLXe-4, v5.3.0b).</p><p>The
configuration works just fine for IPv4, but for some reason, my BGP
communities are not propagated when using the same model under IPv6 AFI.</p><p></p></div></blockquote><div>I had the same problem.</div><br><blockquote type="cite"><div class="jive-rendered-content"><p>....</p><div style="min-height: 8pt; height: 8pt; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0px; "> <br class="webkit-block-placeholder"></div><p> address-family ipv6 unicast</p><p> redistribute static route-map FROM-STATIC-V6-TO-BGP</p><p><strong> neighbor RR-PEER-V6 send-community</strong></p><p>
neighbor 2a00:bf40::XYZ activate </p><p> neighbor 2a00:bf40::XYZ activate </p><p> exit-address-family</p><div><br></div></div></blockquote><div><br></div><div><br></div><div>Try adding "neighbor RR-PEER-V6 activate". Alternatively, I think if you add "send-community [both]" to each individual peer, it fixes it too. My recollection is a little fuzzy, but one of these two should work. Let me know if not.</div><div><br></div><div>It struck me as strange that the peer was already "up", so it would have never occurred to me that the peer-group itself needed an activate.</div><div><br></div><div><br></div><div><br></div></div></body></html>