FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGIES

FALL 2023

FINAL EXAMINATION
COURSE TITLE: CCNA1
COURSE CODE: ISN3201
INSTRUCTOR: Engr. Tanwi Nkiamboh
Student Name Nkumbe Larry Etah

Lab Topology

1
 Activity 1: Connected and Local Routes (20 Marks)
1) Say no when asked if you would like to enter the initial configuration dialog on each router.

2)Configure hostnames on the routers according to the Lab Topology diagram.

To configure hostnames on routers, you typically access the router's command line interface (CLI) via a
terminal emulation software such as PuTTY or directly through console access. Once logged in, you can enter
configuration mode and set the hostname using the following steps:

Router 1
Enable
Configure terminal
Hostname R1
End
Write memory

Router 2
Enable

2
Configure terminal
Hostname R2
End
Write memory

Router 3
Enable
Configure terminal
Hostname R3
End
Write memory

Router 4
Enable
Configure terminal
Hostname R4
End
Write memory

Router 5
Enable
Configure terminal
Hostname R5
End
Write memory

3) Configure IP addresses on R1 according to the Lab Topology diagram

To configure IP addresses on a router (in this case, R1) according to the Lab Topology diagram, you'll need
to access the router's command line interface (CLI) and enter the appropriate commands. Here's a step-by-step
guide:

3
4) Verify routes have been automatically added for the connected and local networks (note that local routes only
appear from IOS 15)
To verify that routes have been automatically added for the connected and local networks on a Cisco router
(assuming IOS 15 or later), you can use the show ip route command. This command displays the router's
routing table, including both directly connected networks and any routes learned through dynamic routing
protocols or configured statically.
Here's how you can use the show ip route command to verify the routes:

4
5) Do you see routes for all networks that R1 is directly connected to? Why or why not?
In the provided example output of the show ip route command, only routes for networks directly connected
to R1 are displayed. This is because the show ip route command typically only shows routes that are directly
connected to the router or routes that the router has learned through dynamic routing protocols or static route
configurations.

6) Should you be able to ping from PC1 to PC2? Verify this.

(Click on PC1 then 'Desktop' and 'Command Prompt' to access its command line interface.)
To verify whether you can ping from PC1 to PC2, you need to ensure that both PCs are properly configured
with IP addresses in the same subnet and that there are no network connectivity issues between them.

As we can see the ping from PC1 to PC2 was successful, it indicates that there is proper network connectivity
between the two PCs and that they can communicate with each other. This means that both PCs are configured
correctly with IP addresses in the same subnet, and there are no network connectivity issues preventing
communication.

Successful ping results typically show a series of replies from the destination IP address, indicating that the
network path between the source and destination is functioning properly. It's a positive sign that the network is
configured correctly and that data can be exchanged between PC1 and PC2.
5
7) Verify the traffic path from PC1 to PC2. Use the tracert' command.

the tracert command completed successfully without any errors and showed the expected output, it confirms
that the network path between PC1 and PC2 is functioning correctly and that there are no issues preventing
communication between them.

8) Should you be able to ping from PC1 to PC3? Verify this.

If you're receiving a message that says "Destination Host Unreachable" and you're unable to ping from PC1 to
PC3, it indicates that there's likely a network connectivity issue preventing communication between the two
PCs. Here are some steps you can take to troubleshoot and resolve the problem:

Check IP configurations:

Verify that PC1 and PC3 have correct IP addresses configured in the same subnet.
Ensure that the subnet masks are correctly configured on both PCs.
Check physical connectivity:

Ensure that the Ethernet cables connecting PC1 and PC3 to the network are securely plugged in at both ends.
Check the status of the network interface on both PCs to ensure they are up and not experiencing any physical
issues.
Check network devices:

If there are switches or routers between PC1 and PC3, ensure that they are powered on and configured correctly.

6
Check the configuration of any intermediary devices to ensure they are not blocking traffic between PC1 and
PC3.
Verify VLAN configuration (if applicable):

If PC1 and PC3 are in different VLANs, ensure that the VLAN configurations are correct on the switches and
that inter-VLAN routing is enabled if necessary.
Check for firewall or security software:

If there are firewall or security software running on PC1 or PC3, check to see if they are blocking ICMP traffic
or traffic between the two PCs.

Remarks
 Activity 1 was not that way difficult to configure the hostnames and ip addresses of all interfaces connected
on R1
 Overall, the network setup seems to be progressing smoothly, with successful ping connectivity between
PC1 and PC2 and a clear understanding of the reason behind the failed ping from PC1 to PC3.

Activity 2: Static Routes (13 Marks)

9) Configure IP addresses on R2, R3 and R4 according to the Lab Topology diagram. Do not configure the
Internet Fast Ethernet 1/1 interface on R4. Do not configure R5.

7
8
As you can see the configuration for all the IP addresses went smoothly

10) Verify PC3 can ping its default gateway at 10.1.2.1

As we can see the pin was successful

11)Configure static routes on R1, R2, R3 and R4 to allow connectivity between all their subnets. Use /24
prefixes for each network.

9
12)Verify connectivity between PC1, PC2 and PC3.

10
11
13) Verify the path traffic takes from PC1 to PC3.

Activity 3: Summary Routes (12 Marks)

14) Remove all the static routes on R1
To remove all static routes on R1, you'll need to access the router's command line interface (CLI) and enter
the appropriate commands. Here's how you can do it:
enable
configure terminal
no ip route <destination_network> <subnet_mask> <next_hop_IP>
Replace <destination_network>, <subnet_mask>, and <next_hop_IP> with the appropriate values for each
static route you want to remove.
end
Write memory

12
15) Verify that PC1 loses connectivity to PC3
If you've removed all static routes on R1 and there are no dynamic routing protocols enabled, it's likely that
PC1 will lose connectivity to PC3, assuming PC3 is not directly connected to the same subnet as PC1. Here's
why:

Without static routes: With no static routes configured on R1, it won't have a specific route to reach networks
beyond its directly connected interfaces.

Routing behavior: R1 will only have routes to directly connected networks, such as the network where PC1 is
located. If PC3 is on a different subnet and there are no dynamic routing protocols to provide routes, R1 won't
know how to reach PC3.

Packet forwarding: When PC1 tries to communicate with PC3, it will send packets to its default gateway
(presumably R1). However, since R1 doesn't have a route to PC3's subnet, it will be unable to forward the
packets to their destination.

To verify that PC1 loses connectivity to PC3:

Attempt to ping PC3 from PC1.

13
If PC1 is unable to ping PC3 and returns "Destination Host Unreachable" or similar message, it indicates that
PC1 has lost connectivity to PC3.

16) Restore connectivity to all subnets with a single command on R1.

If you want to restore connectivity to all subnets with a single command on R1, you can configure a default
route pointing to the next-hop router, which is typically the gateway leading to the rest of the network. This
default route will allow R1 to forward packets to destinations outside of its directly connected subnets.

Here's how to configure a default route on R1:

17) Verify the routing table on R1 does not contain /24 routes to remote subnets.
To verify that the routing table on R1 does not contain /24 routes to remote subnets, you can use the show ip
route command and filter the output to display only the routes with a subnet mask other than /24. Here's how
you can do it:
enable
Conf t
Show ip route
Show ip route | include /24

14
18) Ensure that connectivity is restored between PC1 and PC3.
To restore connectivity between PC1 and PC3, you'll need to ensure that R1 has a route to the subnet where
PC3 is located. Since we're assuming PC3 is not directly connected to the same subnet as PC1 and R1, we'll
need to configure routing on R1 to reach PC3's subnet.

Here's how you can do it:

Remarks
Overall, the network was reconfigured to restore connectivity between PC1 and PC3 by adjusting the routing on
R1. The steps involved removing existing static routes, configuring a default route, and verifying the routing
table to ensure proper routing behavior.
Activity 4: Longest Prefix Match (15 Marks)
19) Configure IP addresses on R5 according to the Lab Topology diagram

15
To configure IP addresses on R5 according to the Lab Topology diagram, you need to access the router's
command line interface (CLI) and enter the appropriate commands. Here's a step-by-step guide:

20) Do not add any additional routes. Does PC1 have reachability to the FastEthernet 0/0 interface on R5? If so,
which path will the traffic take?
Without adding any additional routes, PC1 would not have reachability to the FastEthernet0/0 interface on R5.
This is because PC1 is on a different network/subnet than the FastEthernet0/0 interface on R5, and there are no
routes configured to reach that network from PC1's perspective.

If PC1 were to attempt to reach the FastEthernet0/0 interface on R5, it would send the traffic to its default
gateway, which is R1 in this case. However, since R1 also doesn't have a route to the network where the
FastEthernet0/0 interface on R5 is located, the traffic would not be forwarded beyond R1.

Therefore, without additional routes configured, PC1 would not have reachability to the FastEthernet0/0
interface on R5, and the traffic would not be able to reach its destination.

16
21) Ensure reachability over the shortest possible path from R5 to all directly connected networks on R1.
Achieve this with a single command
To ensure reachability over the shortest possible path from R5 to all directly connected networks on R1 with
a single command, you can configure a default route on R5 pointing towards the FastEthernet0/0 interface of R1.
This default route will instruct R5 to send any traffic with a destination outside of its directly connected
networks to R1, which is the shortest path.

Here's the command to configure the default route on R5:

17
This single command will ensure that R5 can reach all directly connected networks on R1 via the shortest
possible path, as any traffic destined for those networks will be forwarded directly to R1.

22) Verify the path traffic takes from PC1 to the FastEthernet 0/0 interface on R5.
To verify the path that traffic takes from PC1 to the FastEthernet0/0 interface on R5, you can use the tracert
command on PC1. Since R5 is the default gateway for PC1, the tracert command will show the path taken by
the traffic as it exits PC1's network and reaches the FastEthernet0/0 interface on R5.

Here's how you can use the tracert command:

Open a command prompt on PC1: Go to PC1's desktop, open the Command Prompt application.

Use the tracert command: Enter the following command:

tracert <R5_FastEthernet0/0_IP>
Replace <R5_FastEthernet0/0_IP> with the IP address of the FastEthernet0/0 interface on R5.

23) Verify the path the return traffic takes from R5 to PC1.
To verify the path that return traffic takes from R5 to PC1, you can examine the routing table on R5 to
determine the next hop for traffic destined for PC1's network. Additionally, you can use the traceroute
command on R5 to trace the path taken by the return traffic as it travels back to PC1. Here's how you can do it:

24) Ensure that traffic between PC1 and the FastEthernet 0/0 interface on R5 takes the most direct path in both
directions.
To ensure that traffic between PC1 and the FastEthernet0/0 interface on R5 takes the most direct path in both
directions, you need to make sure that the routing configuration on both R1 and R5 is optimized for the shortest
path between them. Here's how you can achieve this:

18
By configuring a default route on R5 and ensuring that R1 has a route to PC1's network, you can ensure that
traffic between PC1 and the FastEthernet0/0 interface on R5 takes the most direct path in both directions. This
setup optimizes routing for efficient communication between the two devices.

25) Verify that traffic between PC1 and the FastEthernet 0/0 interface on R5 takes the most direct path in both
directions.
To verify that traffic between PC1 and the FastEthernet0/0 interface on R5 takes the most direct path
in both directions, you can use the tracert (or traceroute on some systems) command from both PC1 and
R5. This will show the path taken by the traffic in each direction and confirm if it follows the expected
route.

By using tracert or traceroute from both PC1 and R5, you can verify that traffic between them takes the most
direct path in both directions, confirming that the routing configuration is optimized for efficient
communication.

Activity 5: Default Route and Load Balancing (10 Marks)

26) Configure an IP address on the Internet FastEthernet 1/1 interface on R4 according to the lab topology
diagram.
To configure an IP address on the Internet FastEthernet 1/1 interface on R4 according to the lab topology
diagram, follow these steps:

Access the command line interface of R4 using SSH, Telnet, or console access.

Enter privileged EXEC mode by typing:

19
with the appropriate subnet mask. This configuration will assign the specified IP address to the interface and
enable it for communication on the network.

27) Ensure that all PCs have a route out to the internet through the Internet Service Provider connection on R4.
(Note that the lab does not actually have Internet connectivity.)
To ensure that all PCs have a route out to the internet through the Internet Service Provider (ISP) connection on
R4, we'll need to configure R4 to act as the gateway for the PCs and configure default routes on the PCs
pointing to R4. Since the lab does not actually have internet connectivity, we'll simulate the ISP connection on
R4.

Here's how you can achieve this:

Configure IP address on the Internet FastEthernet 1/1 interface on R4:

Follow the steps provided earlier to configure an IP address on the FastEthernet 1/1 interface on R4. This
interface will simulate the connection to the ISP.
Configure R4 as the default gateway on the PCs:

Access the network configuration settings on each PC.

Set the default gateway to the IP address of the FastEthernet 1/1 interface on R4. This tells the PCs to send any
traffic destined for destinations outside their subnet to R4.
Configure a default route on R4:

On R4, configure a default route pointing to the ISP's next-hop router (simulated in this case). This instructs R4
to forward any traffic with a destination outside of its directly connected subnets to the ISP's router (simulated).

20
21
By configuring R4 as the default gateway on the PCs and configuring a default route on R4 pointing to the
simulated ISP's next-hop router, we ensure that all PCs have a route out to the internet (simulated) through the
ISP connection on R4. This setup simulates internet connectivity within the lab environment.

28) Traffic from PC1 and PC2 going to the internet should be load balanced over R2 and R5.
To achieve load balancing for traffic from PC1 and PC2 going to the internet over R2 and R5, we can use equal-
cost multipath (ECMP) routing. ECMP allows traffic to be distributed across multiple paths that have equal cost.

With ECMP configured on R4 and equal-cost routes to the networks behind R2 and R5,
traffic from PC1 and PC2 destined for the internet will be load balanced over R2 and R5,
providing redundancy and efficient utilization of available links.

Difficulties and conclusion

Difficulties:

Configuration Accuracy: Ensuring that hostnames, IP addresses, and routes are configured accurately can be
challenging, as even small errors can lead to connectivity issues.

22
Verification Complexity: Verifying routes and connectivity between devices can be complex, especially in
larger networks with multiple routers and subnets. Ensuring that routes are correctly added and traffic flows
as expected requires thorough verification.

Static Route Configuration: Configuring static routes on multiple routers to enable connectivity between all
subnets requires careful planning and validation. Incorrect static route configurations can result in traffic being
unable to reach its destination.

Load Balancing Implementation: Implementing load balancing for traffic from PC1 and PC2 over R2 and R5
requires additional configuration steps and testing to ensure that traffic is evenly distributed across the
available paths.

Addressing these difficulties through careful planning, methodical execution of tasks, and effective
troubleshooting techniques is essential to successfully configuring the network and achieving the desired
functionality. Additionally, documenting configurations and steps taken during the lab can aid in
troubleshooting and reviewing the setup later.
Conclusion
In conclusion, configuring a network according to the provided lab topology diagram involves several key tasks,
including hostname and IP address configuration, route verification, static route configuration, and ensuring
internet access with load balancing. Successfully completing these tasks requires careful attention to detail,
adherence to the lab instructions, and effective troubleshooting techniques.

23