cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
101
Views
5
Helpful
3
Replies
Highlighted
Beginner

Missing EIGRP Routes

 

 

hello everyone, 

 

I am trying to reach our server to the cloud on 10.65.120.0 network however I am not able to reach it via our remote offices. Though I am able to reach 10.65.1.0 network anywhere. 

 

I noticed on the EIGRP topology, it does not include the 10.65.120.0 network. Is there anything I am missing on my network command? I tried to add 10.65.120.0/21 on EIGRP but no luck. I still cannot see the route from remote office.

 

#show ip bgp nei x.x.30.209 received-routes
BGP table version is 20152948, local router ID is 10.2.2.10
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
*> 10.65.1.0/24 x.x.30.209 100 0 64512 i
*> 10.65.120.0/21 x.x.30.209 100 0 64512 i

 

EIGRP Network config below

!

router eigrp 89
redistribute static
network 10.0.0.0 0.0.0.3
network 10.65.20.0 0.0.0.255
network 10.65.21.0 0.0.0.255
network 10.255.255.0 0.0.0.3
network 10.255.255.12 0.0.0.3
network 10.255.255.16 0.0.0.3
network 10.255.255.64 0.0.0.3
network 10.255.255.72 0.0.0.3
network 10.255.255.80 0.0.0.3
network 10.255.255.100 0.0.0.3
network 10.255.255.104 0.0.0.3
network 10.255.255.116 0.0.0.3
network 10.255.255.120 0.0.0.3
network 10.255.255.148 0.0.0.3
network 10.255.255.152 0.0.0.3
no auto-summary
!

ip route 10.65.0.0 255.255.240.0 Tunnel10 track 101
ip route 10.65.0.0 255.255.240.0 Tunnel11 track 201
ip route 172.31.0.0 255.255.0.0 Tunnel650101 track 201
ip route 10.75.0.0 255.255.224.0 Tunnel3 track 300
ip route 10.65.32.0 255.255.224.0 Tunnel3 track 300
ip route 10.75.0.0 255.255.224.0 Tunnel4 track 400
ip route 10.65.0.0 255.255.240.0 Tunnel10 track 400
ip route 172.31.0.0 255.255.0.0 Tunnel650100 track 500
ip route 0.0.0.0 0.0.0.0 116.214.96.193
ip route 10.20.0.0 255.255.0.0 Tunnel6500101
ip route 10.61.0.0 255.255.0.0 Tunnel63
ip route 10.65.0.146 255.255.255.255 198.18.124.5
ip route 10.65.4.0 255.255.255.0 198.18.124.5
ip route 10.65.21.0 255.255.255.0 10.65.20.1
ip route 10.65.22.0 255.255.255.0 10.65.20.1
ip route 10.65.25.0 255.255.255.0 10.65.20.1
ip route 10.65.26.0 255.255.255.0 10.65.20.1
ip route 10.65.27.0 255.255.255.0 10.65.20.1
ip route 10.65.29.0 255.255.255.0 10.65.20.1
ip route 10.65.30.0 255.255.255.0 10.65.20.1
ip route 10.65.31.0 255.255.255.0 10.65.20.1
ip route 10.65.128.0 255.255.128.0 198.18.124.5
ip route 10.86.0.0 255.255.0.0 10.65.20.1

!

 

I suppose the 10.65.0.0/19 should cover for all the subnets but it doesn't. 

!

#show ip eigrp topology | i 10.65
P 10.65.0.0/19, 1 successors, FD is 2816
P 10.65.4.0/24, 1 successors, FD is 28160
P 10.65.27.0/24, 1 successors, FD is 2816
P 10.65.26.0/24, 1 successors, FD is 2816
P 10.65.25.0/24, 1 successors, FD is 2816
P 10.65.31.0/24, 1 successors, FD is 2816
P 10.65.30.0/24, 1 successors, FD is 2816
P 10.65.29.0/24, 1 successors, FD is 2816
P 10.65.22.0/24, 1 successors, FD is 2816
P 10.65.21.0/24, 1 successors, FD is 2816
P 10.65.20.0/24, 1 successors, FD is 2816
P 10.65.32.0/19, 1 successors, FD is 297244416
P 10.65.128.0/17, 1 successors, FD is 28160
P 10.65.0.146/32, 1 successors, FD is 28160

3 REPLIES 3
Highlighted
Hall of Fame Master

Re: Missing EIGRP Routes

Hello @mudvayne15 ,

if the missing prefix 10.65.120.0/21 is learned in BGP you need to redistribute it into EIGRP

 

ip prefix-list BGP-ROUTE permit 10.65.120.0/21

 

route-map BGP-TO-EIGRP permit 10

match ip address prefix BGP-ROUTE

set metric 10000 100 255 1 1500

 

router eigrp 89

redistribute bgp <your-BGP-ASnumber> route-map BGP-TO-EIGRP

 

In EIGRP a seed metric is needed providing its components where the last one is the MTU.

This is done in the route-map alternatively you could set a default-metric at EIGRP process level.

 

Hope to help

Giuseppe

 

Highlighted
Beginner

Re: Missing EIGRP Routes

Thanks for the help, I used your suggestion and it worked fine
ping 10.65.122.31 so 10.63.11.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.65.122.31, timeout is 2 seconds:
Packet sent with a source address of 10.63.11.2
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 76/78/84 ms


Though my other question is, why the other subnet 10.64.1.0 from BGP is reachable. Is it because of the static route 10.65.0.0/19 redistributed in EIGRP?
Highlighted
Hall of Fame Master

Re: Missing EIGRP Routes

Hello @mudvayne15 ,

I'm happy it worked for you.

>> Though my other question is, why the other subnet 10.64.1.0 from BGP is reachable. Is it because of the static route 10.65.0.0/19 redistributed in EIGRP?

yes your understanding is correct that subnet 10.65.1.0 is covered by 10.65.0.0/19

 

Hope to help

Giuseppe