Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

resolve-request-holdcount

Syntax

Hierarchy Level

Description

Configure the number of initial multicast packets the kernel holds while resolving a multicast route.

In EVPN fabrics, caching these packets during route resolution can lead to transient flooding on Layer 2 interfaces and cause non-interested receiver devices to install Layer 3 multicast routes in the Routing Engine and Packet Forwarding Engine, consuming hardware resources until the routes time out.

Setting the hold count to 0 prevents the kernel from caching the initial multicast packets during route resolution and prevents unnecessary route installation on systems without interested receivers.

Important: After you configure resolve-request-holdcount, deactivate and then activate PIM to push the updated hold count to the kernel for resolve routes.

Options

count—Number of initial multicast packets the kernel holds while resolving a multicast route. Set count to 0 to disable packet caching during route resolution.

Default

If you do not include the resolve-request-holdcount statement, the kernel caches 12 initial multicast packets while resolving a multicast route.

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 26.2R1.