Re: Rip Configuration issue

r.singletary · ‎10-04-2002

I have two (2) Cisco 2501 routers

Rtr A

S1 - ip address 201.100.11.2

E0 - ip address 192.5.5.1

PC - attached to E0 - ip address 192.5.5.5 subnet mask 255.255.255.0

gateway 192.5.5.1

Rtr B

S0 - ip address 201.100.11.1

Problem - Rtr A and Rtr B can ping PC at ip address 192.5.5.5

PC can only ping Rtr A e0 ip address at 192.5.5.1

PC was able to ping through entire network previoulsy

Both Rtr A and Rtr B are runing RIP V1

Rtr A is advertising network 201.100.11.0 and 192.5.5.0

Rtr B is advertising network 201.100.11.0

I have turned on debug for RIP on Rtr A which is sending V1 updates to 255.255.255.255 via E0 192.5.5.1and sending V1 updates to 255.255.255.255 via S1 201.200.11.2

Rtr B is receiving V1 update from 201.100.11.2 on S0 for 192.5.5.0 in 1 hops

sending V1 updates to 255.255.255.255 via S0 201.100.11.1

What is the solution? PC should be able to ping all the way through the network. It was at one point, but stopped after the workstation was rebooted. Is their a bug in RIP?

thisisshanky · ‎10-04-2002

Are you able to ping the router As serial interface ? Can you double check your settings on the PC.

Sankar Nair
UC Solutions Architect
Pacific Northwest | CDW
CCIE Collaboration #17135 Emeritus

r.singletary · ‎10-04-2002

Since I posted the message, I am now able to ping from the Workstation to Router A and Router B. No configuration changes to the Workstation or the Router were performed. This has happened in the past, and I am attempting to troubleshot and see why. I do not understand why it happens.

Also there are no access list and the configuration is a very simple one. Any help would be appreciated.

steve.barlow · ‎10-04-2002

What can't the PC ping, a network on the other side of routerB? RouterB is only advertising one route to routerA, and that's already in routerA's table (directly connected). If there are routes on the other side of routerB, are they in routerA's routing table? Can routerA ping those networks? RouterB can ping the PC but the PC can't ping routerB?

Steve

r.singletary · ‎10-04-2002

The PC can now ping Router A and B. This has happened in the past and I am attempting to troubleshoot. NO configuration changes were perfomed on the PC or routers. This seems like a bug to me.

Any suggestions would be appreciated.

steve.barlow · ‎10-05-2002

When it's not working, can you do an extended ping from the PC interface (e0) to routerb? Also, check the arp table on the PC when it's not working.

Let us know.

Steve

r.singletary · ‎10-09-2002

Steve,

As suggested I checked the arp table on the pc, and discovered the only entry is for RTR A E0 interface. At this point I am only able to ping RTR A at the ip address 192.5.5.1 (which is it's directly connected interface on E0). From the PC I can ping E0 but cannot ping RTR A Serial 1 at ip address 201.100.11.2.

However from RTR B, (which is connected to RTR A via S0), I can ping the PC. From RTR A I can also ping the PC. The only problem I have is pinging in reverse. Going from the PC to RTR A and to RTR B.

Thanks for you help

nnorthedge · ‎10-10-2002

Just a question. Does the LAN the PC is attached have more than one router? The second router could be sending default gateway updates to the PC. Even another workstation attached to 2 LANs could be acting as a router. You may want to check the routing table on the PC the next time it fails to get to RtrB.

Norman

r.singletary · ‎10-12-2002

Norman,

The PC is only attached to one router via its E0 interface. I intentionally kept it simple, to eliminate any other potential issues.

Thanks for your response

Richard