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

NE40E V800R010C10SPC500 Configuration Guide - IP Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - 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).
Configuring Multicast Multi-Topologies

Configuring Multicast Multi-Topologies

With multicast multi-topologies, multicast services can run in a specified topology, which isolates multicast services from unicast services and eliminates the configuration conflict when both multicast services and unidirectional Traffic Engineering (TE) tunnel services are deployed. In deploying multicast multi-topologies, you can specify either a multicast topology instance or a unicast topology instance for running multicast services.

Usage Scenario

  • Currently, multicast services highly depend on unicast routes. During multicast routing, a router searches a unicast routing table for an optimal route. If the unicast optimal route, shared by both multicast services and unicast services, is faulty, the multicast services and unicast services will be interrupted and users will fail to receive the multicast data. With multicast multi-topologies, multicast services can run in a specified topology, which isolates multicast services from unicast services.

  • With both multicast services and unidirectional TE tunnel services deployed, if a unidirectional TE tunnel interface is chosen during multicast routing, the multicast data will fail to pass the Reverse Path Forwarding (RPF) check. The local multicast-topology (MT) feature can address this problem. However, in this situation, a separate Multicast Interior Gateway Protocol (MIGP) routing table has to be maintained, which consumes network resources. With multicast multi-topologies, the system searches for routes only in the unicast routing table, the static multicast routing table, and the MBGP routing table specified by the multicast topology. These routing tables contain no unidirectional TE tunnel interfaces, avoiding the problem that multicast data fails to pass the RPF check when a unidirectional TE tunnel interface is chosen. In addition, no separate MIGP routing tables have to be maintained, so network resources can be properly planned.

When configuring multicast multi-topologies, you can configure a multicast topology instance or a unicast topology instance. A multicast topology can be used in both PIM-SM intra-domain and inter-domain scenarios, but a unicast topology instance can be used only in a PIM-SM intra-domain scenario.

Pre-configuration Tasks

Before configuring multicast multi-topologies, complete the following tasks:

Configuration Procedures

Perform one or more of the following configurations as required.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44067

Downloads: 97

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