We discovered a unique characteristic of IPv6 MVPN that raised some eyebrows when implementing route reflection for it. Why does IPv6 MVPN resolve to inet.3 when most (all?) other AFI 2 VPN subfamilies seem to resolve to inet6.3?
My solution for reflection was to resolve bgp.mvpn-inet6.0 protocol next hop to inet.0. https://kb.juniper.net/InfoCenter/index?page=content&id=KB28667&actp=search Anyone have insight or intuition on the decision making process for this? Thanks, Jason _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
