Is there v4-mapped-v6 labeled route in inet6.3? If not, first step would be to create that using ipv6-tunneling knob. of course there has to be a LSP route to 1.2.3.4 in inet.3 for 1.2.3.4 for it happen. Next step, you could try is to add a "next-table" nexthop route.
set routing-options rib inet6.0 static route ::/0 next-table inet6.3. See if that works. The problem is static route will expect ::ffff:<blah> NH route in inet6.0 which is not possible unless you have traffic-engineering-bgp-igp-both-ribs knob configured. If not then you will have to point the static route to inet6.3 table. Ofcourse, I am saying all this theoretically, you can test to see if that works. Thanks, On Mon, Sep 24, 2018 at 10:10 AM serge vautour <[email protected]> wrote: > Hello, > > Does anyone know if it's possible to create a 6PE static default route? It > tried creating one like this: > > set routing-options rib inet6.0 static route ::/0 next-hop ::ffff:1.2.3.4 > set routing-options rib inet6.0 static route ::/0 resolve > > I have an ISIS-SR label for 1.2.3.4 in inet3.0. When I look at ::/0 it > shows a single label push with the same label as 1.2.3.4. However, there is > no BGP 6PE label 2 service label. Is there a way to tell the box to add > this? > > Thanks, > Serge > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
