Configures a rendezvous point and its associated groups statically, for PIM sparse mode operation.
ipv4 | Specifies an IPv4 address. |
ipv6 | Specifies an IPv6 address. |
ip_address | Specifies a static CRP address. |
none | Deletes the static rendezvous point. |
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.
In PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a central multicast router that is responsible for receiving and distributing multicast packets. If you use a static RP, all switches in your network must be configured with the same RP address for the same group (range).
ExtremeXOS switches support up to 64 static RPs (32 IPv4 and 32 IPv6), and up to 180 groups (group/mask entries) in a single RP policy file. If you configure more than 180 group entries in a single RP policy file, the switch will not process entries added after the first 180.
The policy file contains a list of multicast group addresses served by this RP.
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.
If routers have different group-to-RP mappings, due to misconfiguration of the static RP (or any other reason), traffic is disrupted.
The following example statically configures an RP and its associated groups defined in policy file rp-list:
configure pim crp static 10.0.3.1 rp-list
The following is a sample policy file:
entry extreme1 { if match any { } then { nlri 224.0.0.0/4 ; nlri 239.255.0.0/24 ; nlri 232.0.0.0/8 ; nlri 238.1.0.0/16 ; nlri 232.232.0.0/20 ; } }
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.