Use the output that you saved to show the differences between the outcomes of Exercise 4-b and 4-c with regard to the convergence of RIP.

What will be an ideal response?

The count-to-infinity problem does not occur in this experiment because of triggered updates. And converging time is faster than one of the previous experiment.
```
Router3#debug ip rip
RIP protocol debugging is on
Router3#
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 2, tag 0
5d19h: RIP: received v2 update from 10.0.3.10 on Ethernet0
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.3.10 on Ethernet0
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: RIP: received v2 update from 10.0.3.10 on Ethernet0
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 16 hops (inaccessible)
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 16, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: 10.0.1.0/24 -> 0.0.0.0, metric 13, tag 0
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: received v2 update from 10.0.4.4 on Ethernet1
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.3.3)
5d19h: 10.0.4.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: sending v2 update to 224.0.0.9 via Ethernet1 (10.0.4.3)
5d19h: 10.0.3.0/24 -> 0.0.0.0, metric 1, tag 0
5d19h: RIP: received v2 update from 10.0.3.2 on Ethernet0
5d19h: 10.0.2.0/24 -> 0.0.0.0 in 1 hops
5d19h: 10.0.1.0/24 -> 0.0.0.0 in 12 hops
Router3#no debug ip rip
RIP protocol debugging is off
```