Solved: Issue with routing?!? I know I'm missin... - Page 2

osatronix · ‎02-18-2012

Hi guys

So i decided I will rebuild the whole thing from the begining.

All the addresses and the layout is the same.

I was trying to narrow possible causes - so let me start from here.

-----------------------------------------------------------------------------------------------------------

When on the Router 2 I can ping Routers 1 both interfaces [ .66 and .129]

but

when on Router 1 I can only ping serial interface of Router2 [.65]

I'm attaching debug below. I need to sort that out!!! Please help me.

Thanks.

----------------------------------------------------------------------------------------------------------------

Success rate is 100 percent (5/5), round-trip min/avg/max = 36/37/40 ms

Router---1#

*Mar 1 06:30:54.511: IP: tableid=0, s=192.168.1.66 (local), d=192.168.1.65 (Serial0), routed via FIB

*Mar 1 06:30:54.511: IP: s=192.168.1.66 (local), d=192.168.1.65 (Serial0), len 100, sending

*Mar 1 06:30:54.547: IP: tableid=0, s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), routed via RIB

*Mar 1 06:30:54.547: IP: s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), len 100, rcvd 3

*Mar 1 06:30:54.547: IP: tableid=0, s=192.168.1.66 (local), d=192.168.1.65 (Serial0), routed via FIB

*Mar 1 06:30:54.551: IP: s=192.168.1.66 (local), d=192.168.1.65 (Serial0), len 100, sending

*Mar 1 06:30:54.583: IP: tableid=0, s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), routed via RIB

*Mar 1 06:30:54.583: IP: s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), len 100, rcvd 3

*Mar 1 06:30:54.587: IP: tableid=0, s=192.168.1.66 (local), d=192.168.1.65 (Serial0), routed via FIB

*Mar 1 06:30:54.587: IP: s=192.168.1.66 (local), d=192.168.1.65 (Serial0), len 100, sending

*Mar

Router---1#1 06:30:54.623: IP: tableid=0, s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), routed via RIB

*Mar 1 06:30:54.623: IP: s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), len 100, rcvd 3

*Mar 1 06:30:54.623: IP: tableid=0, s=192.168.1.66 (local), d=192.168.1.65 (Serial0), routed via FIB

*Mar 1 06:30:54.623: IP: s=192.168.1.66 (local), d=192.168.1.65 (Serial0), len 100, sending

*Mar 1 06:30:54.659: IP: tableid=0, s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), routed via RIB

*Mar 1 06:30:54.659: IP: s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), len 100, rcvd 3

*Mar 1 06:30:54.663: IP: tableid=0, s=192.168.1.66 (local), d=192.168.1.65 (Serial0), routed via FIB

*Mar 1 06:30:54.663: IP: s=192.168.1.66 (local), d=192.168.1.65 (Serial0), len 100, sending

*Mar 1 06:30:54.695: IP: tableid=0, s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), routed via RIB

*Mar 1 06:30:54.695: IP: s=192.168.1.65 (Serial0), d=192.168.1.66 (Serial0), len 100, rcvd 3

Router---1#

Router---1#ping 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:

*Mar 1 06:31:19.271: IP: s=192.168.1.66 (local), d=192.168.1.2, len 100, unroutable.

*Mar 1 06:31:21.271: IP: s=192.168.1.66 (local), d=192.168.1.2, len 100, unroutable.

*Mar 1 06:31:23.271: IP: s=192.168.1.66 (local), d=192.168.1.2, len 100, unroutable.

*Mar 1 06:31:25.271: IP: s=192.168.1.66 (local), d=192.168.1.2, len 100, unroutable.

*Mar 1 06:31:27.271: IP: s=192.168.1.66 (local), d=192.168.1.2, len 100, unroutable.

Success rate is 0 percent (0/5)

cadet alain · ‎02-18-2012

Hi,

can you change PPP encapsulation to hdlc with no encap ppp command and do it again.

also if it's not working can you do ping 192.168.1.2 source f0/0 and post the output of the debug.

Regards.

Alain

Don't forget to rate helpful posts.

osatronix · ‎02-19-2012

Hi

I know I'm being pain in the a.s but because of that i can't sleep. I was going to take CCENT exam soon but now I'm realy in doubt.

I did what you suggested and I've chaned encapsulation to HDLC and I was able to ping interface on the other side - BUT only when I was on the router.

When I was trying to ping it from my laptops I couldn't. So I understand that they are routing but not all the traffic???

I'm going mad here.

I removed all the static routing and if you guys could guide me through it - I'm probably doing some stupid mistake when setting this up.

So there is no routing entries and the routing tables are looking like that:

------------

Router1

Gateway of last resort is not set

192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks

C 192.168.1.65/32 is directly connected, Serial0

C 192.168.1.64/26 is directly connected, Serial0

C 192.168.1.128/26 is directly connected, FastEthernet0

----------

Router 2

Gateway of last resort is not set

192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks

C 192.168.1.64/26 is directly connected, Serial0

C 192.168.1.66/32 is directly connected, Serial0

C 192.168.1.0/26 is directly connected, FastEthernet0

Routers are able to reach theirs serial interfaces.

PC on the 192.168.1.0 network can ping .2 interface but I can't ping .65 interface - it says : Dest Host unreachable. BUT I'm able to get .66 interface of Router1.

From the laptops on the 192.168.128 network I can ping .129 interface of Router1 AND its serial interface .66 BUT not .65

What kind of black magic is this????

I'm starting to think that there is something wrong with my hardware.

jamiedoherty · ‎02-19-2012

Ok, you are driving me a little mad too. Let's go with the shotgun approach since precise routing doesn't seem to be working.

On R1:

config t

ip route 0.0.0.0 0.0.0.0 192.168.1.66

On R2:

config t:

ip route 0.0.0.0 0.0.0.0 192.168.1.65

That configures each router to be the other router for its default gateway which will enable full routing between all connected interfaces in this topology. If after those routes go in you still can't ping anything connected from any source interface on either router, then it has to be hardware or something stranger going on and you need to call in a consultant to show you.

osatronix · ‎02-19-2012

Thats what I'm getting

R1

Router---1(config)#ip route 0.0.0.0 0.0.0.0 192.168.1.66

%Invalid next hop address (it's this router)

R2

Router---2(config)#ip route 0.0.0.0 0.0.0.0 192.168.1.65

%Invalid next hop address (it's this router)

I think you meant R1 .65 and R2 .66 - i did that.

Routing tables:

R1

Gateway of last resort is 192.168.1.65 to network 0.0.0.0

192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks

C 192.168.1.65/32 is directly connected, Serial0

C 192.168.1.64/26 is directly connected, Serial0

C 192.168.1.128/26 is directly connected, FastEthernet0

S* 0.0.0.0/0 [1/0] via 192.168.1.65

R2

Gateway of last resort is 192.168.1.66 to network 0.0.0.0

192.168.1.0/24 is variably subnetted, 3 subnets, 2 masks

C 192.168.1.64/26 is directly connected, Serial0

C 192.168.1.66/32 is directly connected, Serial0

C 192.168.1.0/26 is directly connected, FastEthernet0

S* 0.0.0.0/0 [1/0] via 192.168.1.66

When I'm on routers i can ping every single address on any network:

Router1

--------------------------------------------------------------------------------------------------

Router---1#ping 192.168.1.131

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.131, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Router---1#ping 192.168.1.133

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.133, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

Router---1#ping 192.168.1.130

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.130, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Router---1#ping 192.168.1.129

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.129, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Router---1#ping 192.168.1.66

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.66, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 64/65/68 ms

Router---1#ping 192.168.1.65

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.65, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms

Router---1#ping 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/36 ms

Router---1#ping 192.168.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms

Router2

-------------------------------------------------------------------------------------

Router---2#ping 192.168.1.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms

Router---2#ping 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms

Router---2#ping 192.168.1.65

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.65, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 72/80/108 ms

Router---2#ping 192.168.1.66

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.66, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/45/68 ms

Router---2#ping 192.168.1.129

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.129, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/44/64 ms

Router---2#ping 192.168.1.130

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.130, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/45/68 ms

Router---2#ping 192.168.1.131

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.131, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/45/68 ms

Router---2#ping 192.168.1.133

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.133, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/44/64 ms

--------------------------------------------------------------------------------------------

So that works!

But when pinging from the PC or a laptop:

Replay from 192.168.1.64: Destination Host unreachable

jamiedoherty · ‎02-19-2012

I thought this was a crossover T1 with both routers in the same room - those ping times are pretty high if that is the case.

Do the same tests, but source the ping from the Ethernet interface on the router, i.e.:

ping 192.168.1.129 source 192.168.1.1

osatronix · ‎02-19-2012

OK

Router 1

--------------------------------------------------------------------

Router---1#ping 192.168.1.1 source 192.168.1.129

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:

Packet sent with a source address of 192.168.1.129

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms

Router---1#ping 192.168.1.2 source 192.168.1.129

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:

Packet sent with a source address of 192.168.1.129

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms

Router 2

-------------------------------------------------------------------------

Router---2#ping 192.168.1.129 source 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.129, timeout is 2 seconds:

Packet sent with a source address of 192.168.1.2

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/45/68 ms

Router---2#ping 192.168.1.133 source 192.168.1.2

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.1.133, timeout is 2 seconds:

Packet sent with a source address of 192.168.1.2

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 40/45/68 ms

jamiedoherty · ‎02-19-2012

Routing is good, you have a PC issue or some crazy filtering going on that I am not seeing.

View solution in original post

Thotsaphon Lueangwattanaphong · ‎02-19-2012

Hello

1. Test "ping" from hosts behind the routers.

2. Post the output of "debug ip routing" and "debug ip packet detail" on the routers

Toshi

Sent from Cisco Technical Support iPhone App

osatronix · ‎02-19-2012

OK

I've run that on the Router 2:

Router---2#debug ip packet detail

IP packet debugging is on (detailed)

Now I'm generating traffic (pinging laptop .133 on the other side) but i can't see any outcome on the router.

How do I do that?

Thanks.

Thotsaphon Lueangwattanaphong · ‎02-19-2012

Hello

Just run it on R1. Traffic gernerated on hosts behind R1.

Toshi

Sent from Cisco Technical Support iPhone App

View solution in original post

osatronix · ‎02-19-2012

Hi

WOW.

I took an hour brake. Came back and typed the command

Router---1#debug ip routing

IP routing debugging is on

Router---2#debug ip routing

IP routing debugging is on

Now when I'm pinging from the .133 laptop i can reach .1 PC !!!

The output I'm getting from the Router 1:

Router---1#debug ip routing

IP routing debugging is on

Router---1#

*Mar 1 10:34:21.279: RT: NET-RED 0.0.0.0/0

These messages are showing every 1 minute.

*Mar 1 10:36:21.279: RT: NET-RED 0.0.0.0/0

Router---1#

*Mar 1 10:37:21.279: RT: NET-RED 0.0.0.0/0

Router---1#

*Mar 1 10:38:21.279: RT: NET-RED 0.0.0.0/0

There is nothing showing on Router 2 and still cant ping .133 host from .1

What have i done that now i'm able to ping from .133 - typing debug command was all i did???

osatronix · ‎02-19-2012

Thanks a lot.

Have you got any idea what may causing this?

I have all firewalls disabled.

Maybe it's the switch that is doing something odd - i'm just guessing here.

ebarticel · ‎02-19-2012

Do you have both routers and all end devices plugged into one switch?

If yes, I would connect PC directly to one router with a cross-over cable and test again

Eugen

osatronix · ‎02-19-2012

Hi

Thats is exactly how i got this set up.

There is a PPT file attached to my post #1 on the top of this page - so you can see it clearly.

Thanks

Re: Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Re: Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Re: Issue with routing?!? I know I'm missing something.

Re: Issue with routing?!? I know I'm missing something.

Issue with routing?!? I know I'm missing something.

Re: Issue with routing?!? I know I'm missing something.

Re: Issue with routing?!? I know I'm missing something.