Home > Others

Detailed description of the RIP route table list

Source: Internet
Author: User
Developer on Alibaba Coud: Build your first app with APIs, SDKs, and tutorials on the Alibaba Cloud. Read more ＞

Next, let's take a look at the list of RIP route tables. How can we interpret long strings of information? Let's take a closer look.

Section 1st of the RIP route table list: route table under r12001

 
 
    
  
  
  1. R3#sh ip route rip  
    2. 
  
  
  2. 172.16.0.0/30 is subnetted, 3 subnets  
    3. 
  
  
  3. R　172.16.123.0 [120/1] via l72.16.123.5,00:00:12,Serial0  
    4. 
  
  
  4. [120/1] via l72.16.123.9,00:00:12,Serial1 
    5.

Section 2nd of the RIP route table list: Configure r1_2 and no summary

 
 
    
  
  
  1. R3#conft  
    2. 
  
  
  2. Enter configuration commands, one per line. End with CNTL/Z.  
    3. 
  
  
  3. R3(config)#router rip  
    4. 
  
  
  4. R3(config-router)#ver 2  
    5. 
  
  
  5. R3 (config-router)#no auto-summary  
    6. 
  
  
  6. Term_Server>2  
    7. 
  
  
  7. [Resuming connection 2 to R2 ... ]  
    8. 
  
  
  8. R2#conf t  
    9. 
  
  
  9. Enter configuration commands, one per line. End with CNTL/Z.  
    10. 
  
  
  10. R2(config)#router rip  
    11. 
  
  
  11. R2(config-router)#ver 2  
    12. 
  
  
  12. R2(config-router)#no auto-summary  
    13. 
  
  
  13. Term_Server> 1  
    14. 
  
  
  14. [Resuming connection 1 to R1 ... ]  
    15. 
  
  
  15. R1#conft  
    16. 
  
  
  16. Enter configuration commands, one per line. End with CNTL/Z.  
    17. 
  
  
  17. R1(config)#router rip  
    18. 
  
  
  18. R1(config-router)#ver 2  
    19. 
  
  
  19. R1 (config-router)#no auto-summary  
    20. 
  
  
  20. R1(config-rotuer)#end  
    21. 
  
  
  21. R1#  
    22. 
  
  
  22. R1#sh ip prot  
    23. 
  
  
  23. Routing Protocol is "rip"  
    24. 
  
  
  24. Sending updates every 30 seconds, next due in 5 seconds  
    25. 
  
  
  25. Invalid after 180 seconds, hold down 180, flushed after 240  
    26. 
  
  
  26. Outgoing update filter list for all interfaces is  
    27. 
  
  
  27. Incoming update filter list for all interfaces is  
    28. 
  
  
  28. Redistributing: rip  
    29. 
  
  
  29. Default version control: send version 2, receive version 2  
    30. 
  
  
  30. Interface　Send　Recv　Triigered RIP　Key-chain  
    31. 
  
  
  31. Ethemet0 2　2  
    32. 
  
  
  32. Serial0　2　2  
    33. 
  
  
  33. Serial1　2　2  
    34. 
  
  
  34. Automatic network summarization is not in effect  
    35. 
  
  
  35. Routing for Networks:  
    36. 
  
  
  36. 172.16.0.0  
    37. 
  
  
  37. 172.18.0.0  
    38. 
  
  
  38. Routing Information Sources:  
    39. 
  
  
  39. Gateway　DistanceLast Update  
    40. 
  
  
  40. 172.16.123.6　120　00:00:06  
    41. 
  
  
  41. 172.16.123.2　120　00:00:04  
    42. 
  
  
  42. Distance: (default is 120)  
    43. 
  
  
  43. R1#sh ip route rip  
    44. 
  
  
  44. 172.16.0.0/30 is subnetted, 3 subnets  
    45. 
  
  
  45. R　172.16.123.8 [120/1] via 172.16.123.2, 00:00:06, Serial0  
    46. 
  
  
  46. [120/1] via 172.16.123.6, 00:00:22, Serial1  
    47. 
  
  
  47. 172.18.0.0/16 is variably subnetted, 3 subnets, 2 masks  
    48. 
  
  
  48. R　172.18,2,0/28 [120/1] via 172.16.123.2,00:00:06,SerialO  
    49. 
  
  
  49. R　172.18J.O/24 [120/1] via 172.16.123.6, 00:00:22, Serial1 
    50.

Section 3rd of the RIP route table: Configure passive interface

 
 
    
  
  
  1. R1#debug ip rip  
    2. 
  
  
  2. RIP protocol debugging is on  
    3. 
  
  
  3. R1#  
    4. 
  
  
  4. 02:59:47: RIP: received v2 update from 172.16.123.6 on Serial1  
    5. 
  
  
  5. 02:59:47:　172.16.123.8/30 via 0.0.0.0 in 1 hops  
    6. 
  
  
  6. 02:59:47:　172.18.2.0/28 via 0.0.0.0 in 1 hops  
    7. 
  
  
  7. 02:59:47:　172.18.3.0/24 via 0.0.0.0 in 1 hops  
    8. 
  
  
  8. R1#  
    9. 
  
  
  9. 02:59:51: RIP: sending v2 update to 224.0.0.9 via Ethernet 0(172.18.1.1)  
    10. 
  
  
  10. 02:59:51: RIP: build update entries  
    11. 
  
  
  11. 02:59:51: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0  
    12. 
  
  
  12. 02:59:51: 172.16.123.4/30 via 0.0.0.0, metric 1, tag 0  
    13. 
  
  
  13. 02:59:51: 172.16.123.8/30 via 0.0.0,0, metric 2, tag 0  
    14. 
  
  
  14. 02:59:51: 172.18.2.0/28 via 0.0.0.0, metric 2,tab 0  
    15. 
  
  
  15. 02:59:51: 172.183.0/24 via0.0.0.0,metric 2,tag 0  
    16. 
  
  
  16. 02:59:51: RIP: sendiag v2 update to 224.0.:0.9viaSaialC-172.15.t23.1)  
    17. 
  
  
  17. 02:59:51: RIP: build update entries  
    18. 
  
  
  18. 02:59:51: 172.16.123.4/30 via 0.0.0.0, metric 1, tag 0  
    19. 
  
  
  19. 02:59:51: 172.18.1.0/28 via 0.0.0.0, metric 1, tag 0  
    20. 
  
  
  20. 02:59:51: 172.18.3.0/24 via 0.0.0.0, metric 2, tag 0  
    21. 
  
  
  21. R1#  
    22. 
  
  
  22. 02:59:51: RIP: sending v2 update to 224.0.0.9 via Serial1(172.16.123.5)  
    23. 
  
  
  23. 02:59:51: RIP: build update entries  
    24. 
  
  
  24. 02:59:51: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0  
    25. 
  
  
  25. 02:59:51: 172.18.1.0/28 via 0.0.0.0, metric 1, tag 0  
    26. 
  
  
  26. 02:59:51: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0  
    27. 
  
  
  27. R1#u all  
    28. 
  
  
  28. All possible debugging has been turned off  
    29. 
  
  
  29. R1#conft  
    30. 
  
  
  30. Enter configuration commands, one per line. End with CNTL/Z.  
    31. 
  
  
  31. R1(config)#router rip  
    32. 
  
  
  32. R1(config-router)passive-interface ?  
    33. 
  
  
  33. Ethernet IEEE 802.3  
    34. 
  
  
  34. Null　Null interface  
    35. 
  
  
  35. SerialSerial  
    36. 
  
  
  36. defaultSuppres s routing updates. on all interfaces  
    37. 
  
  
  37. R1 (config-router)passive-interface e0  
    38. 
  
  
  38. R1(config-router)#passive-interface s0  
    39. 
  
  
  39. R1(config-router#^Z  
    40. 
  
  
  40. R1#debugiprip  
    41. 
  
  
  41. RIP protocol debugging is on  
    42. 
  
  
  42. R1#  
    43. 
  
  
  43. 03:00:54: RIP: received v2 update from 172.16.123.2 on Serial0  
    44. 
  
  
  44. 03:00:54:　172.16.123.8/30 via 0.0.0.0 in 1 hops  
    45. 
  
  
  45. 03:00:54:　172.18.2.0/28 via 0.0.0.0 in 1 hops  
    46. 
  
  
  46. 03:00:54:　172.18.3.0/24 via 0.0.0.0 in 2 hops  
    47. 
  
  
  47. R1#  
    48. 
  
  
  48. 3:00:56:RIP:sending v2 flash update to 224.0.0.9 via Serial1(172.16.123.5)  
    49. 
  
  
  49. 03:00:56: RIP: build flash update entries  
    50. 
  
  
  50. 03:00:56: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0  
    51. 
  
  
  51. R1#  
    52. 
  
  
  52. 03:01:12:RIP:received v2 update from 172.16.123.6 on Serial1  
    53. 
  
  
  53. 03:01:12: 172.16.123.8/30 via0.0.0.0 in 1 hops  
    54. 
  
  
  54. 03:01:12: 172.18.2.0/28 via 0.0.0.0 in 2 hops  
    55. 
  
  
  55. 03:01:12: 172.18.3.0/24 via 0.0.0.0 in 1 hops  
    56. 
  
  
  56. R1#  
    57. 
  
  
  57. 03:01:17:RIP:sending v2 flash update to 224.0.0.9 via Serial1(172.16.123.5)  
    58. 
  
  
  58. 03:01:17: RIP: build update entries  
    59. 
  
  
  59. 03:01:17: 172.16.123.0/30 via 0.0.0.0, metric 1, tag 0  
    60. 
  
  
  60. 03:01:17: 172.18.1.0/28 via 0.0.0.0,. metric 1,tag 0  
    61. 
  
  
  61. 03:01:17: 172.18.2.0/28 via 0.0.0.0, metric 2, tag 0  
    62. 
  
  
  62. R1#  
    63. 
  
  
  63. 03:01:23:RIP:received v2 update from 172.16.123.2 on Serial1  
    64. 
  
  
  64. 03:01:23:　172.16.123.8/30 via 0.0.0.0 in 1 hops  
    65. 
  
  
  65. 03:01:23:　172.18.2.0/28 via 0.0.0.0 in 1 hops  
    66. 
  
  
  66. 03:01:23:　172.18.3.0/24 via 0.0.0.0 in 2 hops  
    67. 
  
  
  67. R1#conft  
    68. 
  
  
  68. Enter configuration commands, one per line. End with CNTL/Z.  
    69. 
  
  
  69. R1(config)#router rip  
    70. 
  
  
  70. R1 (config-router)#passive-mterface default  
    71. 
  
  
  71. R1(config-router#^Z  
    72. 
  
  
  72. R1#  
    73. 
  
  
  73. Term_Server>2  
    74. 
  
  
  74. [Resuming connection 2 to R2 ... ]  
    75. 
  
  
  75. R2#cle ip route *  
    76. 
  
  
  76. R2#  
    77. 
  
  
  77. Term_Server>3  
    78. 
  
  
  78. [Resuming connection 3 to R3 ... ]  
    79. 
  
  
  79. R3#cle ip route *  
    80. 
  
  
  80. R3#  
    81. 
  
  
  81. Term_Server>1  
    82. 
  
  
  82. [Resuming connection 1 to R1... ]  
    83. 
  
  
  83. R1#sh ip route rip  
    84. 
  
  
  84. 172.16.0.0/30 is subnetted,3 subnets  
    85. 
  
  
  85. R　172.16.123.8[120/1]via 172.16.123.2,00:00:09,Serial1  
    86. 
  
  
  86. [120/1]via 172.16.123.6,00:00:17,Serial0  
    87. 
  
  
  87. 172.18.0.0/16 is variably subnetted,3 subnets,2 masks  
    88. 
  
  
  88. R　172.18.2.0/28[120/1] via 172.16.123.2,00:00:17,Serial0  
    89. 
  
  
  89. R　172.18.3.0/24[120/1] via 172.16.123.6,00:00:09,Serial1  
    90. 
  
  
  90. R1#  
    91. 
  
  
  91. Term_Server>2  
    92. 
  
  
  92. [Resuming connection 2 to R2...]  
    93. 
  
  
  93. R2#  
    94. 
  
  
  94. R2#sh ip route rip  
    95. 
  
  
  95. 172.16.0.0/30 is subnetted,3 subnets  
    96. 
  
  
  96. R　172.16.123.4[120/1]via 172.16.123.10,00:00:24,Serial1  
    97. 
  
  
  97. 172.18.0.0/16 is variably subnetted,2 subnets,2 masks  
    98. 
  
  
  98. R　172.18.3.0/24[120/1] via 172.16.123.10,00:00:24,Serial1  
    99. 
  
  
  99. R2#  
    100. 
  
  
  100. Term_Server>3  
    101. 
  
  
  101. [Resuming connection 3 to R3...]  
    102. 
  
  
  102. R3#sh ip route rip  
    103. 
  
  
  103. 172.16.0.0/30 is subnetted,3 subnets  
    104. 
  
  
  104. R　172.16.123.0120/1] via 172.16.123.9,00:00:26,Serial1  
    105. 
  
  
  105. 172.18.0.0/16 is variably subnetted,2 subnets,2 masks  
    106. 
  
  
  106. R　172.18.2.0/28[120/1] via 172.16.123.9,00:00:26,Serial1 
    107.

(1) by default, the RIP version is in section 1. 1st. In r1_1 configuration, only one route of 172.16.123.0 can be seen in the result of the show ip routerip command of the R3 router.

(2) In section 2nd, set the three routers as r12002 and disable route auto summary. The command used is version2 and no auto-summary, all are issued in router rip mode.

(3) The show ip protocol command displays the configuration information of the RIP route table list after the configuration is changed. It is notable that the versions sent and received are changed to 2, and the automatic network summary does not take effect.

(4) The show ip route rip command shows the expected result, that is, the CIDR blocks 172.18.2.0/28 and 172.18.3.0/24 appear in the routing table, indicating that r1_2 can solve the VLSM problem, allows you to allocate IP addresses flexibly and efficiently.

You can view the route table on another vro to obtain a similar result.

(5) In section 3rd, the debug ip rip command is used to monitor the operating characteristics of r12002. r12002 sends update packages to each interface (E0, S0, and S1 interfaces of R1), and uses the multicast address 224.0.0.9.

(6) The passive-interface e0 and passive-interface s0 commands can be used to set the E0 and S0 interfaces as passive interfaces. the passive interface only receives the route update package, instead of sending the route update package.

(7) The execution result of the debug ip rip command shows the transfer of the RIP package after the passive interface is configured. You can see that only the cited interface and the route update package are sent.

(8) use the passive-interface default command to set all interfaces as passive interfaces.

To view the role of this command, we first clear the route table on each vro, force route table updates, and then view the route table of each vro to list the routes obtained by RIP.

The route table of R1 shows all three CIDR blocks that are not directly connected to it.

The route tables of R2 and R3 do not display the E0 network segment of R1, that is, 172.18.1.0/28. This is because the R1 Router does not publish any RIP information.

This article is an English version of an article which is originally in the Chinese language on aliyun.com and is provided for information purposes only. This website makes no representation or warranty of any kind, either expressed or implied, as to the accuracy, completeness ownership or reliability of the article or any translations thereof. If you have any concerns or complaints relating to the article, please send an email, providing a detailed description of the concern or complaint, to info-contact@alibabacloud.com. A staff member will contact you within 5 working days. Once verified, infringing content will be removed immediately.

Related Keywords:
how to get description of table in sql server mssql table description description of dell laptop description of sunrise description of visual studio description of core iphone description of features

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

What's Trending
Top 10 Tags
datastax versions naming convention zookeeper client class definition md5 microsoft sql server 2005 data structures exception handling error handling
Top 10 Keywords
microsoft download center down wordpress address url site address url wordpress address url windows installer 4 0 download 302 not found web address url definition site address url wordpress db2 integer mac os installation step by step pdf abbreviation for return

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

Get Started for Free

  • Sales Support

    1 on 1 presale consultation

    Chat Contact Sales

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

    Open a Ticket

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.

    Learn More