Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

EIGRP Next Hop

According to technical references, the Next Hop field in the EIGRP IP Internal and External Routes TLVs identifies the next-hop router to send packets destined for a destination network.

I have performed some POC regarding the Next Hop field but it seems doesn't work as it intended to. I have tried a few of IOSs but the results are still the same. Kindly refer to the attached document for the discussion of the problem. The destination network in question - 172.16.1.0/24 is connected to RT3. RT2 has a static route to RT3. RT1 and RT2 are EIGRP neighbors and RT2 redistribute the static route to RT1 as IP external route. But the next hop is still pointing to RT2 instead of RT3 directly.

With OSPF, RT1 will point directly to RT3 when the static route is redistributed from RT2 to RT1. OSPF is making use of the Forwarding Address field in the AS External LSA to achieve this.

I have also attached the sh ip route on RT1 and RT2 when they are running in EIGRP and OSPF respectively.

3 REPLIES

Re: EIGRP Next Hop

do you have

network 172.16.1.0

under RT3 eigrp ?

i think the problem maybe in R3 config

becuase R1 see about network 172.16.1.0 from R2 as it has static route

New Member

Re: EIGRP Next Hop

Hi marwan, I purposely not having the network statement in RT3 in order to observe how EIGRP on RT2 redistributed the static route to RT1. In real world, RT2 and RT3 would probably running BGP and RT2 is redistributing the BGP route into EIGRP.

With OSPF, the static route is redistributed to directly forward the traffic to RT3 instead of going to RT2 which is an extra hop. Thanks.

New Member

Re: EIGRP Next Hop

- bump -

178
Views
0
Helpful
3
Replies