Ccnp first day experiment rip V1 and rip v2

Source: Internet
Author: User


1. Configure the loopback and S1/1 interface IP addresses for r1

R1 (config) # int lo0
R1 (config-If) # IP add 1.1.1.1 255.255.255.0
R1 (config-If) # int S1/1
R1 (config-If) # IP add 12.1.1.1 255.255.255.0
R1 (config-If) # No Shutdown

2. The link is allocated to R1 to R6 and to R6 respectively based on the address.

R2 (config) # int lo0
R2 (config-If) # IP add 192.168.1.1 255.255.255.240
R2 (config-If) # int lo1
R2 (config-If) # IP add 192.168.1.17 255.255.255.255.240
R2 (config-If) # int S1/0
R2 (config-If) # IP add 12.1.1.2 255.255.255.0
R2 (config-If) # No Shutdown
R2 (config-If) # int S1/1
R2 (config-If) # IP add 192.168.1.161 255.255.255.252
R2 (config-If) # No Shutdown
R2 (config-If) # int F0/0
R2 (config-If) # IP add 192.168.1.177 255.255.255.252
R2 (config-If) # No Shutdown

R3 (config) # int lo0
R3 (config-If) # IP add 192.168.1.33 255.255.255.255.240
R3 (config-If) # int lo1
R3 (config-If) # IP add 192.168.1.49 255.255.255.255.240
R3 (config-If) # int S1/0
R3 (config-If) # IP add 192.168.1.162 255.255.255.252
R3 (config-If) # No Shutdown
R3 (config-If) # int S1/1
R3 (config-If) # IP add 192.168.1.165 255.255.255.252
R3 (config-If) # No Shutdown

.....

R6 (config) # int lo0
R6 (config-If) # IP add 192.168.1.129 255.255.255.252
R6 (config-If) # int lo1
R6 (config-If) # IP add 192.168.1.145 255.255.255.252
R6 (config-If) # int S1/0
R6 (config-If) # IP add 192.168.1.174 255.255.255.252
R6 (config-If) # No Shutdown
R6 (config) # int F0/0
R6 (config-If) # IP add 192.168.1.178 255.255.255.252
R6 (config-If) # No Shutdown
R6 (config-If) # int S1/1
R6 (config-If) # IP add 192.168.1.181 255.255.255.252
R6 (config-If) # No Shutdown

R7 (config) # int S1/0
R7 (config-If) # IP add 192.168.1.182 255.255.255.252
R7 (config-If) # No Shutdown

R7 (config-If) # int lo0
R7 (config-If) # IP add 172.16.1.1 255.255.255.0
R7 (config-If) # int S1/1
R7 (config-If) # IP add 78.1.1.1 255.255.255.0
R7 (config-If) # No Shutdown


R8 (config) # int lo0
R8 (config-If) # IP add 172.16.2.1 255.255.255.0
R8 (config-If) # int S1/0
R8 (config-If) # IP add 78.1.1.2 255.255.255.0
R8 (config-If) # No Shutdown

So far, the basic IP configuration has been completed.
----------------------------------------------------------------------------------

Then start rip V2 between R1-R6 and rip V1 between R7 and R8.

R2 (config) # router rip
R2 (config-router) # Version 2
R2 (config-router) # No auto-Summary
R2 (config-router) # network 192.168.1.0

....

R7 (config) # router rip
R7 (config-router) # version 1
R7 (config-router) # network 192.168.1.0
R7 (config-router) # network 172.16.0.0
R7 (config-router) # network 78.0.0.0

....

In this case, there should be 10/28/6/30 route entries in the route entries from R1 to R6.


3 and 4 respectively on R7 and R8

The figure shows that neither R7 nor R8 knows whether the other party's loop exists, because R7 and R8 both enable rip V1, and their updates do not contain a mask, to enable both parties to find the other party's loop back, the second address needs to be used to divide the R7 and R8 loops into the same continuous subnet.

R7 (config) # int S1/1
R7 (config-If) # IP add 172.16.3.1 255.255.255.0 secondary

R8 (config) # int S1/0
R8 (config-If) # IP add 172.16.3.2 255.255.255.0 secondary

Now, you can view the route tables R7 and R8 to learn the other party's cycle.

But the table shows that there is a path between the R1-R6 in R8, but the route table in R7 does not have a route entry between the R1-R6
This is because Rip V1 V2 only receives and sends data packets of its own version.

Use show IP protocols in privileged mode to view

In this case, you need to change the R7 rip to be compatible with V2.

R7 (config) # int S1/0
R7 (config-If) # IP rip send version 1 2
R7 (config-If) # IP rip receive version 1 2

For clear route entries, You can manually combine R6 into a route and send it to R7.
R6 (config) # interface S1/1
R6 (config-If) # IP Summary-address rip 192.168.1.0 255.255.255.0

PS: Here R6 cannot be changed to be compatible with V1. why?


So far, the entire intranet has been reached, that is, the basic configuration has been completed. Policy
-------------------------------------------------------------

3. R2 to R5 loop back access through r3
By default, R2 is returned to R5 through R6 because the following path is 2 hops and the above path is 3 hops.
Therefore, you can manually modify the measurement.

R2 (config) # access-List 1 permit 192.168.1.96 0.0.0.0
R2 (config) # router rip
R2 (config-router) # offset-List 1 in 2 fastethernet 0/0 // number 2 is an increase of 2 hops
Because modifying the offset list is a control layer, it is the in direction of R2.

---------------------------------------------------------------------------

4. Accelerate protocol convergence, ensure update security, and reduce route entries

1). Speed up protocol convergence: that is, modify the four timers of rip on each vro.

R2 (config) # router rip
R2 (config-router) # timers basic 15 90 90 120
PS: the whole network is always needed and scaled down proportionally


2). Reduce route entries: that is, In the R2-R6 each route to the external declaration of each interface on the loop back for manual Summary
R2 (config) # int S1/1
R2 (config-If) # IP Summary-address rip 192.168.1.0 contains too many
R2 (config) # int F0/0
R2 (config-If) # IP Summary-address rip 192.168.1.0 contains too many

-------------------------------------------------------------------------------

5. R2-R8 devices can access r1's loopback

Intranet access to the Internet: Two things need to be done: 1) write the default route; 2) Nat Network Address Translation

1) write the default route
R2 (config) # IP Route 0.0.0.0 0.0.0.0 12.1.1.1
Declare that you are a VBR
R2 (config) # router rip
R2 (config-router) # default-Information originate

2). Nat Network Address Translation

R2 (config) # access-List 2 permit 192.168.1.0 0.0.255
R2 (config) # access-List 2 permit 172.16.0.0 0.0.255
R2 (config) # access-List 2 permit 78.1.1.0 0.0.255
R2 (config) # ip nat inside source list 2 interface S1/0 overload
R2 (config) # int S1/0
R2 (config-If) # ip nat outside
R2 (config-If) # int S1/1
R2 (config-If) # ip nat inside
R2 (config-If) # int F0/0
R2 (config-If) # ip nat inside

------------------------------------------------------
R1 Telnet R2 is actually logged on to R8

1. Enable the remote logon port on R8
R8 (config) # Line vty 0 4
R8 (config-line) # password Cisco

2. Write a static port ing from R2 to R8.
R2 (config) # ip nat inside source static TCP 78.1.1.2 23 12.1.1.2 23

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.

A Free Trial That Lets You Build Big!

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

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

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

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