Configuring PIM Sparse
To configure a RUCKUS device for PIM Sparse, perform the following tasks:
- Configure the following global parameter:
- Configure the following interface parameters:
- Configure the following PIM Sparse global parameters:
RP Configuration Considerations
When configuring a device as a candidate RP
using the rp-candidate command, pay attention to the following considerations:
- When the candidate RP (c-RP) is configured, before explicitly specifying the groups that it serves, the c-RP does, by default, serve all the groups in the PIM SM multicast range, but this includes all groups beginning with 224.x.x.x all the way up to 239.x.x.x. This is reflected in the "rp-candidate add 224.0.0.0 4" line displayed as part of the runtime configuration. This entry will be referred to as the default prefix.
- When any group prefix is explicitly added (and the 224.0.0.0/4 prefix itself can also be explicitly added through the CLI), the default prefix is implicitly removed. Now, the only groups served by the candidate RP, are the groups that have been explicitly added.
- All explicitly added groups can be removed using the "delete" option or "no ... add"
option. However, once all the explicitly added groups are deleted from the candidate
RP group prefix list, the default prefix becomes active once more.
Note: This default group prefix cannot be removed.
- It is not possible to punch holes in the group prefix range. For example, running rp-candidate add 228.0.0.0/16 and then rp-candidate delete 228.0.1.0/24 is not allowed. This syntax cannot be used to ensure that the rp-candidate will serve all group prefixes in the 228.0.0.0/16 range except those in the 228.0.1.0/24 range.