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 Configuration Guide - MPLS 01

This is NE20E-S V800R010C10SPC500 Configuration Guide - 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).
Importing Traffic to an MPLS TE Tunnel

Importing Traffic to an MPLS TE Tunnel

Before importing traffic to an MPLS TE tunnel, familiarize yourself with the usage scenario, complete the pre-configuration tasks for the configuration.

Usage Scenario

An MPLS TE tunnel does not automatically import traffic. To enable traffic to travel along an MPLS TE tunnel, use one of the methods listed in Table 3-8 to import the traffic to the MPLS TE tunnel.
Table 3-8 Methods to import traffic to an MPLS TE tunnel

Methods to Import Traffic to an MPLS TE Tunnel

Principles

Usage Scenario

Related Configuration Links

Use static routes

This is the simplest method for importing the traffic to an MPLS TE tunnel. You only need to configure a static route with a TE tunnel interface as the outbound interface.

Scenario where public-network routes are used to import traffic to a TE or LDP over TE tunnel

Configuring IPv4 Static Routes

Use the auto route mechanism

A TE tunnel is used as a logical link for IGP route calculation. A tunnel interface is used as an outbound interface of a route. The auto route mechanism can be implemented in either of the following modes:

  • IGP shortcut: A device uses a TE tunnel for local route calculation and does not advertise the TE tunnel to its peers as a route. Therefore, the peers of this device cannot use the TE tunnel for route calculation.

  • Forwarding adjacency: A device uses a TE tunnel for local route calculation and advertises the TE tunnel to its peers as a route. Therefore, the peers of this device can use the TE tunnel for route calculation.

Configuring the IGP Shortcut

Configuring Forwarding Adjacency

Policy-Based Routing

The policy-based routing (PBR) allows a device to select routes based on user-defined policies.

TE PBR, the same as IP unicast PBR, is implemented by defining a set of matching rules and behaviors. The rules and behaviors are defined using the apply clause with a TE tunnel interface used as an outbound interface. If packets do not match PBR rules, they are properly forwarded using IP; if they match PBR rules, they are forwarded over specific tunnels.

-

Tunnel Policy

By default, VPN traffic is forwarded through LDP LSPs tunnels. If the default LDP LSPs cannot meet VPN traffic requirement, a tunnel policy is used to direct VPN traffic to a TE tunnel.
  • Select-seq mode: This policy changes the type of tunnel selected for VPN traffic. A TE tunnel is selected as a public tunnel for VPN traffic based on the prioritized tunnel types.
  • Tunnel binding mode: This policy defines a specific destination IP address, and this address is bound to a TE tunnel.

VPN scenario

VPN Tunnel Management Configuration

NOTE:

The preceding methods to import traffic to MPLS TE tunnels apply only to P2P tunnels.

Pre-configuration Tasks

Before you import traffic to an MPLS TE tunnel, configure an RSVP-TE tunnel.

Configuration Procedures

Perform one or more of the following configurations as required.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 19912

Downloads: 35

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