E-Lab 7.2.6a - Troubleshooting RIP Update Issues
Perform a basic configuration of the router Pretoria.
Then configure RIP for the networks 192.168.14.0 and 192.168.15.0 and verify the configuration.
Step 1
Enter privileged EXEC mode.
Step 2
Enter into global configuration mode.
Step 3
Set the hostname to Pretoria.
Step 4
Enter line configuration mode for the console.
Step 5
Set the console password to cisco.
Step 6
Enter the login command.
Step 7
Enter the exit command to return to global configuration mode.
Step 8
Enter line configuration mode for virtual terminals 0 through 4.
Step 9
Set the vty password to cisco.
Step 10
Enter the login command.
Step 11
Exit to global configuration mode.
Step 12
Set the enable password to class.
Step 13
Enter router configuration mode for RIP.
Step 14
Add a network entry for 192.168.15.0.
Step 15
Add a network entry for 192.168.14.0.
Step 16
Use the command end to exit into privileged EXEC mode.
Step 17
Save your configuration.
Step 18
Check that routing updates are being sent using the appropriate debug command.
Step 19
View the routing table.
Note that there is a routing table entry to the FastEthernet network of the neighbouring router, 192.168.16.0.
This shows that the adjacent router is running RIP and advertising the 192.168.16.0 network address.
Step 20
Test the routing by issuing a ping from workstation A to workstation B at 192.168.16.2.
This verifies routing backwards and forwards through the network, because the ping would not be able to return unless there was a route to the ping originator.