F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Network Management Configuration Guide-6PW100

916
NOTE:
To ensure SSM service for all hosts on a subnet, re
g
ardless of the MLD version runnin
g
on the hosts, enable
MLDv2 on the interface that forwards IPv6 multicast traffic onto the subnet.
1028BConfiguring MLD SSM mapping entries
You can perform this configuration task multiple times to map an IPv6 multicast group to different IPv6
multicast sources.
To configure an MLD SSM mapping:
Ste
p
Command Remarks
1570. Enter system view.
system-view N/A
1571. Enter MLD view. mld N/A
1572. Configure an MLD SSM
mapping.
ssm-mapping ipv6-group-address
prefix-length ipv6-source-address
No MLD mappings are configured
by default.
341B
Configuring MLD proxying
This section describes how to configure MLD proxying.
1029BConfiguration prerequisites
Before you configure the MLD proxying feature, complete the following tasks:
• Enable IPv6 forwarding and configure an IPv6 unicast routing protocol so that all devices in the
domain are interoperable at the network layer.
• Enable IPv6 multicast routing.
1030BEnabling MLD proxying
You can enable MLD proxying on the interface in the direction toward the root of the multicast forwarding
tree to make the device serve as an MLD proxy.
1841BConfiguration guidelines
• Each device can have only one interface serving as the MLD proxy interface.
• You cannot enable MLD on interfaces with MLD proxying enabled. Moreover, only the mld
require-router-alert, mld send-router-alert, and mld version commands can take effect on such
interfaces.
• You cannot enable other IPv6 multicast routing protocols (such as IPv6 PIM-DM or IPv6 PIM-SM) on
interfaces with MLD proxying enabled, or vice versa. However, the source-lifetime, source-policy,
and ssm-policy commands configured in IPv6 PIM view can still take effect.
1842BConfiguration procedure
To enable MLD proxying: