Configuring Multiple Rendezvous Points in a Domain
You can configure multiple rendezvous points (RPs) in a shared-tree PIM sparse-mode domain. You need to configure an MSDP local address to enable the RPs in the domain to maintain a consistent view of the active sources.
To configure a router to act as an RP in a domain with other RPs, do the following for each router in the domain that will act as an RP:
- Create the router ID by configuring a unique and routable IP address on the loopback interface and setting the
primaryaddress flag. - Configure a non-unique, but routable, unicast address on the loopback interface.
- Use the non-unique, routable unicast address to configure the PIM router to be the local RP.
- Configure MSDP with the unique and routable address (router ID) as the local address of the peer.
For a sample configuration of multiple RPs, see Example: Configuring a Router to Use Anycast RP. For more information about configuring interfaces, see the JUNOS Network Interfaces and Class of Service Configuration Guide.
Example: Configuring a Router to Use Anycast RP
The following example configures a router to use anycast RP:
[edit]
interfaces {
...
lo0 {
unit 0 {
family inet {
unique routable address[and]router-id;
address 10.1.1.1/32 {
primary;
}
non-unique routable anycast RP address;
address 10.10.10.10/32;
address 127.0.0.1/32;
}
}
}
}
[edit]
routing-options {
interface-routes {
rib-group ifrg;
}
rib-groups {
ifrg {
import-rib [inet.0 inet.2];
}
mcrg {
export-rib inet.2;
import-rib inet.2;
}
}
autonomous-system 1234;
}
[edit]
protocols {
bgp {
group red {
type internal;
family inet any;
neighbor 10.1.1.2 {
local-address 10.1.1.1;
}
}
}
msdp {
rib-group mcrg;
group red {
peer 10.1.1.2 {
local-address 10.1.1.1;
}
}
}
pim {
dense-groups {
224.0.1.39/32;
224.0.1.40/32;
}
rib-group mcrg;
rp {
local {
address 10.10.10.10;
}
}
interface all {
mode sparse-dense;
version 2;
}
interface fxp0.0 {
disable;
}
}
}