MPLS TE - Fundamentals
Hi,
I would like help to understand the concept of a TE tunnels in Huawei and the several possibilities to deploy them.
There are many options to different scenarios. Hedex has great examples, but it's a hard task to choose one option and apply changes in a network already running because of complexity of this matter.
This article has some instructions, but it's still not clear to me:
https://forum.huawei.com/enterprise/en/deploying-mpls-te/thread/506061-861
Which options in MPLS family are mandatory to create a simple TE tunnel and guide traffic on it?
We're running only LDP in our AS (basic OSPF and MPLS in the core). Is it possible to create TE tunnel (and a backup TE tunnel indeed) and guide customer traffic over them?
This image can help understand the aim:
.png)
The goal is to guide traffic from PC1 to PC2 via R1 > R3 > R2 > R4 (1Gbps Path), to keep a backup tunnel over R1 > R3 > R4 (or R1 > R2 > R4) and the last option to use the IGP path (R1 > R4).
Is there any free Advanced Course (step by step) about this topic?
Thanks!
- x
- convention：
- Emotion(0)
|
Also, you can refer to the eNSP project as below: By the way, I didn't configure the backward MPLS TE tunnel in this project.
R1: #R2: #R3: #R4: # |
|
|
Hi @ptomasi,
On R1, the forwarding path will be selected in order: MPLS TE tunnel 1 > MPLS TE tunnel 2 > MPLS TE tunnel 3 > IGP You can refer to the example https://support.huawei.com/hedex/hdx.do?docid=EDOC1000163385&id=dc_cfg_mpls-te_0175&lang=en What should be pointed out, the MPLS TE tunnel is unidirectional, which means the backward traffic wouldn't be transferred in the MPLS TE tunnel unless you assign the corresponding tunnel on R4. |
|
|
|
|
Hi User, MPLS TEOn traditional IP networks, routers select the shortest path as the route regardless of other factors such as bandwidth. Traffic on a path is not switched to other paths even if the path is congested. As a result, the shortest path first rule can cause severe problems on networks. Traffic engineering (TE) monitors network traffic and the load of network components and then adjusts parameters such as traffic management, routing, and resource restraint parameters in real time. These adjustments help prevent network congestion caused by unbalanced traffic distribution. TE can be implemented on a large-scale backbone network using a simple, scalable solution. MPLS, an overlay model, allows a virtual topology to be established over a physical topology and maps traffic to the virtual topology. MPLS can be integrated with TE to implement MPLS TE. As shown in Figure 2-12, two paths are set up between LSR_1 and LSR_7: LSR_1 -> LSR_2 -> LSR_3 -> LSR_6 -> LSR_7 and LSR_1 -> LSR_2 -> LSR_4 -> LSR_5 -> LSR_6 -> LSR_7. Bandwidth of the first path is 30 Mbit/s, and bandwidth of the second path is 80 Mbit/s. TE allocates traffic based on bandwidth, preventing link congestion. For example, 30 Mbit/s and 50 Mbit/s services are running between LSR_1 and LSR_7. TE distributes the 30 Mbit/s traffic to the 30 Mbit/s path and the 50 Mbit/s traffic to the 80 Mbit/s path. MPLS TE can reserve resources by setting up LSPs along a specified path to prevent network congestion and balance network traffic. MPLS TE has the following advantages:
These advantages make MPLS TE the optimal TE solution. MPLS TE allows service providers (SPs) to fully leverage existing network resources to provide diverse services, optimize network resources, and efficiently manage the network. |
|
|
Hi @ptomasi,
On R1, the forwarding path will be selected in order: MPLS TE tunnel 1 > MPLS TE tunnel 2 > MPLS TE tunnel 3 > IGP You can refer to the example https://support.huawei.com/hedex/hdx.do?docid=EDOC1000163385&id=dc_cfg_mpls-te_0175&lang=en What should be pointed out, the MPLS TE tunnel is unidirectional, which means the backward traffic wouldn't be transferred in the MPLS TE tunnel unless you assign the corresponding tunnel on R4. |
|
Also, you can refer to the eNSP project as below: By the way, I didn't configure the backward MPLS TE tunnel in this project.
R1: #R2: #R3: #R4: # |
|
|
Great instructions, thank you! Can you help me to clarify some restless questions in my mind? According to examples, are these mandatory options in any TE scenario? mpls te mpls rsvp-te mpls te cspf interface GigabitEthernet0/0/N mpls te mpls rsvp-te ospf 1 opaque-capability enable area 0.0.0.0 mpls-te enable If we are already running LDP, can we run RSVP too in the label distribution task without problems? Is there a chance to generate conflict between them? - - - Some questions about the lab you shared: Virtual interfaces (TE Tunnels) are configured to have lower cost than physical links? This way will OSPF use TE tunnel as best path from R1 to R4? If yes, is this calculation valid only on R1? Or will R2 and R3 use R1 to get to R4 (because of lower cost of TE Tunnel) even they are directly connected to R4? Will all traffic from R1 to R4 be guided in TE Tunnel? If we want to guide only some Customer to Customer or Transit (Upstream ISP) to Customer, is it possible? In the lab, ip address 100.1.1.1 (loopback 1) is going to use TE Tunnel to get to 100.1.4.1 (loopback 1)? "What should be pointed out, the MPLS TE tunnel is unidirectional, which means the backward traffic wouldn't be transferred in the MPLS TE tunnel unless you assign the corresponding tunnel on R4." Great, in that case we could create another TE Tunnel from R4 to R1 to choose a reverse path or keep backwards traffic being routed via IGP, correct? Thanks again and sorry about too many noob questions. |
|
Comment
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
