Configures the dynamic candidate rendezvous point (CRP) for PIM sparse-mode operation.
| ipv4 | Specifies the IPv4 address family. |
| ipv6 | Specifies the IPv6 address family. |
| vlan_name | Specifies a VLAN name. |
| none | Specifies to delete a CRP. |
| policy | Specifies a policy file name. |
| priority | Specifies a priority setting. The range is 0–255. |
The default setting for priority is 192. Priority value 0 indicates the highest priority.
ExtremeXOS switches support up to 50 RPs in a switch, and up to 180 groups (group/mask entries) in a single RP policy file. If you configure more than 180 group entries in single RP policy file, then the switch will not process entries added after first 180.
The policy file contains the list of multicast group addresses serviced by this RP. This set of group addresses are advertised as candidate RPs. Each router then elects the common RP for a group address based on a common algorithm. This group to RP mapping should be consistent on all routers.
This policy file is not used for filtering purposes. As used with this command, the policy file is just a container for a list of addresses. So a typical policy file used for RP configuration looks a little different from a policy used for other purposes. The following is a sample policy file that configures the CRP for the address ranges 239.0.0.0/24 and 232.144.27.0/24:
entry extreme1 {
if match any {
}
then {
nlri 239.0.0.0/24 ;
nlri 232.144.27.0/24 ;
}
}
The VLAN specified for a CRP must have PIM configured.
To delete a CRP, use the keyword none as the access policy.
The following example configures the candidate rendezvous point for PIM sparse-mode operation on the VLAN HQ_10_0_3 with the policy rp-list and priority set to 30:
configure pim crp HQ_10_0_3 rp-list 30
This command was first available in ExtremeXOS 10.1.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the PIM feature, see the Switch Engine 32.3 Feature License Requirements document.