hit counter script

Example: Preventing Join Messages To False Rps; Example: Configuring Candidate Bsrs; Example: Configuring Candidate Rps - Cisco Catalyst 3850 series Configuration Manual

Ip multicast routing configuration guide
Hide thumbs Also See for Catalyst 3850 series:
Table of Contents

Advertisement

Example: Preventing Join Messages to False RPs

RP announcements from any other devices in the network. Furthermore, the mapping agent does not accept
candidate RP announcements from 172.16.5.1 or 172.16.2.1 if the announcements are for any groups in the
239.0.0.0 through 239.255.255.255 range. This range is the administratively scoped address range.
Related Topics
Filtering Incoming RP Announcement Messages (CLI), on page 152
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 152

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 159
PIMv2 Bootstrap Router, on page 133

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 160
IP Multicast Routing Configuration Guide, Cisco IOS XE Release 3.6E (Catalyst 3850 Switches)
184
Configuring PIM
OL-32598-01

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents