Hi James > James Jun > Sent: 16 May 2015 16:20 > > The problem however is that I'm using the P's also as route-reflectors for > distributing BGP throughout the network. So, I need the RR's to make > correct BGP best-path decisions, but they can't do that on 6PE routes without > having inet6.3 table to reference the ipv4-mapped-in-v6 next-hops against. > I'm sorry I misunderstood the problem so the problem isn't that the P's are trying to do IPv6 lookup instead of label-switch the packets between PEs but the problem is that RRs are not advertising the IPv6 prefixes because they can't select the best paths so the IPv6 prefixes are not being exchanged between the PEs right?
To resolve the NHs you can do: set routing-options rib-groups 0-to-6 import-rib inet.0 set routing-options rib-groups 0-to-6 import-rib inet6.0 set routing-options rib-groups 0-to-6 import-policy loopbacks set protocols isis/ospf rib-group inet 0-to-6 This should create the ipv4-mapped-in-v6 (ffff::ipv4) addresses in inet6 And then you tell BGP to resolve the NHs in inet.6: set routing-options resolution rib bgp.inet6.0 resolution-ribs inet6.0 adam --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com --------------------------------------------------------------------------------------- _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
