139
Enabling PIM-SM globally on the public network
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable IP multicast routing.
multicast routing-enable
Disabled by default.
3.
Enter interface view.
interface
interface-type
interface-number
N/A
4.
Enable PIM-SM.
pim sm
Disabled by default.
Enabling PIM-SM in a VPN instance
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a VPN instance and
enter VPN instance view.
ip vpn-instance
vpn-instance-name
N/A
3.
Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
Not configured by default.
4.
Enable IP multicast routing.
multicast routing-enable
Disabled by default.
5.
Enter interface view.
interface
interface-type
interface-number
N/A
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.
7.
Enable PIM-SM.
pim sm
Disabled by default.
For more information about the
ip vpn-instance
,
route-distinguisher
, and
ip binding
vpn-instance
commands, see
MPLS Command Reference.
Configuring an RP
CAUTION:
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.
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.
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 enable a static RP to work normally, perform this configuration on all the routers in the PIM-SM
domain and specify the same RP address.
To configure a static RP:
