24-19
Catalyst 3550 Multilayer Switch Software Configuration Guide
78-11194-03
Chapter24 Configuring IP Multicast Routi ng Configuring IP Multicast Routing
This section contains this configuration information:
•Setting up Auto-RP in a New Internetwork, page 24-19
•Adding Auto-RP to an Existing Sparse-Mode Cloud, page 24-19
•Preventing Join Messages to False RPs, page 24-20
•Preventing Candidate RP Spoofing, page 24-21
For overview information, see the “Auto-RP” section on page 24-8.
Setting up Auto-RP in a New Internetwork
If you are setting up Auto-RP in a new internetwork, you do not need a d efault RP because you configure
all the interfaces for sparse-dense mode. Follow the process described in the section “Adding Auto-RP
to an Existing Sparse-Mode Cloud” section on page 24 -19. However, skip Step 3 to configure a PIM
router as the RP for the local group.
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:
Command Purpose
Step1 show running-config Verify that a default RP is already configured on all PIM devices and the
RP in the sparse-mode network.
This step is not required for spare-dense-mode environmen ts .
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 rang e 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.
Step2 configure terminal Enter global configuration mode.
Step3 ip pim send-rp-announce interface-id
scope ttl group-list access-list-number
interval seconds
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.