Configuring An Rp - H3C S5600 Series Operation Manual

To do...
Enter interface view
Enable PIM-SM

Configuring an RP

An RP can be manually configured or dynamically elected through the BSR mechanism. For a large
PIM network, static RP configuration is a tedious job. Generally, static RP configuration is just a backup
means for the dynamic RP election mechanism to enhance the robustness and operation manageability
of a multicast network.
Configuring a static RP
If there is only one dynamic RP in a network, manually configuring a static RP can avoid communication
interruption due to single-point failures and avoid frequent message exchange between C-RPs and the
BSR. To enable a static RP to work normally, you must perform this configuration on all the routers in the
PIM-SM domain and specify the same RP address.
Follow these steps to configure a static RP:
To do...
Enter system view
Enter PIM view
Configure a static RP
Configuring a C-RP
In a PIM-SM domain, you can configure routers that intend to become the RP as C-RPs. The BSR
collects the C-RP information by receiving the C-RP-Adv messages from C-RPs or auto-RP
announcements from other routers and organizes the information into an RP-set, which is flooded
throughout the entire network. Then, the other routers in the network calculate the mappings between
specific group ranges and the corresponding RPs based on the RP-set. We recommend that you
configure C-RPs on backbone routers.
To guard against C-RP spoofing, you need to configure a legal C-RP address range and the range of
multicast groups to be served on the BSR. In addition, because every C-BSR has a chance to become
the BSR, you need to configure the same filtering policy on all C-BSRs in the PIM-SM domain.
Follow these steps to configure a C-RP:
To do...
Enter system view
Enter PIM view
Configure candidate
RPs
Use the command...
interface interface-type
interface-number
pim sm
Use the command...
system-view
pim
static-rp rp-address [ acl-number ]
Use the command...
system-view
pim
c-rp interface-type
interface-number [ group-policy
acl-number | priority priority ]*
4-11
Remarks
—
Required
Disabled by default
Remarks
—
—
Optional
No static RP by default
Remarks
—
—
Optional
By default, candidate RPs are not set for the
switch and the value of priority is 0.