Example: Using a Scope Policy for Multicast Scoping
This example configures a multicast scope policy named allow-auto-rp-on-backbone, allowing packets for auto-RP groups 224.0.1.39/32 and 224.0.1.40/32 on backbone-facing interfaces, and rejecting all other addresses in the 224.0.1.0/24 and 239.0.0.0/8 address ranges.
Requirements
Before you begin:
- Configure an interior gateway protocol or static routing. See the Routing Protocols Configuration Guide.
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):
|
Configuration
CLI Quick Configuration
To quickly a scope policy, copy the following commands and paste the commands into the CLI.
Step-by-Step Procedure
Define which packets are allowed.
[edit]user@host# edit policy-options policy-statement allow-auto-rp-on-backbone[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp from interface so-0/0/0.0[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp from interface so-0/0/1.0[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp from route-filter 224.0.1.39/32 exact[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp from route-filter 224.0.1.40/32 exact [edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term allow-auto-rp then acceptDefine 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 orlonger[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term reject-these from route-filter 239.0.0.0/8 orlonger[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# set term reject-these then reject[edit policy-options policy-statement allow-auto-rp-on-backbone]user@host# exitApply the policy.
[edit]user@host# edit routing-options multicast[edit routing-options multicast]user@host# set scope-policy allow-auto-rp-on-backboneIf you are done configuring the device, commit the configuration.
[edit routing-options multicast]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:
When you configure multicast scoping with a scope policy, the show multicast scope operational mode command displays only the name of the scope policy.
Hide Navigation Pane
Show Navigation Pane
Download
SHA1
