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 - WAN Access 01

This is ME60 V800R010C10SPC500 Feature Description - WAN Access
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).
OSPF Local MT

OSPF Local MT

Background

When multicast and an IGP Shortcut-enabled MPLS TE tunnel are configured on a network, the outbound interface of the route calculated by an IGP may not be a physical interface but a TE tunnel interface. The TE tunnel interface on the Device sends multicast Join packets over a unicast route to the multicast source address. The multicast Join packets are transparent to the Device through which the TE tunnel passes. As a result, the Device through which the TE tunnel passes cannot generate multicast forwarding entries.

To resolve the problem, configure OSPF local multicast topology (MT) to create a multicast routing table for multicast packet forwarding.

Principles

On the network shown in Figure 6-18, multicast and an IGP Shortcut-enabled MPLS TE tunnel are configured, and the TE tunnel passes through Device B. As a result, Device B cannot generate multicast forwarding entries.

Figure 6-18 OSPF Local MT

Since the TE tunnel is unidirectional, multicast data packets from the multicast source are sent to a physical interface of Device B. Device B discards these packets, because Device B has no multicast forwarding entry. As a result, services are interrupted.

After local MT is enabled, if the outbound interface of a calculated route is an IGP Shortcut-enabled TE tunnel interface, the route management (RM) module creates an independent Multicast IGP (MIGP) routing table for the multicast protocol, calculates a physical outbound interface for the route, and adds the route to the MIGP routing table. Multicast packets are then forwarded along this route.

After receiving multicast Join packets from Client, interface 1 on Device A forwards these packets to Device B. With local MT enabled, Device B can generate multicast forwarding entries.

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059473

Views: 14665

Downloads: 10

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