Juniper JUNOSE 11.1.X MULTICAST ROUTING, Configuration Manual

Page: 249 / 270

of service (DOS) attacks where large numbers of joins forwarded to each router on
the RPT can result in a PIM state explosion and very high memory consumption.
For information about how to create access lists, see Configuring Routing Policy in
the JUNOSe IP Services Configuration Guide .
ipv6 pim join-filter
■
Use to specify an extended access list that you want this PIM interface to use as
a join filter.
■
You can apply the join filter at the global level or at the interface level.
■
If an interface-level filter exists, it takes precedence over the global-level filter.
■
Example 1
host1(config)# ipv6 pim join-filter gold
■
Example 2
host1(config-interface)# ipv6 pim join-filter gold
■
Use the no version to remove the filter association.
■
See ipv6 pim join-filter.
Configuring PIM SSM
Source Specific Multicast (SSM) is a datagram delivery model that best supports
one-to-many applications, also known as broadcast applications. SSM is networking
technology that targets audio and video broadcast application environments.
To use PIM SSM, MLDv2 must be configured on customer premises equipment
(CPE)–facing interfaces to receivers, and PIM sparse mode must be configured on
CPE-facing interfaces to sources and on core-facing interfaces. After configuring SSM,
you can use the
show ipv6 pim sparse-mode sg-state command to display SSM
group membership information.
To configure PIM SSM, you enable PIM SSM on the router and define the SSM range
of IP multicast addresses.
Figure 22 on page 228 shows how PIM SSM is configured between a receiver and a
source in the network. Interface 1 has MLDv2 enabled and all other interfaces towards
the core or source have PIM SSM enabled.
Configuring PIM SSM
■ 227
Chapter 7: Configuring PIM for IPv6 Multicast