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

Reminder

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

upgrade

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 IGMP Snooping

Licensing Requirements and Limitations for IGMP Snooping

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

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

Version Requirements

Table 10-5 Products and minimum versions supporting IGMP snooping in a VLAN

Product

Minimum Version Required

CE12804/CE12808/CE12812

V100R001C00

CE12816

V100R003C00

CE12804S/CE12808S

V100R005C00

CE12800E

V200R002C50

Feature Limitations

  • 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.
  • After PIM-DM is enabled on a VLANIF interface, IGMP snooping cannot be enabled in the corresponding VLAN. Similarly, after IGMP snooping is enabled in a VLAN, PIM-DM cannot be enabled on the corresponding VLANIF interface.
  • In the scenario when both 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:
    • IGMP snooping must be enabled in a VLAN.
    • PIM (PIM-SM or Bidir-PIM) and IGMP must be enabled on the corresponding VLANIF interface.
  • When configuring the multicast data forwarding mode (IP address-based or MAC address-based) in a VLAN, pay attention to the following points:
    • Configure the forwarding mode of multicast flows in the VLAN before IGMP snooping is enabled in the VLAN. Enable IGMP snooping in the VLAN for the configuration to take effect.

    • If the VLAN is configured as a customer edge (CE) VLAN of Transparent Interconnection of Lots of Links (TRILL) and enabled with IGMP snooping, the multicast packets in the VLAN are forwarded based on MAC addresses, and the forwarding mode cannot be changed.

    • Multiple IPv4 multicast addresses may be mapped to the same IPv4 multicast MAC address according to the multicast IP-and-MAC address mapping mechanism. When the MAC address-based multicast forwarding mode is used in a VLAN and a group IP address for receivers and the multicast IP address reserved for a protocol are mapped to the same IP multicast MAC address, the protocol cannot run normally. For example, IP multicast address 224.0.0.5 is reserved for the OSPF protocol. If a multicast group uses IP multicast address 225.0.0.5, the two IP multicast addresses are both mapped to IP multicast MAC address 01-00-5E-00-00-05. In this case, the OSPF protocol cannot run normally. Make an appropriate IP multicast address plan to prevent this problem.

    • When the MAC address-based multicast forwarding mode is used in a VLAN, the IGMP snooping version cannot be set to v3.
    • A multichassis link aggregation group (M-LAG) system does not support multicast data forwarding based on multicast MAC addresses.
    • When MAC address-based multicast forwarding is configured in a VLAN, multicast forwarding entry creation cannot be triggered by data traffic, but is triggered upon receiving user requests. If no user orders a program, multicast traffic is broadcast in the VLAN by default.
  • If Layer 3 multicast functions (such as IGMP and PIM) are enabled on a VLANIF interface, the corresponding VLAN does not support configuration of an IGMP snooping querier, Report and Leave message suppression, or IGMP snooping proxy. Similarly, if any of the preceding functions is made in a VLAN, Layer 3 multicast functions cannot be enabled on the corresponding VLANIF interface.
  • If a multicast network already has an IGMP querier, it is not recommended to configure an IGMP snooping querier, because the configuration will cause re-election of the IGMP querier. If you configure an IGMP 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 IGMP querier.
  • When configuring IGMP snooping on an M-LAG, ensure that the IGMP snooping querier or IGMP snooping proxy configuration is consistent on the M-LAG master and backup devices.
  • The following pairs of functions cannot be configured in the same VLAN:
    • IGMP snooping querier and IGMP snooping proxy
    • Report and Leave message suppression and IGMP snooping proxy
  • IGMP snooping cannot be used with VLAN mapping.
  • 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.
  • 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.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 44227

Downloads: 13

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