704
Configuring IP Multicast Routing
Configuring IP Multicast Routing
EXAMPLE
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
These sections describe how to set up BSR in your PIMv2 network:
Defining the PIM Domain Border, page 704 (optional)
Defining the IP Multicast Boundary, page 705 (optional)
Configuring Candidate BSRs, page 706 (optional)
Configuring Candidate RPs, page 707 (optional)
Defining the PIM Domain Border
As IP multicast becomes more widespread, the chance 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.
This procedure is optional.
BEFORE YOU BEGIN
Review the Bootstrap Router, page 680 and Guidelines and Limitations, page 686.
To Next Page
Loading...
Need help?
General