97
IMPORTANT:
ll the interfaces on the same router must operate in the same PIM mode in the public network or the same
PN instance.
To enable PIM-SM:
Ste
Command Remarks
1. Enter system view.
system-view
N/A
2. Enable IP multicast routing and
enter MRIB view.
multicast routing [ vpn-instance
vpn-instance-name ]
By default, IP multicast routing is
disabled.
3. Return to system view.
quit N/A
4. Enter interface view.
interface interface-type
interface-number
N/A
5. Enable PIM-SM.
pim sm By default, PIM-SM is disabled.
Configuring an RP
An RP can provide services for multiple or all multicast groups. However, only one RP can forward
multicast traffic for a multicast group at a time.
An RP can be manually configured or dynamically elected through the BSR mechanism. For a
large-scaled PIM network, configuring static RPs is a tedious job. Generally, static RPs are backups for
dynamic RPs to enhance the robustness and operational manageability on a multicast network.
Configuring a static RP
If only one dynamic RP exists on a network, you can configure a static RP to avoid communication
interruption caused by single-point failures. The static RP can also avoid waste of bandwidth due to
frequent message exchange between C-RPs and the BSR. The static RP configuration must be the same on
all routers in the PIM-SM domain.
To configure a static RP:
Ste
Command
Remarks
1. Enter system view.
system-view
N/A
2. Enter 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
IMPORTANT:
hen you configure a C-RP, reserve a relatively large bandwidth between the C-RP and other devices in
the PIM-SM domain.
In a PIM-SM domain, if you want a router to become the RP, you can configure the router as a C-RP. HP
recommends that you configure C-RPs on backbone routers.