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.


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).


Figure 8-39 shows the use of IS-IS MT to separate an IPv4 topology from an IPv6 topology. Device A, Device C, and Device D support IPv4/IPv6 dual-stack; Device B supports IPv4 only and cannot forward IPv6 packets.

Figure 8-39 Separation of the IPv4 topology from the IPv6 topology

If IS-IS MT is not used, Device A, Device B, Device C, and Device D consider the IPv4 and IPv6 topologies the same when using the SPF algorithm for route calculation. The shortest path from Device A to Device D is Device A -> Device B- > Device D. Device B does not support IPv6 and cannot forward IPv6 packets to Device D.

If IS-IS MT is used to establish a separate IPv6 topology, Device A chooses only IPv6 links to forward IPv6 packets. The shortest path from Device A to Device D changes to Device A -> Device C -> Device D. IPv6 packets are then forwarded.

Figure 8-40 shows the use of IS-IS MT to separate unicast and multicast topologies.

Figure 8-40 Separation of the multicast topology from the unicast topology

All ME devices in Figure 8-40 are interconnected using IS-IS. A TE tunnel is set up between Device A (ingress) and Device E (egress). The outbound interface of the route calculated by IS-IS may not be a physical interface but a TE tunnel interface. The ME devices between which the TE tunnel is established cannot set up multicast forwarding entries. As a result, multicast services cannot run properly.

IS-IS MT is configured to solve this problem by establishing separate unicast and multicast topologies. TE tunnels are excluded from a multicast topology; therefore, multicast services can run properly, without being affected by TE tunnels.

Updated: 2019-01-04

Document ID: EDOC1100059473

Views: 14547

Downloads: 10

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