Specifications

B-180
Cisco MWR 2941 Mobile Wireless Edge Router Software Configuration Guide, Release 12.2(33)MRB
OL-21227-02
Appendix B Cisco MWR 2941 Router Command Reference
ip pim rp-address
Usage Guidelines In the Cisco IOS implementation of PIM, each multicast group individually operates in one of the
following modes: dense mode, sparse mode, or bidirectional mode. Groups in sparse mode (PIM-SM)
or bidirectional mode (bidir-PIM) use RPs to connect sources and receivers. All routers in a PIM domain
need to have a consistent configuration for the mode and RP addresses of the multicast groups.
The Cisco IOS software learns the mode and RP addresses of multicast groups through the following
three mechanisms: static group-to-RP mapping configurations, Auto-RP, and bootstrap router (BSR). By
default, groups operate in dense mode. No commands explicitly define groups to operate in dense mode.
Use the ip pim rp-address command to statically define the RP address for PIM-SM or bidir-PIM
groups (an ip pim rp-address command configuration is referred to as a static group-to-RP mapping).
You can configure a single RP for more than one group using an access list. If no access list is specified,
the static RP maps to all multicast groups, 224/4.
You can configure multiple RPs, but only one RP per group range.
If multiple ip pim rp-address commands are configured, the following rules apply:
• Highest RP IP address selected regardless of reachability: If a multicast group is matched by the
access list of more than one configured ip pim rp-address command, then the RP for the group is
determined by the RP with the highest RP address configured.
• One RP address per command: If multiple ip pim rp-address commands are configured, each static
group-to-RP mapping must be configured with a unique RP address (if not, it is overwritten).This
restriction also means that only one RP address can be used to provide RP functions for either sparse
mode or bidirectional mode groups. If you want to configure static group-to-RP mappings for both
bidirectional and sparse mode, the RP addresses must be unique for each mode.
• One access list per command: If multiple ip pim rp-address commands are configured, only one
access list can be configured per static group-to-RP mapping. An access list cannot be reused with
other static group-to-RP mappings configured on a router.
If dynamic and static group-to-RP mappings are used together, the following rule applies to a multicast
group: Dynamic group-to-RP mappings take precedence over static group-to-RP mappings—unless the
override keyword is used.
Examples The following example shows how to set the PIM RP address to 192.168.0.1 for all multicast groups
(224/4) and defines all groups to operate in sparse mode:
ip pim rp-address 192.168.0.1
12.2(33)MRA This command was integrated into Cisco IOS Release 12.2(33)MRA. The
command was only supported for use with PTP redundancy.
12.2(33)MRB This command was integrated into Cisco IOS Release 12.2(33)MRB. This release
does not support the vrf and bidir keywords.
Release Modification