R3303-HP HSR6800 Routers IP Multicast Configuration Guide

117
Ste
p
Command Descri
p
tion
6. Bind the interface with a VPN
instance.
ip binding vpn-instance
vpn-instance-name
By default, an interface belongs to
the public network, and is not
bound with any VPN instance.
For more information about this
command, see MPLS Command
Reference.
7. Enable PIM-SM.
pim sm Disabled by default.
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
method for the dynamic RP election mechanism to enhance the robustness and operational
manageability of a multicast network.
When both PIM-SM and BIDIR-PIM run on the PIM network, do not use the same RP to serve PIM-SM and
BIDIR-PIM. Otherwise, exceptions might occur to the PIM routing table.
Configuring a static RP
If only one dynamic RP exists in a network, manually configuring a static RP can avoid communication
interruption because of single-point failures. It can also avoid frequent message exchange between C-RPs
and the BSR.
To make a static RP to operate correctly, you must perform this configuration on all routers in the PIM-SM
domain and specify the same RP address.
To configure a static RP:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter public network PIM view
or VPN instance PIM view.
pim [ vpn-instance
vpn-instance-name ]
N/A
3. Configure a static RP for
PIM-SM.
static-rp rp-address [ acl-number ]
[ preferred ]
By default, no static RP is
configured.
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. HP recommends you to configure C-RPs on backbone routers.
To guard against C-RP spoofing, you must 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 can become the BSR, you
must configure the same filtering policy on all C-BSRs in the PIM-SM domain.
When configuring a C-RP, ensure a relatively large bandwidth between this C-RP and the other devices
in the PIM-SM domain.
To configure a C-RP: