Traffic engineering with EIGRP

[zeeshanbasit25789]

I have a topology where traffic from R6 to R5 can go through R4 direct connection with R5 or through tunnel between R4 and R5. Right now the traffic is taking the gig link between R4 and R5 for all traffic coming from R6. I am trying to engineer the traffic in a way that if it is coming from the loopback of R6 it should go through the tunnel all other traffic should go through the gig link between R4 and R5.

On R4, I tried using prefix-list and permitted the loopback of R6 and set the next-hop using the route-map and applied to the inbound traffic through EIGRP using distribute-list. But it redirects all traffic coming in from R6 to the tunnel now.

I have tried using extended IP access-list and permited the host of R6 loopback to R5 loopback but it still doesn't work. Any suggestions.

When I tried to apply the distribute-list through EIGRP to the inbound traffic on the link between R4 and R6 nothing works. If I only apply the distribute-list inbound through EIGRP only then it works but with the problem I have explained above.

[zeeshanbasit25789]

Apologies, not sure how it came under switching.

[MHM Cisco World]

If I am right this is not traffic engineer.

Can i see the config.

[zeeshanbasit25789]

R6 loopback is 150.1.6.6/32

R5 loopack is 150.1.5.5/32

R4 to R6 172.1.46.0/24

R4 to R5 172.1.45.0/24

R4 to R5 tunnel 192.1.45.0/24

on R4 I created the access-list

ip access-list extended To-R5

permit ip host 150.1.6.6 host 150.1.5.5

route-map R5 permit 10

match ip address To-R5

set ip next-hop 192.1.45.5

router eigrp CCIE-PREP
!
address-family ipv4 unicast autonomous-system 100
!
topology base
distribute-list route-map R5 in

[MHM Cisco World]

---

@zeeshanbasit25789 wrote:

R6 loopback is 150.1.6.6/32

R5 loopack is 150.1.5.5/32

R4 to R6 172.1.46.0/24

R4 to R5 172.1.45.0/24

R4 to R5 tunnel 192.1.45.0/24

on R4 I created the access-list

ip access-list extended To-R5

permit ip host 150.1.6.6 host 150.1.5.5

route-map R5 permit 10

match ip address To-R5

set ip next-hop 192.1.45.5

router eigrp CCIE-PREP
!
address-family ipv4 unicast autonomous-system 100
!
topology base
distribute-list route-map R5 in

---

Route map set next hop is not work with eigrp 

It work with pbr and bgp( as I know) 

What you need is add static route toward next hop you want and since static route have lower AD than eigrp then traffic will follow via static path.

[zeeshanbasit25789]

Route map set next hop works with EIGRP. But the problem I am facing is that it redirects all traffic to the tunnel not only the traffic from R6 loopback.

I tried prefix-list also but it's the same, I replaced the access-list with the prefix list and allowed only R6 loopback but still all traffic from R6 goes through the tunnel then.

ip prefix-list To-R5 permit 150.1.6.6/32

route-map R5 permit 10

match ip address prefix-list To-R5

set ip next-hop 192.1.45.5

router eigrp CCIE-PREP
!
address-family ipv4 unicast autonomous-system 100
!
topology base
distribute-list route-map R5 in

It works with this config but it sends all traffic to tunnel now instead of only allowed prefix.

[MHM Cisco World]

I dont use before' but if you sure it work and redirect all traffic then use prefix list instead of acl for route map match and check again 

[zeeshanbasit25789]

I am sure it works, been trying it for a while now but this time around not sure what the issue is but thank you for your help. By the way if this doesn't qualify as a traffic engineering, can you kindly advise what will, I would like to read more about it.

[MHM Cisco World]

After change  acl with prefix list 

Use distribute list with interface keywords and select interface toward the router you learn this prefix from

[zeeshanbasit25789]

I have tried that also, if I am using the interface with the distribute list even with prefix-list, nothing works, it works if I don't use the interface keyword with the above mentioned problem. But I am trying again now.

[MHM Cisco World]

Use prefix list not acl with route map interface 

[zeeshanbasit25789]

no doesn't work. I will try something again later and update.

[Joseph W. Doherty]

From what you describe, I would think PBR would be the usual solution.  That's assuming you only intend to direct traffic FROM the loopback (as you wrote) to the tunnel.

If you want the converse, i.e. traffic TO that loopback use the tunnel, that's a more complex problem, as you would need to make the tunnel the better path to just the loopback IP.

[zeeshanbasit25789]

Thanks, I will try PBR and update.

[Martin L]

As mentioned above, I also think PBR is the best option here; However, in case of EIGRP traffic engineering you may want to try using Distribute-list with extended IP access-list.  EIGRP distribute-list using extended ACL has different meaning here.  ACL 'source' field matches the update source of a route while the destination field indicates the network address. This "trick" allows u to control which networks u want to receive and most importantly from where.

Using Prefix-lists, route-maps, offset-lists are more of filtering tools rather then traffic engineering tools. One may argue that only thru EIGRP traffic engineering is using metrics, particularly delay.

Where is this from? What lab? I think I have seen this lab task before....

Regards, ML
**Please Rate All Helpful Responses *