Configuring a Static RP

When only one Rendezvous Point (RP) exists in the network, you can manually configure a static RP rather than a dynamic RP. This can save the bandwidth occupied by message exchange between the Candidate-RP (C-RP) and the BootStrap router (BSR). The configurations about the static RP should be the same on all the devices in a PIM-SM domain.

Context

Static RPs are stable and have low requirements for devices, and therefore they apply to small and middle-sized networks. To use a static RP, ensure that the same RP information and multicast group range are configured for all routers, including the RP in a domain. Dynamic RPs have high reliability and improved maintainability, and therefore they apply to large networks. For details about how to configure a dynamic RP, see Configuring a Dynamic RP.

When the static RP and the dynamic RP are configured in the PIM-SM at the same time, faults may occur in the network. So, confirm the action before you run the command. If you want to use only the dynamic RP in the PIM-SM network, skip the configuration.

Perform the following steps on all FWs in a PIM-SM domain. The FWs where static RP is not configured cannot participate in multicast forwarding in this PIM-SM domain.

Procedure

Access the system view.
system-view
Create a basic ACL and access its view.
acl [ number ] acl-number [ vpn-instance vpn-instance-name ]
Configure rules for the basic ACL.
rule [ rule-id ] { deny | permit } source { source-ip-address { 0 | source-wildcard } | address-set address-set-name | any }

Use parameter source to define the multicast group range to be served by the static RP.
Return to the system view.
quit
Access the PIM view.
pim [ vpn-instance vpn-instance-name ]
Specify the static RP.
static-rp rp-address [ basic-acl-number ] [ preferred ]

You can run the command repeatedly to configure multiple static RPs for the FW.
- rp-address: specifies the static RP address.
- basic-acl-number: specifies the ACL. The ACL defines the range of the multicast group served by the static RP. When the range of multicast groups that multiple static RPs serve overlaps, the static RP with the largest IP address functions as the RP.
- preferred: indicates the preference of the static RP. If the C-RP is configured in the network at the same time, the FW prefers the RP statically specified after preferred is used. Otherwise, C-RP is preferred.
All FWs in the PIM-SM area must be configured with the same static-rp command.
- If no ACL is configured, the static RP serves all multicast groups.
- If an ACL is configured, the device uses configured ACL rules to filter multicast groups to be served by the static RP.
  - If a multicast group matches an ACL rule and the action is permit, the static RP serves this multicast group.
  - If a multicast group matches an ACL rule and the action is deny, the static RP does not serve this multicast group.
  - If a multicast group does not match any ACL rule or if a specified ACL does not exist or does not contain rules, the static RP serves all multicast groups.