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 Multicast Network Management

Licensing Requirements and Limitations for Multicast Network Management

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

Multicast network management is a basic feature of a device and is not under license control.

Version Requirements

Table 14-1 Products and minimum versions supporting this feature

Product

Minimum Version Required

CE12804/CE12808/CE12812

V100R001C00

CE12816

V100R003C00

CE12804S/CE12808S

V100R005C00

CE12800E

V200R002C50

Feature Limitations

  • When configuring multicast functions, you may need to adjust the (S, G) or (*, G) entry timeout period based on the number of multicast entries used on your network. To set the (S, G) or (*, G) entry timeout period, run the source-lifetime interval command in the PIM view of the public network instance or a VPN instance. The following table lists the recommended timeout period values in different conditions. In this table, the number of entries refers the total number of multicast entries in public network instances and VPN instances of all VSs in the system.

    Number of Entries

    Recommended Timeout Period

    Within 1000

    Default value

    1000 to 2000

    1000 seconds

    2000 to 8000

    2000 seconds

    More than 8000

    4000 seconds

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

    Item

    Precautions

    IPv4 Layer 3 multicast is deployed with M-LAG

    In versions earlier than V100R006C00, an M-LAG set up with standalone switches or stack systems does not support IPv4 Layer 3 multicast.

    In V100R006C00 and later versions, an M-LAG set up with standalone switches or stack systems supports IPv4 Layer 3 multicast. Pay attention to the following points:

    • The M-LAG master and backup devices must have the same multicast configuration.
    • On the M-LAG master and backup devices, PIM-SM and IGMP must be enabled on all the VLANIF interfaces that need to run Layer 3 multicast services, and IGMP snooping must be enabled in the corresponding VLANs.
    • The PIM silent function must be configured on the user-side interfaces of the M-LAG master and backup devices.
    • In addition to the peer-link, there must be a direct Layer 3 link between the M-LAG master and backup devices, and PIM must be enabled on the interfaces at both ends of the Layer 3 link.
    • If the Layer 3 link is established between VLANIF interfaces of the M-LAG master and backup devices, STP must be disabled on the VLANIF interfaces, and the corresponding VLAN of the VLANIF interfaces 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.

    On the network when the Receiver is dual-homed to an M-LAG:

    • In versions earlier than V200R003C00, only the M-LAG master member interface forwards multicast traffic to the Receiver.
    • In V200R003C00 and later versions, 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 decimal number of the multicast group address is an odd number, such as the address 225.1.1.1, the M-LAG master member interface forwards the multicast traffic. If the last decimal number of the multicast group address is an even number, such as the address 225.1.1.2, the M-LAG backup member interface forwards the multicast traffic.
    • If the M-LAG master and backup devices run different versions, the multicast traffic forwarding rule is subject to the device running the earlier version.

    IPv4 multicast is deployed with VXLAN

    When configuring multicast replication mode of intra-subnet BUM traffic, ensure that the multicast replication address specified by mcast-group is different from the requested multicast group address. Otherwise, the receiver may receive VXLAN-encapsulated BUM packets.

    Precautions related to resource usage

    • 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: 37206

Downloads: 13

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