To do...
Bind the interface with the
6.
VPN instance.
7.
Enable PIM-SM.
For more information about the ip vpn-instance, route-distinguisher, and ip binding vpn-instance
commands, see MPLS Command Reference.
For more information about the multicast routing-enable command, see IP Multicast Command Reference.
Enabling BIDIR-PIM
Perform this configuration on all routers in the BIDIR-PIM domain.
To do...
1.
Enter system view.
2.
Enter public network PIM view
or VPN instance PIM view.
3.
Enable BIDIR-PIM.
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 used as a
backup means for the dynamic RP election mechanism to enhance the robustness and operation
manageability of a multicast network.
Configuring a static RP
Configure static RP on all routers in the PIM-SM domain and specify the same RP address.
If only one dynamic RP exists 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.
Perform this configuration on all routers in the BIDIR-PIM domain.
To do...
1.
Enter system view.
2.
Enter public network PIM view
or VPN instance PIM view.
3.
Configure a static RP for
BIDIR-PIM.
Use the command...
ip binding vpn-instance
vpn-instance-name
pim sm
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
bidir-pim enable
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
static-rp rp-address [ acl-number ]
[ preferred ] bidir
121
Remarks
Required.
By default, an interface belongs to
the public network, and is not
bound with any VPN instance.
Required.
Disabled by default.
Remarks
—
—
Required
Disabled by default.
Remarks
—
—
Required.
No static RP by default.