Example: Creating a Named Scope for Multicast Scoping

This example configures multicast scoping with four scopes: local, organization, engineering, and marketing.

• Requirements
• Overview
• Configuration
• Verification

Requirements

Before you begin:

• Configure a tunnel interface. See the Junos Network Interfaces Configuration Guide.
• Configure an interior gateway protocol or static routing. See the Routing Protocols Configuration Guide.

Overview

The local scope is configured on a GRE tunnel interface. The organization scope is configured on a GRE tunnel interface and a SONET/SDH interface. The engineering scope is configured on an IP-IP tunnel interface and two SONET/SDH interfaces. The marketing scope is configured on a GRE tunnel interface and two SONET/SDH interfaces. The Junos OS can scope any user-configurable IPv6 or IPv4 group.

To configure multicast scoping by defining a named scope, you must specify a name for the scope, the set of routing device interfaces on which you are configuring scoping, and the scope's address range.

Note: The prefix specified with the prefix statement must be unique for each scope statement. If multiple scopes contain the same prefix, only the last scope applies to the interfaces. If you need to scope the same prefix on multiple interfaces, list all of them in the interface statement for a single scope statement.

When you configure multicast scoping with a named scope, all scope boundaries must include the local scope. If this scope is not configured, it is added automatically at all scoped interfaces. 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 named scopes, copy the following commands and paste the commands into the CLI.

Step-by-Step Procedure

1. Configure the local scope.

   [edit]user@host# edit routing-options multicast[edit routing-options multicast]user@host# set scope local interface gr-2/1/0[edit routing-options multicast]user@host# set scope local prefix fe00::239.255.0.0/128

2. Configure the organization scope.

   [edit routing-options multicast]user@host# set scope organization interface [ gr-2/1/0 so-0/0/0 ][edit routing-options multicast]user@host# set scope organization prefix 239.192.0.0/14

3. Configure the engineering scope.

   [edit routing-options multicast]user@host# set scope engineering interface [ ip-2/1/0 so-0/0/1 so-0/0/2 ][edit routing-options multicast]user@host# set scope engineering prefix 239.255.255.0/24

4. Configure the marketing scope.

   [edit routing-options multicast]user@host# set scope marketing interface [ gr-2/1/0 so-0/0/2 so-1/0/0 ][edit routing-options multicast]user@host# set scope marketing prefix 239.255.254.0/24

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

   [edit routing-options multicast]user@host# commit

Results

Confirm your configuration by entering the show routing-options command.

Verification

To verify that group scoping is in effect, issue the show multicast scope command:

Resolve

Scope name		Group prefix					Interface			Rejects

local				fe00::239.255.0.0/128 		gr-2/1/00

organization 	239.192.0.0/14 gr-2/1/0 	so-0/0/00

engineering 	239.255.255.0/24 ip-2/1/0	so-0/0/1 so-0/0/20

marketing 		239.255.254.0/24 gr-2/1/0 so-0/0/2 so-1/0/00

When you configure scoping with a named scope, the show multicast scope operational mode command displays the names of the defined scopes, prefixes, and interfaces.

Related Topics

• Example: Using a Scope Policy for Multicast Scoping
• Multicast Administrative Scoping