EIGRP routing questions

Unanswered Question
Nov 12th, 2009
User Badges:

We have multiple EIGRP remote connections that come into two Cisco devices. One is a Cisco 3750 and the other is a Cisco 7206. The 7206 is the primary router and the Vlan interface on teh 3750 has a delay of 200 on it. All 10.10.0.0/16 traffic is destined for the Cisco 7206 route but the 10.10.1.0/24 address space. We cannot figure out why if you do a show IP route 10.10.1.75 that it always goes to the 3750. We want it to go the 7206 which has the lower metric.


I hope this makes sense.


Thank you


Dwane

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Amit Singh Thu, 11/12/2009 - 11:54
User Badges:
  • Cisco Employee,

Would you able to paste the network diagram and the device configs please.


dpatkins Thu, 11/12/2009 - 12:16
User Badges:

I have included the attachments. Vlan 244 is our connection the remote areas using EIGRP and Vlan 11 is our connection to our internal network.


Thank you



Attachment: 
Giuseppe Larosa Fri, 11/13/2009 - 08:12
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Dwane,

post a sh ip route of involved subnets


sh ip eigrp topology can also be of help


however, if you want to prefer the c7206 it may be wise on C3750 to put an higher delay value


C3750


interface Vlan244

delay 20000


for example may help


you need to compare with delay as appears on 7206 interface


that is gi0/3.144.


you should manipulate delay on link to remote site that is on path not on interface to other router.


so if this vlan144 is a backbone vlan your changes on C3750 may be not effective because C3750 reports cumulative delay and lowest BW on path to destination IP subnet in vlan144 without taking in account settings on vlan144 itself.


router receiving EIGRP updates will use its own delay and BW to calculater metric from its own point of view


Hope to help

Giuseppe


dpatkins Tue, 11/17/2009 - 08:20
User Badges:

All, thanks for the help. We have the EIGRP issue working, but the incoming traffic is not hitting the route-map. The route-map is configured on the gig0/3.244 sub-interface, but all 10.120.1.x traffic is not going to 10.111.87.251 per the route-map next hop.


Any ideas or is there something special one needs to do to get a route-map to work with EIGRP?


Thank you,


Dwane

dpatkins Tue, 11/17/2009 - 09:13
User Badges:

I think we have found the issue. It was in our match ip ACL. We had 10.120.x.x/24 and used a standard access-list instead of an extended ACL. Thanks for your help.


DWane

Giuseppe Larosa Fri, 11/20/2009 - 10:14
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Dwane,

good news that you solved also the second issue.

You have been kind to provide a feedback on this.


Best Regards

Giuseppe

Actions

This Discussion