Chapter 44
Configuring IP Multicast Routing
Adding Auto-RP to an Existing Sparse-Mode Cloud
This section contains some suggestions for the initial deployment of Auto-RP into an existing
sparse-mode cloud to minimize disruption of the existing multicast infrastructure.
Beginning in privileged EXEC mode, follow these steps to deploy Auto-RP in an existing sparse-mode
cloud. This procedure is optional.
Command
Step 1
show running-config
Step 2
configure terminal
Step 3
ip pim send-rp-announce interface-id
scope ttl group-list access-list-number
interval seconds
Step 4
access-list access-list-number {deny |
permit} source [source-wildcard]
OL-12247-04
Purpose
Verify that a default RP is already configured on all PIM devices and the
RP in the sparse-mode network. It was previously configured with the ip
pim rp-address global configuration command.
This step is not required for spare-dense-mode environments.
The selected RP should have good connectivity and be available across
the network. Use this RP for the global groups (for example 224.x.x.x
and other global groups). Do not reconfigure the group address range that
this RP serves. RPs dynamically discovered through Auto-RP take
precedence over statically configured RPs. Assume that it is desirable to
use a second RP for the local groups.
Enter global configuration mode.
Configure another PIM device to be the candidate RP for local groups.
For interface-id, enter the interface type and number that identifies
•
the RP address. Valid interfaces include physical ports, port
channels, and VLANs.
For scope ttl, specify the time-to-live value in hops. Enter a hop
•
count that is high enough so that the RP-announce messages reach
all mapping agents in the network. There is no default setting. The
range is 1 to 255.
For group-list access-list-number, enter an IP standard access list
•
number from 1 to 99. If no access list is configured, the RP is used
for all groups.
For interval seconds, specify how often the announcement messages
•
must be sent. The default is 60 seconds. The range is 1 to 16383.
Create a standard access list, repeating the command as many times as
necessary.
For access-list-number, enter the access list number specified in
•
Step 3.
The deny keyword denies access if the conditions are matched. The
•
permit keyword permits access if the conditions are matched.
For source, enter the multicast group address range for which the RP
•
should be used.
(Optional) For source-wildcard, enter the wildcard bits in dotted
•
decimal notation to be applied to the source. Place ones in the bit
positions that you want to ignore.
Recall that the access list is always terminated by an implicit deny
statement for everything.
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
Configuring IP Multicast Routing
44-27