Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


Configure virtual private LAN service (VPLS) flooding of unknown unicast, broadcast, and multicast traffic using point-to-multipoint LSPs. Also configure point-to-multipoint LSPs for MBGP MVPNs.

Starting in Junos OS Release 21.1R1, following provider tunnel types are supported on QFX10002, QFX10008, and QFX10016 Switches:

  • Ingress Replication

A point-to-multipoint (P2MP) is a MPLS LSP with a single source and multiple destinations. By taking advantage of MPLS packet replication capability of the network, point-to-multipoint LSPs avoid unnecessary packet replication at the ingress router. Packet replication takes place only when packets are forwarded to two or more different destinations requiring different network paths.

Following are some of the properties of point-to-multipoint LSPs:

  • A P2MP LSP enables use of MPLS for point-to-multipoint data distribution. This functionality is similar to that provided by the IP multicast.
  • The branch LSPs can be added and removed without disruption traffic.
  • A node can be configured as both a transit and egress router for different LPSs of the same point-to-multipoint LSP.
  • LSPs can be configured statically or dynamic or as a combination of both static and dynamic LSPs.

P2MP LSPs are used to carry the IP unicast and multicast traffic.

Following tunnel types are not supported on QFX10002, QFX10008, and QFX10016 Switches:

  • PIM-SSM tree
  • PIM-SM tree
  • PIM-Bidir tree


external-controller pccd

(Optional) Specifies that point-to-multipoint LSP and (S,G) for MVPN can be provided by an external controller.

This option enables an external controller to dynamically configure (S,G) and point-to-multipoint LSP for MVPN. This is for only selective types. When not configured for a particular MVPN routing-instance, the external controller is not allowed to configure (S,G) and map point-to-multipoint LSP to that (S,G).

The remaining statements are explained separately.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 8.3.The selective statement and substatements added in Junos OS Release 8.5.

The ingress-replication statement and substatements added in Junos OS Release 10.4.

In Junos OS Release 17.3R1, the mdt hierarchy was moved from provider-tunnel to the provider-tunnel family inet and provider-tunnel family inet6 hierarchies as part of an upgrade to add IPv6 support for default MDT in Rosen 7, and data MDT for Rosen 6 and Rosen 7. The provider-tunnel mdt hierarchy is now hidden for backward compatibility with existing scripts.

The inter-as statement and its substatements were added in Junos OS Release 19.1R1 to support next generation MVPN inter-AS option B.

external-controller option introduced in Junos OS Release 19.4R1 on all platforms.