Update mechanism of rip Protocol V1 and V2

Update mechanism of rip Protocol V1 and V2

Tutorial topology: www.2cto.com tutorial step: R1: router ripnetwork 1.0.0.0network 192.168.12.0R2: router ripnetwork 2.0.0.0network 192.168.12.0 if the command Version 2 is not run in route configuration mode, RIP version 1 is run. Debug ip ripR2 (config) # router ripR2 (config-router) # network 2.0.0.0R2 (config-router) # network 192.168.12.0R2 (config-router) # * Jun 4 09:40:46. 279: RIP: add Loopback2 to RIP idb list * Jun 4 09:40:46. 279: RIP: sending request on Loopback2 to broadcast throughput 255 // send broadcast update * Jun 4 09:40:47. 099: RIP: add Serial1/0 to RIP idb list * Jun 4 09:40:47. 099: RIP: sending request on Serial1/0 to bytes limit 255 * Jun 4 0 9:40:47. 143: RIP: Replicated ed v1 update from 192.168.12.1 on Serial1/0 * Jun 4 09:40:47. 147: RIP: Update contains 1 routes * Jun 4 09:40:48. 279: RIP: sending v1 flash update to zookeeper 255 via Loopback2 (2.2.2.2) * Jun 4 09:40:48. 279: RIP: Update contains 2 routes * Jun 4 09:40:48. 279: RIP: Update queued * Jun 4 09:40:48. 279: RIP: sending v1 flash update to 255.255.255.255 via Serial1/0 (192.168.12.2) * Jun 4 09:40:48. 279: RIP: Update contains 1 routes * Jun 4 09:40:48. 279: RIP: Update queued * Jun 4 09:40:48. 279: RIP: Update sent via Loopback2 * Jun 4 09:40:48. 279: RIP: Update sent via Serial1/0R1: * Jun 4 09:44:47. 695: RIP: sending v1 update to zookeeper 255 via Serial1/1 (192.168.12.1) * Jun 4 09:44:47. 699: RIP: Update contains 1 routes // only the interface address directly advertised to the neighbor * Jun 4 09:44:47. 699: RIP: Update queued * Jun 4 09:44:47. 699: RIP: Update sent via Serial1/1R1 # * Jun 4 09:44:52. 631: RIP: sending v1 update to zookeeper 255 via Loopback0 (1.1.1.1) * Jun 4 09:44:52. 635: RIP: Update contains 2 routes * Jun 4 09:44:52. 635: RIP: Update queued * Jun 4 09:44:52. 635: RIP: Update sent via Loopback0 // only notify the neighbor of the direct interface address R1 # * Jun 4 09:45:13. 543: RIP: sending v1 update to zookeeper 255 via Serial1/1 (192.168.12.1) * Jun 4 09:45:13. 547: RIP: U Pdate contains 1 routes * Jun 4 09:45:13. 547: RIP: Update queued * Jun 4 09:45:13. 547: RIP: Update sent via Serial1/1 * Jun 4 09:45:13. 595: RIP: Replicated ed v1 update from 192.168.12.2 on Serial1/1 * Jun 4 09:45:13. 599: RIP: Update contains 1 routesR1 # * Jun 4 09:45:20. 487: RIP: sending v1 update to zookeeper 255 via Loopback0 (1.1.1.1) * Jun 4 09:45:20. 491: RIP: Update contains 2 routes * Jun 4 09:45:20. 491: RI P: Update queued * Jun 4 09:45:20. 491: RIP: Update sent via Loopback0 red font indicates that rip V1 will be around 30 s (27 s is displayed in debug information) send an update. If a loopback 0 address 22.22.22.22/24 is added to R2 at this time, we can see from the debug ip rip events: * Jun 4 09:50:12. 159: RIP: sending v1 flash update to 255.255.255.255 via Loopback0 (22.22.22.22)-suppressing null update * Jun 4 09:50:12. 163: RIP: Update sent via Loopback2 now R1 has 22.0.0.0 route R1 # show ip route ripR 2.0.0.0/8 [120/1] via 192.168.12.2, 00:00:13, Serial1/1R 22.0.0.0/8 [120/1] via 192.168.12.2, 00:00:13, Serial1/1 if port 0 of R2 is disabled, after S, set the route hop count to 16. If the update is not received after S, the route will be completely deleted from the route table! Now, after changing the RIP of R2 to V2, what will happen? * Jun 4 09:57:22. 151: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses) * Jun 4 09:57:24. 467: RIP: ignored v1 packet from 192.168.12.1 (illegal version) // prompt that the version is incompatible * Jun 4 09:57:47. 503: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (192.168.12.2) * Jun 4 09:57:47. 507: RIP: Update contains 1 routes * Jun 4 09:57:47. 507: RIP: Update queued * Jun 4 09:57:47. 507: RIP: Update sent via Seri Al1/0 * Jun 4 09:57:50. 219: RIP: sending v2 update to 224.0.0.9 via Loopback2 (2.2.2.2) * Jun 4 09:57:50. 219: RIP: Update contains 2 routes * Jun 4 09:57:50. 223: RIP: Update queued * Jun 4 09:57:50. 223: RIP: Update sent via Loopback2 * Jun 4 09:57:50. 227: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses) * Jun 4 09:57:50. 563: RIP: ignored v1 packet from 192.168.12.1 (illegal version) To change the version of R1, either modify it in the interface mode of R2: interface Serial1/0ip address 192.168.12.2 255.255.255.0ip rip send version 1 // send version 1ip rip receive version 1 // The received version 2debug information is displayed as follows: R2 # * Jun 4 09:59:41. 907: RIP: Replicated ed v1 update from 192.168.12.1 on Serial1/0 * Jun 4 09:59:41. 911: RIP: Update contains 1 routesR2 # * Jun 4 09:59:43. 639: RIP: sending v1 update to zookeeper 255 via Serial1/0 (192.168.12.2) * Jun 4 09:59:43. 639: RIP: Update contains 1 routes * Jun 4 09:59:43. 639: RIP: Update queued * Jun 4 09:59:43. 639: RIP: Update sent via Serial1/0 * Jun 4 09:59:43. 663: RIP: sending v2 update to 224.0.0.9 via Loopback2 (2.2.2.2) * Jun 4 09:59:43. 663: RIP: Update contains 2 routes * Jun 4 09:59:43. 667: RIP: Update queued * Jun 4 09:59:43. 667: RIP: Update sent via Loopback2 * Jun 4 09:59:43. 671: RIP: ignored v2 packet from 2.2.2.2 (sourced From one of our addresses) R2 # show ip route ripR 1.0.0.0/8 [120/1] via 192.168.12.1, 00:00:02, after Serial1/0 is changed to version 1, the information displayed on debug is: r1 (config-router) # * Jun 4 10:03:07. 779: RIP-TIMER: sending timer on Loopback0 expired * Jun 4 10:03:07. 779: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.1.1) // send an update for multicast * Jun 4 10:03:07. 783: RIP: Update contains 3 routes * Jun 4 10:03:07. 783: RIP: Update queued * Jun 4 7.787: RIP: Update sent via Loopback0 * Jun 4 10:03:07. 787: RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses) R1 (config-router) # * Jun 4 10:03:14. 519: RIP-TIMER: age timer expiredR1 (config-router) # * Jun 4 10:03:15. 691: RIP: Replicated ed v2 update from 192.168.12.2 on Serial1/1 * Jun 4 10:03:15. 695: RIP-DB: network_update with 2.0.0.0/8 succeeds // note the difference with the red font below. * Jun 4 10:03:15. 695: RIP-DB: adding 2.0.0.0/8 (metric 1) via 192.168.12.2 on Serial1/1 to RIP database * Jun 4 10:03:15. 699: RIP-DB: network_update with 22.0.0.0/8 succeeds * Jun 4 10:03:15. 699: RIP-DB: adding 22.0.0.0/8 (metric 1) via 192.168.12.2 on Serial1/1 to RIP database * Jun 4 10:03:15. 699: RIP: Update contains 2 routesR1 (config-router) # * Jun 4 10:03:17. 191: RIP-TIMER: sending timer on Serial1/1 expired * Jun 4 10:03:17. 191: RIP: sending v2 update to 224.0.0.9 via Serial1/1 (192.168.12.1) * Jun 4 10:03:17. 195: RIP: Update contains 1 routes * Jun 4 10:03:17. 195: RIP: Update queued * Jun 4 10:03:17. 199: RIP: Update sent via Serial1/1 the debug ip rip database information displayed on R1 and R2 after no auto-summary is entered: R1 (config-router) # * Jun 4 10:04:42. 087: RIP: Replicated ed v2 update from 192.168.12.2 on Serial1/1 * Jun 4 10:04:42. 091: RIP-DB: network_update with 2.2.2.0/24 succeeds * Jun 4 10:04:42. 091: RIP-DB: adding 2.2.2.0/24 (metric 1) via 192.168.12.2 on Serial1/1 to RIP database * Jun 4 10:04:42. 095: RIP-DB: add 2.2.2.0/24 (metric 1) via 192.168.12.2 on Serial1/1 * Jun 4 10:04:42. 095: RIP-DB: Adding new rndb entry 2.2.2.0/24 * Jun 4 10:04:42. 099: RIP-DB: network_update with 22.22.22.0/24 succeeds * Jun 4 10:04:42. 099: RIP-DB: adding 22.22.22.0/24 (metric 1) via 192.168.12.2 on Serial1/1 to RIP database * Jun 4 10:04:42. 103: RIP-DB: add 22.22.22.0/24 (metric 1) via 192.168.12.2 on Serial1/1