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

S7700 and S9700 V200R013C00

This document describes the configurations of IP multicast, including IP multicast basics, IGMP, MLD, IPv4 PIM, IPv6 PIM, MSDP, multicast VPN, layer 3 multicast CAC, IPv4 multicast route management, IPv6 multicast route management, IGMP snooping, MLD snooping, static multicast MAC address, multicast VLAN replication, layer 2 multicast CAC, 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 IPv4 PIM

Licensing Requirements and Limitations for IPv4 PIM

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.

Generally, IPv4 PIM is configured on a device that needs to run IPv4 PIM to monitor and maintain multicast forwarding paths.

License Requirements

IPv4 PIM is a basic feature of a switch and is not under license control.

Version Requirements

Table 4-3  Products and versions supporting IPv4 PIM
Product Product Model Software Version

S7703, S7706, and S7712

V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00

S7703 PoE


S7706 PoE



S9703, S9706, and S9712

V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00, V200R013C00

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

Feature Limitations

  • V200R005 and later versions support IPv4 PIM configuration on physical interfaces that have been switched to Layer 3 mode using the undo portswitch command.
  • Since V200R010, X series cards support IPv4 PIM configuration on dot1q and QinQ termination sub-interfaces only when the VLAN tag to be terminated (or both inner and outer VLAN tags on the QinQ termination sub-interface) is a single VLAN ID, but not a range of VLAN IDs. Sub-interfaces running PIM can only be used as inbound interfaces of multicast streams and cannot be used as outbound interfaces. Cards other than the X series also support IPv4 PIM command configuration on dot1q and QinQ termination sub-interfaces, but they do not support multicast traffic forwarding on these sub-interfaces.
  • PIM-DM and PIM-SM cannot be configured simultaneously in a VPN instance or the public network instance. IPv4 PIM can be configured in a VPN instance, but the VPN instance cannot be bound to a physical interface that has been switched to Layer 3 mode using the undo portswitch command.
  • The VLANIF interface corresponding to the super VLAN cannot be used as an inbound interface of multicast data packets, that is, interface facing the multicast source.
  • A PIM Domain cannot run PIM-DM and PIM-SM simultaneously.
  • If both Layer 2 and Layer 3 multicast services are required in a VLAN, enable IPv4 PIM on the corresponding VLANIF interface first, and then enable IGMP snooping in the VLAN. If IGMP snooping is enabled in the VLAN first, IPv4 PI cannot be enabled on the VLANIF interface.
  • When you configure PIM over GRE on a non-X series card, note the following: If the source interface of the tunnel interface is a Layer 3 physical interface running PIM, the tunnel interface cannot forward multicast traffic.
Updated: 2019-04-08

Document ID: EDOC1100065742

Views: 42754

Downloads: 40

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