From: SFeldberg@xxxxxxxxxxxxx
Date: Fri Nov 09 2001 - 15:50:40 GMT-3
Before any neighbor statements are in place between RIP peers 40.1.1.2 and
40.1.1.4.
r4#debug ip rip
RIP protocol debugging is on
r4#
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
r4#conf t
Enter configuration commands, one per line. End with CNTL/Z.
r4(config)#router rip
r4(config-router)#nei 40.1.1.2
r4(config-router)#
After neighbor statement on R4 referencing R2:
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
Debug output on R2 with neighbor statement only configured on R4
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
r2#
r2(config)#router rip
r2(config-router)#nei 40.1.1.4
r2(config-router)#^Z
Debug output on R2 after both neighbor statements are in place
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: sending v1 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
1d21h: subnet 40.1.1.0, metric 1
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.4 on Ethernet0
1d21h: 44.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.2)
1d21h: network 42.0.0.0, metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (42.1.1.2)
1d21h: network 40.0.0.0, metric 1
1d21h: network 44.0.0.0, metric 2
1d21h: RIP: sending v1 update to 40.1.1.4 via Ethernet0 (40.1.1.2)
1d21h: subnet 40.1.1.0, metric 1
1d21h: network 42.0.0.0, metric 1
Debug output on R4 after both neighbor statements are in place
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 40.1.1.0 in 1 hops
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: sending v1 update to 255.255.255.255 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: sending v1 update to 255.255.255.255 via Loopback0 (44.1.1.4)
1d21h: RIP: build update entries
1d21h: network 40.0.0.0 metric 1
1d21h: network 42.0.0.0 metric 2
1d21h: RIP: sending v1 update to 40.1.1.2 via Ethernet0 (40.1.1.4)
1d21h: RIP: build update entries
1d21h: network 44.0.0.0 metric 1
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 42.0.0.0 in 1 hops
1d21h: RIP: received v1 update from 40.1.1.2 on Ethernet0
1d21h: 40.1.1.0 in 1 hops
1d21h: 42.0.0.0 in 1 hops
The answer to your question is that there is a unicast update that is
generated for the referenced neighbor AND the normal broadcast updates
continue as well.
Steve
"RB"
<slowgo@home. To: "ccielab" <ccielab@groupstudy.
com>
com> cc:
Sent by: Subject: Rip Neigbor statment
nobody@groups
tudy.com
11/09/2001
01:27 PM
Please
respond to
"RB"
I know that the neigbor statement in rip sends out unicast updates to that
neighbor, but does it also send no other updates? Let's say you had
several
routers on an ethernet segment with RIP running, and you used a neigbor
statement from a-b, does c no longer receive rip updates from a?
Thanks,
RBI
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:11 GMT-3