Experiment 5
Experiment 5
Fourth Class
Experiment (5)
Basic Static Route Configuration
Objective
In this experiment you will learn
Introduction:
In this lab activity, you will create a network that is similar to the one shown in the
Topology Diagram. You will then perform the initial router configurations required for
connectivity. Use the IP addresses that are provided in the Addressing Table to apply an
addressing scheme to the network devices. After completing the basic configuration,
test connectivity between the devices on the network. First test the connections
between directly connected devices, and then test connectivity between devices that
are not directly connected. Static routes must be configured on the routers for end-to-
end communication to take place between the network hosts. You will configure the
static routes that are needed to allow communication between the hosts. View the
routing table after each static route is added to observe how the routing table has
changed.
Topology Diagram
Addressing Table
Procedure:
Step 2: Configure the console and virtual terminal line passwords on each of the
routers.
password
login
Step 3: Add the exec-timeout command to the console and virtual terminal lines.
To set the interval that the EXEC command interpreter waits until user input is detected, we
can use the exec-timeout line configuration command. If no input is detected during the
interval, the EXEC facility resumes the current connection. If no connections exist, the EXEC
facility returns the terminal to the idle state and disconnects the incoming session. This
command allows you to control the amount of time a console or virtual terminal line can be
idle before the session is terminated. The syntax follows:
In a lab environment, you can specify “no timeout” by entering the exec-timeout 0 0
command. This command is very helpful because the default timeout for lines is 10
minutes. However, for security purposes, you would not normally set lines to “no timeout”
in a production environment.
R1(config)#line console 0
R1(config-line)#exec-timeout 0 0
R1(config-line)#line vty 0 4
R1(config-line)#exec-timeout 0 0
Step 1: On R1 from privileged EXEC mode, enter the debug ip routing command.
R1#debug ip routing
IP routing debugging is on
The debug ip routing command shows when routes are added, modified, and deleted from
the routing table. For example, every time you successfully configure and activate an
interface, Cisco IOS adds a route to the routing table. We can verify this by observing output
from the debug ip routing command.
As soon as you press the Enter key, Cisco IOS debug output informs you that there is now a
route, but its state is False. In other words, the route has not yet been added to the routing
table.
Step 3: Turn off debugging on router using either no debug ip routing or simply,
undebug all.
From the host PC1, is it possible to ping the default gateway? ________
From the host PC2, is it possible to ping the default gateway? ________
From the host PC3, is it possible to ping the default gateway? ________
Step 2: Use the ping command to test connectivity between directly connected
routers.
From the router R2, is it possible to ping R1 at 172.16.2.1? ________
From the router R2, is it possible to ping R3 at 192.168.1.1? ________
Step 3: Use ping to check connectivity between devices that are not directly
connected.
From the host PC3, is it possible to ping the host PC1? ________
From the host PC3, is it possible to ping the host PC2? ________
From the host PC2, is it possible to ping the host PC1? ________
From the router R1, is it possible to ping router R3? ________
Are all of the relevant interfaces on each router activated (that is, in the up and up state)?
________
How many interfaces are activated on R1 and R3? _______
Why are there three activated interfaces on R2?
__________________________________________
Step 2: View the routing table information for all three routers.
R1# show ip route
What networks are present in the Topology Diagram but not in the routing table for R1?
____________________________________________________________________
What networks are present in the Topology Diagram but not in the routing table for R2?
____________________________________________________________________
What networks are present in the Topology Diagram but not in the routing table for R2?
____________________________________________________________________
Why are all the networks not in the routing tables for each of the routers?
_________________________________________________________________________
What can be added to the network so that devices that are not directly connected can ping
each other?_____________________________________________________________
Step 1: To configure static routes with a next-hop specified, the following syntax:
On the R3 router, configure a static route to the 172.16.1.0 network using the Serial 0/0/1
interface of R2 as the next-hop address.
Step 2: View the routing table to verify the new static route entry.
Notice that the route is coded with an S, which means that the route is a static route.
R3#show ip route
Codes: C - connected,S - static,I - IGRP,R - RIP,M - mobile,B - BGP
D - EIGRP, EX - EIGRP external, O-OSPF, IA - OSPF inter area
N1 -OSPF NSSA external type 1, N2 -OSPF NSSA external type 2
E1 -OSPF external type 1, E2 -OSPF external type 2, E - EGP
i-IS-IS,L1-IS-IS level-1,L2-IS-IS level2,*-candidate default
U - per-user static route, o - ODR
With this route entered in the routing table, any packet that matches the first 24 left-most
bits of 172.16.1.0/24 will be forwarded to the next-hop router at 192.168.1.2.
What interface will R3 use to forward packets to the 172.16.1.0/24 network? ____________
Assume that the following packets have arrived at R3 with the indicated destination
addresses. Will R3 discard the packet or forward the packet? If R3 forwards the packet, with
what interface will R3 send the packet?
Step 3: Use ping to check connectivity between the host PC3 and the host PC2.
From the host PC3, is it possible to ping the host PC2? ________
These pings should fail. The pings will arrive at PC2 if you have configured and verified all
devices. PC2 will send a ping reply back to PC3. However, the ping reply will be discarded at
R2 because the R2 does not have a return route to the 192.168.2.0 network in the routing
table.
Step 4: On the R2 router, configure a static route to reach the 192.168.2.0 network.
What is the next-hop address to which R2 would send a packet destined for the
192.168.2.0/24 network?
Step 5: View the routing table to verify the new static route entry.
Notice that the route is coded with an S, which means the route is a static route.
R2#_________________________________
Step 6: Use ping to check connectivity between the host PC3 and the host PC2.
From the host PC3, is it possible to ping the host PC2? ________
This ping should be successful.
Step 2: View the routing table to verify the new static route entry.
R3#show ip route
Step 4: View the routing table to verify the new static route entry.
R2#show ip route
At this point, R2 has a complete routing table with valid routes to all five networks shown in
the Topology Diagram.
Does this mean that R2 can receive ping replies from all destinations shown in the Topology
Diagram? ________
Why or why not?
_______________________________________________________________________
Step 5: Use ping to check connectivity between the host PC2 and PC1.
This ping should fail because the R1 router does not have a return route to the 172.16.1.0
network in the routing table.
Step 2: View the routing table to verify the new static route entry.
R1#_________________________________
Note that the R1 router now has a default route, the gateway of last resort, and will send all
unknown traffic out Serial 0/0/0, which is connected to R2.
Step 3: Use ping to check connectivity between the host PC2 and PC1.
From the host PC2, is it possible to ping PC1? ________
This ping should be successful this time because the R1 router can return the packet using
the default route.
From the host PC3, is it possible to ping the host PC1? ________
Is there a route to the 172.16.3.0 network in the routing table on the R3 router? ________
172.16.1.0 10101100.00010000.00000001.00000000
172.16.2.0 10101100.00010000.00000010.00000000
172.16.3.0 10101100.00010000.00000011.00000000
The prefix portion will include 172.16.0.0, because this would be the prefix if we turned off
all the bits to the right of the 22nd bit.
Prefix 172.16.0.0
To mask the first 22 left-most bits, we use a mask with 22 bits turned on from left to right:
Mask 255.255.252.0
Configuring a summary route on R3 did not remove the static routes configured earlier
because these routes are more specific routes. They both use /24 mask, whereas the new
summary will be using a /22 mask. To reduce the size of the routing table, we can now
remove the more specific /24 routes.
Step 4: Verify that the routes are no longer in the routing table.
R3 now only has one route to any host belonging to networks 172.16.0.0/24, 172.16.1.0/24,
172.16.2.0/24, and 172.16.3.0/24. Traffic destined for these networks will be sent to R2 at
192.168.1.2.
Step 5: Use ping to check connectivity between the host PC3 and PC1.
This ping should be successful this time because there is a route to the 172.16.3.0 network
on the R3 router, and the R1 router can return the packet using the default route.