[j-nsp] improving global unicast convergence (with or without BGP-PIC)

[Olivier Benghozi]

Hi,

> On 22 apr. 2017 at 22:47, Dragan Jovicic <draganj84 at gmail.com> wrote :
> 
> From documentation:
>> On platforms containing only MPCs chained composite next hops are enabled by default. With Junos OS Release 13.3, the support for chained composite next hops is enhanced to automatically identify the underlying platform capability on composite next hops at startup time, without relying on user configuration, and to decide the next hop type (composite or indirect) to embed in the Layer 3 VPN label.

In fact the most relevant part of this doc is what immediately follows that:
"This enhances the support for back-to-back PE-PE connections in Layer 3 VPN with composite next hops, and eliminates the need for the pe-pe-connection statement."

Actually, only "pe-pe-connection" became useless, if you enable composite for l3vpn.


> There's quite of few options to configure, and a few scenarios which might affect how are they created, such as if your PE is also a P router, and if you have degenerated PE-PE connection to name two,
> +            l3vpn pe-pe-connection;

Since 13.3, only l3vpn.