Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


leaf-tunnel-limit-inet (MVPN Selective Tunnels)


Hierarchy Level


Configure the maximum number of selective leaf tunnels for IPv4 control-plane routes.

The purpose of the leaf-tunnel-limit-inet statement is to supplement the multicast forwarding-cache limit when the MVPN rpt-spt mode is configured and when traffic is flowing through selective service provider multicast service inteface (S-PMSI) tunnels and is forwarded by way of the (*,G) entry, even though the forwarding cache limit has already blocked the forwarding entries from being created.

The leaf-tunnel-limit-inet statement limits the number of Type-4 leaf autodiscovery (AD) route messages that can be originated by receiver provider edge (PE) routers in response to receiving from the sender PE router S-PMSI AD routes with the leaf-information-required flag set. Thus, this statement limits the number of leaf nodes that are created when a selective tunnel is formed.

You can configure the statement only when the MVPN mode is rpt-spt.

This statement is independent of the cmcast-joins-limit-inet statement and of the forwarding-cache threshold statement.

Setting the leaf-tunnel-limit-inet statement or reducing the value of the limit does not alter or delete the already existing and installed routes. If needed, you can run the clear pim join command to force the limit to take effect. Those routes that cannot be processed because of the limit are added to a queue, and this queue is processed when the limit is removed or increased and when existing routes are deleted.





Maximum number of selective leaf tunnels for IPv4.

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 13.3.