Configuring a Multicast Network with a Configuration Editor
To configure the Services Router as a node in a multicast network,
you must perform the following tasks marked (Required). For information about using the J-Web and CLI configuration editors,
see the J-series Services Router Basic LAN and WAN Access Configuration Guide.
Multicast session announcements are handled by two protocols,
the Session Announcement Protocol (SAP) and Session Description Protocol
(SDP). These two protocols display multicast session names and correlate
the names with multicast traffic. Enabling SDP and SAP allows the
router to receive announcements about multimedia and other multicast
sessions from sources. Enabling SAP automatically enables SDP.
For more information on SAP and SDP, see the JUNOS Multicast Protocols Configuration Guide.
The Services Router listens for session announcements on one
or more addresses and ports. By default, the router listens to address
and port 224.2.127.254:9875.
To configure SAP and SDP for the Services Router:
Navigate to the top of the configuration hierarchy
in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 185.
Navigate to the Listen level in the configuration
hierarchy.
In the J-Web interface, select Configuration>View
and Edit>Edit Configuration.
Next to Protocols, click Configure or Edit.
Next to Sap, click Configure or Edit.
Click Add new entry next to
Listen.
From the [edit] hierarchy level, enter
edit protocols sap
(Optional) Enter one or more addresses and ports for the Services
Router to listen to session announcements on. By default, the Services
Router listens to address and port 224.2.127.254:9875.
In the Address box, type the multicast address
the Services Router can listen to session announcements on, in dotted
decimal notation.
In the Port box, type the port number in decimal
notation.
Click OK.
Set the address value to the IP address
that the Services Router can listen to session announcements on, in
dotted decimal notation. For example:
set listen 224.2.127.254
Set the port value to the number of the
port that the Services Router can listen to session announcements
on, in decimal notation. For example:
set listen 224.2.127.254 port 9875.
Configuring IGMP (Required)
The Internet Group Management Protocol (IGMP) manages the membership
of hosts and routers in multicast groups. IGMP is an integral part
of IP and must be enabled on all routers and hosts that need to receive
IP mulitcasts. IGMP is automatically enabled on all broadcast interfaces
when you configure PIM or DVMRP.
For more information on IGMP, see JUNOS Multicast Protocols Configuration Guide.
By default, the Services Router runs IGMPv2. However, you might
still want to set the IGMP version explicitly on an interface, or
all interfaces. Routers running different versions of IGMP negotiate
the lowest common version of IGMP supported by hosts on their subnet.
One host running IGMPv1 forces the Services Router to use that version
and lose features important to other hosts.
To explicitly configure the IGMP version, perform these steps
on each Services Router in the network:
Navigate to the top of the configuration hierarchy
in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 186.
If you are finished configuring the router, commit
the configuration.
Table 186: Explicitly
Configuring the IGMP version
Task
J-Web Configuration Editor
CLI Configuration Editor
Navigate to the Interface level in the
configuration hierarchy.
In the J-Web interface, select Configuration>View
and Edit>Edit Configuration.
Next to Protocols, click Configure or Edit.
Next to Igmp, click Configure or Edit.
Next to Interface, click Add new
entry.
From the [edit] hierarchy level, enter
edit protocols igmp
Set the IGMP version. By default, the Services Router uses IGMPv2,
but this version can be changed through negotiation with hosts unless
explicitly configured.
(See the interface naming conventions in the J-series Services Router Basic LAN and WAN Access Configuration Guide.)
In the Interface name box, type the name of
the interface, or all.
In the Version box, type the version number: 1, 2, or 3.
Click OK.
Set the interface value to the interface
name, or all. For example:
set igmp interface all
Set the version value to 1, 2, or 3. For example:
set igmp interface all version 2
Configuring the PIM Static RP (Optional)
Protocol Independent Multicast (PIM) sparse mode is the most
common multicast protocol used on the Internet. PIM sparse mode is
the default mode whenever PIM is configured on any interface of the
Services Router. However, because PIM must not be configured on the
network management interface of the Services Router, you must disable
it on that interface.
Each any-source multicast (ASM) group has a shared tree through
which receivers learn about new multicast sources and new receivers
learn about all multicast sources. The rendezvous point (RP) router
is the root of this shared tree and receives the multicast traffic
from the source. To receive multicast traffic from the groups served
by the RP, the Services Router must determine the IP address of the
RP for the source.
One common way for the Services Router to locate RPs is by static
configuration of the IP address of the RP. For information about alternate
methods of locating RPs, see the JUNOS Multicast Protocols Configuration Guide.
To configure PIM sparse mode, disable PIM on ge-0/0/0, and configure the IP address of the RP perform these steps on each
Services Router in the network:
Navigate to the top of the configuration hierarchy
in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 187.
Navigate to the Interface level in the
configuration hierarchy.
In the J-Web interface, select Configuration>View
and Edit>Edit Configuration.
Next to Protocols, click Configure or Edit.
Next to Pim, click Configure or Edit.
Next to Interface, click Add new
entry.
From the [edit] hierarchy level, enter
edit protocols pim
Enable PIM on all network interfaces.
(See the interface naming conventions in the J-series Services Router Basic LAN and WAN Access Configuration Guide.)
In the Interface name box, type all.
Set the interface value to all. For example:
set pim interface all
Apply your configuration changes.
Click OK to apply your entries to the configuration.
Changes in the CLI are applied automatically when you execute
the set command.
Remain at the Interface level in the configuration
hierarchy.
Click Add new entry next to Interface.
Remain at the [edit protocols pim interface] hierarchy
level.
Disable PIM on the network management interface.
In the Interface name box, type ge-0/0/0.
Select the check box next to Disable.
Disable the ge-0/0/0 interface:
set pim interface ge-0/0/0 unit 0 disable
Apply your configuration changes.
Click OK to apply your entries to the configuration.
Changes in the CLI are applied automatically when you execute
the set command.
Navigate to the Rp level in the configuration
hierarchy.
On the main Configuration page next to Protocols,
click Configure or Edit.
Next to Pim, click Configure or Edit.
Next to Rp, click Configure or Edit.
From the [edit] hierarchy level, enter
edit protocols pim rp
Configure the IP address of the RP—for example, 192.168.14.27.
Click Configurenext to Static.
Click Add new entry next to
Address.
In the Addr box, type 192.168.14.27.
Click OK.
Set the address value to the IP address of the RP:
set static address 192.168.14.27
Filtering PIM Register Messages from Unauthorized Groups and
Sources (Optional)
When a source in a multicast network becomes active, the source’s
designated router (DR) encapsulates multicast data packets into a
PIM register message and sends them by means of unicast to the rendezvous
point (RP) router.
To prevent unauthorized groups and sources from registering
with an RP router, you can define a routing policy to reject PIM register
messages from specific groups and sources and configure the policy
on the designated router or the RP router. For information about routing
policies, see the JUNOS Policy Framework Configuration Guide
If you configure the reject policy on an RP router, it
rejects incoming PIM register messages from the specified groups and
sources. The RP router also sends a register stop message by means
of unicast to the designated router. On receiving the register stop
message, the designated router sends periodic null register messages
for the specified groups and sources to the RP router.
If you configure the reject policy on a designated router,
it stops sending PIM register messages for the specified groups and
sources to the RP router.
Note:
If you have configured the reject policy on an RP router,
we recommend that you configure the same policy on all the RP routers
in your multicast network.
Note:
If you delete a group and source address from the reject policy
configured on an RP router and commit the configuration, the RP router
will register the group and source only when the designated router
sends a null register message.
Table 189: Stopping Outgoing
PIM Register Messages on a Designated Router
Task
J-Web Configuration Editor
CLI Configuration Editor
Navigate to the Policy options level in
the configuration hierarchy.
In the J-Web interface, select Configuration>View
and Edit>Edit Configuration.
Next to Policy options, click Configure or Edit.
From the [edit] hierarchy level, enter
edit policy-options
Define a policy to not send PIM register messages for a group
and source address.
Next to Policy statement, click Add new entry.
In the Policy name box, type the name of the policy
statement—for example, stop-pim-register-msg-dr.
Next to From, click Configure.
Next to Route filter, click Add
new entry.
In the Address box, type the address of the group—for
example, 224.2.2.2/32.
From the Modifier list, select Exact.
Click OK.
Next to Source address filter, click Add new entry.
In the Address box, type the address of the source—for
example, 20.20.20.1/32.
From the Modifier list, select Exact.
Click OK until you return
to the Policy statement page.
Next to Then, click Configure.
From the Accept reject list, select Reject.
Click OK.
Set the match condition for the group address:
set policy statement stop-pim-register-msg-dr from route-filter
224.2.2.2/32 exact
Set the match condition for the address of a source
in the group:
set policy statement stop-pim-register-msg-dr from source-address-filter
20.20.20.1/32 exact
Set the match action to not send PIM register messages
for the group and source address:
set policy statement stop-pim-register-msg-dr then reject
Configure the stop-pim-register-msg-dr policy on the
designated router.
On the main Configuration page, next to Protocols,
click Configure or Edit.
Next to Pim, click Configure.
Next to Rp, click Configure.
Next to Dr register policy, click Add new entry.
In the Value box, type the name of the policy—for
example, stop-pim-register-msg-dr.
Click OK.
From the [edit] hierarchy level, enter
edit protocols pim rp
Assign the policy on the designated router:
set dr-register-policy stop-pim-register-msg-dr
Configuring a PIM RPF Routing Table (Optional)
By default, PIM uses inet.0 as its reverse-path forwarding
(RPF) routing table group. PIM uses an RPF routing table group to
resolve its RPF neighbor for a particular multicast source address
and for the RP address. PIM can optionally use inet.2 as
its RPF routing table group. The inet.2 routing table is
organized more efficiently for RPF checks.
Once configured, the RPF routing table must be applied to PIM
as a routing table group.
To configure and apply a PIM RPF routing table, perform these
steps on each Services Router in the network:
Navigate to the top of the configuration hierarchy
in either the J-Web or CLI configuration editor.
Perform the configuration tasks described in Table 190.
If you are finished configuring the router, commit
the configuration.
