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 VPN

Licensing Requirements and Limitations for Multicast VPN

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

The multicast VPN feature can be used only after the MPLS feature is enabled, whereas the MPLS feature is under license control. By default, the MPLS feature is disabled on a newly purchased switch. To use the MPLS feature, apply for and purchase the license from the equipment supplier.

Version Requirements

Table 7-5 Products and minimum versions supporting multicast VPN
Product Minimum Version Required
CE12804/CE12808/CE12812/CE12816/CE12804S/CE12808S V100R005C10

Feature Limitations

  • Multicast VPN cannot be used together with VXLAN or EVN.
  • A multichassis link aggregation group (M-LAG) does not support multicast VPN.
  • If MD-based multicast VPN is used on network devices, Protocol Independent Multicast Dense Mode (PIM-DM) and Source-Specific Multicast (SSM) model of Protocol Independent Multicast Sparse Mode (PIM-SM) cannot be used on the public network.
  • Multicast VPN cannot be deployed on BGP/MPLS IPv6 VPN networks.
  • To use the multicast VPN function, you need to run the ip tunnel mode gre command on PE devices to change the tunnel mode to GRE. By default, the tunnel mode on CE12800 series switches is Virtual Extensible Local Area Network (VXLAN).
  • After multicast VPN is configured, multicast traffic may be circulated once during the forwarding process, resulting in reduced forwarding capabilities of the cards.
  • When deploying multicast VPN on a provider edge (PE) device, you are advised not to configure the PE device as the designated router (DR) for a multicast source on the private network. If the PE device is already used as a source DR on the private network, you are advised to deploy the interface that functions as the source DR and the interface connected to the public network on different Line Processing Units (LPUs). Otherwise, since VPN service entries are much more than public network service entries, it may take a long time to recover traffic forwarding after a restart of the PE device.
  • After multicast VPN is configured on a switch, removing interfaces from virtual systems (VSs) is not recommended, because this operation may cause loss of multicast data packets.
  • 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.
  • 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

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100074724

Views: 45729

Downloads: 13

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