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 Static Multicast MAC Addresses

Licensing Requirements and Limitations for Static Multicast MAC Addresses

Involved Network Elements

An IPv4 multicast network may have the following network elements:
  • Multicast source: sends multicast data to receiver hosts. A video server is an example of a multicast source.
  • Device running IPv4 Protocol Independent Multicast (PIM): uses the IPv4 PIM protocol to generate multicast routing entries and forwards multicast data based on multicast routing entries. On an IPv4 multicast network, all Layer 3 devices must run IPv4 PIM; otherwise, multicast forwarding paths cannot be established.
  • Device running the Multicast Source Discovery Protocol (MSDP): forwards multicast data from one PIM network to another. MSDP is mainly used on large-scale networks. If multicast data needs to be transmitted between two autonomous systems (ASs), the devices at the border of the two ASs must run the MSDP protocol.
  • Device running multicast VPN: enables multicast data of a private network to be transmitted over a public network in multicast mode. Such devices are used on VPN networks. For example, if two sites of a VPN network need to exchange multicast data across a public network, multicast VPN must be configured on the provider edge (PE) devices.
  • IGMP querier: exchanges IGMP messages with receiver hosts to create and maintain group memberships. On a multicast network, Layer 3 devices connected to network segments of receivers must run the IGMP protocol or be configured with static IGMP groups. Otherwise, upstream PIM devices cannot know which multicast groups users want to join, and therefore cannot establish multicast forwarding paths.
  • Device running IGMP snooping: listens to IGMP 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, configure IGMP snooping on Layer 2 devices.
  • Receiver: receives multicast data. A receiver can be a PC, a set top box, or any device with a multicast client installed.

Licensing Requirements

Static multicast MAC address binding is a basic feature of a device and is not under license control.

Version Requirements

Table 12-1 Products and minimum versions supporting this feature


Minimum Version Required









Feature Limitations

  • Because static multicast MAC address is a Layer 2 multicast feature, all the static multicast MAC address configurations on interfaces mentioned in this chapter are performed on Layer 2 physical interfaces, including Eth-Trunk interfaces.
  • Before configuring a static multicast MAC address on an interface, ensure that the interface does not belong to a super VLAN.
  • If the static multicast MAC address configured on an interface is an IPv4 multicast MAC address (starting with 0x0100-5e and ending with bit 0), the validity of the static multicast MAC address in different scenarios is listed in the following table.


    Valid or invalid

    No other multicast services configured


    Layer 3 multicast or both Layer 2 and Layer 3 multicast configured


    IP address-based Layer 2 multicast forwarding


    MAC address-based Layer 2 multicast forwarding

    Valid, but may cause conflicts

    A conflict occurs in the following situation: If Internet Group Management Protocol (IGMP) snooping is enabled and Layer 2 multicast forwarding mode is set to MAC address based mode, the switch generates IPv4 multicast MAC address entries with MAC addresses starting with 0x0100-5e. When a static multicast MAC address is configured, a conflict may occur, causing data forwarding errors. For example, VRRP sends protocol packets using IP multicast address, which is mapped to IP multicast MAC address 01-00-5E-00-00-12. If this IP multicast MAC address is configured as a static multicast MAC address on an interface, VRRP protocol packets cannot be forwarded normally.

  • When you configure IPv4 multicast together with other services, pay attention to the following points:
    • An M-LAG does not support static multicast MAC addresses.
    • 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: 45997

Downloads: 13

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