Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

Example: Configuring the PIM SPT Threshold Policy

Requirements

Before you begin:

• Configure the router interfaces. See the Junos OS Network Interfaces Library for Routing Devices.
• Configure an interior gateway protocol or static routing. See the Junos OS Routing Protocols Library for Routing Devices.
• Configure PIM Sparse Mode on the interfaces. See Enabling PIM Sparse Mode.

Overview

Multicast routing devices running PIM sparse mode can forward the same stream of multicast packets onto the same LAN through an RPT rooted at the RP or through an SPT rooted at the source. In some cases, the last-hop routing device needs to stay on the shared RPT to the RP and not transition to a direct SPT to the source. Receiving the multicast data traffic on SPT is optimal but introduces more state in the network, which might not be desirable in some multicast deployments. Ideally, low-bandwidth multicast streams can be forwarded on the SPT, and high-bandwidth streams can use the SPT. This example shows how to configure such a policy.

• spt-threshold—Enables you to configure an SPT threshold policy on the last-hop routing device to control the transition to a direct SPT. When you include this statement in the main PIM instance, the PE router stays on the RPT for control traffic.
• infinity—Applies an SPT cutover threshold of infinity to a source-group address pair, so that the last-hop routing device never transitions to a direct SPT. For all other source-group address pairs, the last-hop routing device transitions immediately to a direct SPT rooted at the source DR. This statement must reference a properly configured policy to set the SPT cutover threshold for a particular source-group pair to infinity. The use of values other than infinity for the SPT threshold is not supported. You can configure more than one policy.
• policy-statement—Configures the policy. The simplest type of SPT threshold policy uses a route filter and source address filter to specify the multicast group and source addresses and to set the SPT threshold for that pair of addresses to infinity. The policy is applied to the main PIM instance.

  This example sets the SPT transition value for the source-group pair 10.10.10.1 and 224.1.1.1 to infinity. When the policy is applied to the last-hop router, multicast traffic from this source-group pair never transitions to a direct SPT to the source. Traffic will continue to arrive through the RP. However, traffic for any other source-group address combination at this router transitions to a direct SPT to the source.

• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.

• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.

• Configuration changes to the SPT threshold policy affect how the routing device handles the SPT transition.
• When the policy is configured for the first time, the routing device continues to transition to the direct SPT for the source-group address pair until the PIM-join state is cleared with the clear pim join command.
• If you do not clear the PIM-join state when you apply the infinity policy configuration for the first time, you must apply it before the PE router is brought up.
• When the policy is deleted for a source-group address pair for the first time, the routing device does not transition to the direct SPT for that source-group address pair until the PIM-join state is cleared with the clear pim join command.
• When the policy is changed for a source-group address pair for the first time, the routing device does not use the new policy until the PIM-join state is cleared with the clear pim join command.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

Step-by-Step Procedure

1. Apply the policy.

   [edit]user@host# edit protocols pim[edit protocols pim]user@host# set spt-threshold infinity spt-infinity-policy[edit protocols pim]user@host# exit
2. Configure the policy.
   [edit]user@host# edit policy-options policy-statement spt-infinity-policy[edit policy-options policy-statement spt-infinity-policy]user@host# set term one from route-filter 224.1.1.1/32 exact[edit policy-options policy-statement spt-infinity-policy]user@host# set term one from source-address-filter 10.10.10.1/32 exact[edit policy-options policy-statement spt-infinity-policy]user@host# set term one then accept[edit policy-options policy-statement spt-infinity-policy]user@host# set term two then reject[edit policy-options policy-statement spt-infinity-policy]user@host# exitpolicy-statement {

3. If you are done configuring the device, commit the configuration.

   [edit]user@host# commit

4. Clear the PIM join cache to force the configuration to take effect.

   [edit]user@host# run clear pim join

Results

Confirm your configuration by entering the show policy-options command and the show protocols command from configuration mode. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

To verify the configuration, run the show pim join command.