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

CLI-based Configuration Guide - IP Multicast

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document describes the principles and configurations of IP multicast, and provides configuration examples.
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 Inter-AS MVPN Option B

Configuring Inter-AS MVPN Option B

Configuring inter-AS MVPN Option B on PEs and ASBRs allows MVPN data to be carried across ASs.

Context

On an inter-AS VPN Option B network, three independent tunnels are used to transmit public network data between two ASs. A P device in an AS cannot obtain routing information of the other AS, and an ASBR in an AS cannot obtain the routes to PEs in the other AS. As a result, the P and ASBR cannot find the next hop of the route towards the multicast source when sending it a PIM Join message, and therefore no MDT can be set up. So, after configuring BGP A-D MVPN, you must enable PIM RPF Vector (with RD information) in VPN instances to implement inter-AS MVPN.

Before configuring inter-AS MVPN Option B, configure inter-AS VPN Option B. For configuration details, see the chapter "Configuring Inter-AS VPN Option A" in the BGP/MPLS IP VPN Configuration of the Huawei AR Series Access Routers CLI-based Configuration - VPN.

Perform the following steps on PEs except the steps on ASBRs.

Procedure

  1. Enable IPv4 multicast routing.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    3. Run:

      ipv4-family

      The IPv4 address family is enabled for the VPN instance and the VPN instance IPv4 address family view is displayed.

    4. Run:

      route-distinguisher route-distinguisher

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

    5. Run:

      multicast routing-enable

      IPv4 multicast routing is enabled in the VPN instance.

  2. Run:

    multicast-domain share-group group-address binding mtunnel number

    A share-group is configured and bound to an MTI.

  3. Configure an MTI.

    A Multicast Tunnel Interface (MTI) can be configured either automatically or manually. If both manual and automatic MTI configurations exist, the manual configuration takes precedence over the automatic configuration.

    • Automatic configuration

    1. Run:

      multicast-domain source-interface interface-type interface-number

      The interface from which an MTI borrows an IP address is specified.

    2. Run:

      quit

      Return to the VPN instance view.

    3. Run:

      quit

      Return to the system view.

    • Manual configuration

    1. Run:

      quit

      Return to the VPN instance view.

    2. Run:

      quit

      Return to the system view.

    3. Run:

      interface mtunnel number

      The MTI interface view is displayed.

    4. Run:

      ip address ip-address { mask | mask-length }

      Or,

      ip address unnumbered interface interface-type interface-number

      An IP address is configured for the MTI.

    5. (Optional) Run:

      mtu mti-mtu

      An MTU is configured for the MTI.

      Configuring a small MTU for the MTI can prevent multicast packets from being fragmented and re-assembled again in public network, improving transmission efficiency.

      The default MTU is 1472 bytes.

    6. Run:

      quit

      Return to the system view.

  4. Configure BGP A-D MVPN (MDT-SAFI A-D mode).

    Perform the following steps on a PE:

    1. Run:

      bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    2. Run:

      ipv4-family mdt

      The BGP-MDT address family view is displayed.

    3. Run:

      peer { group-name | ipv4-address } enable

      The PE is enabled to exchange routing information with a specified peer or peer group.

      NOTE:

      If there are more than one peer or peer group, run this command many times to make that all peers or peer groups can exchange routing information.

    4. Run:

      quit

      Return to the BGP view.

    5. Run:

      quit

      Return to the system view.

    6. Run:

      ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    7. Run:

      ipv4-family

      An IPv4 address family is enabled for the VPN instance and the VPN instance IPv4 address family view is displayed.

    8. Run:

      auto-discovery mdt [ import route-policy route-policy-name ]

      The MDT-SAFI A-D mode is configured.

    Perform the following steps on an ASBR:

    1. Run:

      bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

    2. Run:

      ipv4-family mdt

      The BGP-MDT address family view is displayed.

    3. Run:

      undo policy vpn-target

      VPN target-based filtering is disabled for received VPN routes or label blocks.

    4. Run:

      peer { group-name | ipv4-address } enable

      The ASBR is enabled to exchange routing information with a specified peer or peer group.

      NOTE:

      If there are more than one peer or peer group, run this command many times to make that all peers or peer groups can exchange routing information.

    5. (Optional) Run:

      peer { group-name | ipv4-address | ipv6-address } next-hop-local

      The ASBR is configured to set its IP address as the next-hop addresses of routes when advertising these routes to an IBGP peer or peer group.

  5. Enable PIM RPF Vector (with RD information) function.
    1. Run:

      quit

      Return to the VPN instance view.

    2. Run:

      quit

      Return to the system view.

    3. Run:

      pim vpn-instance vpn-instance-name

      The PIM view of the VPN instance is displayed.

    4. Run:

      rpf-vector rd

      The PIM RPF Vector function (with RD information) is enabled.

    5. (Optional) Run:

      rpf-vector compatible standard

      The standard format is used to encapsulate packets.

      By default, a private format is used to encapsulate packets.

Translation
Download
Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 21337

Downloads: 403

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