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

ME60 V800R010C10SPC500 Feature Description - IP Multicast 01

This is ME60 V800R010C10SPC500 Feature Description - IP Multicast
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).
MT Transmission Along a Share-MDT

MT Transmission Along a Share-MDT

After a share-multicast distribution tree (MDT) is established, multicast tunnel (MT) transmission can be performed.

MT Transmission Along a Share-MDT

  1. A VPN instance on a PE sends a VPN multicast message to a multicast tunnel interface (MTI).

  2. The PE adds the MTI address as the source address and the share-group address as the group address to the message and converts the message to a multicast data message of the public network, regardless of whether the message is a protocol message or a data message. Figure 7-7 shows the encapsulation format of a public network multicast data packet.

  3. The PE forwards the multicast data message to a public network instance.

  4. The public network instance forwards the message to a public network instance on a remote PE along the share-MDT.

  5. The remote PE decapsulates the message, reverts it to a VPN multicast message, and forwards it to a VPN instance.

Figure 7-7 shows the process of converting a VPN multicast packet into a public network multicast data packet and then into a VPN multicast packet. Table 7-1 describes the meaning of each field in a VPN or public network multicast packet.

Figure 7-7 Process of converting a VPN multicast packet

Table 7-1 Fields in a VPN and public network multicast packet

Field

Description

C-IP Header

IP header of a VPN multicast packet.

C-Payload

Type of a VPN multicast packet, which can be a protocol or data packet.

GRE

Generic Routing Encapsulation (GRE) encapsulation.

P-IP Header

IP header of a public network multicast data packet. In this header, the source address is the MTI interface's address, and the destination address is the share-group's address.

Major Tasks in the MT Transmission Process

  • MTIs exchange Hello messages to set up PIM neighbor relationship between VPN instances on each PE.

  • MTIs exchange other protocol messages to set up a VPN MDT.

  • The MT transmits VPN multicast data.

Multicast Protocol Packet Transmission Process

If a VPN runs PIM-SM,

  • MTIs exchange Hello messages to set up PIM neighbors between VPN instances.

  • If receivers and the VPN RP belong to different sites, receivers send Join messages across the public network to set up a shared tree.

  • If the multicast source and the VPN rendezvous point (RP) belong to different sites, registration must be initiated across the public network to set up a source tree.

In the following example, the public network and VPNs run PIM-SM. VPN receivers send Join messages across the public network.

As shown in Figure 7-8, the receiver in VPN A belongs to Site 2 and is connected to CE 2. CE 1 is the RP of the VPN group G (225.1.1.1) and belongs to Site 1.

Figure 7-8 Multicast protocol message transmission process

The multicast protocol message transmission process is as follows:

  1. The receiver instructs CE 2 to receive and forward data of the multicast group G. CE 2 creates the (*, 225.1.1.1) entry, and then sends a Join message to the VPN RP (CE 1).

  2. The VPN instance on PE 2 receives the Join message sent by CE 2, creates the (*, 255.1.1.1) entry, and specifies an MTI as the upstream interface. The instance then forwards the Join message for further processing. The VPN instance on PE 2 considers that the Join message is sent out from the MTI.

  3. PE 2 encapsulates the Join message with the address of the MTI on PE 2 as the source address and the share-group address as the group address, and converts the message to a common multicast data message (11.11.1.2, 239.1.1.1) on the public network. PE 2 forwards the multicast data message to the public network instance on PE 2.

  4. The share-MDT forwards the multicast data message (11.11.1.2, 239.1.1.1) to the public network instance on each PE. PEs decapsulate the message and revert it to the Join message sent to the VPN RP. If the VPN RP (CE 1) resides in the site directly connected with a PE, the PE sends the message to its VPN instances for further processing. Otherwise, the PE discards the Join message.

  5. After receiving the Join message, the VPN instance on PE 1 considers that the message is received from an MTI. The instance creates the (*, 225.1.1.1) entry, and specifies an MTI as the downstream interface and the interface towards CE 1 as the upstream interface. Then, the instance sends the Join message to the VPN RP.

  6. After receiving the Join message from the instance on PE 1, CE 1 updates or creates the (*, 225.1.1.1) entry. The multicast shared tree across VPNs is then set up.

Multicast Data Packet Transmission Process

If a VPN runs PIM-SM,

  • When receivers and the VPN RP belong to different sites, the VPN multicast data is transmitted across the public network along a VPN rendezvous point tree (RPT).

  • When the multicast source and receivers belong to different sites, the VPN multicast data is transmitted across the public network along a source tree.

In the following example, the public network and VPNs run PIM-SM. VPN multicast data is transmitted across the public network along an SPT.

As shown in Figure 7-9, the multicast source in VPN A sends multicast data to the group G (232.1.1.1). The receiver belongs to Site 2 and connects to CE 2.

Figure 7-9 Multicast data message transmission process

The multicast data message transmission process is as follows:

  1. The source sends VPN multicast data (192.1.1.1, 232.1.1.1) to CE 1.

  2. CE 1 forwards the VPN multicast data to PE 1 along the SPT. The VPN instance on PE 1 searches for a matching forwarding entry. If the outbound interface of the forwarding entry contains an MTI, the instance forwards the VPN multicast data for further processing. The VPN instance on PE 1 then considers that the Join message is sent out from the MTI.

  3. PE 1 encapsulates the VPN multicast message with the address of the MTI on PE 1 as the source address and the share-group address as the group address, and converts the message to a public network multicast data message (11.11.1.1, 239.1.1.1). PE 1 forwards the multicast data message to the public network instance.

  4. The share-MDT forwards the multicast data message (11.11.1.1, 239.1.1.1) to the public network instance on each PE. Each PE decapsulates it, reverts it to VPN multicast data, and forwards it to a specific VPN instance for further processing. If there is an SPT downstream interface on the PE, the data is forwarded along the SPT. Otherwise, the data is discarded.

  5. The VPN instance on PE 2 searches for a matching forwarding entry and then sends the VPN multicast data to the receiver. The multicast data message transmission process is then complete.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059456

Views: 10496

Downloads: 13

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