RIP TRIGGERED UPDATES

Ok today i am wrapping up on rip. I am looking at 2 rip features rip triggered
updates and rip source validation.
So rip triggered was brought out for dial links mainly and also could be used on slow
wan links. When you configure rip triggered updates there is no rip control plane
traffic unless there is a change in the network so you are essentially suppressing
the perodic updates of rip  this is enabled logically on both sides of the link
int fa0/0
ip rip triggered

LAB
----
OK i will just have r5 and r4 running a few loopbacks advertising via rip i will
enable triggered updates on both ends


So on r4
--------

r4#sh ip int brief | inc up
Serial0/1/0                10.10.10.3      YES manual up                    up 
Loopback0                  4.4.4.4         YES manual up                    up 
Loopback1                  3.3.3.3         YES manual up                    up 
r4#
r4#sh run | begin router rip
router rip
 version 2
 network 3.0.0.0
 network 4.0.0.0
 network 10.0.0.0
 no auto-summary
r5
---
r5#sh ip int brief | inc up
Serial0/1/0                10.10.10.1      YES manual up                    up 
Loopback0                  5.5.5.5         YES manual up                    up 
Loopback1                  6.6.6.6         YES manual up                    up 
r5#
r5#sh run | begin router rip
router rip
 version 2
 network 5.0.0.0
 network 6.0.0.0
 network 10.0.0.0
 no auto-summary

ok i will do a debug ip rip on r5 just to see the updates periodically going to r4
*Dec 17 13:49:59.815: RIP: received v2 update from 10.10.10.3 on Serial0/1/0
*Dec 17 13:49:59.815:      3.3.3.3/32 via 0.0.0.0 in 1 hops
*Dec 17 13:49:59.815:      4.4.4.4/32 via 0.0.0.0 in 1 hops
*Dec 17 13:50:09.151: RIP: sending v2 update to 224.0.0.9 via Serial0/1/0
(10.10.10.1)
*Dec 17 13:50:09.151: RIP: build update entries
*Dec 17 13:50:09.151:   5.5.5.5/32 via 0.0.0.0, metric 1, tag 0
*Dec 17 13:50:09.151:   6.6.6.6/32 via 0.0.0.0, metric 1, tag 0
so i am periodically getting the send and recieving to/from 10.10.10.3

so on r5
r5(config)#int s0/1/0
r5(config-if)#ip rip triggered
r5(config-if)#

I am still getting the
r5#
*Dec 17 13:52:23.427: RIP: received v2 update from 10.10.10.3 on Serial0/1/0
*Dec 17 13:52:23.427:      3.3.3.3/32 via 0.0.0.0 in 1 hops
*Dec 17 13:52:23.427:      4.4.4.4/32 via 0.0.0.0 in 1 hops
*Dec 17 13:52:24.411: RIP: sending triggered request on Serial0/1/0 to 224.0.0.9
recieving updates from 10.10.10.3 but not the sending i have stop sending perodic
updates

ok so now on r4
---------------
Enter configuration commands, one per line.  End with CNTL/Z.
r4(config)#int s0/1/0
r4(config-if)#ip rip triggered
r4(config-if)#

now on r5 i am no longer getting any updates/sending + recieving from  or to r4

I will now on r5 shutdown the interface int lo0

i know send a triggered update to r4
*Dec 17 13:56:02.751: RIP: send v2 triggered update to 10.10.10.3 on Serial0/1/0
*Dec 17 13:56:02.751: RIP: build update entries
*Dec 17 13:56:02.751:   route 11: 5.5.5.5/32 metric 16, tag 0
*Dec 17 13:56:02.751: RIP: Update contains 1 routes, start 11, end 12
*Dec 17 13:56:02.751: RIP: start retransmit timer of 10.10.10.3
*Dec 17 13:56:02.751: RIP: sending v2 flash update to 224.0.0.9 via Loopback1
(6.6.6.6)
*Dec 17 13:56:02.751: RIP: build flash update entries
*Dec 17 13:56:02.751:   5.5.5.5/32 via 0.0.0.0, metric 16, tag 0
*Dec 17 13:56:02.751: %LINK-5-CHANGED: Interface Loopback0, changed state to
administratively down
*Dec 17 13:56:02.751: RIP: received v2 triggered ack from 10.10.10.3 on