boston(config-if)#ipv6 pim query-interval 40
4. Specify that router Boston will be a remote neighbor of router Chicago, and identify
the IP address on router Boston that will transmit datagrams to router Chicago.
chicago(config-router)#remote-neighbor 2001::1 sparse-mode
5. Specify the location of the interface that will transmit datagrams from router Chicago
to router Boston.
chicago(config-router-rn)#update-source atm 2/1.95
6. Specify that router Chicago will send hello messages to router Boston every 40
seconds.
chicago(config-if)#ipv6 pim query-interval 40
7. See update-source.
Using PIM Sparse Mode Join Filters
You can use PIM sparse mode join filters to prevent multicast state from being created
in the PIM sparse mode router. The filters are applied to join entries in PIM join/prune
messages that are received from PIM sparse mode neighbors.
By denying joins at the edge of a network, you can limit the multicast state and traffic in
the network. By accepting only certain joins, you can control which multicast services an
end user can receive. PIM join filters also reduce the potential for denial 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.
Copyright © 2010, Juniper Networks, Inc.218
JunosE 11.2.x Multicast Routing Configuration Guide
To Next Page
Loading...
Need help?
General
