# MPLS TE Static Routes
**URL:** https://forum.networklessons.com/t/mpls-te-static-routes/33683
**Category:** Lessons Discussion
**Created:** [January 11, 2023, 9:53am UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683 "2023-01-11T09:53:43Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@ReneMolenaar](https://forum.networklessons.com/u/ReneMolenaar)
#### Post date: [January 11, 2023, 9:53am UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683/1 "2023-01-11T09:53:44Z")
This topic is to discuss the following lesson:
> **[MPLS TE Static Routes](https://networklessons.com/mpls/mpls-te-static-routes)**
>
> With a static route you can send traffic with specific destinations down a MPLS TE tunnel. This lesson explains the configuration.
---
### Author:  [@iman.warraich](https://forum.networklessons.com/u/iman.warraich)
#### Post date: [September 29, 2023, 12:16pm UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683/2 "2023-09-29T12:16:22Z")
You only created a one way tunnel, meaning since it is unidirectional, the ping should not work. Is the reverse path being chosen via IGP and not using the tunnel ?
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [October 2, 2023, 5:19am UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683/3 "2023-10-02T05:19:57Z")
Hello Iman
MPLS TE tunnels are indeed unidirectional in nature. If you want to ensure traffic in the other direction is applied with similar TE criteria, then you must create a second TE tunnel for the return traffic.
The path of the return traffic is determined simply by the regular IP routing tables and MPLS forwarding tables that exist within the infrastructure.
In this particular lab, the return traffic does indeed return via the non-TE MPLS and IP routing mechanisms. In the lesson, the verification steps Rene takes are to observe outgoing traffic that uses the tunnel.
I hope this has been helpful!
Laz
---
### Author:  [@fangshucheng](https://forum.networklessons.com/u/fangshucheng)
#### Post date: [February 17, 2025, 10:57pm UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683/4 "2025-02-17T22:57:37Z")
```auto
PE1#show mpls forwarding-table 7.7.7.7 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
24 Pop Label 7.7.7.7/32 0 Tu1 point2point
```
The above shows label 24, but this result shows label 26.
```auto
PE1#traceroute 7.7.7.7 source Loopback 0 numeric probe 1
Type escape sequence to abort.
Tracing the route to 7.7.7.7
VRF info: (vrf in name/id, vrf out name/id)
1 192.168.23.3 [MPLS: Label 26 Exp 0] 4 msec
2 192.168.36.6 4 msec
3 192.168.67.7 6 msec
```
And I find the same thing in my GNS3 lab. The actual MPLS label is not the label shown by command "`show mpls forwarding-table 7.7.7.7 detail` ". Can you please explain why? Thanks.
---
### Author:  [@lagapidis](https://forum.networklessons.com/u/lagapidis)
#### Post date: [February 19, 2025, 5:56am UTC](https://forum.networklessons.com/t/mpls-te-static-routes/33683/5 "2025-02-19T05:56:30Z")
Hello Martin
That’s a good point! It’s important to understand which label is being referred to in each case. From the point of view or PE1, 24 is the local label, which is the label that the local router itself assigns to this prefix. Label 26 is the label assigned by the next hop router. But which is the next hop router? In this case, it is actually the tail end router, or the other end of the tunnel, which is PE2 because we are using LSP tunnels. This is why you only see one label in the traceroute, and not a label for every hop.
If you take a look at the output from the `show mpls forwarding-table 7.7.7.7 detail` command, you’ll actually see both labeles referenced:
```auto
PE1#show mpls forwarding-table 7.7.7.7 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
24 Pop Label 7.7.7.7/32 0 Tu1 point2point
MAC/Encaps=14/18, MRU=1500, Label Stack{26}, via Gi0/1
5254001A70435254001F16328847 0001A000
No output feature configured
```
The local label is 24, but the value you see in the Label Stack is 26. This is the label being pushed onto the packet before being forwarded. Does that make sense?
I hope this has been helpful!
Laz