I'm trying to figure out how to modify the EIGRP within our network and need some guidance. Basically, is there any way within EIGRP to force traffic into one router rather than another? I just need to know how to properly set the weights so that although the network is learned from two different routers via EIGRP the traffic will prefer one router over the other.
You can either
1) filter the eigrp routes so you only receive routes from the router you want but this means you lose any redundancy
2) you manipulate the delay on the interfaces so that one path is preferred over the other. This is the recommended way to influence eigrp metrics
In addition to the possibility of altering the interface delay to change the calculated metric of EIGRP there is another possibility that you might consider. You can configure an offset list. An offset list will add a configurable amount to the EIGRP metric, making that advertisement less attractive. An offset list can be configured for specific interfaces and it can alter the metric of inbound updates or of outbound updates, so you have some flexibility of where to implement the offset list. The offset list can use an access list to identify the routes to alter, so you do not need to alter every route advertised if you only care about certain routes.
your way looks fresh to me
as you said,
An offset list will add a configurable amount to the EIGRP metric,
i did the first step,
router eigrp 100
offset-list 0 in 2
eigrp router-id 220.127.116.11
I am wondering how to add a configurable amount to eigrp metric,
could you please more specific,
Thank you very much,
EIGRP weights need to match in all routers so they cannot be manipulated.
As Jon has explained you can use delay because EIGRP metric is cumulative on delay or if you want a more selective effect you can use offset-list that are able to add delay only to specific prefixes out/in an interface.
Hope to help
I don't quite understand the offset list. It looks like you need to create an access list and refer to that in the offset list correct? I don't see how I would do that when the router will be learning the routes via eigrp when a new location connects to it. Perhaps the interface weight would make more sense to me. Does anybody have any examples of placing a weight on the interface?
Yes you need an access list for the offset list:
You apply an offset list to an interface either in or out.
So lets say you have 3 routers.
R1 (s0/0) is connected to R2 (s0/0)
R1 (s0/1) is connected to R3 (s0/0)
R1 is receiving a route to the same network eg 192.168.5.0/24 from both R2 & R3 but you want the traffic to go via R2.
So you could write an acl that matches the route
access-list 1 permit 192.168.5.0
then you can either apply this offset list to R3 s0/0 interface outbound towards R1 or you can apply it inbound on s0/1 on R1.
As for changing the delay you can simply modify the delay under the interface configuration eg
If you are unsure of the value, from the example we used above
sh int s0/0
sh int s0/1
the output of the above commands will show you the existing delay. You can then increase that delay on the s0/1 interface so the s0/0 path is preferred.
Thanks Jon - That clears it up for me, I think I'll be able to get it in place one of these nights and do some testing. I really appreaciate the help.
Note that using an access list with the offset list is optional. If you do not use an access list (when you use 0 in the place of the access list number) then the added amount is added to all routes learned and processed by the offset list.
If you do use the access list it will identify the routes to which you want to add. If you are bringing up new sites and that adds new routes that need to have the metric increased then you would need to update the access list as part of bring up the new site.