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.


S600-E V200R012C00 Configuration Guide - IP Multicast

This document describes the configurations of IP multicast, including IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN replication, controllable multicast, 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 IGMP Snooping

Licensing Requirements and Limitations for IGMP Snooping

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.

The "IGMP Snooping Configuration" section describes how to configure IGMP snooping on a Layer 2 device.

License Requirements

IGMP snooping is a basic feature of a switch and is not under license control.

Version Requirements

Table 1-5  Products and versions supporting IGMP snooping
Product Model Software Version

V200R010C00, V200R011C00, V200R011C10, V200R012C00

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

Feature Limitations

When configuring IGMP snooping, pay attention to the following points:

  • Because IGMP snooping is a Layer 2 multicast feature, all the IGMP snooping configurations on interfaces mentioned in this chapter are performed on Layer 2 physical interfaces, including Eth-Trunk interfaces.
  • Layer 2 multicast can be configured for the dynamic VLAN delivered in NAC authentication only in V200R011C00 and later versions, but not in versions earlier than V200R011C00.
  • If a switch running IGMP snooping receives IGMPv1 or IGMPv2 Report messages with SSM group addresses (default range:, the switch does not create Layer 2 multicast forwarding entries.
  • On a ring network running IGMP snooping, if the downstream port of a device is configured as a static router port, downstream ports of all devices on the ring network must be configured as static router ports. Otherwise, multicast traffic cannot be forwarded normally if the Layer 2 network topology changes. Therefore, it is not recommended to configure downstream ports as static router ports.
  • If both Layer 2 and Layer 3 multicast services are required in a VLAN, enable IGMP and PIM(IPv4) on the corresponding VLANIF interface first, and then enable IGMP snooping in the VLAN. If IGMP snooping is enabled in the VLAN first, IGMP and PIM (IPv4) cannot be enabled on the VLANIF interface.
  • On a switch running IGMP snooping, multicast flows that are not requested by users are considered unknown multicast flows. Multicast flows are considered unknown if they do not match any entry in the multicast forwarding table or if they match multicast forwarding entries with an empty outbound interface list. These flows are not requested by users. The default method that a switch uses to process unknown IPv4 multicast flows depends on whether Layer 2 multicast is enabled and which Layer 2 multicast forwarding mode is used:
    • If Layer 2 multicast is not enabled on a switch, the switch broadcasts unknown multicast flows.

    • If Layer 2 multicast is enabled on a switch, the switch broadcasts unknown multicast flows in a VLAN, regardless of which Layer 2 multicast forwarding mode is used.

    To prevent broadcast of unknown multicast flows, run the multicast drop-unknown command in a VLAN or run the unknown-frame multicast drop command in a VSI to configure a switch to drop unknown multicast flows.

Updated: 2018-09-01

Document ID: EDOC1100037948

Views: 13235

Downloads: 5

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