Lab_4: Basic Static and Default Route Configuration

Topology Diagram

Addressing Table

Device Interface IP Address ss Subnet Mask e Gateway

G0/0/1 172.16.3.1 255.255.255.0 N/A

R1
G0/0/0 172.16.2.1 255.255.255.0 N/A
G0/1 172.16.1.1 255.255.255.0 N/A
R2 G0/0 172.16.2.2 255.255.255.0 N/A
G0/2 192.168.1.2 255.255.255.0 N/A
G0/0/0 192.168.2.1 255.255.255.0 N/A
R3
G0/0/1 192.168.1.1 255.255.255.0 N/A
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
Objectives

✓ Perform basic configuration tasks on a router.

✓ Configure and activate Ethernet interfaces.
✓ Test connectivity.
✓ Gather information to discover causes for lack of connectivity between devices.
✓ Configure a static route using an intermediate address.
✓ Configure a static route using an exit interface.
✓ Compare a static route with intermediate address to a static route with exit interface.
✓ Configure a default static route.
✓ Configure a summary static route.
✓ Document the network implementation.

Scenario
In this lab activity, you will create a network that is similar to the one shown in the Topology
Diagram. Begin by cabling the network as 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.
Task 1: Cable, Erase, and Reload the Routers.
Step 1: Cable a network that is similar to the one in the Topology Diagram.
Step 2: Clear the configuration on each router.
Clear the configuration on each of the routers using the erase startup-config command and then
reload the routers. Answer no if asked to save changes.
Would you like to enter the initial configuration dialog? [yes/no]: N
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:

Router(config)#line console 0

Router(config-line) #exec-timeout 1
Task 2: Perform Basic Router Configuration.
R1(config)#interface GigabitEthernet0/0/1
R1(config-if)#ip address 172.16.3.1 255.255.255.0
R1(config-if)#no shutdown
Enter interface configuration mode for R1’s WAN interface connected to R2.
R1#configure terminal
Configure the IP address as specified in the Topology Diagram.
R1(config)#interface GigabitEthernet0 0/0/0
R1(config-if)#ip address 172.16.2.1 255.255.255.0
R1(config-if)#no shutdown
R1#show ip route
Task 4: 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 5: Configure IP Addressing on the Host PCs.
Step 1: Configure the host PC2.
Configure the host PC1 with an IP address of 172.16.3.10/24 and a gateway of 172.16.3.1.
Step 2: Configure the host PC2.
Configure the host PC2 with an IP address of 172.16.1.10/24 and a gateway of 172.16.1.1.
Step 3: Configure the host PC3.
Configure the host PC3 with an IP address of 192.168.2.10/24 and a gateway of 192.168.2.1.
Task 6: Test and Verify the Configurations.
Step 1: Test connectivity.
Test connectivity by pinging from each host to the default gateway that has been configured for
that host.
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?
These pings should all fail. Why?
Task 7: 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.
R2#show ip interface brief
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?

Static Route Configuration

Task 8: Configure a Static Route Using a Next-Hop Address.
Step 1: To configure static routes with a next-hop specified, use the following syntax:
On the R3 router, configure a static route to the 172.16.1.0 network using the G0/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)#do show ip route
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?
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 ________________
Task 9: Configure a Static Route Using an Exit Interface.
To configure static routes with an exit interface specified, use the following syntax:
Router(config)# ip route network-address subnet-mask exit-interface
Step 1: On the R3 router, configure a static route.
On the R3 router, configure a static route to the 172.16.2.0 network using the G0/0/1 interface of
the R3 router as the exit interface.
R3(config)# ip route 172.16.2.0 255.255.255.0 gigabitEthernet0/0/1
Step 3: On the R2 router, configure a static route
On the R2 router, configure a static route to the 172.16.3.0 network using the G0/0 interface of
the R2 router as the exit interface.
R2(config)# ip route 172.16.3.0 255.255.255.0 G0/0
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.

Configure a Default Static Route

In the previous steps, you configured the router for specific destination routes. But could you do
this for every route on the Internet? No. The router and you would be overwhelmed. To minimize
the size of the routing tables, add a default static route. A router uses the default static route when
there is not a better, more specific route to a destination. Instead of filling the routing table of R1
with static routes, we could assume that R1 is a stub router. This means that R2 is the default
gateway for R1. If R1 has packets to route that do not belong to any of R1 directly connected
networks, R1 should send the packet to R2. However, we must explicitly configure R1
with a default route before it will send packets with unknown destinations to R2. Otherwise, R1
discards packets with unknown destinations.
To configure a default static route, use the following syntax:
Router(config)#ip route 0.0.0.0 0.0.0.0 { ip-address | interface }
Step 1: Configure the R1 router with a default route.
Configure the R1 router with a default route using the G0/0/0 interface of R1 as the next-hop
interface.
R1(config)#ip route 0.0.0.0 0.0.0.0 172.16.2.2
R1(config)#
Step 2: View the routing table to verify the new static route entry.
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?
Task 12: Summary, Reflection, and Documentation
With the completion of this lab, you have:
✓ Configured your first network with a combination of static and default routing to provide full
connectivity to all networks
✓ Observed how a route is installed in the routing table when you correctly configure and activate
and interface
✓ Learned how to statically configure routes to destinations that are not directly connected
✓ Learned how to configure a default route that is used to forward packets to unknown
destinations
✓ Learned how to summarize a group of networks into one static route to reduce the size of a
routing table

Lab Report (Group of three)

In the following exercise, fill in the blanks to document the process as the ping travels from
source to destination. “Path Determination and Switching Function.” Based on the ICMP
process on PC3 formulates a ping request to PC2 and sends the reply to the IP process.
1. The IP process on PC3 encapsulates the ping packet with a source IP address of
________________ and destination IP address of _______________
2. PC3 then frames the packet with the source MAC address of (indicate device name) ___
_____and the destination MAC address of (indicate device name) ___________
3. Next, PC3 sends the frame out on the media as an encoded bit stream.
4. R3 receives the bit stream on its _____________ interface. Because the destination MAC
address matches the receiving interface’s MAC address, R3 strips off the Ethernet header
5. R3 looks up the destination network address _______________ in its routing table. This
destination has a next-hop IP address of ________________. The next-hop IP address is
reachable out interface _____________.
6. R3 encapsulates the packet in an HDLC frame and forwards the frame out the correct
interface. (Because this is a point-to-point link, no address is needed. However, the address
field in the HDLC packet contains the value 0x8F.)
7. R2 receives the frame on the ____________ interface. Because the frame is HDLC, R2
strips off the header and looks up the network address __________________ in its routing
table. This destination address is directly connected to the ___________interface.
8. R2 encapsulates the ping request in a frame with the source MAC address of (indicated
device name) _____ and the destination MAC address of (indicate device name) ________.
9. R2 then sends the frame out on the media as an encoded bit stream.
10. PC2 receives the bit stream on its ___________ interface. Because the destination MAC
address matches the MAC address of PC2, PC2 strips off the Ethernet header.
11. The IP process on PC2 examines the ___________ IP address to make sure that it matches
its own IP address. Then PC2 passes the data to the ICMP process.
12. The ICMP process on PC2 formulates a ping reply to PC3 and sends the reply to the IP
process.
13. The IP process on PC2 encapsulates the ping packet with a source IP address of
________________ and destination IP address of _______________.
14. PC2 then frames the packet with the source MAC address of (indicate device name)
________and the destination MAC address of (indicate device name) __________.
15. PC2 then sends the frame out on the media as an encoded bit stream.
16. R2 receives the bit stream on its _____________ interface. Because the destination MAC
address matches the receiving interface’s MAC address, R2 strips off the Ethernet header.
17. R2 looks up the destination network address _______________ in its routing table. This
destination has a next-hop IP address of _____________. The next-hop IP address is
reachable out interface ____________
18. R2 encapsulates the packet in an HDLC frame and forwards the frame out the correct
interface. (Because this is a point-to-point link, no address is needed. However, the address
field in the HDLC packet contains the value 0x8F.)
19. R3 receives the frame on the ___________ interface. Because the frame is HDLC, R3 strips
off the header and looks up the destination network address ____________ in its routing
table. This destination address is directly connected to the ______________ interface.
20. R3 encapsulates the ping request in a frame with the source MAC address of (indicated
device name) ________ and the destination MAC address of (indicate device name)
________.
21. R3 then sends the frame out on the media as an encoded bit stream.
22. PC3 receives the bit stream on its ______________ interface. Because the destination
MAC address matches the MAC address of PC3, PC3 strips off the Ethernet header.
23. The IP process on PC3 examines the _______ IP address to make sure that it matches its
own IP address. Then PC3 passes the data to the ICMP process.