cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
603
Views
0
Helpful
8
Replies

Routing Next Hop Issue

chueymtz
Level 1
Level 1

 

Based on the route configurations below, I am having issues getting to the next hop. I recently created a 10.78.x.x network that needs to follow the same as the 10.76.x.x network which currently works. I need both of these to be able to hit anything on a 10.0.0.0 network. So far I can't get it to work on the 10.78.x.x side of it, need some suggestions.

 

Router 1:

ip forward-protocol nd
ip telnet source-interface Vlan x
ip http server
ip http authentication local
ip http secure-server
ip route 0.0.0.0 0.0.0.0 10.76.2.10
ip route 10.233.4.0 255.255.254.0 172.16.2.2
ip route 10.243.4.x 255.255.254.0 172.16.2.2 
ip route 172.2x.x.0 255.255.255.0 10.76.200.1

Router 2:

ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
ip route 10.0.0.0 255.0.0.0 10.76.1.2 200
ip route 172.2x.0.0 255.255.0.0 10.76.1.2
ip route 172.2x.2x.0 255.255.255.0 10.76.1.2

If I run a traceroute from anything on 10.76.x.x it works getting to based on the route below:

Tracing route to 10.11x.0.1xx
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.76.2.1
2 1 ms <1 ms <1 ms 10.76.200.1
3 <1 ms 1 ms <1 ms 10.76.1.2
4 2 ms 7 ms 2 ms 10.16x.0.x
5 1 ms 1 ms 1 ms 10.16x.0.1x
6 2 ms 1 ms 1 ms 10.11x.0.1x

When I try to ping from my new 10.78.x.x network I cannot reach the same sites that are on 10.11x.0.1xx

Tracing route to 0.11x.0.1xx
over a maximum of 30 hops:

1 7 ms 7 ms 9 ms 10.78.2.129
2 8 ms 7 ms 7 ms 10.76.200.1
3 * *

I know it is a route issue I just don't know what I need to input to make it work.

8 Replies 8

Go to this router 10.76.200.1

Do 

Show ip route 10.11x.0.1xx longest

Then check egress interface

Check the router connected to this interface 

Now in that router do

Show ip route <source subnet of traceroute you use> longest

This will help you to detect routing issues 

MHM

Router 1#sho ip route 10.1x.0.1xx
Routing entry for 10.0.0.0/8
Known via "static", distance 200, metric 0
Redistributing via eigrp 99
Advertised by eigrp 99 metric 10240 1 100 1 1500
Routing Descriptor Blocks:
* 10.76.1.2
Route metric is 0, traffic share count is 1

Router 2#sh ip route 10.1x.0.1xx
Routing entry for 10.0.0.0/8
Known via "eigrp 99", distance 170, metric 250368, precedence routine (0), type external
Redistributing via eigrp 99
Last update from 10.76.200.1 on TenGigabitEthernet1/1/1, 2w0d ago
Routing Descriptor Blocks:
* 10.76.200.1, from 10.76.200.1, 2w0d ago, via TenGigabitEthernet1/1/1
Route metric is 250368, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 10240 Kbit
Reliability 100/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1

This is what I got

Router 1:

router eigrp 99
network 10.76.0.0 0.0.0.255
network 10.76.200.0 0.0.0.255
network 10.78.0.0 0.0.0.255
network 192.168.1.0
redistribute static metric 10240 1 100 1 1500
passive-interface GigabitEthernet1/0/2

 

 

Router 2:

outer eigrp 99
network 10.76.0.0 0.0.0.255
network 10.76.2.0 0.0.0.255
network 10.76.200.0 0.0.0.255
network 10.78.0.0 0.0.0.255
network 10.78.2.0 0.0.0.255
network 172.16.0.0
network 192.168.0.0
network 192.168.2.0

 

analysis the output 10.1x.0.1xx

R1

Router 1#sho ip route 10.1x.0.1xx

Routing entry for 10.0.0.0/8
Known via "static", distance 200, metric 0
Redistributing via eigrp 99
Advertised by eigrp 99 metric 10240 1 100 1 1500
Routing Descriptor Blocks:
* 10.76.1.2
Route metric is 0, traffic share count is 1

10.1x.0.1xx is static route toward 10.76.1.2 then this will redistribute into EIGRP 99

R2

Router 2#sh ip route 10.1x.0.1xx
Routing entry for 10.0.0.0/8
Known via "eigrp 99", distance 170, metric 250368, precedence routine (0), type external
Redistributing via eigrp 99
Last update from 10.76.200.1 on TenGigabitEthernet1/1/1, 2w0d ago
Routing Descriptor Blocks:
* 10.76.200.1, from 10.76.200.1, 2w0d ago, via TenGigabitEthernet1/1/1
Route metric is 250368, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 10240 Kbit
Reliability 100/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1

10.76.200.1 is R1 IP of interface connect to R2 and the route is learn via R2 

all above meanig that the R2 have route toward R1 for 10.1x.0.1xx

try ping from R2 toward 10.1x.0.1xx
it can that there is ACL drop the traceroute for this new IP 

MHM

 

I can ping from both r1 and r2, traceroute shows the following 

HQ_9300#traceroute 10.110.0.144
Type escape sequence to abort.
Tracing the route to 10.110.0.144
VRF info: (vrf in name/id, vrf out name/id)
1 10.76.200.1 1 msec 1 msec 1 msec
2 10.76.1.2 1 msec 1 msec 1 msec
3 10.1xx.0.1xx 1 msec 2 msec 4 msec
4 10.1xx.0.x 2 msec 2 msec 3 msec
5 10.1xx.0.1xx 2 msec * 3 msec

 

Router 1#sho ip route 10.1x.0.1xx <<- this is same as 10.110.0.144 ??
you use xx in subnet and I can not get exactly the subnet you have issue with 
also the last trace is OK which in not same as original post ?

please do 
show ip route <the subnet with issue > longest 
share this in both router
MHM
 

Hello,

 

All of your routers need to know how to get to and from your source and destination. From the first traceroute it looks like all your routers know how to get from 10.76.x.x to 10.11x.0.1xx.

However on the second traceroute it stops at 10.76.200.1. Does that device and all the devices after it know how to get back to your new network of 10.78.x.x.?

Can you provide a show ip route for that network on that router and the next device?

-David

Router 1#sh ip route

Gateway of last resort is 10.76.200.40 to network 0.0.0.0

D*EX 0.0.0.0/0 [170/28416] via 10.76.200.40, 6d01h, GigabitEthernet1/0/1
[170/28416] via 10.76.200.36, 6d01h, GigabitEthernet1/0/1
[170/28416] via 10.76.200.22, 6d01h, GigabitEthernet1/0/1
[170/28416] via 10.76.200.2, 6d01h, GigabitEthernet1/0/1
10.0.0.0/8 is variably subnetted, 34 subnets, 6 masks
S 10.0.0.0/8 [200/0] via 10.76.1.2
C 10.76.1.0/30 is directly connected, GigabitEthernet1/0/2
L 10.76.1.1/32 is directly connected, GigabitEthernet1/0/2
D 10.76.2.0/24 [90/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
D 10.76.4.0/24 [90/28416] via 10.76.200.4, 7w0d, GigabitEthernet1/0/1
D 10.76.6.0/24 [90/28416] via 10.76.200.6, 7w0d, GigabitEthernet1/0/1
D 10.76.8.0/24
[90/28416] via 10.76.200.8, 23:53:19, GigabitEthernet1/0/1
D 10.76.10.0/24 [90/28416] via 10.76.200.10, 7w0d, GigabitEthernet1/0/1
D 10.76.12.0/24 [90/28416] via 10.76.200.12, 3w0d, GigabitEthernet1/0/1
D 10.76.14.0/24 [90/28416] via 10.76.200.14, 7w0d, GigabitEthernet1/0/1
D 10.76.16.0/24 [90/28416] via 10.76.200.16, 7w0d, GigabitEthernet1/0/1
D 10.76.18.0/24 [90/28416] via 10.76.200.18, 2w1d, GigabitEthernet1/0/1
D 10.76.22.0/24 [90/28416] via 10.76.200.22, 7w0d, GigabitEthernet1/0/1
D 10.76.24.0/24
[90/28416] via 10.76.200.24, 6d01h, GigabitEthernet1/0/1
D 10.76.28.0/24 [90/28416] via 10.76.200.28, 7w0d, GigabitEthernet1/0/1
D 10.76.32.0/24 [90/28416] via 10.76.200.32, 7w0d, GigabitEthernet1/0/1
D 10.76.34.0/24
[90/28416] via 10.76.200.34, 2d02h, GigabitEthernet1/0/1
D 10.76.36.0/24 [90/28416] via 10.76.200.36, 7w0d, GigabitEthernet1/0/1
D 10.76.38.0/24 [90/28416] via 10.76.200.38, 7w0d, GigabitEthernet1/0/1
D 10.76.40.0/24 [90/28416] via 10.76.200.40, 7w0d, GigabitEthernet1/0/1
D 10.76.42.0/24 [90/28416] via 10.76.200.42, 7w0d, GigabitEthernet1/0/1
D 10.76.44.0/24 [90/28416] via 10.76.200.44, 7w0d, GigabitEthernet1/0/1
C 10.76.200.0/24 is directly connected, GigabitEthernet1/0/1
L 10.76.200.1/32 is directly connected, GigabitEthernet1/0/1
D 10.78.2.0/25 [90/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
D 10.78.2.128/25 [90/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
D 10.78.6.128/25 [90/28416] via 10.76.200.6, 7w0d, GigabitEthernet1/0/1
D 10.78.8.0/25
[90/28416] via 10.76.200.8, 23:53:19, GigabitEthernet1/0/1
D 10.78.8.128/25
[90/28416] via 10.76.200.8, 23:53:19, GigabitEthernet1/0/1
D 10.78.12.0/25 [90/28416] via 10.76.200.12, 3w0d, GigabitEthernet1/0/1
D 10.78.18.0/24 [90/28416] via 10.76.200.18, 1w0d, GigabitEthernet1/0/1
D 10.78.22.128/25
[90/28416] via 10.76.200.22, 4w5d, GigabitEthernet1/0/1
D EX 10.23x.4.0/23 [170/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
D EX 10.24x.4.0/23 [170/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
172.16.0.0/23 is subnetted, 20 subnets
D 172.16.2.0 [90/28416] via 10.76.200.2, 2w0d, GigabitEthernet1/0/1
D 172.16.4.0 [90/28416] via 10.76.200.4, 7w0d, GigabitEthernet1/0/1
D 172.16.6.0 [90/28416] via 10.76.200.6, 7w0d, GigabitEthernet1/0/1
D 172.16.8.0 [90/28416] via 10.76.200.8, 23:53:19, GigabitEthernet1/0/1
D 172.16.10.0 [90/28416] via 10.76.200.10, 7w0d, GigabitEthernet1/0/1
D 172.16.12.0 [90/28416] via 10.76.200.12, 3w0d, GigabitEthernet1/0/1
D 172.16.14.0 [90/28416] via 10.76.200.14, 7w0d, GigabitEthernet1/0/1
D 172.16.16.0 [90/28416] via 10.76.200.16, 7w0d, GigabitEthernet1/0/1
D 172.16.18.0 [90/28416] via 10.76.200.18, 2w1d, GigabitEthernet1/0/1
D 172.16.22.0 [90/28416] via 10.76.200.22, 7w0d, GigabitEthernet1/0/1
D 172.16.24.0 [90/28416] via 10.76.200.24, 6d01h, GigabitEthernet1/0/1
D 172.16.28.0 [90/28416] via 10.76.200.28, 7w0d, GigabitEthernet1/0/1
D 172.16.32.0 [90/28416] via 10.76.200.32, 7w0d, GigabitEthernet1/0/1
D 172.16.34.0 [90/28416] via 10.76.200.34, 2d02h, GigabitEthernet1/0/1
D 172.16.36.0 [90/28416] via 10.76.200.36, 7w0d, GigabitEthernet1/0/1
D 172.16.38.0 [90/28416] via 10.76.200.38, 7w0d, GigabitEthernet1/0/1
D 172.16.40.0 [90/28416] via 10.76.200.40, 7w0d, GigabitEthernet1/0/1
D 172.16.42.0 [90/28416] via 10.76.200.42, 7w0d, GigabitEthernet1/0/1
D 172.16.44.0 [90/28416] via 10.76.200.44, 7w0d, GigabitEthernet1/0/1
D 172.16.50.0 [90/28416] via 10.76.200.50, 1w6d, GigabitEthernet1/0/1
172.2x.0.0/16 is variably subnetted, 2 subnets, 2 masks
S 172.2x.0.0/16 [1/0] via 10.76.1.2
S 172.2x.xx.0/24 [1/0] via 10.76.1.2
D 192.168.10.0/24 [90/156160] via 10.76.200.10, 7w0d, GigabitEthernet1/0/1
D 192.168.12.0/24 [90/28416] via 10.76.200.12, 3w0d, GigabitEthernet1/0/1
D 192.168.14.0/24 [90/156160] via 10.76.200.14, 7w0d, GigabitEthernet1/0/1
D 192.168.18.0/24 [90/156160] via 10.76.200.18, 2w1d, GigabitEthernet1/0/1
D 192.168.22.0/24 [90/156160] via 10.76.200.22, 4w3d, GigabitEthernet1/0/1
D 192.168.32.0/24 [90/156160] via 10.76.200.32, 7w0d, GigabitEthernet1/0/1
D 192.168.34.0/24
[90/156160] via 10.76.200.34, 2d02h, GigabitEthernet1/0/1
D 192.168.36.0/24 [90/156160] via 10.76.200.36, 7w0d, GigabitEthernet1/0/1
D 192.168.38.0/24 [90/156160] via 10.76.200.38, 7w0d, GigabitEthernet1/0/1
D 192.168.40.0/24 [90/156160] via 10.76.200.40, 7w0d, GigabitEthernet1/0/1
D 192.168.42.0/24 [90/156160] via 10.76.200.42, 7w0d, GigabitEthernet1/0/1
D 192.168.44.0/24 [90/156160] via 10.76.200.44, 7w0d, GigabitEthernet1/0/1
D 192.168.50.0/24 [90/156160] via 10.76.200.50, 1w6d, GigabitEthernet1/0/1

Router 2#sh ip route
Gateway of last resort is 10.76.2.10 to network 0.0.0.0

S* 0.0.0.0/0 [1/0] via 10.76.2.10
10.0.0.0/8 is variably subnetted, 35 subnets, 5 masks
D EX 10.0.0.0/8
[170/250368] via 10.76.200.1, 2w0d, TenGigabitEthernet1/1/1
C 10.76.2.0/24 is directly connected, Vlan100
L 10.76.2.1/32 is directly connected, Vlan100
D 10.76.4.0/24 [90/3072] via 10.76.200.4, 2w0d, TenGigabitEthernet1/1/1
D 10.76.6.0/24 [90/3072] via 10.76.200.6, 2w0d, TenGigabitEthernet1/1/1
D 10.76.8.0/24
[90/3072] via 10.76.200.8, 23:56:12, TenGigabitEthernet1/1/1
D 10.76.10.0/24
[90/3072] via 10.76.200.10, 2w0d, TenGigabitEthernet1/1/1
D 10.76.12.0/24
[90/3072] via 10.76.200.12, 1w1d, TenGigabitEthernet1/1/1
D 10.76.14.0/24
[90/3072] via 10.76.200.14, 2w0d, TenGigabitEthernet1/1/1
D 10.76.16.0/24
[90/3072] via 10.76.200.16, 1w1d, TenGigabitEthernet1/1/1
D 10.76.18.0/24
[90/3072] via 10.76.200.18, 2w0d, TenGigabitEthernet1/1/1
D 10.76.22.0/24
[90/3072] via 10.76.200.22, 1w1d, TenGigabitEthernet1/1/1
D 10.76.24.0/24
[90/3072] via 10.76.200.24, 6d01h, TenGigabitEthernet1/1/1
D 10.76.28.0/24
[90/3072] via 10.76.200.28, 2w0d, TenGigabitEthernet1/1/1
D 10.76.32.0/24
[90/3072] via 10.76.200.32, 2w0d, TenGigabitEthernet1/1/1
D 10.76.34.0/24
[90/3072] via 10.76.200.34, 2d02h, TenGigabitEthernet1/1/1
D 10.76.36.0/24
[90/3072] via 10.76.200.36, 2w0d, TenGigabitEthernet1/1/1
D 10.76.38.0/24
[90/3072] via 10.76.200.38, 2w0d, TenGigabitEthernet1/1/1
D 10.76.40.0/24
[90/3072] via 10.76.200.40, 1w1d, TenGigabitEthernet1/1/1
D 10.76.42.0/24
[90/3072] via 10.76.200.42, 2w0d, TenGigabitEthernet1/1/1
D 10.76.44.0/24
[90/3072] via 10.76.200.44, 2w0d, TenGigabitEthernet1/1/1
C 10.76.200.0/24 is directly connected, TenGigabitEthernet1/1/1
L 10.76.200.2/32 is directly connected, TenGigabitEthernet1/1/1
C 10.78.2.0/25 is directly connected, Vlan500
L 10.78.2.1/32 is directly connected, Vlan500
C 10.78.2.128/25 is directly connected, Vlan300
L 10.78.2.129/32 is directly connected, Vlan300
D 10.78.6.128/25
[90/3072] via 10.76.200.6, 2w0d, TenGigabitEthernet1/1/1
D 10.78.8.0/25
[90/3072] via 10.76.200.8, 23:56:12, TenGigabitEthernet1/1/1
D 10.78.8.128/25
[90/3072] via 10.76.200.8, 23:56:12, TenGigabitEthernet1/1/1
D 10.78.12.0/25
[90/3072] via 10.76.200.12, 1w1d, TenGigabitEthernet1/1/1
D 10.78.18.0/24
[90/3072] via 10.76.200.18, 1w0d, TenGigabitEthernet1/1/1
D 10.78.22.128/25
[90/3072] via 10.76.200.22, 1w1d, TenGigabitEthernet1/1/1
S 10.23x.4.0/23 [1/0] via 172.16.2.2
S 10.24x.4.0/23 [1/0] via 172.16.2.2
172.16.0.0/16 is variably subnetted, 21 subnets, 2 masks
C 172.16.2.0/23 is directly connected, Vlan200
L 172.16.2.1/32 is directly connected, Vlan200
D 172.16.4.0/23
[90/3072] via 10.76.200.4, 2w0d, TenGigabitEthernet1/1/1
D 172.16.6.0/23
[90/3072] via 10.76.200.6, 2w0d, TenGigabitEthernet1/1/1
D 172.16.8.0/23
[90/3072] via 10.76.200.8, 23:56:12, TenGigabitEthernet1/1/1
D 172.16.10.0/23
[90/3072] via 10.76.200.10, 2w0d, TenGigabitEthernet1/1/1
D 172.16.12.0/23
[90/3072] via 10.76.200.12, 1w1d, TenGigabitEthernet1/1/1
D 172.16.14.0/23
[90/3072] via 10.76.200.14, 2w0d, TenGigabitEthernet1/1/1
D 172.16.16.0/23
[90/3072] via 10.76.200.16, 1w1d, TenGigabitEthernet1/1/1
D 172.16.18.0/23
[90/3072] via 10.76.200.18, 2w0d, TenGigabitEthernet1/1/1
D 172.16.22.0/23
[90/3072] via 10.76.200.22, 1w1d, TenGigabitEthernet1/1/1
D 172.16.24.0/23
[90/3072] via 10.76.200.24, 6d01h, TenGigabitEthernet1/1/1
D 172.16.28.0/23
[90/3072] via 10.76.200.28, 2w0d, TenGigabitEthernet1/1/1
D 172.16.32.0/23
[90/3072] via 10.76.200.32, 2w0d, TenGigabitEthernet1/1/1
D 172.16.34.0/23
[90/3072] via 10.76.200.34, 2d02h, TenGigabitEthernet1/1/1
D 172.16.36.0/23
[90/3072] via 10.76.200.36, 2w0d, TenGigabitEthernet1/1/1
D 172.16.38.0/23
[90/3072] via 10.76.200.38, 2w0d, TenGigabitEthernet1/1/1
D 172.16.40.0/23
[90/3072] via 10.76.200.40, 1w1d, TenGigabitEthernet1/1/1
D 172.16.42.0/23
[90/3072] via 10.76.200.42, 2w0d, TenGigabitEthernet1/1/1
D 172.16.44.0/23
[90/3072] via 10.76.200.44, 2w0d, TenGigabitEthernet1/1/1
D 172.16.50.0/23
[90/3072] via 10.76.200.50, 1w6d, TenGigabitEthernet1/1/1
172.2x.0.0/16 is variably subnetted, 2 subnets, 2 masks
D EX 172.2x.0.0/16
[170/250368] via 10.76.200.1, 2w0d, TenGigabitEthernet1/1/1
S 172.2x.xx.0/24 [1/0] via 10.76.200.1
D 192.168.10.0/24
[90/128512] via 10.76.200.10, 2w0d, TenGigabitEthernet1/1/1
D 192.168.12.0/24
[90/3072] via 10.76.200.12, 1w1d, TenGigabitEthernet1/1/1
D 192.168.14.0/24
[90/128512] via 10.76.200.14, 2w0d, TenGigabitEthernet1/1/1
D 192.168.18.0/24
[90/128512] via 10.76.200.18, 2w0d, TenGigabitEthernet1/1/1
D 192.168.22.0/24
[90/128512] via 10.76.200.22, 1w1d, TenGigabitEthernet1/1/1
D 192.168.32.0/24
[90/128512] via 10.76.200.32, 2w0d, TenGigabitEthernet1/1/1
D 192.168.34.0/24
[90/128512] via 10.76.200.34, 2d02h, TenGigabitEthernet1/1/1
D 192.168.36.0/24
[90/128512] via 10.76.200.36, 2w0d, TenGigabitEthernet1/1/1
D 192.168.38.0/24
[90/128512] via 10.76.200.38, 2w0d, TenGigabitEthernet1/1/1
D 192.168.40.0/24
[90/128512] via 10.76.200.40, 1w1d, TenGigabitEthernet1/1/1
D 192.168.42.0/24
[90/128512] via 10.76.200.42, 2w0d, TenGigabitEthernet1/1/1
D 192.168.44.0/24
[90/128512] via 10.76.200.44, 2w0d, TenGigabitEthernet1/1/1
D 192.168.50.0/24
[90/128512] via 10.76.200.50, 1w6d, TenGigabitEthernet1/1/1

Hello
Can you post a topology diagram it would be much easier to interpret


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
Review Cisco Networking for a $25 gift card