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

NE20E-S V800R010C10SPC500 Feature Description - MPLS 01

This is NE20E-S V800R010C10SPC500 Feature Description - MPLS
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).
P2MP TE Applications for IPTV

P2MP TE Applications for IPTV

Service Overview

There is an increasing diversity of multicast services, such as IPTV, multimedia conference, and massively multiplayer online role-playing games (MMORPGs), and multimedia conferences. These services are transmitted over a service bearer network with the following functions:
  • Forwards multicast traffic even during traffic congestion.
  • Rapidly detects network faults and switches traffic to a standby link.

Networking Description

Point-to-multipoint (P2MP) Traffic Engineering (TE) is used on the IP/MPLS backbone network shown in Figure 4-50. P2MP TE helps the network prevent multicast traffic congestion and maintain reliability.
Figure 4-50 P2MP TE applications for multicast services

Feature Deployment

Figure 4-50 illustrates how P2MP TE tunnels are used to transmit IP multicast services. The process consists of the following stages:

  • Import multicast services.

    • An Internet Group Management Protocol (IGMP) static group is configured on a network-side interface of each service router (SR). SR1 run the Protocol Independent Multicast (PIM). Ingress PE1 functioning as a host sends an IGMP Join message to SR1. After receiving the message, SR generates a multicast forwarding entry and forwards multicast traffic to a PE. A traffic policy is configured to allow each PE to direct multicast traffic to a separate P2MP tunnel interface.
    • A static IGMP group is configured on a P2MP TE tunnel interface on each ingress. PIM is enabled on the ingress nodes. After receiving an IGMP Join message from a downstream device, each ingress generates a multicast forwarding entry. Each ingress then sends an IGMP Join message to an SR.
  • Establish a P2MP TE tunnel.

    Using the following configuration is recommended:
    • Configuring an explicit path is recommended. The configuration must prevent the re-merge or cross-over problem.
    • Resource Reservation Protocol (RSVP) neighbor-based authentication is configured to improve network protocol security.
    • RSVP Srefresh is configured to increase the efficiency of network resource use.
    • P2MP TE FRR is configured to improve network reliability.
  • Forward multicast services.

    • Leaf nodes PE3, PE4, PE5, and PE6 shown in Figure 4-50 run PIM to generate multicast forwarding entries.
    • AR1 establishes PIM neighbor relationships with PE3 and PE4, and AR2 establishes PIM neighbor relationships with PE5 and PE6.
    • Multicast source proxy is configured on leaf nodes PE3 through PE6 to allow these PEs to receive Join messages sent by ARs. After receiving the Join messages, these PEs terminate them.
    • Reverse path forwarding (RPF) check is disabled on leaf PEs.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055123

Views: 5863

Downloads: 21

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