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 V200R005C00

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).
Configuring a VXLAN I-PMSI Tunnel

Configuring a VXLAN I-PMSI Tunnel

Context

In a distributed VXLAN gateway scenario, PMSI tunnels are logical tunnels used for a VXLAN underlay network to carry VPN-based multicast data. An I-PMSI tunnel connects all PEs on the same MVPN. Therefore, all PEs on the same MVPN can receive multicast data traffic from the I-PMSI tunnel. Considering that VXLAN tunnels have been established between PEs functioning as VXLAN gateways, VXLAN is used to establish I-PMSI tunnels.

Perform the following steps on each of the PEs functioning as VXLAN gateways:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast mvpn mvpn-id

    An MVPN ID is configured.

    By default, no MVPN ID is configured.

    An MVPN ID is the IP address of the originator PE on an MVPN. An MVPN ID is mainly used as the Administrator field value in the VRF Route Import extended community attribute. If no MVPN ID is configured, BGP EVPN routes and C-multicast routes sent by a PE cannot carry the VRF Route Import extended community attribute.

    VRF Route Import is an extended MVPN community attribute used to advertise and receive C-multicast routes. In a VXLAN-based Layer 3 multicast scenario, this attribute is contained in a BGP EVPN route that a sender PE advertises to a receiver PE. Upon receipt of the BGP EVPN route, the receiver PE saves the attribute and carries this attribute in a C-multicast route when sending this route to the sender PE. When there are multiple sender PEs, each sender PE that receives a C-multicast route can determine, according to this attribute, whether the C-multicast route should be processed by itself and which VPN routing table that the C-multicast route should be installed into. The VRF Route Import extended community is in the format of Administrator field: Local Administrator field, where Administrator field represents the local device's MVPN ID.

    NOTE:

    The MVPN ID configured on a distributed VXLAN gateway must be the same as the gateway's VTEP IP address. If VXLAN gateways are deployed in M-LAG active-active mode, the master and backup gateways must have the same VTEP IP address.

  3. Run ip vpn-instance vpn-instance-name

    The VPN instance view is displayed.

  4. Run ipv4-family

    The VPN instance IPv4 address family view is displayed.

  5. Run route-distinguisher route-distinguisher

    An RD is configured for the VPN instance IPv4 address family.

    By default, no RD is configured for the VPN instance IPv4 address family.

    A VPN instance IPv4 address family takes effect only after having an RD configured. The RD of each VPN instance must be unique on a PE.

  6. Run multicast routing-enable

    Multicast routing is enabled for the VPN instance IPv4 address family.

    By default, multicast routing is not enabled for a VPN instance IPv4 address family.

  7. Run multicast mvpn route-import local-admin-id local-admin-id

    A local VPN instance ID of the sender PE on the MVPN is configured.

    By default, no local VPN instance ID is configured for a sender PE on an MVPN.

    The VRF Route Import extended community is in the format of Administrator field: Local Administrator field, where Local Administrator field represents the sender PE's local VPN instance ID.

    NOTE:

    A local VPN instance cannot share the same local-admin-id value with other VPN instances.

  8. Run mvpn

    The VPN instance IPv4 address family MVPN view is displayed.

  9. (Option) Run vpn-target vpn-target &<1-8> [ both | export-extcommunity | import-extcommunity ]

    An MVPN target is configured for the VPN instance MVPN address family.

    By default, no MVPN target is configured for the VPN instance MVPN address family. The VPN instance MVPN address family uses the VPN target configured in the VPN instance IPv4 address family view as the MVPN target.

    MVPN targets control MVPN route learning between MVPN sites. An MVPN target can be an import or export MVPN target. An export MVPN target is contained in an MVPN route to be advertised to a remote BGP MVPN peer. After receiving an MVPN route, a BGP MVPN peer compares the received export MVPN target with the local import MVPN target to determine whether the MVPN route can be added to the MVPN routing table of the local VPN instance.

    When the routes of a VPN instance MVPN address family need to be isolated from those of an IPv4 address family belonging to the same VPN instance, perform this step for configure an MVPN target for the VPN instance MVPN address family.

  10. Run c-multicast signaling bgp

    BGP is configured as the signaling protocol for transmitting C-multicast routes.

    By default, no signaling protocol is configured for transmitting C-multicast routes.

    In an IPv4 Layer 3 multicast over VXLAN scenario, after receiving a PIM Join/Prune message or IGMP Join message from a VPN, a receiver PE converts the PIM Join/Prune message into a C-multicast route and sends the C-multicast route to a multicast source-side PE. To configure a signaling protocol for transmitting the C-multicast route, run the c-multicast signaling command.

  11. (Optional) Run auto-discovery inter-as

    Inter-AS automatic discovery is enabled.

    By default, inter-AS automatic discovery is disabled.

    In a scenario where an NG MVPN crosses different ASs, to enable PEs in different ASs to exchange Intra-AD routes for automatic MVPN peer discovery, perform this step.

  12. (Optional) Run spt-only mode

    The PIM SM MDT is configured not to be set up across the public network.

    If a receiver uses the (S, G) join mode, skip this step. By default, no PIM-SM MDT is set up on a multicast network.

    If a receiver uses the (*, G) join mode, perform this step to configure a PIM-SM MDT setup mode.

  13. (Option) Run import msdp

    The function of transmitting (S, G) entry information in Multicast Source Discovery Protocol (MSDP) Source Active (SA) messages to the remote PE through BGP Source Active A-D routes is enabled.

    By default, (S, G) entry information in MSDP SA messages is not transmitted to the remote PE through BGP Source Active A-D routes.

    If PIM-SM MDT setup is not across the public network, you can configure a PE or CE as a VPN instance's rendezvous point (RP). If a CE is configured as an RP, the CE needs to establish an MDSP peer relationship with its connected PE and transmit (S, G) entry information to the PE through MSDP SA messages. To enable this PE to transmit the (S, G) entry information to the remote PE through BGP Source Active A-D routes, perform this step.

  14. (Option) Run export msdp

    The function of transmitting (S, G) entry information in BGP Source Active A-D routes to the RP through MSDP SA messages is enabled.

    By default, (S, G) entry information in BGP Source Active A-D routes are not transmitted to the RP through MSDP SA messages.

    If PIM-SM MDT setup is not across the public network, you can configure a PE or CE as a VPN instance's RP. If a CE is configured as an RP, the CE needs to establish an MDSP peer relationship with its connected PE. To enable this PE to transmit (S, G) entry information in BGP Source Active A-D routes to the CE configured as the RP, perform this step.

  15. (Option) Run rpt-prune-delay delay-time

    A pruning delay time is configured when the RPT switches to SPT in a scenario where a PIM-SM MDT is set up across the public network.

    By default, the pruning delay time is 60 seconds.

  16. Run ipmsi-tunnel

    The MVPN I-PMSI view is displayed.

  17. Run vxlan static

    VXLAN is configured as the protocol for establishing an I-PMSI tunnel.

    By default, no protocol is specified for establishing an I-PMSI tunnel.

  18. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100039595

Views: 47679

Downloads: 85

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