Practical-1

Construction of Straight-through and cross-over cable:

 Introduction to Networking Cabling:

Network cabling forms the backbone of computer networking, enabling devices to

communicate efficiently within a network. It involves the physical medium used to transmit
data signals, such as copper cables, fiber optics, or wireless connections. Proper cabling
ensures reliable and high-speed data transmission, reducing latency and minimizing errors in
communication. Its importance lies in its ability to establish robust network infrastructure for
homes, businesses, and data centers.

Types of Network Cables:

1. Straight-Through Cable:
o Definition: A cable where the same wiring standard (T568A or T568B) is
used on both ends.
o Use Case: Connects dissimilar devices, such as computers to switches or
routers.
2. Crossover Cable:
o Definition: A cable where one end follows T568A, and the other follows
T568B wiring standard.
o Use Case: Connects similar devices, such as computer to computer or switch
to switch.

 Objective of the Practical:

The primary objective of this practical is to understand the fundamental concepts of

network cabling, differentiate between straight-through and crossover cables, and learn
their specific use cases. Additionally, it aims to provide hands-on experience in creating
and testing these cables to establish proper network connections.

 Materials and Equipment:

List of the materials and equipment used in this practical are given below:

1) Ethernet Cables (Cat5e, Cat6, or Cat6a):

 Definition: Twisted-pair cables used to transmit data signals in computer networks.

They come in categories like Cat5e (basic Ethernet), Cat6 (higher speeds and less
crosstalk), or Cat6a (supports faster and longer-distance transmissions).
 Purpose: Provides a physical medium for data transmission between devices.
 2) RJ45 Connectors:

 Definition: Standardized connectors used at the ends of Ethernet cables. They feature
8 pins that correspond to the 8 wires in the cable.
 Purpose: Enables the connection of Ethernet cables to networking devices like
switches, routers, or computers.

3) Crimping Tool:

 Definition: A handheld tool designed to attach RJ45 connectors securely to Ethernet

cables by pressing the pins into the wires.
 Purpose: Ensures proper electrical contact between the cable wires and the connector
pins.

4) Cable Stripper/Cutter:

 Definition: A small tool used to strip the outer insulation of Ethernet cables without
damaging the internal wires.
 Purpose: Prepares cables for connecting RJ45 connectors by exposing the internal
wires for proper arrangement.

5) Cable Tester:

 Definition: A device used to check the functionality of Ethernet cables by testing for
continuity, proper wiring, and connection.
 Purpose: Verifies that the cable is working correctly and identifies any faults like
mis-wiring or broken connections.

 Methodology:

 Steps for Straight-Through Cable Construction:

1. Strip the Cable Jacket:

o Use a cable stripper to remove about 1–2 inches of the outer insulation
from both ends of the Ethernet cable. Take care not to damage the internal
wires.

2. Untwist and Arrange the Wires:

o Separate the twisted pairs and untwist each pair. Arrange the individual
wires according to either the T568A or T568B wiring standard (the same
standard on both ends).
o T568B Color Order:
1. Orange/White
2. Orange
 3. Green/White
4. Blue
5. Blue/White
6. Green
7. Brown/White
8. Brown

3. Trim the Wires:

o Cut the wires evenly using a cable cutter, leaving about 0.5 inches exposed
beyond the jacket.

4. Insert the Wires into the RJ45 Connector:

o Slide the arranged wires into the RJ45 connector, ensuring each wire is in
the correct slot and the cable jacket is firmly inside the connector.

5. Crimp the Connector:

o Place the connector into the crimping tool and press firmly to secure the
wires and lock the pins.

6. Repeat for the Other End:

o Perform the same steps on the other end, ensuring the wiring matches the
chosen standard (T568A or T568B).

 Steps for Crossover Cable Construction:

1. Understand the Wiring Difference:

o A crossover cable has T568A wiring on one end and T568B on the other.
o T568A Color Order:
1. Green/White
2. Green
3. Orange/White
4. Blue
5. Blue/White
6. Orange
7. Brown/White
8. Brown

2. Strip the Cable Jacket:

o Remove the outer insulation from both ends of the Ethernet cable using a
cable stripper.

3. Untwist and Arrange the Wires:

o Untwist and arrange the wires following T568A on one end and T568B on
the other.
 4. Trim the Wires:
o Cut the wires evenly and leave about 0.5 inches exposed beyond the cable
jacket.

5. Insert the Wires into the RJ45 Connector:

o Insert the wires into the RJ45 connector for each end, ensuring proper
alignment with their respective standards.

6. Crimp the Connector:

o Securely crimp the connectors on both ends using a crimping tool.

7. Test the Cable:

o Use a cable tester to verify continuity and proper wiring for both straight-
through and crossover cables.

 Figures:
 Observations and Results:

 Observation:

1. Testing Process:
o Continuity Test: The constructed cables were tested using a cable tester.
Both ends of the cable were connected to the tester, which checked each wire
for proper continuity and alignment.
o The LEDs on the tester indicated whether the wiring was correctly aligned
according to the chosen standard (T568A or T568B).

2. Challenges Encountered:
o Improper Crimping: Some RJ45 connectors were not securely crimped,
leading to loose wires and intermittent connections.
 Resolution: Re-crimped the connectors using consistent pressure with
the crimping tool.
o Misalignment of Wires: In a few attempts, the wires were not arranged in the
correct order before insertion into the connector.
 Resolution: Carefully rearranged the wires according to the wiring
standard and trimmed them evenly before reinserting into the
connector.
o Wire Damage: Excessive force during stripping caused slight nicks in the
internal wires.
 Resolution: Used a cable stripper more carefully to avoid damaging
the wires.

 Result

 After resolving the challenges, the cables were tested again, and all wires showed
correct continuity and functionality.
 Both straight-through and crossover cables were fully functional and able to
establish proper network connections between devices.

 Discussion:

 Comparison of Straight-Through and Crossover Cable Construction:

 Straight-Through Cable:
o Both ends follow the same wiring standard, either T568A or T568B.
o Simpler to construct as there is no need to alternate wiring standards.
 o Used primarily to connect dissimilar devices (e.g., PC to switch, router to
switch).

 Crossover Cable:
o One end follows T568A, and the other follows T568B.
o Requires attention to ensure the correct wiring standard is used on each end.
o Used to connect similar devices (e.g., PC to PC, switch to switch).

 Significance of Using the Correct Cable Type:

 Straight-Through Cable: Essential for connecting devices that require different

communication roles, such as a computer (end device) to a switch (network device).
It ensures proper signal transmission by aligning the transmit (Tx) and receive (Rx)
pins.
 Crossover Cable: Necessary for direct communication between devices with similar
roles (e.g., PC to PC) where transmit pins on one device must connect to receive pins
on the other.

Using the wrong cable type in a scenario may result in no connection or communication
errors. However, many modern devices support auto-MDI/MDIX, which automatically
adjusts for cable type.

 Reflection and Learning:

 This practical provided hands-on experience in constructing and testing Ethernet

cables, reinforcing the importance of proper wire arrangement, crimping, and testing.
 Key takeaways:
o Attention to detail is critical during wire arrangement to prevent errors like
misalignment.
o Tools like crimpers and cable testers are indispensable for achieving
functionality.
o Understanding the differences between cable types enhances the ability to
troubleshoot and deploy networks effectively.
 Overall, the practical highlighted the foundational role of network cabling in
ensuring reliable communication in computer networks.
 Conclusion:

The practical provided valuable insights into the construction and testing of straight-
through and crossover Ethernet cables, emphasizing their specific use cases in
networking. Key takeaways include:

 Understanding the differences between T568A and T568B wiring standards.

 Proper use of tools such as crimping tools, cable testers, and cable strippers.
 The critical role of straight-through cables for connecting dissimilar devices and
crossover cables for connecting similar devices.

Attention to detail emerged as a fundamental aspect of cable construction. Precise wire

arrangement, correct crimping, and thorough testing are essential to ensure proper
functionality and avoid network connectivity issues. This practical not only enhanced
technical skills but also highlighted the importance of accuracy in creating reliable
network infrastructure.
Practical-2
Setup of Cisco Packet Tracer:

 Introduction:
Cisco Packet Tracer is a powerful network simulation tool developed by Cisco Systems.
It provides a virtual environment to design, configure, and simulate network topologies
without the need for physical hardware. The tool supports a wide range of networking
devices and protocols, making it ideal for learning and practicing network configuration,
troubleshooting, and design.

Importance of Using Simulation Tools Like Cisco Packet Tracer:

 Cost-Effective Learning: Allows students and professionals to practice
networking concepts without expensive hardware.
 Hands-On Experience: Offers a safe environment to experiment with
configurations, protocols, and troubleshooting techniques.
 Scenario Simulation: Enables testing of real-world network setups and complex
scenarios, enhancing problem-solving skills.
 Preparation for Certification: Supports the learning objectives of certifications
like CCNA, providing practical experience with Cisco devices and networks.
 Error Analysis: Offers instant feedback on configurations, helping users identify
and correct mistakes efficiently.
 Cisco Packet Tracer serves as an invaluable tool for understanding and mastering
computer networking concepts in a practical, interactive manner.

 Download:

1. Visit the Official Website:

o Open your browser and go to the Cisco Networking Academy website:
https://www.netacad.com.

2. Create or Log In to a Cisco Account:

o If you don’t already have a Cisco account, click on Sign Up and fill in the
necessary details to create one.
o If you already have an account, log in using your credentials.
 3. Navigate to the Resources Section:
o Once logged in, go to the Resources section or look for "Packet Tracer" in the
navigation menu.

4. Locate the Download Page:

o Find the Cisco Packet Tracer download page under resources or tools.

5. Choose the Appropriate Version:

o Select the version compatible with your operating system:
 Windows: Typically a .exe file.
 macOS: A .dmg file for installation.
 Linux: A .deb or .tar.gz file, depending on your distribution.

6. Download and Install:

o Click on the download link and save the file to your device.
o Follow the installation instructions specific to your operating system to complete
the setup.

By downloading Cisco Packet Tracer, you gain access to a versatile tool for network
simulation, which is invaluable for learning and practicing networking concepts.

 Setting Up an Account:

1. Go to the Cisco Website:

o Open your browser and visit the official Cisco Networking Academy website:
https://www.netacad.com.

2. Click on "Sign Up":

o On the homepage, look for the Sign Up option and click on it to start the account
registration process.

3. Fill Out the Registration Form:

o Complete the registration form by providing the required details such as:
 Full Name
 Email Address
 Password (Create a strong password that meets the criteria)
 Country/Region
 Date of Birth (if needed)
o Agree to the terms and conditions, and privacy policy if prompted.

4. Confirm Your Email Address:

o After submitting the registration form, you will receive a confirmation email from
Cisco Networking Academy.
 o Check your inbox (and spam folder, if necessary) for an email with a verification
link.
o Click the link to verify your email address and activate your account.

5. Log In to Your Cisco Account:

o Once your email is confirmed, return to the Cisco Networking Academy website.
o Click on Login and enter your newly created account credentials (email and
password).

6. Access Downloads and Resources:

o After logging in, you can now access a variety of networking resources, including
Cisco Packet Tracer, courses, and other tools available under the "Resources"
section.

By setting up an account, you gain access to valuable learning materials, networking simulations,
and hands-on tools that are essential for advancing your knowledge in computer networking.

 Installation Process:

1. Locate the Installation File:

o After the download is complete, go to your Downloads folder (or the folder
where your browser saves downloaded files).
o Find the installation file, which should be named something like
PacketTracer_.exe for Windows, PacketTracer_.dmg for macOS, or
PacketTracer_.deb/.tar.gz for Linux.

2. Run the Installer:

o Double-click the installation file to start the setup process. Depending on your
operating system, you might see a security prompt asking if you want to allow the
file to make changes to your device. Click Yes or Open to proceed.

3. Follow the Installation Prompts:

o Accept the Terms and Conditions: The installer will present the terms of use for
Cisco Packet Tracer. Read the terms and check the box indicating that you accept
them before continuing.
o Choose the Installation Directory: The installer will ask you where you want to
install the software. The default directory (usually C:\Program Files\Cisco
Packet Tracer on Windows) is recommended. If you prefer a different location,
select the directory of your choice.
o Wait for the Installation to Complete: The installer will copy the necessary files
to your computer. This process may take a few minutes.
4. Launch Cisco Packet Tracer:
o Once the installation is complete, the installer may offer an option to launch Cisco
Packet Tracer immediately. If not, you can find it in your Start Menu
(Windows) or Applications folder (macOS) and click to open it.

5. Log In Using Your Cisco Networking Academy Account:

o When Packet Tracer opens, you will be prompted to log in. Enter the email and
password you used to sign up for your Cisco Networking Academy account.
o After logging in, the software will be activated and ready for use.
o Demo given below:

Fig: Login Interface

 Fig: Logged-in Interface

Now that Cisco Packet Tracer is installed and activated, you can start using it to design and
simulate network configurations, practice networking protocols, and improve your network
troubleshooting skills.

 Conclusion:
The installation of Cisco Packet Tracer was successfully completed. The process involved
downloading the software, following the installation steps, and activating it using a Cisco
Networking Academy account. The setup ensures access to a fully functional network
simulation environment, enabling hands-on practice in designing, configuring, and
troubleshooting network topologies.

This installation marks the first step toward leveraging Cisco Packet Tracer as a powerful tool
for learning and practicing networking concepts, enhancing technical skills, and preparing for
real-world network.
Practical-3
Setup P2P and Client Server Network and verifying it, using Cisco
Packet Tracer:

 Introduction:

In computer networking, the Peer-to-Peer (P2P) and Client-Server models represent

two distinct approaches to organizing and managing networks. Each model has unique
characteristics, use cases, and advantages.

1) Peer-to-Peer (P2P) Networks:

 Definition: A decentralized network model where all devices (peers) are equal
and share resources directly without a central server.
 Key Characteristics:
o No dedicated server; each device acts as both a client and server.
o Simple to set up, cost-effective for small networks.
o Limited scalability and security.
 Example Use Case: File sharing between two PCs.

2) Client-Server Networks:

 Definition: A centralized network model where client devices request services,

and a central server provides those services.
 Key Characteristics:
o Centralized management with a dedicated server.
o Scalable, with better performance and security for larger networks.
o More complex and costly to implement.
 Example Use Case: A corporate network where employees access shared files or
applications hosted on a server.

 Objectives of the Practical:

1. Set up a Peer-to-Peer Network:

o Establish a direct connection between devices and share resources such as
files or printers.

2. Set up a Client-Server Network:

o Configure a server to provide services (e.g., file sharing) to multiple client
devices.
 3. Verify Connectivity:
o Test the functionality of both network setups using tools like ping
commands or shared resource access.

This practical aims to provide hands-on experience with configuring and understanding
the fundamental differences between Peer-to-Peer and Client-Server networks, laying the
foundation for real-world network management.

 Materials and Software:

1. Cisco Packet Tracer Software:

 Purpose: A simulation tool used to design, configure, and test network setups
virtually.
 Features:
o Enables creating and testing both Peer-to-Peer (P2P) and Client-Server
networks.
o Provides devices like PCs, servers, and networking equipment for
configuration.
o Helps visualize and troubleshoot network connectivity issues.

2. Basic Knowledge of IP Addressing:

 IP Address:
o A unique numerical identifier assigned to devices in a network to enable
communication.
o IPv4 is used for this practical. It consists of 32 bits divided into four octets
(e.g., 192.168.1.1).
o Divided into two parts: Network ID (identifies the network) and Host ID
(identifies the device).
 Why IPv4?
o IPv4 is widely used in small-scale networks and is sufficient for the scope of
this practical.
o It uses Private IP Ranges (e.g., 192.168.x.x, 10.x.x.x) for internal
communication.

These tools and resources will allow you to simulate, configure, and test network
connectivity efficiently, helping you gain practical insights into network design and
management.
 Methodology:

 Peer-to-Peer (P2P) Network Setup:

 Step 1: Create the Topology

o Open Cisco Packet Tracer and add two PCs to the workspace.
o Connect the PCs using a crossover cable (represented as a copper straight-
through in modern switches if auto-MDIX is enabled).

 Step 2: Configure IP Addresses

o Access each PC's configuration:
1. Click on PC1 → Go to the Desktop tab → Select IP Configuration.
 Set IP Address: 192.168.1.1
 Set Subnet Mask: 255.255.255.0
2. Repeat for PC2 with:
 IP Address: 192.168.1.2
 Subnet Mask: 255.255.255.0

 Step 3: Verify Connectivity

o Open the Command Prompt on PC1 (Desktop tab → Command Prompt).
o Run the ping command:
o ping 192.168.1.2
o Observe the reply messages to confirm successful communication.

 Client-Server Network Setup:

 Step 1: Create the Topology

o Add one PC (Client) and one Server in the workspace.
o Connect the PC and Server using a straight-through cable via a switch.

 Step 2: Assign Static IP Addresses

o Configure the Server:
1. Select the Server → Go to the Desktop tab → IP Configuration.
 IP Address: 192.168.1.100
 Subnet Mask: 255.255.255.0
o Configure the Client:
1. Select the PC → Go to the Desktop tab → IP Configuration.
 IP Address: 192.168.1.10
 Subnet Mask: 255.255.255.0

 Step 3: Configure Server Services

o Click on the Server → Go to the Services tab → Enable a basic service (e.g.,
HTTP or FTP).
 Step 4: Verify Connectivity
o Use the ping command from the Client to test the Server's IP address (e.g., ping
192.168.1.100).
o To test server services (e.g., HTTP), open a web browser on the PC, type the
server's IP (e.g., http://192.168.1.100), and check if the service is accessible.

 Figures:

 P2P Connection: Demonstrates direct device communication without intermediaries,

useful for small networks.

Fig: P2P Connection

Fig: Verifying Connectivity of P2P
 Client-Server Connection: Highlights centralized resource management, critical for
scalable and secure network designs.

Fig: Client-Server Connection Interface

 Fig: Verifying Connectivity of Client-Server

This methodology ensures proper configuration and testing of both P2P and Client-Server
networks, offering practical insights into real-world networking scenarios.

 Observations and Results:

 Observation:

 A Peer-to-Peer (P2P) and Client-Server network was set up in Cisco Packet Tracer
using necessary devices (PCs, Switches, Routers, and Servers).
 IP addresses were assigned manually for P2P and dynamically via DHCP for the
Client-Server network.
 Devices were connected using appropriate cables (crossover or straight-through,
depending on the scenario).
 The ping command was used to verify connectivity between devices.
 In P2P, each device communicated directly using assigned IPs.
 In Client-Server, the server assigned IP addresses dynamically, and clients accessed
server resources.
  Result:

 P2P Network: Successful ping responses verified that devices directly communicated
using assigned IPs.

 Client-Server Network:
o Clients successfully obtained IP addresses from the DHCP server.
o Ping responses between clients and servers confirmed proper configuration.
o Resources from the server (e.g., website or file sharing) were accessible by the
clients.

 Discussion:

 Differences Observed Between P2P and Client-Server Networks:

1. Structure and Communication:

o P2P: Devices communicated directly without a central authority. Each device
acted as both client and server.
o Client-Server: A centralized server provided services or resources to multiple
clients.

2. IP Configuration:
o P2P: Static IP configuration was required for devices to communicate.
o Client-Server: The server assigned IPs dynamically using the DHCP service.

3. Scalability and Complexity:

o P2P: Suitable for small networks but becomes inefficient with an increase in
devices.
o Client-Server: Easily scalable, handling a larger number of clients
effectively.

4. Resource Sharing:
o P2P: Limited to local file sharing between devices.
o Client-Server: Centralized resources like databases, web services, and
applications are accessible.

 Applications in Real-World Scenarios:

1. P2P Networks:
o Small office or home networks for file sharing (e.g., LAN gaming).
o File-sharing platforms (e.g., BitTorrent).
 2. Client-Server Networks:
o Corporate offices for central resource management (e.g., database servers,
email servers).
o Web hosting and online services (e.g., websites, cloud storage).

By analyzing the results, it's evident(obvious) that P2P is more suitable for small, informal
setups, whereas Client-Server networks are ideal for structured and scalable environments
requiring centralized control and management.

 Conclusion:

From this practical, the following conclusions were drawn:

1. P2P Network:
o Simple and cost-effective for small-scale networks.
o Devices can communicate directly but require manual configuration and are
less scalable.
o Suitable for limited resource sharing in small groups or localized
environments.

2. Client-Server Network:
o Offers centralized management, dynamic IP assignment, and better scalability.
o Efficient for large networks with multiple devices requiring centralized
resources and services.
o Ideal for environments such as businesses, organizations, and web-based
applications.

Overall, understanding both network types is crucial for designing and implementing
appropriate networking solutions based on specific requirements.
Practical-4
Observing IP address and MAC address using commands in
command prompt, setting IP address and default gateway in PC,
using Cisco Packet Tracer:

 Introduction:

Networking plays a vital role in the seamless communication between devices in a network.
The IP address and MAC address are two critical components that facilitate this
communication. An IP address is used to identify a device on a network, while the MAC
address, a unique identifier assigned to network interfaces, ensures data is sent to the correct
device within a local network. In this practical, we will use basic networking commands in
the Command Prompt to observe and analyze the IP and MAC addresses of a PC.
Additionally, we will practice setting static IP addresses and configuring the default gateway
to enable proper communication within a network. The practical will be carried out using
Cisco Packet Tracer, a powerful network simulation tool that allows us to design and
troubleshoot network environments, providing an interactive platform for learning network
configuration.

 Objectives of the practical:

1. Observe and Verify IP and MAC Addresses:

o Use Command Prompt commands (such as ipconfig and getmac) to display
and examine the IP address and MAC address of a PC.
o Understand the purpose of both addresses in network communication: the IP
address for routing data across networks and the MAC address for local
device identification.

2. Set Static IP Address:

o Learn how to configure a static IP address on a PC through both the
Command Prompt and the network settings menu.
o Understand the importance of static IP addressing in scenarios where fixed
device addresses are required (e.g., for servers or network printers).

3. Configure Default Gateway:

o Set a default gateway on a PC to allow communication between different
networks.
o Understand the role of the default gateway in routing traffic to external
networks, such as the internet.
 4. Network Simulation using Cisco Packet Tracer:
o Use Cisco Packet Tracer to design and simulate a small network setup,
including the configuration of IP addresses and default gateways.
o Learn to configure routers, switches, and PCs in Packet Tracer, ensuring that
devices can communicate with one another based on the configurations
applied.

5. Troubleshooting and Connectivity Check:

o Verify network connectivity using commands like ping and tracert to test
communication between devices.
o Troubleshoot any connectivity issues related to incorrect IP address or
gateway configurations.

This practical will help deepen your understanding of networking fundamentals and prepare
you for real-world network configuration tasks.

 Materials and Software:

 Materials:

o A computer or laptop with access to a network connection.

o Network cables and devices (e.g., switches, routers) if working with physical
hardware, or network simulation devices in Cisco Packet Tracer.

 Software:

o Command Prompt (Windows): This built-in utility allows users to execute

network-related commands such as ipconfig and getmac to observe IP and
MAC addresses.

o Cisco Packet Tracer: A network simulation tool that allows users to create
virtual network setups. It provides a platform for configuring network devices
like routers, switches, and computers, and simulating the process of setting IP
addresses and default gateways. In this practical, Cisco Packet Tracer will be
used to simulate a network environment for hands-on experience in
configuring IP addresses and gateways.

 Key Features:

o ipconfig command: Used to view the IP configuration of a computer,

including the IP address, subnet mask, and default gateway.
 o getmac command: Displays the MAC address of the computer's network
adapter.

o Cisco Packet Tracer: Used to configure and observe network settings in a

virtual environment, allowing the setting of IP addresses, default gateways,
and testing network connectivity.

These materials and tools provide a comprehensive setup for observing and configuring network
settings, allowing students to practice both command-line operations and network configuration
in a simulated environment.

 Methodology:

 Steps involved in it:

Step 1: Observing IP and MAC Address on a PC Using Command Prompt

 Open Command Prompt on the PC (Press Win + R, type cmd, and press Enter).
 Type the command ipconfig /all to display detailed network configuration
information.

o Result: The command will show the IP address, subnet mask, default
gateway, and MAC address of the network interface.

Step 2: Setting IP Address and Default Gateway in the PC's Network

Configuration

 Go to the "Desktop" tab in Cisco Packet Tracer.

 Click on "IP Configuration."
 Assign a static IP address by filling in the IP Address, Subnet Mask, and Default
Gateway fields.

o Example:
 IP Address: 192.168.1.10
 Subnet Mask: 255.255.255.0
 Default Gateway: 192.168.1.1

 Click "Save" to apply the settings.

Step 3: Observing the Changes in the Network

 Use the ipconfig command again in the Command Prompt to verify that the
changes have been applied successfully.
  Ensure that the IP address, subnet mask, and default gateway match the
configuration set in Cisco Packet Tracer.

Step 4: Configuring IP and MAC Address in Cisco Packet Tracer

 In Cisco Packet Tracer, place a PC, Router, and Switch.

 Connect the PC to the Switch, and connect the Switch to the Router using
appropriate cables.
 Set up the IP configuration on the router's interface and ensure it matches the
gateway set on the PC.

o Example: Router Interface IP: 192.168.1.1 (Gateway for the PC).

Step 5: Testing Network Connectivity

 After completing the configuration, test the network connectivity.

 Open the Command Prompt on the PC and type the command ping 192.168.1.1
(Router's IP address).
 If the network is correctly set up, the PC will successfully ping the router,
confirming connectivity.

 Figures:
Fig: Observing IP and MAC Address

Fig: Setup Interface

 Fig: Verifying Connectivity with Router

 Observations and Results:

 Observing IP and MAC Address on a PC:

o After executing the ipconfig /all command in the Command Prompt, the
following details were observed:

 IP Address: The IP address assigned to the network interface was

displayed, confirming the device’s network configuration.
 Subnet Mask: The subnet mask (255.255.255.0) was displayed,
indicating the size of the network.
 Default Gateway: The gateway IP address (e.g., 192.168.1.1) was
displayed, which facilitates communication with devices outside the
local network.
 MAC Address: The MAC address was shown for the network adapter,
confirming the hardware address used for local network
communication.

 Setting IP Address and Default Gateway on the PC:

o The static IP address (e.g., 192.168.1.10) and default gateway (e.g.,
192.168.1.1) were successfully configured on the PC using the "IP
Configuration" window in Cisco Packet Tracer.
 o The changes were reflected immediately, and the configuration appeared in the
Command Prompt when the ipconfig command was executed again.

 Testing Network Connectivity:

o After setting the IP address and default gateway, a successful ping test was
conducted between the PC and the router using the command ping 192.168.1.1.
o The ping test results showed successful replies, confirming that the PC could
communicate with the router and, by extension, other devices in the network.

 General Observations:
o The process of configuring IP addresses and gateways on the PC was
straightforward and was effectively simulated in Cisco Packet Tracer.
o The ipconfig /all command provided a clear display of the network
configuration, including the MAC and IP addresses.
o The PC was able to communicate with the router successfully, which indicates
that the network settings were configured correctly and that the devices were
properly connected in the network topology.

 Results:
o The assignment of static IP addresses and default gateways was successful.
o The ping test confirmed proper connectivity between the PC and the router.
o All network configurations were verified through both the Cisco Packet Tracer
interface and the Command Prompt, showing consistency and accuracy in the
results.

 Discussion:

In this practical, we explored fundamental networking tasks such as observing IP and MAC
addresses, setting static IP addresses and default gateways, and testing network connectivity
using Cisco Packet Tracer and Command Prompt. The practical provided a hands-on
understanding of network configurations, which are essential for managing real-world
networks.

1. IP and MAC Address Observations:

o The use of the ipconfig /all command was crucial in revealing the IP address,
subnet mask, default gateway, and MAC address of the network adapter. This
highlighted the importance of the IP address in identifying devices on a
network and the MAC address in enabling communication at the data link
layer.
o Understanding both the IP address (logical addressing) and MAC address
(physical addressing) is important for troubleshooting network issues, as each
serves a different function in communication. While the IP address is used for
routing traffic across networks, the MAC address is essential for local network
communication.
 2. Setting Static IP Address and Default Gateway:
o Configuring a static IP address on the PC and setting the default gateway were
important steps in creating a functional network. The static IP ensures that the
device has a fixed address in the network, which is crucial for servers or
devices that need to maintain a consistent identity.
o The default gateway serves as the exit point for traffic that needs to go beyond
the local network. By setting the correct gateway, the PC was able to
communicate with devices on other networks, as confirmed by the successful
ping test.

3. Network Connectivity Testing:

o The successful ping test demonstrated the importance of proper network
configuration. When the IP address, subnet mask, and gateway were set
correctly, the network connection was established without issues.
o If the IP configuration or default gateway had been incorrect, the ping test
would have failed, which would help identify configuration issues. This
emphasizes the need for careful network setup and the role of diagnostic tools
like ping and ipconfig in troubleshooting.

4. Cisco Packet Tracer Simulation:

o Cisco Packet Tracer proved to be a powerful tool for simulating network
setups and visualizing the connections between devices. It allowed for the
configuration of both network devices (like routers and switches) and end
devices (like PCs) in a controlled environment.
o While the practical demonstrated basic networking concepts, Cisco Packet
Tracer can be used to create more complex networks with multiple devices,
protocols, and routing configurations, providing a deeper understanding of
network design and troubleshooting.

5. Real-World Relevance:
o The skills learned in this practical are directly applicable to real-world
networking scenarios. Setting static IPs and default gateways, along with
understanding how to observe and troubleshoot network configurations, are
essential skills for network administrators.
o The ability to identify and address issues related to IP addressing and network
connectivity is fundamental to maintaining functional networks in both home
and enterprise environments.

 Conclusion:

This practical reinforced key networking concepts, such as IP configuration, the role of MAC
addresses, and network connectivity troubleshooting. It also highlighted the importance of
tools like ipconfig and ping for managing and diagnosing network configurations.
Understanding these basics is foundational for anyone pursuing a career in networking or IT.
Practical-5
Configuration of network using HUB and observing the working of
HUB, Using Cisco Packet Tracer:

 Introduction:

In this practical, we will configure a simple network using a HUB and observe its
working behavior. A HUB, operating at the physical layer (Layer 1) of the OSI model,
connects multiple devices in a LAN and broadcasts data packets to all connected devices,
unlike switches or routers which direct data to specific destinations. This basic
functionality helps in understanding fundamental networking concepts like data
transmission and topologies.

Using Cisco Packet Tracer, we will design and simulate the network, focusing on
configuring the HUB and analyzing data flow. This practical provides insights into
network interactions and highlights the limitations of HUBs in modern networking.

 Objectives of the practical:

1. To understand the working of a HUB: Learn how a HUB facilitates communication

between devices by transmitting data to all connected nodes within the network.

2. To configure a network using a HUB: Set up a basic network infrastructure with

multiple devices connected to a HUB in Cisco Packet Tracer.

3. To observe data transmission in a HUB-based network: Monitor and analyze how

the HUB broadcasts data to all connected devices, and understand how each device
reacts to incoming data packets.

4. To compare the functionality of a HUB with other devices: Gain insights into the
limitations of a HUB in terms of bandwidth sharing, data collisions, and network
efficiency compared to switches or routers.

5. To explore network traffic behavior in a HUB-based network: Investigate how

data is transmitted in a shared medium, and identify challenges like network
congestion and security concerns in such a setup.

6. To understand network topologies and design: Learn about the basic topologies
(like star topology) used with HUBs and how network design impacts performance.

This practical will help students grasp fundamental networking concepts while also providing
hands-on experience with networking tools and the dynamics of data flow in a basic LAN
setup.
  Materials and Software:

1. Hardware:
o Computers or Laptops: Required for running the network simulation software.
These devices must meet the minimum system requirements for Cisco Packet
Tracer to ensure smooth operation.
o Ethernet cables (virtual): These are used within Cisco Packet Tracer to
establish connections between network devices such as the HUB and end devices
(PCs).

2. Software:
o Cisco Packet Tracer: A powerful network simulation tool developed by Cisco,
used to design and simulate network topologies. It allows users to virtually
configure network devices, observe their behavior, and analyze data transmission
within a controlled environment. In this practical, Cisco Packet Tracer will be
used to simulate the entire network setup, including the configuration of the
HUB and other network devices.

3. Network Devices (within Packet Tracer):

o HUB: A networking device used to connect multiple devices in a local area
network (LAN). It operates at the physical layer (Layer 1) of the OSI model and
broadcasts data to all connected devices, regardless of the intended recipient.
o PCs or Laptops: End-user devices used for testing the network configuration
and observing how data packets are transmitted across the HUB. These devices
will be configured with IP addresses and connected to the HUB for
communication.
o Ethernet Cables: Virtual cables used in Cisco Packet Tracer to establish
physical connections between network devices. These cables allow for
communication between the HUB and the PCs.

These materials and software tools will provide the foundation for simulating a simple network
using a HUB, configuring the devices, and analyzing data flow and network behavior in a
virtual environment.

 Methodology:

1. Network Design and Setup:

o Launch Cisco Packet Tracer and create a new project.
o From the Device Type Selection Box, choose the HUB and drag it into the
workspace.
o Select PCs or Laptops from the device selection area and place them in the
workspace. Ensure at least three devices are connected to the HUB to observe
data transmission behavior.
 o Use Ethernet cables to connect each PC to the HUB. Ensure the correct
connections are made (i.e., the straight-through cables are used to connect
devices to the HUB).

2. IP Configuration:
o Configure each PC with a unique IP address and subnet mask. This step
ensures that devices can communicate with one another through the network.
o Set the Default Gateway to the IP address of the HUB (if required for future
exercises or expanded network configurations).

3. Verifying Connections:
o Use the Simulation Mode in Cisco Packet Tracer to visualize the flow of data
packets between devices.
o Select the PC from which you want to send data and initiate a ping command
to another connected PC. This will test the basic connectivity and allow
observation of data packet transmission through the HUB.
o Check if the data packets are broadcasted to all devices connected to the HUB,
regardless of the recipient, as expected in a HUB-based network.

4. Observing Data Transmission:

o While the ping command is running, observe the behavior of the HUB. It
should broadcast the data to all connected devices (including PCs that are not
the intended recipient).
o Monitor the Simulation Panel to view the packet details, including source,
destination, and data transmission.

5. Troubleshooting and Analysis:

o If any PC does not receive data or the ping fails, troubleshoot by verifying IP
address configurations, network connections, and cable types.
o Analyze the network traffic to understand how the HUB handles data.
Observe any collisions or delays in packet delivery that may occur due to the
shared bandwidth nature of a HUB.

By following this methodology, students will be able to configure and test a simple network
using a HUB, analyze its data transmission process, and gain practical insights into basic
networking concepts.
 Figures:

Fig: Hub Connection Interface

 Fig: Verifying Connectivity

 Observations and Results:

 Observations:
1.Network Configuration:
o The HUB was successfully configured and connected to multiple PCs using
Ethernet cables in Cisco Packet Tracer.
o Each PC was assigned a unique IP address and subnet mask, ensuring
proper network communication.

2.Data Transmission via HUB:

o Upon initiating the ping command between connected PCs, it was observed
that the HUB broadcasted the data packets to all connected devices, not just
the intended recipient.
o Even though only one PC was the target of the ping request, all other PCs in
the network received the packet, which is characteristic of a HUB's
behavior at the physical layer.

3.Impact of Broadcasting:
o The broadcasted data was sent to all devices connected to the HUB. Non-
target PCs processed the packet but did not respond, as they recognized the
data was not addressed to them.
o Network collisions were observed in the simulation when multiple PCs sent
data packets at the same time. This led to delays and retransmissions,
 highlighting one of the key limitations of using a HUB—lack of intelligent
data forwarding.

4.Simulating Network Traffic:

o In the Simulation Mode, the Simulation Panel showed details of the data
packets being transmitted, including source, destination, and protocol used.
o The data was correctly transmitted across the network, and the ping
command results confirmed the successful communication between all
connected devices.

5.Limitations of HUB:
o Bandwidth Sharing: All devices connected to the HUB share the same
bandwidth. When one PC sends data, others experience delays due to the
shared medium.
o Collisions: As multiple devices send data at the same time, collisions
occurred, leading to retransmission of data packets. This inefficiency
becomes more evident with an increased number of connected devices.
o Lack of Security: Since data is broadcasted to all devices, any device on the
network can capture the data meant for others, posing security risks.

6.Comparison to Switch/Router:
o Unlike a switch or router, which intelligently forward data packets only to
the intended destination, the HUB broadcasts the packets to all devices. This
makes the HUB less efficient and prone to network congestion and security
vulnerabilities.

 Results:

 The practical confirmed that the HUB functions by broadcasting data packets to
all devices, resulting in network inefficiencies and potential security issues.
 Observations showed that as the number of devices increased, the chances of
collisions and network delays also increased, reinforcing the limitations of using a
HUB in larger, modern networks.
 The comparison with more advanced devices like switches and routers
highlighted the need for more intelligent data forwarding mechanisms in
contemporary networks.
 Discussion:

This practical demonstrated the behavior of a HUB in a simple network configuration. The
HUB, which operates at the physical layer of the OSI model, broadcasts data packets to all
connected devices. This results in several key observations:

1. Broadcasting and Data Transmission:

o The HUB’s broadcasting mechanism sends data to all devices, regardless of
the destination. This leads to unnecessary network traffic, as devices not
intended to receive the data still process it. This inefficiency becomes more
apparent in larger networks with many devices.

2. Collisions and Bandwidth Sharing:

o The HUB operates as a shared medium where all devices compete for
bandwidth. When multiple devices send data simultaneously, collisions occur,
resulting in delays and the need for retransmissions. This significantly reduces
network efficiency, especially as the number of devices increases.

3. Security Issues:
o A major limitation of the HUB is its lack of security. Since it broadcasts data
to all connected devices, any device on the network can intercept and read
packets, making the network vulnerable to unauthorized access. This is a
significant issue compared to switches and routers, which forward data only to
the intended recipient.

4. Comparison to Switches/Routers:
o Unlike the HUB, switches intelligently forward data to the correct destination,
minimizing collisions and improving network efficiency. Routers provide
even more advanced capabilities, managing traffic between different
networks. The practical highlighted why HUBs are largely outdated in modern
networking.

 Conclusion:

The practical illustrated the limitations of HUBs, particularly in terms of network congestion,
collisions, and security risks. While HUBs are useful for basic networking education, they
are not suitable for larger or more security-conscious networks, where switches and routers
offer better performance and security.
Practical-6

Configuration of network using Switch and observing the

working of Switch, Using Cisco Packet Tracer:

 Introduction:

In this practical, we will configure a network using a Switch and observe its working
behavior. A Switch operates at the Data Link Layer (Layer 2) of the OSI model and is
used to connect multiple devices within a network. Unlike a HUB, which broadcasts data
packets to all connected devices, a Switch intelligently forwards data only to the device
that is the intended recipient. This behavior improves network efficiency, reduces
collisions, and enhances overall performance. Using Cisco Packet Tracer, we will
design and configure a network involving multiple devices connected through a switch.
We will observe the data transmission process and analyze how the switch manages the
flow of data within the network.

 Objectives of the practical:

1) To understand the working of a Switch: Learn how a Switch forwards data

packets only to the intended recipient, improving network efficiency.

2) To configure a network using a Switch: Set up a network in Cisco Packet

Tracer, connecting devices through a Switch and assigning IP addresses to each
device.

3) To observe data transmission in a Switch-based network: Monitor how the

Switch handles data traffic, forwarding packets only to the device with the
matching MAC address.

4) To compare the functionality of a Switch with a HUB: Understand how the

intelligent data forwarding mechanism of a Switch overcomes the limitations of
a HUB, such as collisions and unnecessary broadcast traffic.

5) To analyze network performance: Observe the reduction in collisions and

network congestion when using a Switch compared to a HUB-based setup.

6) To explore advanced networking concepts: Gain insights into the role of a

Switch in more complex network topologies and its advantages in large-scale
networks.
 Materials and Software:

1. Hardware:
o Computers or Laptops: Required to run the Cisco Packet Tracer
software. The devices must meet the minimum system requirements to
ensure smooth performance.
o Ethernet cables (virtual): Used within Cisco Packet Tracer to connect
devices to the Switch.

2. Software:
o Cisco Packet Tracer: A network simulation tool developed by Cisco,
used to design, configure, and visualize network topologies. It allows
users to configure switches, analyze data flow, and simulate real-world
network behavior.

3. Network Devices (within Packet Tracer):

o Switch: A network device operating at Layer 2 (Data Link Layer) of the
OSI model, responsible for intelligently forwarding data packets to the
intended recipient based on the MAC address.
o PCs or Laptops: End-user devices used for testing the network. Each
device will be configured with unique IP addresses for communication.
o Ethernet Cables: Virtual cables used to establish connections between
the PCs and the Switch, facilitating data transmission.

These materials and software components will enable the setup and analysis of a switch-
based network, providing a hands-on understanding of how switches efficiently manage
data flow in a local area network (LAN).

 Methodology:
1. Network Design and Setup:
o Open Cisco Packet Tracer and create a new project.
o From the Device Type Selection Box, drag and place a Switch into the
workspace.
o Add at least three PCs or laptops to the workspace to act as end devices.
o Use Ethernet cables to connect each PC to the switch. Ensure the proper
ports are used (PC: FastEthernet, Switch: any port).

2. IP Address Configuration:
o Click on each PC and open the Desktop tab > IP Configuration.
o Assign a unique IP address and subnet mask to each PC.
o Example:
 PC1: IP - 192.168.2.1, Subnet Mask - 255.255.255.0
  PC2: IP - 192.168.2.2, Subnet Mask - 255.255.255.0
 PC3: IP - 192.168.2.3, Subnet Mask - 255.255.255.0

3. Testing Connectivity:
o Use the ping command from one PC to another to test network
connectivity.
o For example, open the Command Prompt on PC1 and type ping
192.168.1.2 to test communication with PC2.

4. Observation of Switch Behavior:

o Switch to Simulation Mode in Cisco Packet Tracer.
o Send a packet from one PC to another. Observe how the Switch uses the
MAC address table to forward the data packet directly to the intended
recipient, without broadcasting it to all devices.
o View the MAC address table by clicking on the switch, navigating to the
CLI tab, and using the command show mac-address-table.

5. Analyzing Efficiency:
o Test simultaneous communication between multiple PCs and observe that
no collisions occur. The switch ensures efficient packet forwarding.
o Compare the data flow with HUB behavior to highlight the advantages of
the switch.

6. Troubleshooting:
o If connectivity fails, verify the following:
 Proper IP address assignment.
 Correct cable connections.
o Re-test the network after resolving any issues.

By following this methodology, the behavior of the switch in efficiently managing data
transmission can be effectively demonstrated and understood.
 Figures:

Fig: Switch Connection Interface

 Fig: Verifying Connectivity

 Observations and Results:

 Observations:

1. Data Transmission via Switch:

o When a PC sent a packet to another PC, the Switch forwarded the data only to
the intended recipient.
o Unlike a HUB, the switch avoided broadcasting the data to all connected
devices, ensuring efficient and targeted communication.

2. MAC Address Table Creation:

o The Switch dynamically built a MAC address table by learning the MAC
addresses of the connected devices and mapping them to the corresponding
switch ports.
o The MAC address table could be viewed using the show mac-address-table
command in the switch’s CLI.

3. No Collisions Observed:
o When multiple PCs sent data simultaneously, the switch handled the traffic
efficiently without any collisions.
o This behavior confirmed that the switch provides a collision-free
environment, unlike a HUB.
 4. Successful Ping Test:
o All ping commands between the PCs were successful, confirming proper
connectivity and communication within the network.
o The round-trip times were minimal, indicating efficient data transmission.

5. Simulation Observations:
o In Simulation Mode, data packets were observed being forwarded directly to
the destination port, bypassing other devices.
o The simulation validated the switch’s role in directing traffic based on the
MAC address table, preventing unnecessary network congestion.

6. Improved Network Efficiency:

o The network demonstrated higher efficiency compared to a HUB-based setup.
Bandwidth was better utilized as data packets were not unnecessarily
broadcasted.

7. Enhanced Security:
o The switch’s targeted data transmission ensured that only the intended
recipient received the packets. Other devices on the network could not
intercept the data, enhancing security.

 Results:

 The practical confirmed that switches provide efficient, collision-free, and secure
communication within a network by using MAC address-based forwarding.
 The switch’s ability to intelligently manage traffic made it a superior alternative to a
HUB for modern networking environments.
 The use of Cisco Packet Tracer effectively demonstrated the working of a switch,
providing insights into its behavior and advantages.

 Discussion:

This practical demonstrated the configuration and working of a Switch in a network,

highlighting its advantages over a HUB and its role in improving network performance and
security. The key points of discussion are as follows:

1. Efficient Data Forwarding:

o The switch uses a MAC address table to forward data directly to the intended
recipient. This targeted forwarding eliminates unnecessary traffic, unlike a
HUB, which broadcasts data to all devices. This behavior was clearly
observed during the simulation.
 2. Collision-Free Communication:
o Unlike a HUB-based network, the switch prevents data collisions by
managing traffic intelligently. Multiple devices were able to communicate
simultaneously without interfering with each other, ensuring smooth and
efficient communication.

3. Improved Network Performance:

o The absence of unnecessary broadcasts and collisions led to better utilization
of network bandwidth. This was evident in the successful and quick execution
of ping tests, where packets reached their destination efficiently with minimal
delays.

4. Enhanced Security:
o The switch provides better security by ensuring that data packets are
forwarded only to the intended recipient. In contrast, a HUB broadcasts
packets to all devices, making data vulnerable to interception. This
characteristic makes switches more suitable for modern networks where
security is a priority.

5. Dynamic MAC Address Learning:

o The switch dynamically built a MAC address table, mapping the MAC
addresses of devices to specific ports. This feature enables the switch to
handle network traffic efficiently and adapt to changes in the network.

6. Comparison to HUB:
o The practical highlighted the significant advantages of switches over HUBs,
such as:
 No broadcasting of all packets.
 Elimination of collisions.
 Improved bandwidth usage.
 Enhanced data security.

7. Relevance in Modern Networks:

o Switches are essential components of modern LANs due to their ability to
handle multiple devices and high traffic loads efficiently. The practical
emphasized the scalability and reliability of switches compared to HUBs,
which are rarely used in contemporary networking.

 Conclusion:

The experiment successfully demonstrated the superior capabilities of a switch in

managing network traffic. By efficiently forwarding data, preventing collisions, and
ensuring security, switches play a critical role in modern network infrastructures. The
practical reinforced the importance of switches in creating reliable and scalable networks,
making them a fundamental component in both small and large-scale environments.
Practical-7
Configuration of network using Router and observing the
working of DHCP, Using Cisco Packet Tracer:

 Introduction:

This practical focuses on configuring a network using a Router and enabling the Dynamic
Host Configuration Protocol (DHCP) to automatically assign IP addresses to connected
devices. A Router operates at the Network Layer (Layer 3) of the OSI model and is
responsible for directing data packets between different networks. Additionally, the DHCP
protocol simplifies network management by dynamically assigning IP addresses, subnet
masks, gateways, and DNS server addresses to devices within a network.

Using Cisco Packet Tracer, a router is configured to act as a DHCP server, eliminating the
need for manual IP address configuration on end devices. The practical will demonstrate how
DHCP operates, its efficiency in automating IP address allocation, and its role in preventing
IP address conflicts. Observations will highlight how routers function as DHCP servers and
manage network communication effectively.

 Objectives of the practical:

1. To understand the working of a Router: Learn how a Router functions at the

network layer (Layer 3) of the OSI model to direct data packets between different
networks.

2. To configure a network using a Router: Set up a basic network using a Router in

Cisco Packet Tracer, connecting multiple devices across different subnets.

3. To configure and observe DHCP (Dynamic Host Configuration Protocol): Learn

how a Router can be configured to assign IP addresses dynamically to devices within
a network using DHCP.

4. To analyze the DHCP process: Observe the steps involved in the DHCP process,
including IP address assignment, lease duration, and renewal.

5. To compare static and dynamic IP addressing: Understand the advantages of

DHCP over static IP addressing in terms of ease of management and scalability.

6. To troubleshoot and verify network configurations: Use tools like ping and IP
configuration checks to verify DHCP functionality and network connectivity.
 7. To explore network communication between different subnets: Observe how the
Router facilitates communication between devices in different subnets and handles
routing based on IP addresses.

 Materials and Software:

1. Hardware:
o Computer or Laptop: Required to run Cisco Packet Tracer software, with
specifications capable of handling simulation tasks.
o Ethernet Cables (Virtual): Used to establish connections between network
devices in the Cisco Packet Tracer environment.

2. Software:
o Cisco Packet Tracer: A network simulation tool used for designing,
configuring, and analyzing network setups, including DHCP configuration on
a router.
o Operating System: Windows, macOS, or Linux, as supported by Cisco
Packet Tracer.

3. Network Devices (Virtual):

o Router: Configured to function as a DHCP server, assigning IP addresses
dynamically to connected devices.
o Switch: Used to connect multiple end devices (PCs) to the router for efficient
data distribution.
o PCs or Laptops: End-user devices that will receive IP addresses from the
DHCP server during the practical.

4. Additional Tools (within Packet Tracer):

o Command Prompt on PCs: Used to test connectivity and verify IP address
assignment using commands like ipconfig and ping.
o Simulation Mode: Helps observe the DHCP discovery process step-by-step,
including DHCP Discover, Offer, Request, and Acknowledgment messages.

5. Network Addressing Information:

o IP Address Pool: A predefined range of IP addresses to be allocated by the
DHCP server (e.g., 192.168.1.1 – 192.168.1.254).
o Subnet Mask, Default Gateway, and DNS Server Information: Required
for DHCP configuration on the router.
These materials and software will enable the design, configuration, and analysis of a router-
based DHCP-enabled network, providing hands-on experience with automated IP address
management.

 Methodology:

1. Network Setup in Cisco Packet Tracer:

o Open Cisco Packet Tracer and create a new project.
o Drag and place the following devices into the workspace:
 Router (to act as the DHCP server).
 Switch (to connect multiple end devices).
 PCs or Laptops (at least three as client devices).
o Use Ethernet cables to connect:
 Router’s GigabitEthernet 0/0 port to the switch.
 Switch to all PCs using appropriate ports.

2. Configuring the Router as a DHCP Server:

o Click on the router and access the CLI tab.
o Assign an IP address to the router’s GigabitEthernet 0/0 interface:
 Router> enable
 Router# configure terminal
 Router(config)# interface GigabitEthernet 0/0
 Router(config-if)# ip address 192.168.1.1 255.255.255.0
 Router(config-if)# no shutdown
 Exit the interface configuration mode.

3. Enable DHCP on the Router:

o Define the DHCP pool and configure necessary parameters:
 Router(config)# ip dhcp pool LAN
 Router(dhcp-config)# network 192.168.1.0 255.255.255.0
 Router(dhcp-config)# default-router 192.168.1.1
 Router(dhcp-config)# dns-server 8.8.8.8

o Exclude IP addresses reserved for specific devices or purposes (e.g., the

router’s IP):
 Router(config)# ip dhcp excluded-address 192.168.1.1

4. Configuring PCs for DHCP:

o Click on each PC, navigate to Desktop > IP Configuration, and set the IP
configuration to DHCP.
o Observe as the PC requests an IP address from the DHCP server and receives
a valid IP address, subnet mask, default gateway, and DNS server.
 5. Testing Connectivity:
o Use the Command Prompt on each PC to run the ipconfig command and
verify the automatically assigned IP addresses.
o Conduct ping tests between PCs to confirm connectivity.
o Test the router's connection by pinging its IP address (192.168.1.1).

6. Observing the DHCP Process:

o Switch to Simulation Mode in Cisco Packet Tracer.
o Send a DHCP request from one PC and observe the DHCP discovery process:
 DHCP Discover: The PC broadcasts a request for an IP address.
 DHCP Offer: The router responds with an available IP address.
 DHCP Request: The PC requests the offered IP address.
 DHCP Acknowledge: The router confirms the allocation of the IP
address.

7. Troubleshooting (if required):

o Verify that the router’s interface is active (no shutdown).
o Check for proper cable connections and ensure PCs are set to DHCP.

This methodology ensures a complete understanding of how routers enable DHCP in a

network to automate IP address assignment and manage communication effectively.
 Figures:
Fig: Router Connection and DHCP Enable Interface
 Fig: Verifying Connectivity

 Observations and Results:

 Observations:

1. Dynamic IP Address Allocation:

o All connected PCs were successfully assigned IP addresses, subnet
masks, default gateways, and DNS server addresses automatically by
the DHCP server configured on the router.

2. DHCP Discovery Process:

o The DHCP process followed these steps, as observed in Simulation
Mode:
 DHCP Discover: PCs broadcast a request to locate the DHCP
server.
 DHCP Offer: The router responded with an available IP address.
 DHCP Request: PCs requested the offered IP address.
 DHCP Acknowledge: The router confirmed the allocation of the
requested IP address.
 3. Unique IP Addresses Assigned:
o Each device received a unique IP address within the defined pool,
avoiding conflicts. Example:
 PC1: 192.168.1.2
 PC2: 192.168.1.3
 PC3: 192.168.1.4

4. Connectivity Validation:
o Ping tests confirmed successful communication between PCs and the
router, as well as among PCs.
o Round-trip times for pings were minimal, indicating efficient network
communication.

5. Router Functionality as DHCP Server:

o The router effectively managed the IP address pool and dynamically
assigned IP addresses to requesting devices.
o The show ip dhcp binding command on the router displayed the list of
allocated IP addresses and their corresponding MAC addresses.

6. No Manual Configuration Needed:

o PCs set to DHCP mode required no manual configuration, simplifying
network setup and management.

7. Simulation Observations:
o In Simulation Mode, DHCP packets were broadcasted initially but
targeted responses from the router followed, demonstrating the interaction
between the DHCP client (PC) and server (router).
8. Error Handling:
o Any IP conflicts or errors were avoided by excluding reserved addresses
(e.g., router’s IP: 192.168.1.1) from the DHCP pool.

 Results:

 The practical successfully demonstrated the use of a Router as a DHCP server

for automating IP address assignment.
 The DHCP process improved network efficiency by reducing manual
configuration efforts and preventing IP conflicts.
 Communication within the network was seamless, validating the correct
implementation of DHCP and the router’s functionality.
 Discussion:

This practical demonstrated the configuration of a router as a DHCP server and the role
of DHCP in automating IP address allocation in a network. The following points
summarize the key aspects observed during the experiment:

1. Efficiency of DHCP:
o DHCP significantly reduces the administrative overhead of manually
assigning IP addresses to each device in a network. All PCs received valid IP
addresses automatically, along with other necessary configurations like the
subnet mask, default gateway, and DNS server.

2. DHCP Discovery Process:

o The four-step DHCP process (Discover, Offer, Request, Acknowledge) was
clearly observed in the simulation. This process ensures seamless interaction
between DHCP clients (PCs) and the server (router) for IP address
assignment.

3. Error Prevention:
o By excluding specific addresses (e.g., the router’s IP) from the DHCP pool,
potential IP address conflicts were avoided. This demonstrates the importance
of proper DHCP configuration for effective network management.

4. Router as a DHCP Server:

o Configuring the router as a DHCP server highlighted its dual role:
 Serving as a gateway for routing data between networks.
 Managing dynamic IP address allocation within the local network.
o The show ip dhcp binding command proved valuable in verifying the DHCP
server's functionality and monitoring the assigned IP addresses.

5. Advantages in Large Networks:

o DHCP's ability to dynamically assign and manage IP addresses is especially
advantageous in large or dynamic networks where manually configuring
devices would be impractical and prone to errors.

6. Connectivity and Functionality:

o The successful ping tests between devices and the router confirmed proper
configuration and connectivity. The network operated efficiently, with
minimal delay in data transmission.

7. Comparison to Static IP Configuration:

o Static IP configuration is time-consuming and less flexible, particularly in
networks with frequent device changes. In contrast, DHCP ensures scalability,
automation, and ease of network management.
8. Simulation Observations:
o The simulation in Cisco Packet Tracer provided a detailed visualization of
DHCP communication. This was particularly helpful in understanding how
the protocol ensures reliable and conflict-free IP address assignment.

 Conclusion:

The practical highlighted the importance of DHCP in modern networks, demonstrating its
ability to simplify IP address management and enhance network efficiency. Configuring
the router as a DHCP server proved to be an effective solution for automating network
setup, ensuring seamless communication, and preventing potential issues such as IP
conflicts. This functionality makes DHCP an essential feature in both small-scale and
large-scale networks.
Practical-8
Configuration of DHCP server and verifying it, releasing the leased
IP, renew of the IP, Using Cisco Packet Tracer:

 Introduction:

The Dynamic Host Configuration Protocol (DHCP) automates the process of assigning IP
addresses to devices on a network, thereby reducing manual configuration efforts. In this
practical, we will configure a DHCP server on Cisco Packet Tracer, which will dynamically
allocate IP addresses to clients in a local area network (LAN). This process includes defining IP
address pools, setting up the default gateway, and specifying DNS servers. The practical will
also demonstrate how to verify the server's configuration, release and renew IP leases on client
devices, and troubleshoot any issues that arise during the process.

 Objectives of the practical:

1. Configure a DHCP Server:

o Set up a DHCP server on a Cisco router using Packet Tracer.
o Define an IP address pool (range of IP addresses) that the server will assign to
client devices.
o Specify the subnet mask, default gateway, and DNS servers for the clients.

2. Verify DHCP Configuration:

o Use the appropriate commands in Packet Tracer to ensure that the DHCP
server is functioning correctly and clients are receiving IP addresses
automatically.
o Check the DHCP binding table to confirm that IP addresses are allocated
properly.

3. Release the Leased IP:

o Demonstrate the release of an IP address on a client device using the "ipconfig
/release" command (on a Windows client) or equivalent commands in Packet
Tracer.
o Verify that the IP address is returned to the DHCP server pool.

4. Renew the Leased IP:

o Show how to renew a client device's IP address using the "ipconfig /renew"
command (or equivalent in Packet Tracer).
o Observe how the DHCP server allocates a new IP address or reassigns the
same one.
 5. Troubleshoot DHCP Issues:
o Identify and resolve potential DHCP problems, such as misconfigured server
settings or client devices not receiving IP addresses.
o Use diagnostic tools like "show ip dhcp binding" and "debug dhcp" to
troubleshoot issues in the DHCP process.

This practical will enhance your understanding of DHCP operations and how to manage IP
address distribution efficiently in a network environment.

 Materials and Software

To successfully perform this practical, the following materials and software are required:

1. Hardware (Simulated in Cisco Packet Tracer):

o Router(s) to act as a DHCP server.
o Switch(es) for connecting network devices.
o End devices (e.g., PCs, laptops) as DHCP clients.

2. Software:
o Cisco Packet Tracer:
A powerful network simulation tool used to design and configure the network,
including setting up and testing DHCP functionalities.
o Operating System Commands (Simulated):
Commands such as ipconfig for Windows devices or equivalent for
Linux/other systems to verify and manage IP configurations.

3. Network Configuration Details:

o Subnet information (IP range, subnet mask, and default gateway).
o DNS server address (if required).
o Access to Packet Tracer's CLI for configuring devices and testing.

These materials and software are essential to simulate, configure, and validate the DHCP
server's functionality in a controlled environment.

 Methodology:
The methodology outlines the step-by-step process to configure, test, and verify the DHCP
server using Cisco Packet Tracer. Follow these steps to complete the practical:
Step 1: Setting Up the Network

1. Launch Cisco Packet Tracer and create a new workspace.

2. Add the following devices to the workspace:
o One router to act as the DHCP server.
o One or more switches to interconnect the devices.
o Multiple end devices (e.g., PCs or laptops) to act as DHCP clients.
3. Connect the devices using copper straight-through cables:
o Router to Switch.
o Switch to PCs or laptops.

Step 2: Configuring the DHCP Server

1. Click on the router and open its CLI (Command Line Interface).
2. Enter the configuration mode:
3. enable
4. configure terminal
5. Configure the DHCP settings:

o Define the IP address pool:

 ip dhcp pool <pool_name>
 network <network_address> <subnet_mask>
 default-router <default_gateway>
 dns-server <dns_server_address>
o Exclude IP addresses (if required) to reserve them for static devices:
 ip dhcp excluded-address <start_ip> <end_ip>

Step 3: Verifying DHCP Configuration

1. Check the DHCP configuration on the router:

 show running-config
2. Verify the assigned IP addresses to client devices:
 show ip dhcp binding

Step 4: Testing the DHCP Functionality

1. Configure the PCs to receive IP addresses dynamically:

o Go to the PC’s Desktop tab → IP Configuration.
o Select DHCP to enable automatic IP assignment.
2. Verify the assigned IP address on the PC:
o Open the Command Prompt on the PC.
o Run the command:
 ipconfig
 Step 5: Releasing and Renewing IP Addresses

1. Release the currently leased IP address:

o In the PC’s Command Prompt, run:
 ipconfig /release
2. Renew the IP address:
o In the Command Prompt, run:
o ipconfig /renew
3. Verify the new IP address assignment using ipconfig.

Step 6: Troubleshooting (If Necessary)

1. Use the following router commands to troubleshoot DHCP issues:

o Check the DHCP binding table:
 show ip dhcp binding
o Debug DHCP operations:
 debug dhcp detail
2. Check for common issues like:
o Incorrect IP pool configuration.
o Overlapping IP ranges.
o Excluded IP address conflicts.

By following these steps, the DHCP server will be configured, tested, and verified successfully
in Cisco Packet Tracer.

 Figures:
Fig: Router Connection and DHCP Configuration Interface
 Fig: Verifying Connectivity, Releasing and Renewing IP Addresses

6. Observations and Results

 Observations:

1. DHCP Server Configuration:

o The DHCP server was successfully configured on the router using the
specified IP pool, subnet mask, default gateway, and DNS server.
o Excluded IP addresses were correctly reserved for static devices.

2. Dynamic IP Allocation:
o All client devices (PCs and laptops) received IP addresses dynamically from
the DHCP server.
o The assigned IP addresses were within the defined range of the IP pool.
o Each device received the correct subnet mask, default gateway, and DNS
server configuration.

3. Releasing and Renewing IP Addresses:

o After using the ipconfig /release command on a client device, its IP address
was successfully removed.
o The ipconfig /renew command reallocated a new or the same IP address to the
client, depending on availability.
 4. Verification of DHCP Binding:
o The DHCP binding table on the router displayed the MAC addresses of client
devices and their corresponding leased IP addresses.
o The lease expiration time was observed to be set according to the default or
configured duration.

5. Troubleshooting:
o No errors were encountered during configuration.
o Debugging commands like debug dhcp detail showed real-time DHCP request
and acknowledgment messages, confirming the successful DHCP process.

 Results:

1. The DHCP server was configured successfully to dynamically assign IP addresses to

devices in the network.
2. All devices in the network were able to automatically obtain valid IP configurations,
ensuring seamless communication within the LAN.
3. The release and renewal of IP addresses were performed successfully, demonstrating
proper DHCP functionality.
4. Troubleshooting tools were effectively used to verify and monitor the DHCP process.

The practical successfully demonstrated the configuration and operation of a DHCP server using
Cisco Packet Tracer, meeting all the objectives outlined.

 Discussion:
This practical demonstrated the efficient configuration and functionality of a DHCP server
using Cisco Packet Tracer, highlighting the importance of automating IP address
management in modern networks.

1. Automation and Scalability:

o DHCP eliminates the need for manual IP configuration, reducing
administrative overhead in large networks.
o It ensures scalability by dynamically assigning IP addresses from a predefined
pool, preventing duplication and conflicts.

2. Configuration Observations:
o The proper configuration of IP pools, default gateways, and DNS servers is
crucial for seamless client-server communication.
o Excluding reserved IP addresses (e.g., for servers or printers) ensures that they
are not assigned to other devices.
 3. Dynamic Lease Management:
o The release and renewal of IP addresses demonstrated how DHCP effectively
manages IP address allocation.
o By reassigning IPs as needed, DHCP optimizes IP utilization in networks with
limited address ranges.
4. Troubleshooting and Validation:
o Commands like show ip dhcp binding and debug dhcp detail are valuable for
diagnosing issues related to DHCP configuration and operation.
o Real-time logging of DHCP requests and acknowledgments provided deeper
insights into the client-server interaction.

 Applications in Real-World Scenarios:

1. Enterprise Networks:
o DHCP is widely used in enterprises where hundreds or thousands of
devices connect to the network daily.
o It simplifies IP management and minimizes downtime caused by manual
errors.
2. Dynamic Environments:
o Networks with frequently changing devices, such as guest networks or IoT
setups, benefit significantly from DHCP’s flexibility.

 Challenges and Limitations:

1. Single Point of Failure:

o If the DHCP server fails, clients will be unable to obtain IP addresses,
disrupting the network. Redundancy (e.g., DHCP failover) can mitigate
this risk.
2. Security Concerns:
o Unauthorized DHCP servers (rogue DHCP servers) can lead to IP
conflicts or malicious activity. Enabling DHCP snooping on switches can
prevent such issues.

 Conclusion:

This practical successfully demonstrated the configuration and management of a DHCP

server. It underscored the significance of DHCP in maintaining efficient and automated
network operations. The release, renewal, and troubleshooting processes highlighted the
protocol’s dynamic nature, making it an indispensable tool in both small and large-scale
networks. Future improvements could include exploring advanced DHCP configurations like
DHCP relay or failover mechanisms.
Practical-9
Configuration of FTP, HTTP, DNS and e-mail server, Using Cisco
Packet Tracer:

 Introduction:

In this practical, the focus is on configuring essential network services—FTP, HTTP, DNS,
and Email servers—using Cisco Packet Tracer. These services are vital for enabling file
transfers, hosting websites, resolving domain names, and facilitating email communication
within a network. By configuring these servers, users can simulate and understand their
functionality, operation, and integration in a LAN environment. This practical also highlights
the significance of these services in real-world networking and IT systems.

 Objectives of the practical:

1. FTP Server Configuration:

o Set up an FTP server to enable secure file sharing and transfers.
o Test the upload and download of files between clients and the FTP server.

2. HTTP Server Configuration:

o Configure an HTTP server to host and deliver web pages.
o Test the client’s ability to access web pages using a browser.

3. DNS Server Configuration:

o Configure a DNS server to resolve domain names to IP addresses.
o Test the functionality by accessing services (e.g., websites) using domain names
instead of IP addresses.

4. Email Server Configuration:

o Set up an Email server for sending and receiving emails.
o Test email communication between clients using the configured server.

5. Integration and Testing:

o Verify the connectivity and interaction between the configured servers and client
devices.
o Simulate real-world scenarios such as hosting a website, transferring files, and
sending emails to ensure proper operation of all services.
 6. Troubleshooting and Validation:
o Use diagnostic tools and commands in Packet Tracer to identify and resolve
potential issues in server configurations.

By the end of this practical, you will understand how to configure and test these core network
services, ensuring their seamless operation in a simulated environment.

 Materials and Software:

To successfully perform the practical on configuring FTP, HTTP, DNS, and Email servers
using Cisco Packet Tracer, the following materials and software are required:

 Hardware Components (Simulated in Cisco Packet Tracer):

1. Servers:
o A server device in Packet Tracer to act as the FTP, HTTP, DNS, and
Email server.
2. Switches:
o Network switches to interconnect servers and client devices.
3. End Devices:
o PCs, laptops, or other devices as clients to test the configured servers.
4. Router:
o If required, to provide routing functionality between networks or enable
internet-like connectivity.

 Software Requirements:

1. Cisco Packet Tracer:

o A simulation tool used to configure and test the servers, including network
devices and client-server communication.
2. Operating System Commands for Testing:
o FTP Testing:
 Commands like ftp <server_ip> to upload and download files.
o HTTP Testing:
 A web browser or the built-in Packet Tracer browser to access
hosted websites.
o DNS Testing:
 Commands like nslookup <domain> to verify domain name
resolution.
o Email Testing:
 Built-in email clients to send and receive test emails.
  Configuration Details Required:

1. FTP Server:
o Files to upload/download.
o Usernames and passwords for access control.
2. HTTP Server:
o Web pages (HTML files) to host on the server.
3. DNS Server:
o A list of domain names and their corresponding IP addresses for
resolution.
4. Email Server:
o User accounts, email addresses, and passwords for client devices.

These materials and software provide the foundation to simulate and test the configuration of
FTP, HTTP, DNS, and Email servers, ensuring their functionality in a controlled
environment.

 Methodology:
The methodology outlines the step-by-step procedure for configuring and testing FTP,
HTTP, DNS, and Email servers using Cisco Packet Tracer.

Step 1: Network Setup

1. Add Devices:
o Place the following devices in the workspace:
 One server to host FTP, HTTP, DNS, and Email services.
 One or more switches for interconnecting devices.
 Multiple PCs or laptops as client devices.

2. Connect Devices:
o Use copper straight-through cables to connect:
 Server to the switch.
 Client devices to the switch.

3. Assign IP Addresses:
o Manually assign static IP addresses to the server.
o Configure client devices to obtain IP addresses dynamically (or assign them
manually as needed).
Step 2: Configuring the FTP Server

1. Select the server and open the Services tab.

2. Navigate to the FTP service:

o Turn on the FTP service.
o Add a username and password for client authentication.
3. Add files to the server for uploading/downloading by clients.

Step 3: Configuring the HTTP Server

1. In the server's Services tab, go to HTTP:

o Enable the HTTP service.
2. Upload a sample HTML webpage to the server.
3. Test the HTTP service by accessing the hosted webpage from a client device using
the browser.

Step 4: Configuring the DNS Server

1. Open the DNS service in the server’s Services tab.

2. Enable the DNS service and configure domain names:
o Add mappings of domain names (e.g., example.com) to their respective IP
addresses.
3. Test the DNS service from client devices:
o Use the nslookup command or access the domain through the browser to
verify resolution.

Step 5: Configuring the Email Server

1. Go to the Email service in the server’s Services tab.

o Enable the Email service.
2. Create email accounts for users with unique email addresses and passwords.
3. Configure the email client on PCs:
o Enter the server's IP address, username, and password.
4. Test the service:
o Send and receive emails between client devices using the configured email
accounts.

Step 6: Testing and Verification

1. FTP Testing:
o From a client device, open the Command Prompt.
o Use the command:
 ftp <server_ip>
o Verify successful file uploads and downloads using the put filename and get
filename commands in FTP.
 2. HTTP Testing:
o Open the browser on a client device.
o Access the hosted webpage using the server’s IP address or domain name.

3. DNS Testing:
o Run the nslookup command on a client device to check domain resolution.
o Access the server using the configured domain name.

4. Email Testing:
o Send a test email from one client device to another.
o Verify that the email is sent and received successfully.

Step 7: Troubleshooting

1. Check for connectivity issues using the ping command.

2. Verify server configurations and ensure services are enabled.
3. Use Packet Tracer's real-time simulation to debug and monitor client-server
communication.

By following this methodology, the configuration and functionality of FTP, HTTP, DNS, and
Email servers can be successfully demonstrated in Cisco Packet Tracer.

 Figures:

Fig: Device Configuration Interface

1. FTP Server:
 Fig: FTP Server Configuration and Verification

2. HTTP Server:

Fig: HTTP Server Configuration and Verification

3. DNS Server:

Fig: DNS Server Configuration and Verification

4. Email Server:

Fig: Email Server Configuration and Verification

 Observations and Results:

 Observations:

1. FTP Server Configuration:

o The FTP service was successfully configured on the server, allowing
client devices to connect using FTP commands.
o Files were successfully uploaded and downloaded from the server using
the put and get commands in the Command Prompt.
o Username and password authentication worked as expected, ensuring
secure access to the server.

2. HTTP Server Configuration:

o The HTTP service was enabled and the server successfully hosted a
webpage.
o The webpage was accessible from client devices using the server's IP
address and domain name.
o The content of the webpage was displayed correctly when accessed via the
browser.

3. DNS Server Configuration:

o The DNS service was configured to map domain names to corresponding
IP addresses.
o Domain names were successfully resolved to IP addresses when queried
using the nslookup command.
o Clients were able to access services using domain names instead of IP
addresses, confirming proper DNS resolution.

4. Email Server Configuration:

o The Email service was successfully configured on the server, and email
accounts were created for the client devices.
o Emails were sent from one client device and successfully received on the
other, confirming proper email functionality.
o The client devices were able to send and receive messages without issues.

 Results:

1. FTP Results:
o File Upload/Download: Files were transferred successfully between the
client and server. The put command was used to upload files, and the get
command was used to download files.
o Successful FTP Session: The FTP session was stable, and the server
responded to commands without errors.
 2. HTTP Results:
o Webpage Access: Clients were able to access the hosted webpage from
the browser using both the IP address and the configured domain name.
o Content Display: The HTML content was displayed correctly without
issues, confirming that the HTTP service was working as intended.

3. DNS Results:
o Domain Name Resolution: The nslookup command correctly resolved
the configured domain names to their respective IP addresses.
o Service Verification: Clients were able to use domain names to access
services, demonstrating that DNS resolution was functional.

4. Email Results:
o Email Sending/Receiving: Emails were successfully sent from one client
device and received on the other, confirming the functionality of the email
server.
o Successful Communication: The email client application worked
seamlessly for sending and receiving messages between configured
accounts.

Overall, the practical successfully demonstrated the configuration and testing of FTP, HTTP,
DNS, and Email services using Cisco Packet Tracer. All services operated correctly, meeting
the expected outcomes.

 Discussion:
This practical provided valuable hands-on experience in configuring and testing four
essential network services—FTP, HTTP, DNS, and Email servers—using Cisco Packet
Tracer. These services are critical for enabling file sharing, web hosting, domain name
resolution, and email communication within a network.

 Key Insights:

1. FTP Server Configuration and Usage:

o FTP allows secure and efficient file transfers between devices in a network.
By configuring the FTP server, we were able to observe the direct interaction
between clients and the server, confirming the importance of user
authentication and proper file management.
o The put and get commands in FTP demonstrated how files are uploaded and
downloaded. This hands-on experience shows how FTP can be used in real-
world scenarios like sharing large files across a corporate network or
between different departments.
2. HTTP Server and Web Hosting:
o The HTTP server configuration allowed us to simulate a simple web hosting
environment. By uploading an HTML webpage to the server, we observed
how client devices can access web content using a browser.
o This highlights the fundamental role of web servers in hosting websites and
applications, enabling users to interact with content online. Through this
practical, it became clear how HTTP servers form the backbone of web
hosting and content delivery.

3. DNS Server and Name Resolution:

o The DNS server configuration showed the significance of domain name
resolution. The ability to map human-readable domain names (like
example.com) to IP addresses simplifies the process of accessing services on
the network.
o Clients were able to access services by using domain names instead of IP
addresses, which is closer to real-world network setups. The practical
demonstrated the crucial role of DNS in making network resources more
accessible and user-friendly.

4. Email Server and Communication:

o The Email server setup demonstrated how email systems are configured and
how clients can send and receive messages. By creating email accounts and
testing communication between client devices, we were able to replicate the
basic functionality of an email system within a network.
o This setup emphasized the importance of email servers in managing
communications within organizations, whether for internal communication or
external email exchanges.

 Applications in Real-World Scenarios:

1. Enterprise Networks:
o These services (FTP, HTTP, DNS, and Email) are fundamental in
enterprise networks. FTP can be used for file transfers between
employees, HTTP serves internal and external websites, DNS ensures easy
access to these resources, and email servers facilitate communication.
o Configuring and managing these services properly ensures seamless
operation in an organization and avoids network downtime.

2. Internet Infrastructure:
o HTTP and DNS are essential components of the internet infrastructure.
While HTTP servers host websites, DNS servers ensure that users can
access these sites by resolving domain names to IP addresses. The practice
of these configurations in a controlled environment highlights their
relevance in daily internet operations.
  Challenges and Limitations:

1. Security Considerations:
o In real-world networks, security is crucial. FTP, for instance, can be
vulnerable to unauthorized access if not configured correctly. Using secure
alternatives like FTPS or SFTP is recommended for sensitive data
transfers.
o Similarly, securing the Email server to prevent unauthorized access and
spam is vital. Implementing proper authentication mechanisms and
encryption protocols (e.g., SSL/TLS) is essential.

2. Scalability and Performance:

o While this practical provided a foundational understanding of these
services, real-world networks require scalable solutions to handle
thousands or millions of users. Configurations in larger networks often
involve additional layers of load balancing, fault tolerance, and
redundancy to ensure consistent performance.

 Conclusion:

This practical successfully demonstrated the configuration and integration of essential

network services, allowing a deeper understanding of how FTP, HTTP, DNS, and Email
servers work together to provide key network functionalities. Through hands-on simulation,
we were able to observe the real-world application of these services in enabling
communication and resource sharing within a network. Future improvements could include
exploring advanced configurations like securing these services with encryption, load
balancing, and redundancy mechanisms to ensure high availability in production
environments.
Practical-10
Static routing and Dynamic routing (RIP, OSPF, EIGRP, BGP),
Using Cisco Packet Tracer:

 Introduction:

Routing is a fundamental aspect of computer networks, allowing devices to communicate

across different networks. In this practical, the focus is on configuring and testing static
routing and dynamic routing protocols—RIP, OSPF, EIGRP, and BGP—using Cisco
Packet Tracer. Static routing involves manually specifying paths for data to follow, while
dynamic routing allows routers to automatically share information about network topology
and adjust to changes in the network. This practical will help simulate real-world routing
scenarios, providing hands-on experience in managing and optimizing network traffic.

 Objectives of the practical:

1. Static Routing Configuration:

o Understand and configure static routes on Cisco routers.
o Manually specify paths to reach remote networks using static routing.
o Test connectivity between devices using static routes.

2. Dynamic Routing Protocols Configuration:

o RIP (Routing Information Protocol):
 Configure RIP version 2 to share routing information across
routers.
 Verify network reachability and the propagation of routing
updates.
o OSPF (Open Shortest Path First):
 Configure OSPF to enable routers to share information about
network topology using link-state routing.
 Verify OSPF neighbors and test routing table propagation.
o EIGRP (Enhanced Interior Gateway Routing Protocol):
 Set up EIGRP to allow routers to exchange routing information
efficiently using distance vector and link-state techniques.
 Verify neighbor relationships and network reachability.
o BGP (Border Gateway Protocol):
 Configure BGP for inter-domain routing between different
autonomous systems (AS).
 Test BGP route propagation and inter-network communication.
 3. Routing Table Analysis:
o Analyze the routing tables for each routing protocol to understand how
routes are learned and maintained.
o Identify and troubleshoot any issues related to route propagation and
network connectivity.

4. Testing and Troubleshooting:

o Test the functionality of each routing protocol by performing ping and
traceroute operations.
o Use diagnostic tools such as show ip route and show ip protocols to verify
proper configuration and troubleshoot issues.

By the end of this practical, you will have a solid understanding of both static and dynamic
routing, and be able to configure and troubleshoot different routing protocols in a simulated
network environment using Cisco Packet Tracer.

 Materials and Software:

To perform the practical on Static Routing and Dynamic Routing Protocols (RIP, OSPF,
EIGRP, BGP) using Cisco Packet Tracer, the following materials and software are
required:

 Hardware Components (Simulated in Cisco Packet Tracer):

1. Routers:
o A minimum of two routers to simulate network connectivity and route
configuration. Multiple routers may be required to simulate larger network
setups or various routing protocols.
2. Switches:
o Network switches to connect routers and client devices (if needed) to
simulate a more complex network environment.
3. End Devices:
o PCs or laptops to serve as client devices for testing the connectivity across
the network. These devices will be used to verify routing configurations
by sending ping and traceroute requests.

 Software Requirements:

1. Cisco Packet Tracer:

o A network simulation tool used to configure and test static and dynamic
routing protocols. Cisco Packet Tracer allows the creation of virtual
networks, providing a hands-on environment to simulate routing,
switching, and network topology configurations.
2. Router OS Configuration Commands:
 o Basic Cisco router commands for configuring static routes and dynamic
routing protocols.
o For example:
 Static Routing Configuration:

 ip route <destination_network> <subnet_mask>

<next_hop_ip>

 RIP Configuration:

 router rip
 version 2
 network <network_address>

 OSPF Configuration:

 router ospf <process_id>

 network <network_address> <wildcard_mask> area
<area_id>

 EIGRP Configuration:

 router eigrp <as_number>

 network <network_address>
 no auto-summary

 BGP Configuration:

 router bgp <asn>

 Networking Tools for Testing:

1. Ping Command:
o For testing connectivity between devices (routers and PCs).
o Command:
 ping <destination_ip>
2. Traceroute Command:
o To trace the path taken by packets from source to destination, verifying
the routing path.
o Command:
 traceroute <destination_ip>
3. Show Commands:
o For verifying the router’s routing table and protocol configurations:
  Show IP Route:

 show ip route

 Show IP Protocols:

 show ip protocols

With these materials and software tools, this practical will allow you to configure static and
dynamic routing protocols (RIP, OSPF, EIGRP, and BGP), analyze routing tables, and
troubleshoot routing issues in a simulated network environment.

 Methodology:

The methodology for this practical involves the step-by-step configuration and testing of
Static Routing and Dynamic Routing Protocols (RIP, OSPF, EIGRP, and BGP) using
Cisco Packet Tracer. The process includes configuring the routers, assigning IP addresses,
configuring routing protocols, and testing the network connectivity to verify proper routing
behavior.

Step 1: Network Setup

1. Add Devices:
o Place at least two routers in the Packet Tracer workspace. For dynamic
routing protocols, multiple routers (typically 3 or more) are required to
demonstrate inter-router communication.
o Place switches (optional) if needed to connect devices in different segments.
o Add PCs or laptops to test connectivity and routing.
2. Configure IP Addressing:
o Assign static IP addresses to the interfaces of each router. Ensure that the IP
address ranges are appropriately planned for each network segment.
o Assign IP addresses to the PCs connected to the routers, either manually or via
DHCP if applicable.

Step 2: Static Routing Configuration

1. Router Configuration:
o Access the router CLI (Command Line Interface) to begin configuring static
routes.
o Use the following command to configure static routes on each router to direct
traffic to remote networks:

 ip route <destination_network> <subnet_mask> <next_hop_ip>

 o Configure routes on all routers to ensure full connectivity between networks.

2. Verification:
o Check the routing table to verify the correct static routes have been added.
Use the command:

 show ip route

o Use ping and traceroute commands to test connectivity between the devices
connected to the routers:

 ping <destination_ip>
 traceroute<destination_ip>

Step 3: RIP (Routing Information Protocol) Configuration

1. Enable RIP on Routers:

o Enter global configuration mode and start RIP on each router:

 router rip
 version 2
 network <network_address>

2. Verify RIP Configuration:

o Check the routing table to verify that RIP routes are propagated:

 show ip route

o Verify the RIP neighbor relationship:

 show ip rip database

3. Test Connectivity:
o Use ping and traceroute to test the connectivity between different devices
and verify that RIP routes are being learned and propagated.

Step 4: OSPF (Open Shortest Path First) Configuration

1. Enable OSPF on Routers:

o Enter global configuration mode and configure OSPF on each router:

 router ospf <process_id>

 network <network_address> <wildcard_mask> area
<area_id>
 2. Verify OSPF Configuration:
o Check the OSPF routing table:

 show ip route ospf

o Verify OSPF neighbors:

 show ip ospf neighbor

3. Test Connectivity:
o Use ping and traceroute commands to verify OSPF routes and connectivity
between devices.

Step 5: EIGRP (Enhanced Interior Gateway Routing Protocol) Configuration

1. Enable EIGRP on Routers:

o Enter global configuration mode and configure EIGRP on each router:
o router eigrp <as_number>
o network <network_address>
o no auto-summary
2. Verify EIGRP Configuration:
o Check the EIGRP routing table:

 show ip route eigrp

o Verify EIGRP neighbors:

 show ip eigrp neighbors

3. Test Connectivity:
o Test the reachability of devices using ping and traceroute. Ensure that
EIGRP has propagated routes correctly across the network.

Step 6: BGP (Border Gateway Protocol) Configuration

1. Enable BGP on Routers:

o Enter global configuration mode and configure BGP for inter-domain routing:

 router bgp <asn>

 network <network_address> mask <subnet_mask>

2. Verify BGP Configuration:

o Check the BGP routing table:

 show ip route bgp

 o Verify BGP neighbor relationships:

 show ip bgp summary

3. Test Connectivity:
o Use ping and traceroute to verify the BGP routes are correctly propagated
and that inter-domain communication is functional.

Step 7: Routing Table Analysis

 After configuring the static and dynamic routing protocols, examine the routing tables
on each router to confirm that the appropriate routes have been learned and that they
are being used to forward packets.
 Use the following command to view the routing table:
o show ip route
 Ensure that the routing tables reflect the expected paths based on the routing
protocols configured.

Step 8: Troubleshooting and Verification

1. Verify Routing Configuration:

o Use show ip protocols and show ip route to check the router's routing table
and verify that routing protocols are properly configured.
2. Test Connectivity:
o Test the network connectivity between devices using ping and traceroute
commands to confirm that the routing protocols are propagating routes
correctly.
3. Use Debugging Tools:
o If routing is not functioning correctly, use debugging tools in Packet Tracer,
such as ping and show commands, to trace and troubleshoot issues in the
configuration.

By following these steps, you will configure static routing and dynamic routing protocols,
verify their operation, and ensure that the network connectivity between devices is working
as expected.
 Figures:

Fig: Router Configuration Interface

1) Static Routing:
 Fig: Static Routing Configuration and Verifying Connectivity

2) Dynamic Routing:

a) RIP (Routing Information Protocol):

 Fig: RIP Configuration and Verifying Connectivity

b) OSPF (Open Shortest Path First):

 Fig: OSPF Configuration and Verifying Connectivity

c) EIGRP (Enhanced Interior Gateway Routing Protocol):

 Fig: EIGRP Configuration and Verifying Connectivity

d) BGP (Border Gateway Protocol):

Fig: Three Router Configuration Interface For BGP

 Fig: BGP Configuration and Verifying Connectivity

 Observations and Results:

During the practical on Static Routing and Dynamic Routing Protocols (RIP, OSPF,
EIGRP, BGP) using Cisco Packet Tracer, the following observations and results were
recorded:

 Observations:

1. Static Routing:
o After configuring static routes on the routers, packets were successfully
forwarded between different networks.
o The routing table displayed manually configured routes with the S (Static)
code.
o Connectivity was verified using ping and traceroute, which showed the
exact paths defined by the static routes.

2. Dynamic Routing Protocols:

o RIP (Routing Information Protocol):
 RIP successfully propagated routes between connected routers.
 The routing table showed entries learned via RIP, marked with the
R code.
 RIP updates occurred every 30 seconds, as observed during testing.
 o OSPF (Open Shortest Path First):
 OSPF established neighbor relationships, as verified by the show
ip ospf neighbor command.
 The routing table displayed routes learned via OSPF, marked with
the O code.
 OSPF used cost as the metric, and packets were routed through the
shortest-cost path.

o EIGRP (Enhanced Interior Gateway Routing Protocol):

 EIGRP established neighbor adjacencies and exchanged routing
information.
 The routing table displayed EIGRP-learned routes with the D
(Dynamic) code.
 EIGRP utilized composite metrics (bandwidth and delay), and the
path with the lowest metric was chosen.

o BGP (Border Gateway Protocol):

 BGP successfully established peering between routers in different
autonomous systems.
 Routes learned via BGP were displayed in the routing table,
marked with the B code.
 BGP updates and advertisements were successfully propagated
between autonomous systems.

3. Routing Table Analysis:

o Each router maintained an updated routing table, showing learned routes
and the protocol associated with each route.
o The routing tables changed dynamically based on the configurations of
RIP, OSPF, EIGRP, and BGP.

4. Testing Connectivity:
o Ping tests between devices in different networks confirmed successful
routing.
o Traceroute outputs matched the expected paths based on the routing
protocol configurations.

5. Performance Observations:
o Static Routing:
 Required manual configuration for every route, which is time-
consuming for large networks.
o Dynamic Routing Protocols:
 Automatically adjusted to changes in the network, such as link
failures or topology updates.
  Results:

1. Static Routing:
o Successful communication was established between devices using
manually configured static routes.
o Static routes were accurately displayed in the routing tables.

2. Dynamic Routing Protocols:

o RIP, OSPF, EIGRP, and BGP were successfully configured, and routes
were dynamically propagated across the network.
o Connectivity was maintained even when link changes occurred,
demonstrating the adaptability of dynamic routing protocols.

3. Routing Metrics:
o RIP used hop count as the metric (limited to 15 hops).
o OSPF selected paths based on link cost.
o EIGRP utilized a composite metric based on bandwidth and delay.
o BGP focused on policy-based routing, choosing paths based on AS
preferences.

4. Network Reachability:
o All configured networks were reachable using both static and dynamic
routing.
o The connectivity was verified using ping and traceroute commands,
which confirmed that packets followed the expected paths.

5. Protocol Comparison:
o Static routing required manual setup, making it ideal for small, stable
networks.
o Dynamic routing protocols demonstrated their scalability and adaptability
to larger, more complex networks.

 Discussion:

The practical exercise on Static Routing and Dynamic Routing Protocols (RIP, OSPF,
EIGRP, and BGP) has provided valuable insights into the operation of various routing
techniques and their application in real-world networking scenarios. Each routing method
serves a different purpose, and understanding their functionality is essential for network
administrators and engineers.
 Static Routing vs. Dynamic Routing:

1. Static Routing:
o Advantages:
 Static routing is simple and offers full control to the network
administrator. It ensures a predictable routing path, making it
suitable for small, stable networks where the topology does not
change frequently.
 It consumes minimal network resources since no routing updates
are exchanged between routers, making it less resource-intensive.
 It is secure since there is no routing exchange; routes are explicitly
configured and must be manually updated.

o Disadvantages:
 The main drawback of static routing is its scalability. In larger
networks, manually configuring routes for each destination is time-
consuming and impractical.
 Changes in network topology, such as a router failure or new route
addition, require manual updates to the routing table, which
introduces potential human error and downtime.

2. Dynamic Routing:
o Advantages:
 Dynamic routing protocols automatically adjust to network
changes, such as link failures or changes in network topology,
making them more adaptable and suitable for larger, more complex
networks.
 They reduce the administrative burden by automatically
discovering and maintaining routing paths. As a result, they allow
for easier scaling in large networks.
 They provide a fault-tolerant network since they can reroute traffic
when a link or path becomes unavailable.

o Disadvantages:
 Dynamic routing protocols consume more bandwidth and router
resources because they constantly exchange routing updates to
maintain the routing table.
 They introduce complexity, requiring proper configuration and
understanding of routing protocols. Misconfigurations or incorrect
routing updates can lead to network instability or suboptimal
routing.
 Dynamic Routing Protocols:

1. RIP (Routing Information Protocol):

o RIP is the simplest dynamic routing protocol, relying on hop count as
the metric to determine the best path. However, its limitation of a
maximum of 15 hops restricts its use in larger networks.
o RIP is a distance-vector protocol, which means it broadcasts its entire
routing table at regular intervals. This can cause network congestion
and instability in larger networks.
o RIP is best suited for small to medium-sized networks where
simplicity and ease of implementation are prioritized over optimal
performance.

2. OSPF (Open Shortest Path First):

o OSPF is a link-state routing protocol that uses cost (based on
bandwidth) as the metric to determine the best path. This makes OSPF
more efficient and scalable compared to RIP, as it supports larger
networks.
o OSPF performs faster convergence and is more efficient in terms of
bandwidth utilization because it only sends updates when there are
changes to the network topology.
o The complexity of OSPF configurations and its use of areas (to
minimize routing table size) make it suitable for larger and more
hierarchical network architectures.

3. EIGRP (Enhanced Interior Gateway Routing Protocol):

o EIGRP combines the benefits of both distance-vector and link-state
protocols, offering fast convergence and the ability to scale efficiently.
o It uses a metric that includes bandwidth, delay, load, and reliability,
making EIGRP more flexible and capable of making more granular
routing decisions.
o EIGRP is more efficient than RIP and OSPF in many cases,
particularly in smaller to medium-sized enterprise networks where
quick convergence and minimal overhead are critical.

4. BGP (Border Gateway Protocol):

o BGP is an inter-domain routing protocol, used for routing between
different autonomous systems (ASes) in the internet. Unlike the
internal routing protocols like RIP, OSPF, and EIGRP, BGP focuses
on path selection based on policies, making it highly flexible but more
complex to configure.
o BGP operates using path vectors and provides policy-based routing
decisions, making it suitable for large-scale networks such as the
internet.
 o The major challenge with BGP is its complexity and the need for
detailed policy configuration to manage routes between ASes
effectively.

 Testing and Connectivity:

The ping and traceroute commands were instrumental in verifying the functionality of
the static and dynamic routing protocols. By examining the routing tables, we observed
that routes learned through RIP, OSPF, EIGRP, and BGP were correctly propagated
across the network and reflected in the routers’ routing tables. The testing confirmed that
packets followed the expected paths, and the dynamic protocols adapted to changes in the
network topology (e.g., router reboots or link failures).

Through traceroute, we also observed how the routing protocols made decisions on the
path selection, highlighting differences in how each protocol handles traffic forwarding.
For example, OSPF and EIGRP demonstrated the ability to reroute traffic efficiently in
case of link failures, whereas RIP took longer to stabilize due to its periodic updates.

 Challenges Encountered:

 Configuration Complexity:
Configuring OSPF, EIGRP, and BGP required a deeper understanding of the routing
concepts and command syntax, which posed some challenges initially. The
interdependencies between different network interfaces and the need for accurate IP
addressing required careful attention.
 Troubleshooting:
While static routing had fewer issues, troubleshooting dynamic protocols, especially
BGP, required a more detailed approach. The command outputs (e.g., show ip bgp
summary or show ip ospf neighbor) were essential in diagnosing misconfigurations or
issues with route propagation.
 Protocol Behavior Differences:
The behavior of the different routing protocols in terms of convergence time,
scalability, and resource consumption varied, and understanding these differences
was crucial in selecting the right protocol for each specific network scenario.

 Conclusion:

The practical successfully demonstrated the configuration and behavior of static routing and
dynamic routing protocols (RIP, OSPF, EIGRP, and BGP). Each protocol's functionality and
performance were verified, and the network connectivity was tested successfully. The results
emphasized the advantages of dynamic routing protocols in terms of automation and
scalability, while also showcasing the simplicity and control of static routing for smaller
networks.