Configuring Pimv2 Bsr - Cisco Catalyst 3550 series Software Configuration Manual

Configuring IP Multicast Routing
Command
Step 5 show running-config
Step 6
copy running-config startup-config
To remove a filter on incoming RP announcement messages, use the no ip pim rp-announce-filter
rp-list access-list-number group-list access-list-number global configuration command.
This example shows a sample configuration on an Auto-RP mapping agent that is used to prevent
candidate RP announcements from being accepted from unauthorized candidate RPs:
Switch(config)# ip pim rp-announce-filter rp-list 10 group-list 20
Switch(config)# access-list 10 permit host 172.16.5.1
Switch(config)# access-list 10 permit host 172.16.2.1
Switch(config)# access-list 20 deny 239.0.0.0 0.0.255.255
Switch(config)# access-list 20 permit 224.0.0.0 15.255.255.255
In this example, the mapping agent accepts candidate RP announcements from only two devices,
172.16.5.1 and 172.16.2.1. The mapping agent accepts candidate RP announcements from these two
devices only for multicast groups that fall in the group range of 224.0.0.0 to 239.255.255.255. The
mapping agent does not accept candidate 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.

Configuring PIMv2 BSR

BSR automates the distribution of group-to-RP mappings to all routers and multilayer switches in a
PIMv2 network. It eliminates the need to manually configure RP information in every device in the
network. However, instead of using IP multicast to distribute group-to-RP mapping information, BSR
uses hop-by-hop flooding of special BSR messages to distribute the mapping information. For overview
information, see the
These sections describe how to set up BSR in your PIMv2 network:
•
•
•
•
Defining the PIM Domain Border
As IP multicast becomes more widespread, the chances of one PIMv2 domain bordering another PIMv2
domain is increasing. Because these two domains probably do not share the same set of RPs, BSR,
candidate RPs, and candidate BSRs, you need to constrain PIMv2 BSR messages from flowing into or
out of the domain. Allowing these messages to leak across the domain borders could adversely affect the
normal BSR election mechanism and elect a single BSR across all bordering domains and co-mingle
candidate RP advertisements, resulting in the election of RPs in the wrong domain.
Catalyst 3550 Multilayer Switch Software Configuration Guide
34-22
"Bootstrap Router" section on page
Defining the PIM Domain Border, page 34-22
Defining the IP Multicast Boundary, page 34-24
Configuring Candidate BSRs, page 34-25
Configuring Candidate RPs, page 34-26
Purpose
Verify your entries.
(Optional) Save your entries in the configuration file.
34-8.
Chapter 34 Configuring IP Multicast Routing
78-11194-09