Here you will find various Cisco CCNA 200-301 labs we have decided to provide FREE to you! These labs were created and we felt they were not advanced enough for our CCNA Lab Workbook. They are either not complex enough, do not cover multiple concepts, or do not have enough commentary explaining what we want to accomplish in each lab and why you are doing each step. These labs are basically just simple configurations and not what we would really call labs. Why? Because they do not really help you learn.
Objective: In this lab, you will configure RIP routes between both routers. This will allow your routers to route packets so that all routers and all hosts will be able to reach (ping) each other. Once your configuration is complete, you will use basic techniques to test your network’s connectivity.
Hardware Requirements
- Two routers with one serial port and two FastEthernet or Gigabit ports
- One back to back DTE/DCE serial cable
- IOS version 12.x or later
- A PC running a terminal emulation program
- Cisco console kit
Setup
- Configure the cabling as shown in the network diagram
- If the routers have a startup-config, erase it and perform a reload of the routers.
Router Configurations
RouterA
Router>en
Router#config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname RouterA
RouterA(config)#int loopback0 (Defines a virtual interface that I used as test point)
RouterA(config-if)#ip address 10.1.1.1 255.255.255.0
RouterA(config-if)#no shut
RouterA(config-if)#int g0/0/0
RouterA(config-if)#ip address 148.1.1.1 255.255.255.0
RouterA(config-if)#no shut
RouterA(config-if)#int s0/0/0
RouterA(config-if)#ip address 192.1.1.1 255.255.255.252
RouterA(config-if)#no shut
RouterA(config-if)#
RouterA(config-if)#Router Rip (Enables the RIP routing process on the router)
RouterA(config-if)#Version 2
RouterA(config-router)#network 10.0.0.0 (Specifies what interfaces will receive and send RIP routing updates. It also specifies what networks will be advertised)
RouterA(config-router)#network 148.1.0.0
RouterA(config-router)#network 192.1.1.0
RouterB
Router>en
Router#config t
Router(config)#hostname RouterB
RouterB(config-if)#int lo1
RouterB(config-if)#ip address 152.1.1.1 255.255.255.0
RouterB(config-if)#no shut
RouterB(config-if)#int s0/0/0
RouterB(config-if)#ip address 192.1.1.2 255.255.255.252
RouterB(config-if)#clockrate 500000 (Acts as DCE providing clock)
RouterB(config-if)#no shut
RouterB(config-if)#router rip (Enables the RIP routing process on the router)
RouterB(config-if)#version 2
RouterB(config-router)#network 192.1.1.0 (Specifies what interfaces will receive and send RIP routing updates. It also specifies what networks to be advertised)
RouterB(config-router)#network 152.1.1.0
Monitoring and Troubleshooting the Configuration
RIP is a very simple protocol to configure and troubleshot. Show the IP routing table on
RouterA with the show ip route command.
RouterA#show ip route
Find the routing table entries received using the RIP routing protocol.
From RouterA, monitor the routing packets being passed using the debug ip rip command. Notice that on interface serial 0/0/0, the router does not advertise the networks it learned from RouterB (152.1.1.0 and 193.1.1.0) but on all other interfaces, those networks are advertised. This is split horizons at work – remember that when split horizons is enabled, the router will never advertise a route back through the interface from which it was learned.
RouterA#debug ip rip
RIP protocol debugging is on
From RouterA, monitor the routing updates being passed using the debug ip rip command. Notice that now all routes are being advertised out Serial 0/0/0, including the routes learned from RouterB on Serial 0/0/0.
Remember that RIP is a very easy routing protocol to use and troubleshot. It uses hop count as it’s metric and has a maximum hop count of 15 and the destination is considered unreachable at 16. RIP manages this by changing the administrative distance of hop 16 to 255 which is considered unreachable. Also, remember that RIP is a classfull routing protocol and therefore does not include the subnet mask in the routing update. RIP assumes that everyone is using the same subnet mask. One of the primary reasons this came about was because RIP was developed before the need for subnetting came to be.
Save your current configurations to NVRAM.
End of Lab