Yea, I figured I would need to do something along those lines. Our CORE is currently dual stacked and running OSPF for v4 and v6 with prefixes being advertised so that was a little bit more work than desired.
So my fix was leaving everything as is and just changing the next-hop from self to the IPv4 address of the advertising PE under the v6 group which is basically what would be happening anyway if I deleted the groups and added everything to the v4 group. My overall goal was to try to get IPv6 prefixes to use the same LSP's as their IPv4 counterparts with as little trouble as possible. (not adding new protocols or changing existing protocols if possible) Simplest way I found was just changing the next hop. Everything worked as expected when that was done. I just didn't know if there was anything else anyone else was doing of if anyone came across a similar situation. I now know about LDPv6, which will be looked into and I still have some research to do on SPRING. ________________________________ From: juniper-nsp <juniper-nsp-boun...@puck.nether.net> on behalf of Olivier Benghozi <olivier.bengh...@wifirst.fr> Sent: Wednesday, August 29, 2018 2:08 PM To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] LSP's with IPV6 on Juniper For 6PE you have to: - delete the iBGP ipv6 groups - add family ipv6 labeled-unicast explicit-null to the IPv4 iBGP groups - add ipv6-tunneling to protocol mpls. - make sure your IGP is not advertising IPv6 addresses This is the way it's configured, with either RSVP-TE or LDP. > Le 29 août 2018 à 15:10, craig washington <craigwashingto...@hotmail.com> a > écrit : > > When I set this up in the lab (logical systems) and followed the Juniper > documentation for setting up 6PE the IPV6 prefixes didn't resolve to LSP's. > The documentation says to add labeled unicast with explicit null and > tunneling. > I had 2 groups, one for v4 and one for v6. I added the commands to v4 group > and didn't see a change. > I removed it all and tried adding it to v6 group and no change. > The only way I got it to work was with mpls tunneling for v6 and on the > export policy for the v6 group I changed the next hop from self to the v4 > address of the advertising PE. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp juniper-nsp Info Page - puck.nether.net<https://puck.nether.net/mailman/listinfo/juniper-nsp> puck.nether.net To see the collection of prior postings to the list, visit the juniper-nsp Archives.. Using juniper-nsp: To post a message to all the list members, send email to juniper-nsp@puck.nether.net. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
