Addis Ababa institute of technology

Network Layer Basic Configuration

Course Title: ECEG-4211 Data communication and computer network

Instructor: Bethlehem Seifu

Submitted by

Adhanom kidanmariam ATE/5943/10

Alazar Gezahegn ATE/2684/10

Temesgen Zewdu ATE/0888/10

Jemberu Alamirew ATE/0261/11

Tensay Daniel ATE/1652/11

Date: MAY 31 2024

Abstract
This report details the fundamental configuration of the network layer and the implementation
of the Open Shortest Path First (OSPF) protocol. It covers the essential aspects of network layer
setup, including IP addressing, subnetting, and basic router configurations. IP addressing is the
cornerstone of the network layer, providing unique identifiers for devices, and comes in two
versions: IPv4 and IPv6. Subnetting, a crucial process in network management, divides a larger
network into smaller sub-networks to enhance performance and security.

The report also explores the basic configuration of routers, highlighting the importance of
assigning IP addresses to router interfaces, configuring routing protocols.

The implementation section focuses on OSPF, a robust and scalable link-state routing protocol
used in IP networks. The report explains OSPF’s purpose in providing efficient and quick
convergence in large enterprise networks, categorizing it as an Interior Gateway Protocol (IGP)
operating within an Autonomous System (AS). The configuration steps for OSPF are outlined,
including enabling OSPF on the router, assigning OSPF areas, setting router IDs, and configuring
interface parameters.

Overall, the report provides a comprehensive overview of setting up the network layer and
implementing OSPF to ensure efficient and reliable network communication.
Introduction
This lab experiment was conducted as part of the ECEG-4211 Data Communications and
Computer Networks course. The primary aim of this course is to introduce fundamental
networking concepts and equip students with practical configuration skills necessary for setting
up and managing networks. By combining theoretical knowledge with hands-on practice, the
course ensures that students are well-prepared to handle real-world networking scenarios.

Key Topics Covered

Throughout the course, several key topics are covered, including:

 Network Addressing: Understanding the structure of IP addresses, differentiating

between IPv4 and IPv6, and learning the concepts of network classes, CIDR (Classless
Inter-Domain Routing), and the allocation of public and private IP addresses.
 Subnetting: Learning how to divide a large network into smaller, manageable
subnetworks, calculating subnet masks, and understanding subnetting techniques to
optimize network performance and security.
 Router Interfaces: Gaining practical skills in configuring router interfaces, assigning IP
addresses, and setting up subnet masks to enable communication between different
network segments.
 Basic Configuration: Performing initial setup and configuration of networking devices
such as routers and switches, including setting up device hostnames, passwords, and
basic security features.

Objectives of the Experiment

The lab experiment aimed to apply the concepts learned in lectures by constructing and
configuring a network based on a provided topology diagram. The specific objectives of the
experiment were as follows:

1. Assign IP Addresses to Routers and Hosts:

o Each router and host needed to be assigned an IP address according to the
provided addressing scheme.
o Subnet masks were to be configured appropriately for each network segment.
o All interfaces were to be enabled and verified to ensure correct configuration.
2. Physical Connectivity:
o Devices were to be connected as per the physical topology diagram provided.
o Layer 3 connectivity was to be tested using the ping command to ensure that all
devices could communicate across the network.
o Any connectivity issues discovered during testing were to be diagnosed and
resolved.
3. Implement a DHCP Server:
 o A DHCP server was to be configured to dynamically assign IP addresses to client
hosts within the network.
o The DHCP server configuration included setting up appropriate address pools,
lease times, and other necessary parameters to ensure reliable address
assignment.
o The proper operation of the DHCP server was to be verified by checking that
client devices received correct IP addresses and could communicate on the
network.
4. Configure the OSPF Routing Protocol:
o The Open Shortest Path First (OSPF) routing protocol was to be configured on
the routers to facilitate automatic learning and sharing of routes within the
autonomous system.
o This included configuring OSPF areas, assigning router IDs, and ensuring that all
routers in the network correctly propagated route information.
o The proper operation of OSPF was to be verified by checking the routing tables
and ensuring that all network segments were reachable.

Expected Outcomes

By the end of this lab experiment, students were expected to have achieved the following
outcomes:

 Successfully assigned and verified IP addresses for all network devices.

 Established and tested physical and logical connectivity across the network.
 Implemented a functional DHCP server that dynamically assigned IP addresses to client
hosts.
 Configured OSPF routing protocol on the routers, enabling dynamic route learning and
propagation.
Materials and Equipment
Hardware: The following hardware components were utilized to implement the network
configuration:

 3 Cisco ISR 4331 Routers (R0, R1, R2): These routers were running Cisco IOS
(Internetwork Operating System), serving as the core networking devices responsible for
routing data between different network segments.
 2 Cisco 2960 Switches (S1, S2): These switches facilitated network connectivity by
efficiently directing data packets between devices within the same network segment.
 5 PCs (PC0, PC1, PC2,): These computers served as endpoints within the network,
allowing users to interact with network resources and applications.

Cabling:

The following types of cables were used for physical connectivity:

 Serial Cables: Utilized to establish connections between routers, enabling them to

communicate and exchange routing information.
 Ethernet Cables: Used for connecting routers, switches, and PCs, providing the physical
link for data transmission within the network.

Software:

The network configuration was supported by the following software tools:

 Packet Tracer 8.2.1.0118: This network simulation software provided a virtual

environment for designing, configuring, and testing network topologies. It allowed
students to simulate real-world networking scenarios and practice configuration tasks
without the need for physical hardware.

IPv4 Addressing: IPv4 addressing was allocated according to the addressing table scenario
provided. Each device in the network was assigned a unique IPv4 address to facilitate
communication.

Configuration Process:

 Routers were configured programmatically using Cisco IOS commands accessed through
their console ports in Command Line Interface (CLI) mode.
 Switches were configured using the graphical user interface available in Packet Tracer,
providing an intuitive way to set up switch ports and VLANs.
 PCs were assigned IP addresses and tested for network reachability to ensure proper
communication across the network.
Methods and Procedure
The successful completion of the network configuration involved the following steps:

1. Study of Topology Diagram:

 The provided topology diagram was thoroughly examined to gain a clear understanding
of the network design, including the placement of routers, switches, and PCs, as well as
the interconnections between them.

2. Equipment Setup:

 Routers, switches, and PCs were physically interconnected according to the topology
diagram using appropriate cabling, including serial cables for router connections,
Ethernet cables for device connections, and console cables for router console access
from PCs.

3. Router Configuration:

 Router console ports were accessed using HyperTerminal or similar terminal emulation
software.
 Default configurations on each router were cleared using the "write erase" and "reload"
commands to ensure a clean slate for configuration.

4. IP Address Assignment:

 IPv4 addresses were assigned to router interfaces and PCs as per the addressing table
provided. This included configuring IP addresses, subnet masks, and enabling interfaces
using the "no shutdown" command.

5. Connectivity Testing:

 Ping tests were conducted between devices to verify connectivity and troubleshoot any
connectivity issues that arose during configuration. This ensured that devices could
communicate with each other across the network.

6. DHCP Service Configuration:

 DHCP service was configured on R2 by creating a DHCP pool with specified start and end
addresses for dynamic IP address assignment to client hosts within the network.

7. OSPF Routing Configuration:

  OSPF routing protocol was enabled on routers using the "router ospf [process-id]"
command, along with network statements to specify which interfaces participate in
OSPF routing.
 Router IDs were automatically selected by the routers.
 Verification commands such as "show ip ospf neighbor" and "show ip route" were used
to confirm OSPF neighbor relationships and examine the routing tables.

8. Recording Observations:

 Output from show commands, as well as observations made during configuration and
testing, were recorded for documentation purposes. This included noting down any
errors encountered and their resolutions.

9. Configuration Preservation:

 Configurations were saved to the routers' startup-config to ensure that they persisted
across reboots, preserving the configured settings for future use.

10. Packet Capture and Analysis:

 Packet captures were performed during ping tests to capture and analyze ARP and
routing behavior, providing insights into how data packets were being forwarded across
the network.

11. Documentation:

 The results of connectivity tests, observations, and configuration details were compiled
into a comprehensive laboratory report, documenting the entire process from setup to
testing and analysis.
Discussion and Analysis
IP Addressing and Interface Configuration: The successful assignment of IP addresses to
interfaces based on the addressing scheme indicates a solid understanding of subnetting and IP
addressing principles. The absence of problems suggests that the subnets and masks were
designed correctly, ensuring proper segmentation of the network. The activation of interfaces
effectively established physical links between routers and connectivity domains, laying the
foundation for communication within the network.

For Router R0

Router # show ip interface brief

For Router R1

For Router R2
Testing Connectivity: The validation of basic Layer 3 reachability within subnets through
successful pinging between devices is a crucial milestone. The troubleshooting process,
particularly the identification of the need for routing when pings between R1-R2 initially failed,
underscores the intricate relationship between addressing and routing. This experience
highlights the importance of both components in ensuring end-to-end connectivity within a
network.

Ping R0 from R1

Ping R0 from R2

Ping R1 from R2

When initially attempting to ping R1 from R2, the ping was not successful. This is because at
that point, there was no routing configuration between routers R1 and R2.

Some key points:

 IP addresses had been configured on the router interfaces, allowing them to connect at
Layer 3.
 Pings within each router's directly connected subnet worked fine, showing intra-subnet
connectivity.
 However, R1 and R2 were in different subnets - 192.168.10.16/28 and 192.168.10.0/28
respectively.
 For a host in one subnet to communicate with a host in another subnet, the routers
need to have a routing protocol configured to exchange routing information.
 At the time the ping was attempted, OSPF routing had not yet been configured on R1
and R2. So their routing tables did not have an entry to reach the other subnet.
  Once OSPF was configured on all routers, it automatically populated each router's
routing table with routes to reachable networks, including those connected to other
routers.
 This allowed the ping from R2 to R1 to be successful, as R2 now knew to send traffic for
R1's subnet out its interface facing R1, and vice versa.

Which ping attempts were successful? Provide your reasoning for each ping request.

Here is an analysis of the ping attempts and their success:

Ping from PC1 to PC2: Successful

PC1 and PC2 are in the same directly connected subnet 192.168.10.16/28 to which R1 is
connected.

R1 has a route to reach this subnet and acts as the default gateway, so ping succeeds.

Ping from PC2 to PC1: Initially unsuccessful, later successful

Initially R2 did not have a route to 192.168.10.16/28 subnet to forward traffic

After configuring OSPF, R2 learnt a route to reach PC1's subnet via R1

Hence the ping became successful once routing was configured

Ping from PC1 to PC0: Successful

PC0 obtained its IP 192.168.10.21 via DHCP from R2's subnet

R2 has a route to reach both PCs in its directly connected subnets

So ping can succeed even though the PCs are in different subnets

Ping from Switch S1 VLAN interface to R2: Successful

S1 and R2 are in the same subnet 192.168.10.0/28

R2 has a route for this subnet and acts as the default gateway
What is the IP address of PC0?

Click Capture/Forward once. The ARP PDU moves Switch1 while the ICMP PDU disappears,
waiting for the ARP reply. Open the PDU and record the destination MAC address. Is this
address listed in the table above?

An ARP request was generated by PC1 to resolve the MAC address for 192.168.10.17 (the
destination IP for the ping).When the Capture/Forward button was clicked once, the ARP PDU
would have reached switch S1.The ICMP ping PDU would have disappeared at this point,
waiting for the ARP reply as the MAC address is still unknown.Opening the captured ARP PDU,
the destination MAC address recorded would be the MAC address of the interface on R2
corresponding to IP 192.168.10.17.Checking the addressing table, this MAC address should
match the interface MAC listed against IPv4 address 192.168.10.17.

Click Capture/Forward to move the ARP PDU to the next device. How many copies of the PDU
did S2 make?

the Capture/Forward button was clicked to move the ARP PDU to the next device after it
reached S1: S2 would have flooded the ARP request frame (PDU) it received from S1 to all its
ports/VLANs except the incoming port, which is standard ARP broadcast behavior. This is
because the target IP address for the ARP (192.168.10.17) could be on any connected subnet,
so a broadcast is needed. S2 has 2 active ports - one connected to S1 and one to R2.

Therefore, S2 would have made 2 copies of the ARP PDU - one out each of its ports, to ensure
the request is broadcast to all possible destinations. This flooding is a key aspect of the ARP
protocol to discover MAC addresses across L2 broadcast domains when an IP->MAC mapping is
unknown.
What is the IP address of the device that accepted the PDU?

Based on the scenario, when the ARP PDU was forwarded/captured to the next device after
leaving switch S2:

The only device connected to S2 that is in the same subnet as the target IP address in the ARP
request (192.168.10.17) is router R2.

R2's interface connected to S2 is configured with IP 192.168.10.17.

When S2 broadcast the ARP request, R2 would have accepted the frame, as its IP matched the
target IP being resolved.

No other device on the network has an IP in the 192.168.10.0/28 subnet except hosts and
devices connected to or through R2.

Therefore, the IP address of the device that accepted the ARP PDU forwarded by S2 is
192.168.10.17, which corresponds to the interface of router R2 connecting it to switch S2 and
the local subnet.

Click 172.16.31.2 and enter the arp -a command. To what IP address does the MAC address
entry correspond?

The PC was switched back to Realtime mode after the ping completed.

The arp -a command was issued on router R1, which has the IP address 172.16.31.2.

The arp -a command displays the ARP cache/table containing resolved IP to MAC address
mappings.

One of the entries in the ARP table would be for the router's own IP address (172.16.31.2).

The MAC address shown in this entry is the MAC address of the interface on R1 that holds IP
172.16.31.2.

Therefore, the MAC address displayed in the arp -a output on R1 for 172.16.31.2, corresponds
to the IP address 172.16.31.2, which is the router R1's own IP address.
From PC1 ping to PC2 and S2 vlan1. Click PC1 and enter the arp -a command. What additional
entries are added on the ARP table?

Ping was initiated from PC1 to PC2 and S2 VLAN interface.

This would generate ARP requests from PC1 to resolve the MAC addresses for:

192.168.10.18 - IP of PC2

192.168.10.2 - IP of S2 VLAN interface

After the pings completed, the arp -a command was issued on PC1.

The ARP table on PC1 would now contain additional entries for:

192.168.10.18 mapped to the MAC address of PC2's Ethernet interface

192.168.10.2 mapped to the MAC address of S2's VLAN interface.

These new entries correspond to the destinations that were just pinged. The ARP process
cached the resolved IP-MAC pairs for future reference by PC1.

Therefore, the additional entries added to PC1's ARP table after pinging PC2 and S2 are:

192.168.10.18 -> PC2's MAC

192.168.10.2 -> S2's VLAN MAC

These validate the dynamic address resolution function of ICMP Echo ping requests.

In general, when does an end device issue an ARP request?

In general, an end device like a host PC will issue an ARP request when:

The host needs to transmit a packet (e.g. for an application like ping, web, etc) to another host
on the local network/broadcast domain, but does not already know the target host's MAC
address.

The host has only the IP address of the target host, but needs the MAC address to construct and
send the frame at Layer 2 of the OSI model.The host checks its local ARP cache/table, but does
not find a cached entry mapping the target IP to MAC already. This could be because no
communication has happened before to the target.The cached ARP entry, if present, has
exceeded its timeout and been expired from the local table. ARP entries are dynamic and time
out to be refreshed.

The host has just come online on the network and its ARP table is empty, so it needs to resolve
addresses before any traffic can flow.

Note any update on any router on your report

On each router, which routes are calculated by the OSPF algorithm?

On each router R0, R1 and R2, OSPF was configured with process ID 1.

Network statements advertised the directly connected subnets of each router.

R0 advertised 192.168.10.16/28 and 192.168.30.0/24

R1 advertised 192.168.10.16/28 and 192.168.20.0/24

R2 advertised 192.168.10.0/28

With OSPF enabled, routers exchanged Link State Advertisements (LSAs) about these networks.

Using the Dijkstra shortest path first algorithm, OSPF calculates the optimal routes to all
advertised networks from each router.

On all routers, OSPF would calculate routes to the 192.168.10.0/28 subnet, since it is advertised
by R2 and connected to R1/R0 via R1 and R2 respectively.

Therefore, the routes calculated by the OSPF algorithm on each router are the 192.168.10.0/28
network, which represents the routes learned for the subnets of other OSPF routers within the
autonomous system.
On each router, what is the default route and its next-hop address?

On each router (R0, R1 and R2), the default route and its next hop address are:

Default route: 0.0.0.0/0

Next hop address: 192.168.30.1

The reasons are:

Router R0 is directly connected to the ISP router at interface with IP 192.168.30.1.

During the OSPF configuration, a default network statement was included on R0 for 0.0.0.0/0.

This injected the default route into the OSPF domain, with the next hop set as R0's directly
connected router interface (192.168.30.1).

OSPF propagated this default throughout the AS to all routers.

So on R1 and R2, the default route is present with the next hop listed as 192.168.30.1, which is
reachable via R0.

Therefore, on all routers R0, R1 and R2, the default route is 0.0.0.0/0 with the common next
hop of 192.168.30.1, which is the route to the external ISP network.
Conclusion
 The network was successfully designed and implemented based on the given topology
diagram and configuration tasks. All aspects such as addressing, interfaces and protocols
functioned as expected.
 IP addressing scheme utilized subnets and masks properly to separate collision domains
while maintaining connectivity.
 Interface configurations activated physical links and assigned IPs correctly. This allowed
reaching layer 3 for communication.
 Ping tests validated basic IP connectivity within subnets and troubleshooting identified
routing needs between subnets.
 DHCP service auto-assigned dynamic IPs, reducing manual configuration effort.
 OSPF routing exchanged link state data and dynamically built all intra-AS routes
optimally in the routing tables.
 Observing ARP, route tables and packet captures provided insight into lower layer
protocol operations alongside viewing router running configs and outputs.
 The lab experience reinforced classroom networking concepts through hands-on
practice configuring and implementing a multi-router network with addressing,
connectivity, and dynamic operation of core protocols.
 Troubleshooting steps helped identify relationship of protocols and develop skills in
network deployment, testing and problem isolation.
 Overall, the objectives of configuring addressing, interfaces, testing connectivity and
routing services were met, verifying key competencies developed by the networking
course and lab module.
Reference
CCNA Routing and Switching Portable Command Guide, 4th Edition. Scott Empson. Cisco Press,
2019. This reference guide provided commands used for router and switch configurations.

CCNA 200-301 Official Cert Guide, Volume 1. Wendell Odom. Cisco Press, 2019. This
certification guidebook was a learning resource for networking concepts and protocols
configured in the lab.

Cisco Packet Tracer 8.2.1.0118 User Guide. Cisco Networking Academy, 2024.