Configuring An Rp - 3Com MSR 50 Series Configuration Manual

1182 C 71: PIM C
HAPTER ONFIGURATION

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 devices 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 public instance PIM view or
VPN instance 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.
Follow these steps to configure a C-RP:
To do...
Enter system view
Enter public instance PIM view or
VPN instance PIM view
Configure an interface to be a
C-RP
Configure a legal C-RP address
range and the range of multicast
groups to be served
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
static-rp rp-address
[ acl-number ] [ preferred ]
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
c-rp interface-type
interface-number [ group-policy
acl-number | priority priority |
holdtime hold-interval |
advertisement-interval
adv-interval ] *
crp-policy acl-number
Remarks
-
-
Optional
No static RP by default
Remarks
-
-
Optional
No C-RPs are
configured by default
Optional
No restrictions by
default