[CCNAv6 S2] 3.2.1.8 Packet Tracer - Configuring RIPv2



Packet Tracer – Configuring RIPv2
Objectives

Part 1: Configure RIPv2

Part 2: Verify Configurations

Background

Although RIP is rarely used in modern networks, it is useful as a foundation for understanding basic network routing. In this activity, you will configure a default route, RIP version 2, with appropriate network statements and passive interfaces, and verify full connectivity.

Part 1:     Configure RIPv2
Step 1:     Configure RIPv2 on R1.

a.     Use the appropriate command to create a default route on R1 for all Internet traffic to exit the network through S0/0/1.

b.    Enter RIP protocol configuration mode.

c.     Use version 2 of the RIP protocol and disable the summarization of networks.

d.    Configure RIP for the networks that connect to R1.

e.     Configure the LAN port that contains no routers so that it does not send out any routing information.

f.     Advertise the default route configured in step 1a with other RIP routers.

g.    Save the configuration.

Step 2:     Configure RIPv2 on R2.

a.     Enter RIP protocol configuration mode.

b.    Use version 2 of the RIP protocol and disable the summarization of networks.

c.     Configure RIP for the networks directly connected to R2.

d.    Configure the interface that contains no routers so that it does not send out routing information.

e.     Save the configuration.

Step 3:     Configure RIPv2 on R3

Repeat Step 2 on R3.

Part 2:     Verify Configurations
Step 1:     View routing tables of R1, R2, and R3.

a.     Use the appropriate command to show the routing table of R1. RIP (R) now appears with connected (C) and local (L) routes in the routing table. All networks have an entry. You also see a default route listed.

b.    View the routing tables for R2 and R3. Notice that each router has a full listing of all the 192.168.x.0 networks and a default route.

Step 2:     Verify full connectivity to all destinations.

Every device should now be able to ping every other device inside the network. In addition, all devices should be able to ping the Web Server.




Configuration R1:

enable
configure terminal
ip route 0.0.0.0 0.0.0.0 s0/0/1
router rip
 version 2
 no auto-summary
 network 192.168.1.0
 network 192.168.2.0
 passive-interface s0/0/1
 passive-interface g0/0
 default-information originate
end
write memory
!

Configuration R2:

enable
configure terminal
router rip
 version 2
 no auto-summary
 network 192.168.2.0
 network 192.168.3.0
 network 192.168.4.0
 passive-interface g0/0
 end
write memory
!


Configuration R3:

enable
configure terminal
router rip
 version 2
 no auto-summary
 network 192.168.4.0
 network 192.168.5.0
 passive-interface g0/0
end
write memory
!


END !~!


Link Download:  Here


Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

Hình ảnh
Packet Tracer - Configuring IPv4 Static and Default Routes Addressing Table Objectives Part 1: Examine the Network and Evaluate the Need for Static Routing Part 2: Configure Static and Default Routes Part 3: Verify Connectivity Background In this activity, you will configure static and default routes. A static route is a route that is entered manually by the network administrator to create a reliable and safe route. There are four different static routes that are used in this activity: a recursive static route, a directly attached static route, a fully specified static route, and a default route. Part 1:     Examine the Network and Evaluate the Need for Static Routing a.     Looking at the topology diagram, how many networks are there in total? b.    How many networks are directly connected to R1, R2, and R3? c.     How many static routes are required by each router to reach networks that are not directly ...
Đọc thêm

[CCNAv6 S2] 8.3.1.2 Packet Tracer - Skills Integration Challenge

Hình ảnh
Packet Tracer – Skills Integration Challenge Addressing Table VLAN Port Assignments and DHCP Information Scenario In this culminating activity, you will configure VLANs, trunks, DHCP Server, DHCP relay agents, and configure a router as a DHCP client. Requirements Using the information in the tables above, implement the following requirements: ·         Create VLANs on S2 and assign VLANs to appropriate ports. Names are case-sensitive ·         Configure S2 ports for trunking. ·         Configure all non-trunk ports on S2 as access ports. ·         Configure R1 to route between VLANs. Subinterface names should match the VLAN number. ·         Configure R1 to act as a DHCP server for the VLANs attached to S2. -       Create a DHCP pool for each VLAN. Names are case-sensitive. -       Assign the ap...
Đọc thêm

[CCNAv6 S3] 7.2.3.5 Packet Tracer - Troubleshooting EIGRP for IPv4

Hình ảnh
Packet Tracer – Troubleshooting EIGRP for IPv4 Addressing Table Scenario In this activity, you will troubleshoot EIGRP neighbor issues. Use show commands to identify errors in the network configuration. Then, you will document the errors you discover and implement an appropriate solution. Finally, you will verify full end-to-end connectivity is restored. Troubleshooting Process 1.     Use testing commands to discover connectivity problems in the network and document the problem in the Documentation Table. 2.     Use verification commands to discover the source of the problem and devise an appropriate solution to implement. Document the proposed solution in the Documentation Table. 3.     Implement each solution one at a time and verify if the problem is resolved. Indicate the resolution status in the Documentation Table. 4.     If the problem is not resolved, it may be necessary to first remove the implemented solution befor...
Đọc thêm