[j-nsp] 6PE without family inet6 labeled-unicast
Andrey Kostin
ankost at podolsk.ru
Sun Jul 22 15:28:58 EDT 2018
Hi Pedro,
Thanks for your comment. I agree with you that penultimate LSP forwards
traffic based on received label without IPv6 lookup. In my scenario,
default PHP is used and all routers have family inet6 configured, so it
just works.
Pedro Marques Antunes via juniper-nsp писал 21.07.2018 05:36:
> The IPv6 explicit null label works as an overlay for the IPv6 traffic
> carried over the core.
>
> In a PHP scenario, the ultimate LSR will still forward based on the
> received MPLS transport label. Therefore I do not think it will
> require
> an IPv6 routing table. However it still needs to forward IPv6
> packets.
> Not a problem with recent routers. But this might have been a problem
> in
> the days when you would have devices without any IPv6 capabilities.
> On
> Junos boxes though, `family inet6` is still required on the egress
> interface.
>
> In a UHP scenario, the penultimate LSR is expected to forward a
> packet
> with the IPv4 explicit null label (3). But this cannot be used with
> an
> IPv6 packet. The overlay is mandatory in such a scenario.
>
> On Friday, 20 July 2018 at 21:40:26 +0100, Dan Peachey wrote:
>> Hi,
>>
>>Presumably the penultimate LSR has the IPv6 iBGP routes? i.e. it
>> knows how
>>to IPv6 route to the destination. The last LSR->LER hop should just
>> be IPv6
>>routed in that case.
>>
>>I've noticed this behaviour before whilst playing with 6PE on lab
>> devices.
>>It would of course break if you were running IPv4 core only.
>>
>>Cheers,
>>
>>Dan
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list