Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?



  • Support to change the default re-merge behavior on the P2MP LSP (PTX10008)—You can change the default re-merge behavior on a RSVP point-to-multipoint (P2MP) label-switched path (LSP). The term re-merge refers to the case of an ingress or transit node (re-merge node) that creates a re-merge branch intersecting the P2MP LSP at another node in the network. This may occur due to events such as an error in path calculation, an error in manual configuration, or network topology changes during the establishment of the P2MP LSP.

    [See Re-merge Behavior on Point-to-Multipoint LSP Overview.]

  • Install prefixes for RSVP-TE LSPs using PCEP (PTX SeriesQFX Series)–Starting in Junos OS Evolved Release 21.1R1, you can configure different prefixes for Path Computation Element (PCE)-initiated and PCE-delegated RSVP-TE LSPs using the Path Computation Element Protocol (PCEP). Prior to this feature, for PCE-initiated LSPs, you could install prefixes as routes through templates and map the templates to the LSPs. For Path Computation Client (PCC)-configured LSPs, although you could install prefixes on the device, this information was not reported to the PCE.

    With this feature, you can install prefixes for external RSVP-TE LSPs through PCEP communication, and enable the PCC to report installed prefixes for all local RSVP-TE LSPs to the PCE . This support provides you better traffic engineering capabilities and allows Junos OS to interoperate with other vendor's PCC or PCE.

    [See Support of the Path Computation Element Protocol for RSVP-TE Overview.]