New Training: Configure and Verify TLOC Extensions
In this 8-video skill, CBT Nuggets trainer Keith Barker explains the need of TLOC extensions, and how to configure and verify them. Watch this new networking training.
Watch the full course: Cisco CCNP Implementing Cisco SD-WAN Solutions
This training includes:
- 8 videos
- 36 minutes of training
You’ll learn these topics in this skill:
- Introduction to TLOC Extensions
- Overview of TLOC Extensions
- Planning out TLOC Extensions
- Configure a TLOC extension
- Configure a Tunnel Interface
- Applying TLOC Extensions
- Verifying TLOC Extensions
- TLOC Extension Summary
What It Means to Abstract Your Router Location
In network engineering, there’s a concept called RLOCs – or Routing Locators. RLOCs let you abstract your router and exchange it with location-based mapping, allowing the position to be represented by the routing location, not an endpoint.
RLOCs are related to TLOCs, Transport Locators, in that a TLOC is location-based mapping. Three things need to be present for TLOCs: first is a system-IP — it doesn’t even need to be reachable though. Second, the transport color — which are generally arbitrary. Last is the encapsulation type — either IPSec or GRE. With all those three pieces of information in hand, you can generate a TLOC. Practically speaking, TLOCs are the instructions for data plane set-up.
And on top of that, TLOCs can be extended with aptly named TLOC Extensions, and these allow for transport redundancy. vEdge routers typically have only one connection to their respective transport cloud. But in the event of a transport failure, you lose connectivity. It’s with TLOC Extensions that you can connect your vEdge to a neighboring vEdge in the same site and achieve redundancy.