422
Step
Command
Remarks
3.
Configure an RD for the VPN
instance.
route-distinguisher
route-distinguisher
Not configured by default.
4.
Enable IPv6 multicast
routing.
multicast ipv6 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 IPv6 PIM-SM.
pim ipv6 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 IPv6 PIM-SM and IPv6 BIDIR-PIM run on the IPv6 PIM network, do not use the same RP
to serve IPv6 PIM-SM and IPv6 BIDIR-PIM. Otherwise, exceptions might occur to the IPv6 PIM
routing table.
An RP can be manually configured or dynamically elected through the BSR mechanism. For a large
IPv6 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 operation
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, you must perform this configuration on all routers in the IPv6
PIM-SM domain and specify the same RP address.
To configure a static RP:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter public network IPv6
PIM view or VPN instance
IPv6 PIM view.
pim ipv6
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure a static RP for
IPv6 PIM-SM.
static-rp
ipv6-rp-address
[
acl6-number
] [
preferred
]
No static RP by default.
Configuring a C-RP
In an IPv6 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. Hewlett Packard
Enterprise recommends you configure C-RPs on backbone routers.