Troubleshooting RIP with debug/sh ip route information

Stigmatas

Debug ip rip
07:12:56 RIP: received v1 update from 172.16.100.2 on S0/0
07:12:56 172.16.10.0 in 1 hops
07:12:56 172.16.20.0 in 1 hops
07:12:56 172.16.30.0 in 1 hops

sh ip route

Gateway of last resort is not set.

172.16.0.0/24 Is subnetted, 8 subnets
C 172.16.0.0 is directly connected, FastEthernet 0/0
C 172.16.0.0 is directly connected, Loopback2
R 172.16.0.0 is directly connected, Loopback1
R 172.16.0.0 is directly connected, Loopback0
R 172.16.0.0 [120/2] via 172.16.100.2, 00:00:04, Serial 0/0
S 172.16.0.0 [120/2] via 172.16.150.15
R 172.16.0.0 [120/2] via 172.16.100.2 00:00:04, Serial 0/0
R 172.16.0.0 [120/2] is directly connected, Serial 0/0

Can you tell why users can't access 172.16.20.0?

After giving it some thought.. does the static route or the AD have anything to do with why?

Could someone give me their answer so maybe it goes into my head why. I have the answer from the book but to me it's not clear....

Thanks in advance for the help and clarification.

Stigmatas

Via page 398 hops are inconsistent - Lammle Forum lol

R 172.16.0.0 [120/2] is directly connected, Serial 0/0

That line should be this. Route type changed, and hop count.

**C 172.16.0.0 [120/1] is directly connected, Serial 0/0

Upon 2nd review of problem. Is there a confusion between these two lines which cause the problem?

c 172.16.150.0 is directly connected, fa 0/0
and
s 172.16.20.0 [120/2] via 172.16.150.15 ????

Stigmatas

So here is my full understanding incase anyone else actually thought about helping.
RIP when it updates, send it's FULL routing table to neighboring routers. So to get to 172.16.20.0 you can to go through S0/0 which is shown here "received v1 update from 172.16.100.2 on S0/0" in the debug ip rip output.

Now looking at the sh ip route, you can see to get to 172.16.20.0 you have to go through 172.16.150.15. 172.16.150.15 is not a network ID. It is a node.
To get to 172.16.150.15 you have to go through FA0/0 is NOT in the equation.
Essentially you have routed all packets going to 172.16.20.0 to a blackhole. Until that static route is fixed, you will not be able to reach that network 172.16.20.0.

Rip does not find it's way home. It doesn't come back around the network to get to where it has to go. On hop at a time. If the information is not at the next hop, you are SOL.

tech-airman

Stigmatas,

Stigmatas wrote: »

Debug ip rip
07:12:56 RIP: received v1 update from 172.16.100.2 on S0/0
07:12:56 172.16.10.0 in 1 hops
07:12:56 172.16.20.0 in 1 hops
07:12:56 172.16.30.0 in 1 hops

sh ip route

Gateway of last resort is not set.

172.16.0.0/24 Is subnetted, 8 subnets
C 172.16.0.0 is directly connected, FastEthernet 0/0
C 172.16.0.0 is directly connected, Loopback2
R 172.16.0.0 is directly connected, Loopback1
R 172.16.0.0 is directly connected, Loopback0
R 172.16.0.0 [120/2] via 172.16.100.2, 00:00:04, Serial 0/0
S 172.16.0.0 [120/2] via 172.16.150.15
R 172.16.0.0 [120/2] via 172.16.100.2 00:00:04, Serial 0/0
R 172.16.0.0 [120/2] is directly connected, Serial 0/0

Can you tell why users can't access 172.16.20.0?

Relative to this router, where is network 172.16.20.0?

Stigmatas wrote: »

After giving it some thought.. does the static route or the AD have anything to do with why?

What does AD stand for?

Stigmatas wrote: »

Could someone give me their answer so maybe it goes into my head why. I have the answer from the book but to me it's not clear....

Thanks in advance for the help and clarification.

Stigmatas

There is no more information in the book that what I provided for you.
AD = administrative distance.

CCNA: Cisco Certified Network ... - Google Books

is the page and what it looks like.

page 398