No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Configuration Guide - IP Multicast

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, PIM (IPv4), PIM (IPv6), MSDP, multicast VPN, multicast route management (IPv4), multicast route management (IPv6), IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN, multicast network management.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Licensing Requirements and Limitations for MLD Snooping

Licensing Requirements and Limitations for MLD Snooping

Involved Network Elements

An IPv6 multicast network may have the following network elements:
  • Multicast source: sends multicast data to receiver hosts. For example, a video server is a multicast source.
  • Device running IPv6 Protocol Independent Multicast (PIM): uses the IPv6 PIM protocol to generate multicast routing entries and forwards multicast data based on multicast routing entries. On an IPv6 multicast network, all Layer 3 devices must run IPv6 PIM; otherwise, multicast forwarding paths cannot be established.
  • MLD querier: exchanges MLD messages with receiver hosts to create and maintain group memberships. On an IPv6 multicast network, Layer 3 devices connected to network segments of receivers must run the MLD protocol or be configured with static MLD groups. Otherwise, upstream PIM devices cannot know the multicast groups that users want to join, and therefore cannot establish multicast forwarding paths.
  • Device running MLD snooping: listens on MLD messages exchanged between upstream Layer 3 multicast devices and receiver hosts to create and maintain Layer 2 multicast forwarding entries, which are used for accurate multicast data forwarding on a Layer 2 network. To prevent broadcasting of multicast packets on a Layer 2 network and conserve network bandwidth, it is recommended that you configure MLD snooping on Layer 2 devices.
  • Receiver: multicast users that receive multicast data. A receiver can be a PC, a set top box, or any device with multicast client installed.

Licensing Requirements

The MLD snooping feature can be used only after the IPv6 feature is enabled, whereas the IPv6 feature is under license control. By default, the IPv6 feature is disabled on CE12800 and CE12800E series switches. To use the IPv6 feature, apply for and purchase the license from the equipment supplier.

Version Requirements

Table 11-6 Products and minimum versions supporting MLD snooping


Minimum Version Required



CE12800E configured with FD-X series cards


Feature Limitations

  • Because MLD snooping is a Layer 2 multicast feature, all the MLD snooping configurations on interfaces mentioned in this chapter are performed on Layer 2 physical interfaces, including Eth-Trunk interfaces.
  • When configuring MLD SSM mapping on a switch, you are advised to enable MLDv2 on interfaces of the switch to ensure that hosts running any MLD version on the shared network segment can obtain SSM services.
  • If Layer 3 multicast functions (such as MLD and IPv6 PIM) are enabled on a VLANIF interface, the corresponding VLAN does not support configuration of the MLD snooping querier, Report message suppression, or MLD snooping proxy. Similarly, if you configure MLD snooping querier, Report message suppression, or MLD snooping proxy in a VLAN, the corresponding VLANIF interface does not support configuration of Layer 3 multicast functions.
  • If a multicast network already has an MLD querier, you are not advised to configure an MLD snooping querier, because the configuration will cause MLD querier re-election. If you configure an MLD snooping querier on a switch, ensure that the source IP address of the General Query messages sent from the switch is larger than the IP address of the upstream MLD querier.
  • The following pairs of functions cannot be configured in the same VLAN:
    • MLD snooping querier and MLD snooping proxy
    • Report message suppression and MLD snooping proxy
  • MLD snooping cannot be used together with VLAN mapping.
  • In the scenario when both IPv6 Layer 2 and Layer 3 multicast are enabled, that is, when Layer 2 multicast is configured in a VLAN and Layer 3 multicast is configured on the corresponding VLANIF interface, the following functions must be configured simultaneously to ensure normal on-demand forwarding of multicast traffic:
    • MLD Snooping must be enabled in a VLAN.
    • IPv6 PIM (PIM-SM or Bidir-PIM) and MLD must be enabled on the corresponding VLANIF interface.
  • When configuring IPv6 multicast and other services, pay attention to the following points:
    • In versions earlier than V200R003C00, M-LAG does not support IPv6 multicast. In V200R003C00 and later versions, an M-LAG set up with standalone switches or stack systems supports IPv6 multicast.
    • Multicast resources are shared by multiple services including VLAN, MAC, Eth-Trunk, M-LAG, Layer 2 protocol transparent transmission, Layer 3 physical interface, and multicast. If multicast resources in the system are insufficient for any of these services you are configuring, the system will display a configuration failure message. To solve this problem, you can delete some unnecessary service configuration, for example, delete unused VLANs.

    • If the number of multicast entries in a virtual system (VS) exceeds the upper limit defined in the resource template, an active/standby switchover may cause changes in multicast traffic forwarding. For example, after an active/standby switchover, a multicast flow that previously failed to be forwarded may be forwarded, whereas a multicast flow that was previously forwarded normally may fail to be forward. In this situation, increase the number of resources for multicast services in the VS.
    • Multicast services share extended TCAM resources with the Ethernet virtual network (EVN) feature. If multicast services occupy a certain number of extended TCAM resources on an LPU, the system displays a message indicating configuration conflict when EVN is configured on the LPU. To prevent this problem, set the number of extended TCAM resources for multicast services to 0 on the LPU with EVN configured, and then reset the LPU for the configuration to take effect.
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 38044

Downloads: 13

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next