Related Topics
Filtering Incoming RP Announcement Messages (CLI), on page 134
Example: Preventing Join Messages to False RPs
If all interfaces are in sparse mode, use a default-configured RP to support the two well-known
groups 224.0.1.39 and 224.0.1.40. Auto-RP uses these two well-known groups to collect and distribute
RP-mapping information. When this is the case and the ip pim accept-rp auto-rp command is configured,
another ip pim accept-rp command accepting the RP must be configured as follows:
Device(config)# ip pim accept-rp 172.10.20.1 1
Device(config)# access-list 1 permit 224.0.1.39
Device(config)# access-list 1 permit 224.0.1.40
Related Topics
Preventing Join Messages to False RPs (CLI), on page 134
Example: Configuring Candidate BSRs
This example shows how to configure a candidate BSR, which uses the IP address 172.21.24.18 on a port as
the advertised BSR address, uses 30 bits as the hash-mask-length, and has a priority of 10.
Device(config)# interface gigabitethernet1/0/2
Device(config-if)# ip address 172.21.24.18 255.255.255.0
Device(config-if)# ip pim sparse-dense-mode
Device(config-if)# ip pim bsr-candidate gigabitethernet1/0/2 30 10
Related Topics
Configuring Candidate BSRs (CLI), on page 141
PIM v2 BSR, on page 120
Example: Configuring Candidate RPs
This example shows how to configure the device to advertise itself as a candidate RP to the BSR in its PIM
domain. Standard access list number 4 specifies the group prefix associated with the RP that has the address
identified by a port. That RP is responsible for the groups with the prefix 239.
Device(config)# ip pim rp-candidate gigabitethernet1/0/2 group-list 4
Device(config)# access-list 4 permit 239.0.0.0 0.255.255.255
Related Topics
Configuring the Candidate RPs (CLI), on page 142
IP Multicast Routing Configuration Guide, Cisco IOS XE Release 3SE (Catalyst 3650 Switches)
OL-29890-01 159
Configuring PIM
Example: Preventing Join Messages to False RPs
To Next Page
Loading...
Need help?
General
