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).
Inter-AS MVPN

Inter-AS MVPN

Configuring inter-AS MVPN allows MVPN data to be carried across ASs.

Figure 7-20  Inter-AS MVPN

As shown in Figure 7-20, ASs 100 and 200 are deployed between Source 1 and PC3. Source 1 is required to provide multicast services for PC3. Inter-AS MVPN must be deployed to enable Source 1 to provide multicast services for PC3.

Among two types of inter-AS MVPN, OptionA supports Any-Source Multicast (ASM) and Source-Specific Multicast (SSM), whereas OptionB only support MDT-SAFI auto-discovery (A-D) of MVPN BGP A-D in SSM.

  • Inter-AS MVPN OptionA: an independent multicast domain (MD) is established in each AS, and VPN multicast data is transmitted between MDs.
  • Inter-AS MVPN OptionB: each P does not know the route to the other AS, and each ASBR does not know the route to the PE in the other AS. This hinders the establishment of a multicast distribution tree across ASs because the next hop to the multicast source cannot be identified when PIM Join messages are sent. To solve this problem, the PIM Vector technique is used. Based on PIM Vector, PEs and ASBRs check the BGP MDT SAFI route to obtain the BGP neighbor information (Vector information containing RD information), and add the Vector information to the PIM Join messages. In this manner, a multicast distribution tree can be established across ASs.
Translation
Download
Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 20913

Downloads: 401

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