> For the complete documentation index, see [llms.txt](https://ccie-sp.gitbook.io/ccie-spv5.1-labs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ccie-sp.gitbook.io/ccie-spv5.1-labs/labs/isis/troubleshooting-te-tunnel.md).

# Troubleshooting TE Tunnel

Load **isis.with.te.tshoot.init.cfg**

```
#IOS-XE
config replace flash:isis.with.te.tshoot.init.cfg

#IOS-XR
configure
load bootflash:isis.with.te.tshoot.init.cfg
commit replace
y
```

A TE tunnel is setup on R1 with destination XR2. The tunnel is not coming up. Without making any changes to any other router besides R1, bring the tunnel up.

Do the same for the TE tunnel on XR2 with destination R1.

## Answer <a href="#id-5d9a0452-ec88-425f-b382-30982909d9cb" id="id-5d9a0452-ec88-425f-b382-30982909d9cb"></a>

```
#R1
mpls traffic-eng path-selection overload allow middle

#XR2
mpls traffic-eng
 path-selection
  ignore overload mid
```

## Explanation <a href="#id-0eec46d9-b90b-4c28-b389-66225d4ac9b3" id="id-0eec46d9-b90b-4c28-b389-66225d4ac9b3"></a>

On R1, we see that the tunnel is down due to no path to the destination. However, this by itself does not tell us all that much.

<div align="left"><figure><img src="/files/hlhSoFOSCNguRQ1dz01X" alt=""><figcaption></figcaption></figure></div>

If we **debug mpls traffic-eng path lookup**, we still don’t get that much useful output. We see tha tthe path lookup simply failed - a path cannot be found.

<div align="left"><figure><img src="/files/eO2QXDkCgXBIfxacbfYA" alt=""><figcaption></figcaption></figure></div>

If we look at the TED, we come across a hint. The node R2 is marked with “no SPF.”

<div align="left"><figure><img src="/files/IIz7i3Lf0pJEYBRt3fmP" alt=""><figcaption></figcaption></figure></div>

The reason for this is that R2 has the overload bit set:

<div align="left"><figure><img src="/files/Kww7vZ0gaodKUdnXkfGE" alt=""><figcaption></figcaption></figure></div>

When a node has the OL bit set, it cannot be used in CSPF for TE calculation. Recall that an ISIS node with the OL bit set can never be used as transit for any prefixes (other than directly attached prefixes), so this makes sense that the node cannot be used in CSPF either. However, we can force the router to ignore the OL bit for TE tunnels using the following command:

```
#R1
mpls traffic-eng path-selection overload allow head|middle|tail
```

By allowing mid nodes to have the OL bit set, the tunnel will come up on R1:

<div align="left"><figure><img src="/files/1g9199adop4hhMSvb4Zn" alt=""><figcaption></figcaption></figure></div>

### IOS-XR as the headend <a href="#id-99c8243b-762a-4357-8447-05bb677c5b60" id="id-99c8243b-762a-4357-8447-05bb677c5b60"></a>

Fortunately, IOS-XR gives us much better indication of the issue. We know that some transit node has the OL bit set, but not which node.

<div align="left"><figure><img src="/files/gD5HyOObCYss48FKbyW7" alt=""><figcaption></figcaption></figure></div>

The TED on XR2 shows us that R2 is overloaded:

<div align="left"><figure><img src="/files/NjGvMUFlB8UKKLCvuoZx" alt=""><figcaption></figcaption></figure></div>

A similar command allows us to still use overloaded routers for TE tunnels:

```
#XR2
mpls traffic-eng
 path-selection
  ignore overload head|mid|tail
```

By ignoring the OL bit for mid nodes, we can get the tunnel to come up:

<div align="left"><figure><img src="/files/OUHNMUdcK0jFZ63nGIek" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ccie-sp.gitbook.io/ccie-spv5.1-labs/labs/isis/troubleshooting-te-tunnel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
