383
Step
Command
Remarks
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 MLD.
mld enable
Disabled by default.
For more information about the
ip vpn-instance
,
route-distinguisher
, and
ip binding
vpn-instance
commands, see
MPLS Command Reference
.
Configuring the MLD version
Because MLD message types and formats vary with MLD versions, the same MLD version should be
configured for all routers on the same subnet before MLD can work properly.
Configuring an MLD version globally
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter public network MLD
view or VPN instance MLD
view.
mld
[
vpn-instance
vpn-instance-name
]
N/A
3.
Configure an MLD version
globally.
version
version-number
MLDv1 by default.
Configuring an MLD version on an interface
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Configure an MLD version on
the interface.
mld version
version-number
MLDv1 by default.
Configuring an interface as a static member interface
To test IPv6 multicast data forwarding, you can configure an interface as a static member of an IPv6
multicast group or an IPv6 multicast source and group. Then, it will receive IPv6 multicast data
addressed to that IPv6 multicast group.
Configuration guidelines
•
When you configure an interface of an IPv6 PIM-SM device as a static member of an IPv6
multicast group or an IPv6 multicast source and group:
{
If the interface is enabled with IPv6 PIM-SM, it must be an IPv6 PIM-SM DR.
{
If this interface is enabled with MLD instead of IPv6 PIM-SM, it must be an MLD querier.
For more information about IPv6 PIM-SM and DR, see "
