This lab uses both autoRP and static RP while in Sparse mode. When both are configured, autoRP takes precedence and if for whatever reason the RP info is lost, it falls to the statically configured RP.
You can also limit the groups that a particular RP will be the RP for.
Config:
R2 - the autoRP candidate
!
ip pim rp-address 150.1.2.2 1
ip pim send-rp-announce Loopback0 scope 16
ip pim send-rp-discovery Loopback0 scope 16
!
logging alarm informational
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
!
R1-R6 (minus R4), the other PIM routers
!
ip pim rp-address 150.1.2.2 1
!
logging alarm informational
access-list 1 permit 224.0.1.39
access-list 1 permit 224.0.1.40
Verification:
R1#sh ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 150.1.2.2 (?), v2v1
Info source: 150.1.2.2 (?), elected via Auto-RP
Uptime: 00:13:45, expires: 00:02:10
Acl: 1, Static
RP: 150.1.2.2 (?)
R1#
Removed autoRP from R2
R1#sh ip pim rp mapping
PIM Group-to-RP Mappings
Acl: 1, Static
RP: 150.1.2.2 (?)
R1#
R1#
