Brocade Multi-Service IronWare Multicast Configuration Guide (Supporting R05.6.00) - Manual (Page 57)

Multi-Service IronWare Multicast Configuration Guide 45
53-1003032-02
PIM Sparse
1
• Enter ve num for a virtual interface.
• Enter loopback num for a loopback interface.
• Enter tunnel num for a GRE tunnel interface to be configured. The GRE tunnel interface is
enabled under the router PIM configuration.
By default, this command configures the device as a candidate RP for all group numbers beginning
with 224. As a result, the device is a candidate RP for all valid PIM Sparse group numbers. You can
change this by adding or deleting specific address ranges. Consider the following when configuring
the RP.
• When the candidate RP is configured, before explicitly specifying the groups that it serves, the
c-rp does, by default, serve all the groups in the PIMSM 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 configs. 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 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. This default group prefix CANNOT BE
REMOVED.
• It is not possible to punch holes in the group prefix range. For instance executing
rp-candidate add 228.0.0.0/16
and then,
rp-candidate delete 228.0.1.0/24
is not permissible. It 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.
The following example narrows the group number range for which the device is a candidate RP by
explicitly adding a range.
Brocade(config-pim-router)# rp-candidate add 224.126.0.0 16
Syntax: [no] rp-candidate add group-addr mask-bits
The group-addr mask-bits specifies the group address and the number of significant bits in the
subnet mask. In this example, the device is a candidate RP for all groups that begin with 224.126.
When you add a range, you override the default. The device then becomes a candidate RP only for
the group address ranges you add.
You also can delete the configured rp-candidate group ranges by entering the following command.
Brocade(config-pim-router)# rp-candidate delete 224.126.22.0 24
Syntax: [no] rp-candidate delete group-addr mask-bits
The usage of the group-addr mask-bits parameter is the same as for the rp-candidate add
command.
.Updating PIM-Sparse forwarding entries with new RP configuration
If you make changes to your static RP configuration, the entries in the PIM-Sparse multicast
forwarding table continue to use the old RP configuration until they are aged out.