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


To have a better experience, please upgrade your IE browser.


NE20E-S V800R010C10SPC500 Feature Description - IP Multicast 01

This is NE20E-S 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).
Multicast over P2MP TE Tunnels

Multicast over P2MP TE Tunnels

Using point-to-multipoint (P2MP) Traffic Engineering (TE) tunnels to carry multicast services on an IP/Multiprotocol Label Switching (MPLS) backbone network provides high TE capabilities and reliability and reduces operational expenditure (OPEX).


IP and MPLS are generally used to forward packets on traditional core and backbone networks. Deployment of multicast services, such as IPTV, multimedia conferences, and real-time online games continues to increase on IP/MPLS networks. These services require sufficient bandwidth, assured QoS, and high reliability on the bearer network. Currently, the following multicast solutions are used to run multicast services, but these solutions cannot meet the requirements of multicast services and network carriers:
  • IP multicast technology: It can be deployed on point-to-point (P2P) networks to run multicast services, reducing network upgrade and maintenance costs. Similar to IP unicast, IP multicast does not support QoS or traffic planning and has low reliability. Multicast applications place high demands on real-time transmission and reliability, and IP multicast technology cannot meet these requirements.
  • Establishing a dedicated multicast network: A dedicated multicast network is usually constructed over Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH). SONET/SDH has high reliability and provides a high transmission rate. However, such a network is expensive to construct, incurs significant OPEX, and must be maintained separately.
IP/MPLS backbone network carriers require a multicast solution with high TE capabilities to run multicast services on existing IP/MPLS backbone network devices.

Multicast over P2MP TE tunnels can meet the carriers' requirements by establishing tree tunnels to transmit multicast data. It has the advantages of high IP multicast packet transmission efficiency and assured MPLS TE end-to-end (E2E) QoS.


Deploying P2MP TE on an IP/MPLS backbone network brings the following benefits:
  • Improves network bandwidth utilization.

  • Provides sufficient bandwidth for multicast services.

  • Simplifies network deployment using multicast protocols by not requiring PIM and IGMP to be deployed on core devices on the network.

Related Concepts

P2MP TE data forwarding is similar to IP multicast data forwarding. A branch node copies MPLS packets, swaps existing labels with outgoing labels in the MPLS packets, and sends each separate copy of the MPLS packets over every sub-LSP. This process increases network bandwidth resource usage.

For details on P2MP TE concepts, see Related Concepts in the HUAWEI NE20E-S Feature Description - MPLS.

Technologies Used by Multicast over P2MP TE Tunnels

If P2MP TE tunnels are used to transmit multicast services, the ingresses and egresses of the P2MP TE tunnels must be configured properly to ensure multicast traffic transmission after the traffic passes through the P2MP TE tunnels, as shown in Figure 4-42.
Figure 4-42 Networking diagram for multicast over P2MP TE tunnels
  • Ingresses

    The P2MP tunnel interfaces of the ingresses (PE1 and PE2) direct multicast data to the P2MP TE tunnel.

  • Egresses

    The egresses (PE3, PE4, PE5, and PE6) must be configured to ignore the Unicast Reverse Path Forwarding (URPF) check. Whether to configure multicast source proxy on the egresses is based on the location of the rendezvous point (RP).

    • Ignoring the URPF check

      The egresses must be configured to ignore the URPF check during multicast traffic forwarding.

    • Multicast source proxy

      In a multicast over P2MP TE scenario where PIM-SM is used, if an RP is deployed at the egress side, the multicast source cannot send a Register message to the RP because it cannot find an available route to the RP. In this case, multicast source proxy can be used to enable the egress to register multicast source information with the RP.

      If a multicast data packet for a group in the any-source multicast (ASM) address range is directed to an egress and the egress is not directly connected to the multicast source and does not function as the RP to which the group corresponds, the multicast data packet stops being forwarded. As a result, downstream hosts cannot receive these multicast data packets. Multicast source proxy can be used to address this problem. To allow forwarding of multicast data packets to the downstream hosts, multicast source proxy enables the egress to send a Register message to the RP deployed on a source-side device in a PIM domain, such as AR1 or AR2.

Updated: 2019-01-03

Document ID: EDOC1100055119

Views: 13502

Downloads: 20

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