Switching to an SPT for PIM Sparse Mode
PIM sparse mode initiates multicast using a shared tree. You can configure PIM sparse
mode to switch to an SPT when a source starts sending multicast messages, or you can
prevent PIM sparse mode from switching to an SPT. Multicasting over an SPT can be
more efficient than multicasting over a shared tree (see “PIM Sparse Mode” on page 80).
ipv6 pim spt-threshold
• Use to specify when PIM sparse mode switches from a shared tree to an SPT.
• Specify a nonzero integer or the keyword infinity to prevent PIM sparse mode from
switching to an SPT.
• Specify a value of 0 to configure PIM to switch to an SPT when a source starts sending
multicast messages.
• Example
host1(config)#ipv6 pim spt-threshold 4
• Use the no version to restore the default, 0.
• See ipv6 pim spt-threshold.
Configuring PIM Sparse Mode Remote Neighbors
You must use PIM sparse mode remote neighbors to run multicast services over
BGP/MPLS VPNs.
NOTE: Although you can configure PIM sparse mode remote neighbors, you can not
use these remote neighbors for BGP/MPLS VPNs.
To configure a pair of E Series routers to act as PIM remote neighbors:
1. On one router, specify the other router to be a remote neighbor, and identify the IP
address of the interface on the other router that is used for the connection to this
router.
host1(config-router):boston#remote-neighbor 1001::1 sparse-mode
2. Specify the location of the local interface whose address is used as the source
address for the PIM connection to a remote neighbor.
host1(config-router-rn):boston#update-source atm 2/1.108
3. (Optional) Specify how often the router sends hello messages to the remote neighbor.
host1(config-router-rn):boston#query-interval 40
4. Repeat Steps 2 to 3 for the other router.
query-interval
Copyright © 2010, Juniper Networks, Inc.216
JunosE 11.2.x Multicast Routing Configuration Guide
To Next Page
Loading...
Need help?
General
