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 IP Multicast Over VXLAN

Licensing Requirements and Limitations for IP Multicast Over VXLAN

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.
  • 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

Before deploying IP multicast over VXLAN, ensure that the virtual extensible LAN (VXLAN) feature has been deployed on the network. The VXLAN functions on devices are under license control. By default, the VXLAN functions are not enabled on a newly bought device. You can contact the device reseller and purchase licenses. For more information about the licensing requirements for VXLAN functions, see Licensing Requirements and Limitations for VXLANS in CloudEngine 8800, 7800, 6800, and 5800 Series Switches Configuration Guide-VXLAN.

Version Requirements

Table 14-12 Products and minimum versions supporting IPv4 Layer 3 multicast over VXLAN

Product

Minimum Version Required

CE8860EI/CE8850EI/CE7855EI/CE7850EI/CE6875EI/CE6870EI/CE6865EI/CE6860EI/CE6856HI/CE6855HI/CE6851HI/CE6850U-HI/CE6850HI

V200R005C00

CE6857EI

V200R005C10

CE8861EI/CE8868EI

V200R005C10

Table 14-13 Products and minimum versions supporting IGMP snooping over VXLAN

Product

Minimum Version Required

CE6850HI/CE6850U-HI/CE6851HI/CE6855HI/CE6856HI/CE6860EI/CE6870EI

V200R002C50

CE6857EI

V200R005C10

CE6865EI

V200R005C00

CE6875EI

V200R003C00

CE7850EI/CE7855EI/CE8850-32CQ-EI/CE8860EI

V200R002C50

CE8850-64CQ-EI

V200R005C00

CE8861EI/CE8868EI

V200R005C10

Feature Limitations

Limitations on IP Multicast Over VXLAN

Before deploying IP multicast over VXLAN, ensure that the VXLAN feature has been deployed on the network. For details about the VXLAN-related feature dependencies and limitations, see Licensing Requirements and Limitations for VXLANs in CloudEngine 8800, 7800, 6800, and 5800 Series Switches Configuration Guide-VXLAN.

Limitations on IPv4 Layer 3 Multicast Over VXLAN
  • IPv4 Layer 3 multicast over VXLAN can be deployed on standalone devices, stack systems, or M-LAG. The two devices that form an M-LAG system must both have a service loopback interface configured or neither of them has a service loopback interface configured. An M-LAG system needs to be comprised of identical switch models.
  • The device supports only IPv4 Layer 3 multicast over IPv4 VXLAN in the distributed VXLAN gateway scenario. Both the overlay network and underlay network must be IPv4 networks.
  • When IPv4 Layer 3 multicast over VXLAN is configured on a VXLAN tunnel endpoint (VTEP), the multicast source or receiver can join a BD only through a Layer 2 sub-interface and cannot join a BD through binding between a VLAN and BD.
  • A multicast source can be dual-homed to VXLAN active-active devices through an M-LAG, and cannot be connected to multiple VTEPs in other modes.
  • IPv4 Layer 3 multicast over VXLAN requires the VTEP to encapsulate multicast traffic into BUM multicast replication packets (outer encapsulation destination IP address: address of the underlay multicast group). The underlay multicast group addresses (specified by mcast-group) corresponding to a same Layer 3 VNI must be the same, whereas the underlay multicast group addresses (specified by mcast-group) corresponding to different Layer 3 VNIs can be the same or different. Note that the multicast group address of public network users' video on demand (VOD) service must not be the same as the multicast replication address (mcast-group) of BUM packets. Otherwise, the BUM packets encapsulated in VXLAN packets may be forwarded to the public network user side.
  • Note the following when deploying IPv4 Layer 3 multicast over VXLAN on the CE8860EI, CE8850EI, CE7855EI, CE7850EI, CE6860EI, CE6856HI, CE6855HI, CE6851HI, CE6850HI, or CE6850U-HI. The following limitations do not apply when deploying IPv4 Layer 3 multicast over VXLAN on other switch models.
    • When these devices function as Layer 3 VXLAN gateways, configure loopback interfaces on them.
    • The CE8860EI, CE8850EI, CE7855EI, CE7850EI, CE6860EI, CE6856HI, CE6855HI, CE6851HI, CE6850HI, and CE6850U-HI forward multicast traffic based on MAC addresses, and they do not support the following networking modes and IGMPv3. Therefore, avoid the following networking modes during network planning when the preceding models are involved.
      • Same multicast group address but different multicast source addresses, for example, (192.168.1.1, 224.0.1.1) and (192.168.2.1,224.0.1.1)
      • Same multicast source address but different multicast group address, with multicast group addresses being mapped to the same multicast MAC address, for example, (192.168.1.1, 224.0.1.1) and (192.168.1.1, 225.0.1.1)
      • Different multicast source addresses and different multicast group addresses, with multicast group addresses being mapped to the same multicast MAC address, for example, (192.168.1.1, 224.0.1.1) and (192.168.2.1, 225.0.1.1), as shown in Figure 14-16
      Figure 14-16 Different multicast source addresses and different multicast group addresses, with multicast group addresses being mapped to the same multicast MAC address

  • Among PIM protocols, only PIM SM (ASM or SSM model) is supported on the overlay and underlay networks after IPv4 Layer 3 multicast over VXLAN is configured. PIM DM and Bidir-PIM are not supported. If the overlay network is running PIM-SM in the ASM model, the rendezvous points (RPs) must be in the same L3VPN instance or the routes of the local L3VPN instance must be reachable.
  • The MVPN ID configured on the distributed VXLAN gateway must be the VTEP IP address. If the multi-chassis link aggregation group (M-LAG) (active-active gateways) is deployed, the VTEP IP addresses configured on the master and backup M-LAG devices must be the same.
  • When IPv4 Layer 3 multicast over VXLAN is deployed with M-LAG:
    • 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.
    • In V200R005C00, only the M-LAG master device decapsulates VXLAN multicast packets, and the M-LAG backup device does not. In V200R005C10 and later versions, both the M-LAG master and backup devices decapsulate VXLAN multicast packets.
    • In V200R005C00, an M-LAG member device cannot be configured with both IPv4 Layer 3 multicast over VXLAN and PIM. That is, M-LAG member devices cannot function as the border leaf nodes when running IPv4 Layer 3 multicast over VXLAN. In V200R005C10 and later versions, M-LAG member devices can function as the border leaf nodes when running IPv4 Layer 3 multicast over VXLAN, except the device where the service loopback interface needs to be configured.
    • In V200R005C00, the same Route Distinguisher (RD) must be configured for the VPN instance IPv4 address family on the M-LAG master and backup devices. In V200R005C10 and later versions, if different RDs are configured for the VPN instance IPv4 address family on the M-LAG master and backup devices, you can run the c-multicast ad-route-ignore command to configure a device to ignore the local A-D route check in the route validity check performed after receiving the C-multicast route from a BGP MVPN peer. This command prevents the M-LAG master or backup device from invalidating the C-multicast route.

    • The IPv4 Layer 3 multicast over VXLAN function cannot be upgraded from V200R005C00 to V200R005C10 or later if active-active gateways are deployed using M-LAG. It is recommended that IPv4 Layer 3 multicast over VXLAN be deployed on devices running V200R005C10 or later.
  • A BGP MVPN neighbor relationship cannot be configured in the BGP multi-instance view.
  • When IPv4 Layer 3 multicast over VXLAN is deployed in an M-LAG system, the M-LAG master and backup devices must have the same Route Distinguisher (RD) for the VPN instance IPv4 address family.
  • When the underlay multicast outbound interface is a VLANIF interface, the corresponding VLAN cannot be the default VLAN to which the physical interface is added. Use Layer 3 physical interfaces as underlay multicast outbound interfaces.
  • When a super virtual fabric (SVF) functions as a virtual tunnel end point (VTEP), only the SVF in centralized forwarding mode supports IPv4 Layer 3 multicast in the distributed VXLAN gateway scenario, and the parent switch must support the VXLAN.
  • IPv4 Layer 3 multicast over VXLAN cannot be used together with Segment VXLAN and IGMP snooping over VXLAN services.
Limitations on IGMP Snooping Over VXLAN
  • When IGMP snooping over VXLAN is configured on a VXLAN tunnel endpoint (VTEP), the multicast source or multicast receiver can join a BD only through a Layer 2 sub-interface and cannot join a BD through binding between a VLAN and BD.
  • After IGMP snooping is enabled in a BD, the encapsulation type on the Layer 2 sub-interface bound to the BD cannot be changed and cannot be set to default.
  • After IGMP snooping is enabled in a BD, multicast replication of intra-subnet BUM traffic is not supported in the VNI bound to this BD, but this function is supported in the VNIs bound to other BDs. If both IGMP snooping over VXLAN and multicast replication of intra-subnet BUM traffic are configured on a network, the requested multicast group address must differ from the multicast replication address of BUM traffic specified by mcast-group. If the two addresses are the same, the receiver may receive VXLAN-encapsulated BUM packets.
  • Because the device forwards multicast data packets in a BD based on MAC addresses, do not use a group address on the network if the group address maps to the same multicast MAC address as a multicast IP address reserved for a protocol. Otherwise, the protocol that uses the multicast IP address cannot run normally. For example, Open Shortest Path First (OSPF) uses 224.0.0.5 to send protocol packets. This multicast IP address maps to multicast MAC address 01-00-5E-00-00-05. If multicast data packets are forwarded based on MAC addresses and use multicast IP address 225.0.0.5 (also mapping to 01-00-5E-00-00-05), the OSPF protocol cannot run normally.

  • 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 BD:
    • IGMP snooping querier and IGMP snooping proxy
    • Report and Leave message suppression and IGMP snooping proxy
  • IGMP snooping over VXLAN cannot be used with Segment VXLAN and IPv4 Layer 3 multicast over VXLAN.
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100075361

Views: 25534

Downloads: 33

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