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 8800, 7800, 6800, and 5800 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 IPv6 Multicast Route Management

Licensing Requirements and Limitations for IPv6 Multicast Route Management

Involved Network Elements

An IPv6 multicast network may have the following network elements:
  • Multicast source: sends multicast data to receiver hosts. For example, a video server is a multicast source.
  • Device running IPv6 Protocol Independent Multicast (PIM): uses the IPv6 PIM protocol to generate 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: exchanges MLD messages with receiver hosts to create and maintain group memberships. On an IPv6 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.
  • Device running MLD snooping: listens on 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: multicast users that receive multicast data. A receiver can be a PC, a set top box, or any device with multicast client installed.

Licensing Requirements

IPv6 multicast route management is a basic feature of CE8800, CE7800, CE6800, and CE5800 series switches and is not under license control.

Version Requirements

Table 8-7 Products and minimum versions supporting this feature
Product Minimum Version Required
CE5810EI V100R002C00
CE5850EI V100R002C00
CE5850HI V100R003C00
CE6810EI V100R003C00
CE6850EI V100R002C00
CE6850-48S6Q-HI V100R005C00
CE6850-48T6Q-HI/CE6850U-HI/CE6851HI V100R005C10
CE6855HI V200R001C00
CE6856HI V200R002C50
CE6857EI V200R005C10
CE6860EI V200R002C50
CE6865EI V200R005C00
CE6870-24S6CQ-EI/CE6870-48S6CQ-EI V200R001C00
CE6870-48T6CQ-EI V200R002C50
CE6875EI V200R003C00
CE7850EI V100R003C00
CE7855EI V200R001C00
CE8850-32CQ-EI V200R002C50
CE8850-64CQ-EI V200R005C00
CE8860EI V100R006C00
CE8861EI/CE8868EI V200R005C10

Feature Limitations

  • Before configuring IPv6 multicast route management, enable IPv6 multicast routing.

  • When a CE5855EI switch acts as a leaf switch in an SVF system, its interfaces support IPv6 multicast.

  • In the scenario where Fast Channel Change (FCC) is enabled, it is recommended that you use the multicast ipv6 cpu-forward disable command to disable software forwarding for IPv6 multicast packets.

  • When you configure IPv6 multicast together with other services, pay attention to the following points:
    Table 8-8 Precautions to be observed when you configure IPv6 multicast together with other services

    Item

    Precautions

    IPv6 Layer 3 multicast is deployed with M-LAG

    In versions earlier than V200R003C00, M-LAG does not support IPv6 Layer 3 multicast.

    In V200R003C00 and later versions, for CE6870EI and CE6875EI, an M-LAG set up with standalone switches or stack systems supports IPv6 Layer 3 multicast, and other models do not support IPv6 Layer 3 multicast. Pay attention to the following points:
    • In addition to the peer-link, there must be a direct Layer 3 link between the M-LAG master and backup devices. STP must be disabled on the interfaces at both ends of the Layer 3 link.
    • The M-LAG master and backup devices must have the same multicast configuration.
    • On the M-LAG master and backup devices, IPv6 PIM-SM and MLD must be enabled on all the VLANIF interfaces that need to run Layer 3 multicast services, and MLD snooping must be enabled in the corresponding VLANs.
    • The PIM silent (IPv6) function must be configured on the user-side interfaces of the M-LAG master and backup devices.
    • If the Layer 3 link is established on a VLANIF interface of the M-LAG master and backup devices, the VLANIF interface must run the IPv6 PIM protocol, and the corresponding VLAN cannot be allowed on the peer-link.
    • If the peer-link is selected as the optimal link to the RP or multicast source by the unicast routing protocol, multicast traffic with the peer-link interface as the outbound interface may fail to be forwarded. To prevent this problem, ensure that the Layer 3 link between the M-LAG master and backup devices has a route cost smaller than or equal to the route cost of the peer-link, so that the Layer 3 link is selected as the optimal route by the unicast routing protocol.

    In V200R003C00 and later versions, if the Receiver is dual-homed to an M-LAG:

    Both the M-LAG master and backup member interfaces forward multicast traffic to the Receiver, implementing load sharing. The M-LAG master and backup devices share load according to the following rule: If the last hexadecimal number of the multicast group address is an odd number, such as the addresses FF1E::1 and FF1E::B, the M-LAG master member interface forwards the multicast traffic. If the last hexadecimal number of the multicast group address is an even number, such as the addresses FF1E::2 and FF1E::A, the M-LAG backup member interface forwards the multicast traffic.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 25535

Downloads: 33

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