static routes (optimal next hop)

Mr.Robot255

Hi all

im just on Packet tracer setting up some labs

say for example i have 4 routers in a ring and a switch off each router with one pc connected to each switch
For static routes from Router5 in pic i was using all the same next hop , so to reach PC 2 i'd use 10.41.12.2 (gig0/1 of router4 in pic) and same next hop if i wanted to reach PC0

my question is will the extra hops matter should i be thinking of best paths?
i am thinking of setting it up that its easier to remember one next hop and to configure this way, but for optimality would i better off choosing the nearest next hop to destination/direction its heading

pujan96

if you set up all your next hops to r4 you would then need to configure a static route to R7 and then R6, not pretty efficent???

Mr.Robot255

im not sure i understand what you mean Pujan

i am setting static routes from all routers , each routers static route next hop will be the next routers nearest int going in a clockwise direction if that makes sense.
router5 next hop for static routes will be router4 gig0/1
router4 next hop for static routes will be router7 gig0/2
router7 next hop for static routes will be router6 gig0/1 (which is bottom left router)
router6 next hop for static routes will be router5 gig0/2

am i doing it wrong?

i have set that up and at the moment all can ping each other except PC0 bottom left corner, it can ping its default gateway im in process of finding my fault.

networker050184

Will it matter? In a lab no. In a production environment where those routers are hundreds or thousands of miles apart? Yeah probably. Would you want users hanging off R5 to take a path with 100ms or 10ms latency?

In the real world you'd probably just set up a routing protocol and be done with it though.

DCD

Do a "show IP route" for each router. You probably don't have route back. It will be easier if you post the PT file or the configuration for each router.

Priston

If PC1 has to send a large file to PC0 and PC2 has to send a large file to PC3, do you want the file transfers sharing the same bandwidth?

Mr.Robot255

yes routing protocols must come in icnd2 (RIPv2 icnd1) this is a lab from udemy posted the other day here.

out of curiosity whats best method to upload packet tracer files to here? i tried to attach one but said file not accepted.

Mr.Robot255

here is the packet tracer file i uploaded it to filedropper.

if this is a misconfiguration on my end can someone point me in right direction to solve it. Don't actually tell me what the problem is, i wanna see can i solve these problems. Unless its a random glitch (doubtful )

im sure its at router6 or possibly PC0 (bottom left) i have run show ip int brief , show ip route it all looks fine to me.

Router6 can ping everyone tho, it can ping the 3 other PCs and each interface on every other router.
sometimes they fail first try but succeed 2nd try
PC0 however can only ping as far as the 3 interfaces on attached router6


http://www.filedropper.com/staticroutestracer

Ismaeljrp

Have you implemented Cisco's recommended troubleshooting steps?

Ping the local host loopback
Ping the local host NIC
Ping the default gateway
Ping the remote IP

Then do a tracert or traceroute. Start troubleshooting from the last hop in the trace.

Mr.Robot255

yes as far as i know i have tried all that

the problem seems to be somewhere within router6 gig 0/0 10.41.33.1/24
network i.d 10.41.33.0 /24


im at a loss on this one now






i can ping gig 0/1 and gig 0/2 from all other devices except gig 0/0


GigabitEthernet0/0 is up, line protocol is up (connected)
Hardware is CN Gigabit Ethernet, address is 000c.85ae.a601 (bia 000c.85ae.a601)
Internet address is 10.41.33.1/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is RJ45
output flow-control is unsupported, input flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00,
Last input 00:00:08, output 00:00:05, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: fifo
Output queue :0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
34 packets input, 4352 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 1017 multicast, 0 pause input
0 input packets with dribble condition detected
26 packets output, 3328 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out

Ismaeljrp

Found your issue.

I'll give you a hint. Use the extended ping options on router 6.

Ping from a source address of 10.41.33.1. You will see it fails. The issue with this topology, is it is a ring topology. Review the the cons of using a Ring topology. Now once you have reviewed that, verify each router you expect should be the next hop.

Remember that Ping actually tests two way traffic. Sometimes it's not an issue of you arriving to your destination, it may be the echo replies not reaching you.

Mr.Robot255

Hi Ismaeljrp

i have never used or seen that extended ping options before i will go over properly in the morning

thanks for replying

Ismaeljrp

Extended ping is very handy, I believe it's also an exam objective to know how to use it for troubleshooting.

Glad to help and good luck with your studies.

DCD

Mr.Robot255 wrote: »

Hi all

my question is will the extra hops matter should i be thinking of best paths?
i am thinking of setting it up that its easier to remember one next hop and to configure this way, but for optimality would i better off choosing the nearest next hop to destination/direction its heading

The way you should do it is the nearest next hop address.

Mr.Robot255

thanks again for replies

the error was at router 4 (top left in pic) the static route i entered was wrong so i was missing a route cos of the typo

10.41.41.0/24 [1/0] via 10.41.24.2 it should have been 10.41.33.0/24 [1/0] via 10.41.24.2