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.

English  

English

Example: Using a Scope Policy for Multicast Scoping

Requirements

Before you begin:

• Configure an interior gateway protocol or static routing. See the Junos OS Routing Protocols Library for Routing Devices.

Overview

Each referenced policy must be correctly configured at the [edit policy-options] hierarchy level, specifying the set of routing device interfaces on which to configure scoping, and defining the scope's address range as a series of route filters. Only the interface, route-filter, and prefix-list match conditions are supported for multicast scope policies. All other configured match conditions are ignored. The only actions supported are accept, reject, and the policy flow actions next-term and next-policy. The reject action means that joins and multicast forwarding are suppressed in both directions on the configured interfaces. The accept action allows joins and multicast forwarding in both directions on the interface. By default, scope policies apply to all interfaces. The default action is accept.

Note: Multicast scoping configured with a scope policy differs in some ways from scoping configured with a named scope (which uses the scope statement): You cannot apply a scope policy to a specific routing instance, because all scope policies apply to all routing instances. In contrast, a named scope does apply individually to a specific routing instance. In contrast to scoping with a named scope, scoping with a scope policy does not automatically add the local scope at scope boundaries. You must explicitly configure the local scope boundaries. The local scope limits the use of the multicast group 239.255.0.0/16 to an attached LAN.

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. Define which packets are allowed.

   [edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp from interface so-0/0/0.0user@host# set term allow-auto-rp from interface so-0/0/1.0user@host# set term allow-auto-rp from route-filter 224.0.1.39/32 exactuser@host# set term allow-auto-rp from route-filter 224.0.1.40/32 exact user@host# set term allow-auto-rp then accept

2. Define which packets are not allowed.

   [edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term reject-these from route-filter 224.0.1.0/24 orlongeruser@host# set term reject-these from route-filter 239.0.0.0/8 orlongeruser@host# set term reject-these then reject

3. Apply the policy.

   [edit routing-options multicast]user@host# set scope-policy allow-auto-rp-on-backbone

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

   user@host# commit

Results

Confirm your configuration by entering the show policy-options and show routing-options commands.

Verification

To verify that the scope policy is in effect, issue the show multicast scope configuration mode command:

Scope policy: [ allow-auto-rp-on-backbone ]

When you configure multicast scoping with a scope policy, the show multicast scope operational mode command displays only the name of the scope policy.