From: Hobbs (deadheadblues@gmail.com)
Date: Sat Nov 29 2008 - 19:56:08 ARST
I have seen this to, it seems like the receiver is supposed to increment
upon receipt, not when advertising. But that's not the way it is and I think
this explanation may be wrong:
"When a router receives a routing update that contains a new or changed
destination network entry, the router adds 1 to the metric value indicated
in the update and enters the network in the routing table."
From:
http://www.cisco.com/en/US/docs/internetworking/technology/handbook/RIP.html
Check this out (I have R2-R4 in similar scenario):
R2 sends with metric 2 (redistributing from ospf)
R2#debug ip rip
RIP protocol debugging is on
R2#
Nov 29 21:47:13.215: RIP: sending v2 update to 224.0.0.9 via Serial0/1/0.24
(172.31.24.2)
Nov 29 21:47:13.215: RIP: build update entries
Nov 29 21:47:13.215: 210.7.7.7/32 via 0.0.0.0, metric 2, tag 0
R4 receives it metric 2:
*Nov 29 15:54:11.922: RIP: received v2 update from 172.31.24.2 on
Serial0/0/0
*Nov 29 15:54:11.922: 210.7.7.7/32 via 0.0.0.0 in 2 hops
R4 installs it with metric 2
R4#show ip route | inc 210.7.7.7
R 210.7.7.7 [120/2] via 172.31.24.2, 00:00:18, Serial0/0/0
R4#
After this it's obvious that the router only increments it upon advertising.
R4 advertisements have the metric as 3.
On 11/29/08, Modular <modulartx@gmail.com> wrote:
>
> I'm working on a Lab where I redistribute router R2s connected (Loopback)
> interfaces into RIP and set the metric (hop) of those routes to 5. This is
> being done on R2. R2 has a RIP peer, R1, that is receiving those
> redistributed routes. When I look at the metric/hop for those routes on R1
> it's 5?? When I look at those redistributed routes on R2, in the Rip
> database, their metric is 5. Shouldn't the hop count increase from 5 to 6
> between R2 and R1 and the metric of these routes on R1 be 6?? How can the
> metric for a route be 5 in the Rip database on R2 and also be 5 in the
> routing table on R1??
>
> Thanks for the help,
> Mod
>
>
> R2#show run | be router rip
> router rip
> version 2
> redistribute connected route-map rip-connected
>
> route-map rip-connected permit 10
> match interface Loopback0 Loopback1 Loopback2 Loopback3
> set metric 5
>
> R2#show ip rip database | begin 200.0.0.5
> 200.0.0.5/32 redistributed
> [5] via 150.100.100.5,
>
> R1#show ip rip database | be 200.0.0.5
> 200.0.0.5/32
> [5] via 150.100.12.2, 00:00:17, FastEthernet0
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:32 ARST