How to Modify EIGRP Metrics Using Offset Lists

When managing large and complex networks, engineers often need to influence routing decisions made by EIGRP (Enhanced Interior Gateway Routing Protocol). One powerful tool for this task is the *offset-list* command. It allows administrators to manipulate the metrics of routes learned via EIGRP, subtly adjusting the protocol’s behavior to fit specific network requirements.

But how this command behaves—and is configured—can differ depending on the software feature sets and architecture improvements that have come with newer versions of IOS. Let's dive into how to apply this and what you should watch out for when working across different setups.

### What Is an Offset List?

An offset list in EIGRP is used to **increase the metric of incoming or outgoing routes**. By doing this, you effectively make some routes less preferred, or push traffic away from certain links. This can be useful for load balancing, backup route preferences, or traffic engineering.

The command typically looks like this:

Router(config)#access-list 22 permit 192.168.30.0

Router(config)#router eigrp 55

Router(config-router)#offset-list 22 in 10000 Serial0/1

Here, an access list identifies the routes, and the `offset-list` increases the metric for those routes as they come in on interface Serial0/1 by 10,000 units.

### Practical Example

Suppose you have a WAN connection and want to ensure it's only used if the primary path fails. By increasing the metric of routes learned via the backup link, EIGRP will favor the primary route unless it becomes unavailable. This is a clean and efficient way to manage route preference without altering bandwidth or delay values manually.

### Behind the Scenes: What's Changing?

While the *offset-list* syntax remains consistent, internal behavior and interface support have evolved. In earlier builds, the feature primarily worked with **classic EIGRP** (sometimes referred to as "EIGRP named mode" wasn't available yet). Configuration was done directly under `router eigrp` mode.

In more modern systems, **named EIGRP configuration** is encouraged and introduces better scalability and modularity. Here, offset lists can be applied within address-family configuration blocks, which adds a layer of control but may surprise engineers familiar with older-style setups.

### Key Differences to Watch For

- **Interface syntax support**: In some environments, interface references like `Serial0.1` may require full logical interface identification. Newer systems might need `Serial0/1.100` rather than the shorthand.

- **Named mode vs classic mode**: If you're using named mode, your offset-list command must be placed under the `address-family ipv4 autonomous-system` section.

- **Access-list flexibility**: ACLs now support both numbered and named styles, and extended ACLs can also be used, offering more precision when identifying routes.

### Helpful Tip

Always verify the effect of your offset list using the `show ip protocols` and `show ip route` commands. They help confirm the metric change and how EIGRP is treating each route.

### More on EIGRP

If you're new to EIGRP or want to explore more about its inner workings, check out its [Wikipedia page](https://en.wikipedia.org/wiki/Enhanced_Interior_Gateway_Routing_Protocol) for a broader overview of how the protocol works, including its DUAL algorithm, route summarization, and metric calculations.

---

Offset lists might seem like a small tweak in your routing configuration toolbox, but they can be incredibly powerful when used correctly. Whether you're building a failover mechanism or just trying to nudge EIGRP in the right direction, it's a tool worth mastering.