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).
Process of Establishing a Share-MDT

Process of Establishing a Share-MDT

The multicast distribution tree (MDT) that takes the Share-Group address as the group address is called a Share-MDT. The VPN uniquely identifies a Share-MDT by using a Share-Group.

The public network can run PIM-SM or PIM-DM. The process of establishing a Share-MDT is different in the two cases.

Establishing a Share-MDT in a PIM-SM Network

Figure 7-7  Establishing a Share-MDT in a PIM-SM network

As shown in Figure 7-7, the public network runs PIM-SM. The process of establishing a Share-MDT is as follows:

  1. The PIM P-instance on PE1 sends a Join message with the Share-Group address being the multicast group address to the Rendezvous Point (RP) in the public network. PEs that receive the Join message then create the (*, 239.1.1.1) entry on themselves. PE2 and PE3 also send Join messages to the RP in the public network. A Rendezvous Point Tree (RPT) is thus formed in the MD, with the RP being the root and PE1, PE2, and PE3 being leaves.

  2. The PIM P-instance on PE1 sends a Register message with the Multicast Tunnel Interface (MTI) address being the source address and the Share-Group address being the group address to the RP in the public network. The RP then creates the (11.1.1.1, 239.1.1.1) entry on itself. PE2 and PE3 also send Register messages to the RP in the public network. Thus, three independent RP-source trees that connect PEs to the RP are formed in the multicast domain (MD).

In the PIM-SM network, an RPT (*, 239.1.1.1) and three independent RP-source trees form a Share-MDT.

Establishing a Share-MDT in a PIM-DM Network

Figure 7-8  Establishing a Share-MDT in a PIM-DM network

As shown in Figure 7-8, the public network runs PIM-DM. The process of establishing a Share-MDT is as follows.

A flooding-pruning process is initiated on the entire public network with the PIM P-instance on PE1 being a multicast source, the Share-Group address being the multicast group address, and other PEs that support VPN A being group members. During this process, the (11.1.1.1, 239.1.1.1) entry is created on the PEs along the path in the public network. A Shortest Path Tree (SPT) with PE1 being the root and PE2 and PE3 being leaves is thus set up. PE2 and PE3 also start the similar flooding-pruning process in the public network to form two SPTs.

As a result, in the PIM-DM network, three independent SPTs are created and form a Share-MDT.

Translation
Download
Updated: 2019-06-12

Document ID: EDOC1000097181

Views: 21351

Downloads: 403

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