< Home

Licensing Requirements and Limitations for Static Multicast MAC Addresses

Involved Network Elements

An IPv4 multicast network consists of the following network elements:
  • Multicast source

    A device that sends multicast data to receiver hosts. For example, a video server is a multicast source.

  • IPv4 Protocol Independent Multicast (PIM) device

    A device that uses the IPv4 PIM protocol to generate and maintain 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.

  • Multicast Source Discovery Protocol (MSDP) device

    A device that forwards multicast data from one PIM network to another. For example, if multicast data needs to be transmitted between two autonomous systems (ASs), the devices at the border of the ASs must run the MSDP protocol.

  • Multicast VPN device

    Multicast VPN enables multicast data of a private network to be transmitted over a public network. Multicast VPN 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 needs to be configured on the PE devices.

  • IGMP querier

    A device that 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 the multicast groups that users want to join, and therefore cannot establish multicast forwarding paths.

  • IGMP snooping device

    A device that 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, it is recommended that you configure IGMP snooping on Layer 2 devices.

  • Receiver

    A multicast user that receives multicast data. A receiver can be a PC, a set top box, or any device with multicast client installed.

An IPv6 multicast network consists of the following network elements:
  • Multicast source

    A device that sends multicast data to receiver hosts. For example, a video server is a multicast source.

  • IPv6 Protocol Independent Multicast (PIM) device

    A device that uses the IPv6 PIM protocol to generate and maintain 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

    A device that exchanges MLD 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 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.

  • MLD snooping device

    A device that listens to 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

    A multicast user that receives multicast data. A receiver can be a PC, a set top box, or any device with multicast client installed.

Static multicast MAC address binding is a Layer 2 multicast feature. Similar to IGMP/MLD snooping, this feature is also used to reduce bandwidth consumption caused by broadcast of multicast data packets on a Layer 2 network.

Licensing Requirements

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

Feature Support in V200R019C10

All models of S2720, S5700, and S6700 series switches support Static multicast MAC address.

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

When configuring static multicast MAC addresses, pay attention to the following points:

  • Static multicast MAC address binding is a Layer 2 multicast feature, so all the static multicast MAC address configurations on interfaces mentioned in this chapter are performed on Layer 2 physical interfaces, including Eth-Trunk interfaces.
  • In V200R002 and later versions, IP multicast MAC addresses (IPv4 multicast MAC addresses starting with 0x01-00-5e or IPv6 multicast MAC addresses starting with 0x3333) can be configured as static MAC addresses. When configuring an IP multicast MAC address as a static multicast MAC address on an interface, ensure that IGMP/MLD snooping is not enabled in the VLAN to which the interface belongs.
  • A static multicast MAC address you configure must be a multicast MAC address with the rightmost bit as 1 (xxxx xxx1).
  • The VLAN specified in the static multicast MAC address configuration command cannot be a super-VLAN or control VLAN of a Smart Ethernet Protocol (SEP) segment, control VLAN of an Ethernet Ring Protection Switching (ERPS) ring, or control VLAN of a Rapid Ring Protection Protocol (RRPP) ring.
  • Before configuring static multicast MAC addresses on an interface of the S2720-EI (V200R011C10 and later versions), S5700S-28X-LI-AC, S5700S-52X-LI-AC, S5710-X-LI, S5720-LI, S5720S-LI, S6720-LI, S6720S-LI, S6720-SI, S6720S-SI, S5700-SI, S5720S-SI, S5720-SI, S5720I-SI, S5720I-SI, S5730-SI, and S5730S-EI, set the multicast data forwarding mode to MAC address based mode in the VLAN to which the interface belongs.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >