Computer Networks

Lab Manual: 8

Basic Static Routes Configuration and Summary of Static Route

Session: Fall 2021

School of Systems and Technology

UMT Lahore Pakistan

98
CN LAB-8
Basic Static Route Configuration and summary of static route

Objective:

Perform basic configuration tasks on a router. Configure and activate Serial and Ethernet
interfaces, default static route and summary of static route.

Basic knowledge and theory:

Scenario
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

99
 Device Interface IP Address Subnet Mask Default Gateway
Fa0/0 172.16.3.1 255.255.255.0 N/
R1
S0/0/0 172.16.2.1 255.255.255.0 N/
Fa0/0 172.16.1.1 255.255.255.0 N/
R2 S0/0/0 172.16.2.2 255.255.255.0 N/
S0/0/1 192.168.1.2 255.255.255.0 N/
FA0/0 192.168.2.1 255.255.255.0 N/
R3
S0/0/1 192.168.1.1 255.255.255.0 N/
PC1 NIC 172.16.3.10 255.255.255.0 172.16.3.1
PC2 NIC 172.16.1.10 255.255.255.0 172.16.1.1
PC3 NIC 192.168.2.10 255.255.255.0 192.168.2.1

Task 1: Perform Basic Router Configuration.

Note: If you have difficulty with any of the commands in this task, see Lab 1.5.1: Cabling a Network
and Basic Router Configuration.

Step 1: Use global configuration commands.

On the routers, enter global configuration mode and configure the basic global
configuration commands including:
• hostname
• no ip domain-lookup
• enable secret

Step 2: Configure the console and virtual terminal line passwords on each of the routers.
• password
• login
Step 3: Enter interface configuration mode for R1’s WAN interface connected toR2.
R1#configure terminal

Enter configuration commands, one per line.End with

CNTL/Z. R1(config)#interface Serial 0/0/0

Configure the IP address as specified in the Topology Diagram.

R1(config-if)#ip address 172.16.2.1 255.255.255.0
R1(config-if)#no shutdown
As soon as you press the Enter key, Cisco IOS debug output informs you that there is now a

100
route, but its state is False. Because R1 is the DCE side of our lab environment, we must
specify how fast the bits will be clocked between R1 and R2.

Step 4: Enter the clock rate command on R1.

You can specify any valid clocking speed. Use the ? to find the valid rates. Here, we used
64000 bps.
R1(config-if)#clock rate 64000

Some IOS versions display the output shown above every 30 seconds. Why is the state of
the route still
False? What step must you now take to make sure that the interface is fully
configured?

Step 5: Configure the FastEthernet0/0 interface.

Configure the FastEthernet0/0 interface with the IP address172.16.3.1/24.
R1(config)#interface fastethernet 0/0
R1(config-if)#ip address 172.16.3.1 255.255.255.0
R1(config-if)#no shutdown
%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0,
changed state to up
R1(config-if)#

Task 2: Finish Configuring Router Interfaces

Step 1: Configure Remaining R2 Interfaces

Finish configuring the remaining interfaces on R2 according to the Topology Diagram and
Addressing Table.

Step 2: Configure R3 Interfaces

Console into R3 and configure the necessary interfaces according to the Topology
Diagram and Addressing Table.

Task 3: Configure IP Addressing on the Host PCs.

Step 1: Configure the host PC1.
Configure the host PC1 with an IP address of 172.16.3.10/24 and a default gateway of
172.16.3.1.

Step 2: Configure the host PC2.

101
Configure the host PC2 with an IP address of 172.16.1.10/24 and a default gateway of
172.16.1.1.

Task 4: Gather Information.

Step 1: Check status of interfaces.
Check the status of the interfaces on each router with the command show ip interface
brief. The following output is for R2

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.

What networks are present in the Topology Diagram but not in the routing table for R1?

102
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?

103
Task 5: Test and Verify the Configurations.
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?

you should be able to successfully ping from R2 to R1 and from R2 to R3.

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? -----------

These pings should all fail. Why?

Task 6: Configure a Static Route Using a Next-Hop Address.

Step 1: To configure static routes with a next-hop specified, use the following syntax:
Router(config)# ip route network-address subnet-mask ip-address

• network-address:—Destination network address of the remote

network to be added to the routing table.
• subnet-mask—Subnet mask of the remote network to be added to the
routing table. The subnet mask can be modified to summarize a group of
networks.
• ip-address—Commonly referred to as the next-hop router’s IP address.

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.

R3(config)#ip route 172.16.1.0 255.255.255.0 192.168.1.2

R3(config)#
Step 2: View the routing table to verify the new static route entry.

104
Notice that the route is coded with an S, which means that the route is a static route.

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 through Task 7, “Gather Information.” 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?

R2(config)#ip route 192.168.2.0 255.255.255.0 192.168.1.1

R2(config)#

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.

105
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.
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 7: Use ping to check connectivity between the host PC3 and PC1.
From the host PC3, is it possible to ping the host PC1? ---------------

Step 8: On the R3 router, configure a static route to reach the 172.16.1.0 network.
R3(config)#ip route 172.16.3.0 255.255.255.0 192.168.1.2
R3(config)#

Step 9: On the R1 router, configure a static route to reach the 172.16.3.0 network and
192.168.2.0

R1(config)#ip route 172.16.2.0 255.255.255.0 172.16.2.2

R1(config)#ip route 192.168.2.0 255.255.255.0 172.16.2.2

106
Step 10: On the R2 router, configure a static route to reach the 172.16.3.0 network.

R2(config)#ip route 172.16.3.0 255.255.255.0 172.16.2.1

R2(config)#

Step 11: Use ping to check connectivity all PC This ping should be successful

Finally, you should document your network implementation. On each router, capture
the following command output to a text (.txt) file and save for future reference.
• show running-config
• show ip route
• show ip interface brief

107