Lakshmi Narain College of Technology, Bhopal

LABORATORY MANUAL
B.Tech. Semester- VI

COMPUTER NETWORK LAB

Subject code: AL602

Submitted to – Dr.Vinod Pathak

Submitted by – Aditya Kinkar

Department of AIML
 List of Experiments

Experiment Submission Remarks

S. Program Name date
Date
No.

1 To study the Comparative Analysis of Network Simulators

2 To learn and configuration of networking hardware like RJ-45

connector, Network cables, crimping tool, etc
To learn and implement basic command of Computer network
3 like PING, traceroute etc.

Configure and implement a network using Packet Tracer.

4
a. Creating a First Network
b. Sending Simple Text Messages in Realtime Mode
c. Establishing a Web Server Connection
Using the PC’s Web Browser
Configure network devices, such as hubs and switches within
5 a network topology using Packet Tracer software.

Configure network topology to implement VLANs with

6 trunking using Packet Tracer software.

Configure and implementation of a router within Network

7 using Packet Tracer.

Configure network topology and implement static routing

8 using Packet Tracer Software.

Configure network topology and implement dynamic routing

protocol such as RIP, OSPF etc. using Packet Tracer.
9
Configure a network and implement remote login of router
10 and Management using Packet Trace
 LAB EXPERIMENT 1

OBJECTIVE: To study the Comparative Analysis of Network Simulators

BRIEF DESCRIPTION:
CISCO PACKET TRACER
1. The robust simulation tool used to visualize networks.
2. Packet Tracer provides valuable tips and best practices for using Cisco Packet Tracer.
3. Learn the basic operations of Packet Tracer: - File commands, visualization and
configuration of networking devices.
4. Simulate the interactions of data traveling through the network.
5. Learn to visualize the network in logical and physical modes.
6. Reinforce your understanding with extensive hands-on networking and IOT activities.
7. Get immediate feedback on your work through built-in quizzes and tests.
8. Connect with the global Cisco Networking Academy community.

System requirement
The following configuration is recommended by Cisco to successfully install and run Packet
Tracer 7.0 :

1. Microsoft Windows (7 / 8.1 / 10) or Linux Ubuntu (14.04 64-bits)

2. At least Pentium 4 (2.5 GHz)

3. A minimum of 2GB RAM (4GB recommended)

4. 700 MB of storage space

5. A minimum screen resolution of 1024 x 768

Summary

Packet Tracer is a cross-platform visual simulation tool designed by Cisco Systems that allows
users to create network topologies and imitate modern computer networks. The software allows
users to simulate the configuration of Cisco routers and switches using a simulated command
line interface.

Packet Tracer is a cross-platform visual simulation tool designed by Cisco Systems that allows
users to create network topologies and imitate modern computer networks. The software allows
users to simulate the configuration of Cisco routers and switches using a simulated command line
interface. Packet Tracer makes use of a drag and drop user interface, allowing users to add and
remove simulated network devices as they see fit. The software is mainly focused towards Certified
Cisco Network Associate Academy students as an educational tool for helping them learn
fundamental CCNA concepts.

NS-2/NS-3
1. ns (from network simulator) is a name for a series of discrete event network simulators,
specifically ns-1, and ns-2.
2. All of them are discrete-event computer network simulators, primarily used in
research and teaching.

System Requirements
1. Linux (x86 and x86_64): gcc/g++ versions 4.9 and above
2. Note: If you are using RHEL or Centos, you will likely need to install a more up-to-date compiler than
the default; search for how to enable 'software collections' or 'devtoolset' on these distributions. Other
Linux distributions typically have a suitable default compiler (at least version 4.9).
3. MacOS Apple LLVM: version 8.0.0 and above (version 7.0.0 may work)
4. FreeBSD and Linux (x86_64): clang/LLVM version 3.9 and above (older versions down to 3.3 may
work)
5. The minimum Python version supported is 2.7 or greater (version 2), or version 3.4 or greater (version
3).

Summary

NETWORK SIMULATOR 3

ns-3 has been developed to provide an open, extensible network simulation platform, for
networking research and education.
In brief, ns-3 provides models of how packet data networks work and perform, and provides a
simulation engine for users to conduct simulation experiments.
Some of the reasons to use ns-3 include to perform studies that are more difficult or not possible
to perform with real systems, to study system behavior in a highly controlled, reproducible
environment, and to learn about how networks work.
NETWORK SIMULATOR 2

It is not possible to run a simulation in ns-2 purely from C++ (i.e., as a main() program without
any OTcl). Moreover, some components of ns-2 are written in C++ and others in OTcl.

In ns-3, the simulator is written entirely in C++, with optional Python bindings.

Simulation scripts can therefore be written in C++ or in Python.

New animators and visualizers are available and under current development. Since ns-
3 generates pcap packet trace files, other utilities can be used to analyze traces as well.

WIRESHARK

1. Wireshark is a network packet analyzer. A network packet analyzer will try to capture
network packets and tries to display that packet data as detailed as possible.
2. You could think of a network packet analyzer as a measuring device used to examine
what’s going on inside a network cable, just like a voltmeter is used by an electrician to
examine what’s going on inside an electric cable (but at a higher level, of course).
3. Wireshark is perhaps one of the best open source packet analyzers available today.

System Requirements
The amount of resources Wireshark needs depends on your environment and on the size of the
capture file you are analyzing. The values below should be fine for small to medium-sized capture
files no more than a few hundred MB. Larger capture files will require more memory and disk
space. If Wireshark runs out of memory it will crash.

1. Microsoft Windows
2. Unix/Linux

Summary
In late 1997 Gerald Combs needed a tool for tracking down network problems and wanted to learn
more about networking so he started writing Ethereal (the original name of the Wireshark project)
as a way to solve both problems.

In October, 1998 Guy Harris was looking for something better than tcpview so he started applying
patches and contributing dissectors to Ethereal.
 The list of people who have contributed to the project has become very long since then, and almost
all of them started with a protocol that they needed that Wireshark or did not already handle. So
they copied an existing dissector and contributed the code back to the team.In 2006 the project
moved house and re-emerged under a new name: Wireshark.In 2008, after ten years of
development, Wireshark finally arrived at version 1.0. This release was the first deemed complete,
with the minimum features implemented. Its release coincided with the first Wireshark Developer
and User Conference, called Sharkfest.In 2015 Wireshark 2.0 was released, which featured a new
user interface.

OmNet++

1. OMNeT++ is an extensible, modular, component-based C++ simulation library and

framework, primarily for building network simulators.
2. "Network" is meant in a broader sense that includes wired and wireless communication
networks, on-chip networks, queueing networks, and so on.
3. Domain-specific functionality such as support for sensor networks, wireless ad-hoc
networks, Internet protocols, performance modeling, photonic networks, etc., is provided
by model frameworks, developed as independent projects. OMNeT++ offers an Eclipse-
based IDE, a graphical runtime environment, and a host of other tools.
4. There are extensions for real-time simulation, network emulation, database integration,
SystemC integration, and several other functions.
5. Although OMNeT++ is not a network simulator itself, it has gained widespread popularity
as a network simulation platform in the scientific community as well as in industrial
settings, and building up a large user community.

System Requirements
1. simulation kernel library
2. NED topology description language
3. GUI for simulation execution, links into simulation executable (Tkenv)
4. command-line user interface for simulation execution (Cmdenv)
5. utilities (makefile creation tool, etc.)
6. documentation, sample simulations, etc.
7. OMNeT++ IDE based on the Eclipse platform

Summary
OverSim is an OMNeT++-based open-source simulation framework for overlay and peer-to-peer
networks, developed at the Institute of Telematics, Karlsruhe Institute of Technology, Germany.

The simulator contains several models for structured (e.g. Chord, Kademlia, Pastry) and unstructured
(e.g. GIA) peer-to-peer protocols. An example implementation of the framework is an
implementation of a peer-to-peer SIP communications network.
Research tool- OverSim provides a convenient platform for simulating large-scale complex overlay
protocols and applications. Though it can be overwhelming at first, you will realize its power when
you develop a better understanding of the tool.
 LAB EXPERIMENT 2

OBJECTIVE: To learn handling and configuration of networking hardware like RJ-45 connector,
Network cables, crimping tool, etc

BRIEF DESCRIPTION: Familiarize yourself with common networking hardware components,

such as RJ-45 connectors, network cables (Ethernet, twisted pair, etc.), crimping tools, cable testers,
and cable strippers. Understand the purpose and functionality of each hardware component in a
network setup.

STEPS FOR HANDLING NETWORK HARDWARE:

1. RJ-45 Connector Handling:

Learn the proper handling of RJ-45 connectors to prevent damage and ensure secure connections.
Understand the different parts of an RJ-45 connector, including the cable strain relief, wiring
channels, and contacts.

2. Network Cable Preparation:

Learn how to prepare network cables for termination by stripping the outer jacket using a cable
stripper. Understand the appropriate length of cable required for specific network connections.

3. Wiring Standard and Color Coding:

Study the wiring standards for Ethernet connections and the corresponding color codes for each
wire. Learn how to arrange the individual wires in the correct order before inserting them into the
RJ-45 connector.

4. Crimping Process:
Practice the crimping process using a crimping tool to secure the wires within the RJ-45
connector. Understand the proper technique for applying pressure while crimping to ensure a
reliable connection.

5. Cable Testing and Verification:

Use a cable tester to verify the continuity and proper wiring of the network cable.
Learn how to interpret the results displayed by the cable tester to identify any potential issues.

6. Hands-on Practice:
Engage in hands-on practice by creating various network connections using RJ-45 connectors,
network cables, and crimping tools.
Experiment with different cable types, lengths, and wiring standards to gain proficiency.

7. Troubleshooting:
Understand common issues that may arise during the handling and configuration of networking
hardware. Learn troubleshooting techniques to identify and resolve problems, such as loose
connections, faulty crimps, or incorrect wiring.
RJ-45 connector

Twisted pair Cable

Climping Tool
 LAB EXPERIMENT 3

OBJECTIVE: To learn and implement basic command of Computer network like PING, traceroute etc.

BRIEF DESCRIPTION: The experiment aims to familiarize participants with basic network commands
such as PING and Traceroute and provide hands-on experience in implementing these commands. The
participants will learn how to use these commands to troubleshoot network connectivity issues and
gather information about network paths.

STEPS FOR HANDLING NETWORK HARDWARE:

1. Familiarize yourself with the network hardware: Take some time to understand the different
networking devices involved, such as routers, switches, and network interface cards (NICs).
Learn about their functions and how they connect to form a network.
2. Connect the hardware: Connect the networking hardware according to the network topology you
are trying to implement. This may involve connecting computers to switches, switches to routers,
or routers to the internet service provider's modem.
3. Verify physical connections: Ensure that all cables are securely connected and properly seated.
Check for any loose connections or damaged cables that may affect network connectivity.
4. Power on the devices: Power on the networking devices in the correct order, starting from the
modem and moving through the network hierarchy (if applicable). Allow sufficient time for the
devices to boot up and establish connections.
5. Configure IP addresses: Assign IP addresses to the network devices, such as computers and
routers, using either static IP addressing or dynamic IP assignment protocols like DHCP. Ensure
that each device has a unique IP address within the network.
6. Test network connectivity using PING: Open a command prompt or terminal window on a
computer connected to the network. Use the PING command followed by the IP address or
hostname of another device on the network to check if there is a response. For example, "ping
192.168.0.1" or "ping www.example.com".
7. Perform traceroute: Traceroute is a command used to trace the route that packets take from your
computer to a target destination. In the command prompt or terminal, use the "traceroute"
command followed by the IP address or domain name of the destination. This will display the
hops (routers) the packets take to reach the destination.
8. Analyze the results: Analyze the output of the PING and traceroute commands. Look for any
 timeouts, high latency, or unexpected routes. This information can help identify network issues
and potential bottlenecks.

9. Troubleshoot network problems: If any connectivity issues arise, troubleshoot the network by
checking physical connections, verifying IP configurations, and ensuring that network devices are
functioning correctly. Use appropriate troubleshooting techniques to identify and resolve the
problems.
10. Document and learn from the experiment: Keep a record of your configurations, commands used, and
the results obtained. Take note of any lessons learned or challenges faced during the experiment. This
documentation will be helpful for future reference and knowledge enhancement.
11. EXPRIMENT SETUP : Design topology in packet tracer
 LAB EXPERIMENT 4

OBJECTIVE: Configure and implement a network using Packet Tracer.

a. Creating a First Network

b. Sending Simple Text Messages in Realtime Mode
c. Establishing a Web Server Connection Using the PC’s Web Browser

BRIEF DESCRIPTION: The client–server model is a distributed application structure in computing that
partitions tasks or workloads between the providers of a resource or service, called servers, and service
requesters, called clients. Often clients and servers communicate over a computer network on separate
hardware, but both client and server may reside in the same system. A server is a host that is running one or
more server programs which share their resources with clients. A client does not share any of its resources,
but requests a server's content or service function. Clients therefore initiate communication sessions with
servers which await incoming requests.

STEPS FOR HANDLING NETWORK:

PROGRAM NO – 4 (a)

1. Start creating a network by first selecting the End Devices. Add a Generic PC and a Generic Server
to the workspace.
2. Under Connections, select the Copper Straight-through cable (solid black line) and connect the
devices with it. The red lights on the link indicate that the connection is not working. Now, use the
Delete tool to remove the Copper Straight-through cable, and use a Copper Cross-over cable (dashed
line) instead. The lights should turn green at this point. If the mouse pointer is held over either devices,
the link status will be shown as “Up.” The network should look similar to this:
3. Click on the PC. While paying attention to the link lights, turn the power on, off, and on again.
Follow the same steps for the server. The link lights turn red when the device is off. This means
that the link is down or is not working. The link lights turn green when the device is turned back
on.
4. Try all three ways to learn about the devices. First, mouse over the devices to see basic
configuration information about them. Second, click on each device with the Select tool to show
the device configuration window, which provides several ways to configure the device. Third,
use the Inspect tool to view the tables the network device will build as it learns about the network
around it. In this example, open the ARP table. Since the devices have not been configured yet,
the ARP tables are empty. Always remember to close the windows after viewing them or they will
clutter the workspace.
5. Open the PC configuration window and change the settings using the Config tab. Change the
display name to Client and set the DNS server to 192.168.0.105. Under Interface, click
FastEthernet and set the IP address as 192.168.0.110. Packet Tracer automatically calculates
other parameters. Make sure that the Port Status box is checked. For future reference, note that
other Ethernet interface settings, such as bandwidth, duplex, MAC address, and subnet mask can
be modified using this window.
6. Go to the Desktop Tab and click on IP Configuration. Notice that the IP address, subnet mask
and DNS server can be changed here as well.
7. Open the Server configuration window and go to the Config tab. Change the display name to
Web Server. Click FastEthernet and set the IP address as 192.168.0.105. Make sure that the Port
Status is also on. Click DNS and set the domain name as www.firstlab.com. Set the IP address as
192.168.0.105 and click Add. Finally, check to make sure that the service for DNS is on.
 8. Reposition the network devices by dragging them to a new location. Add a network description by
using the “i” button on the upper right corner. Then add some text labels within the Logical Workspace
by using the Place Note tool.
9. Load a background grid using the Set Tiled Background button.
10. Save your work using the File > Save As option and create a meaningful filename.

PROGRAM NO – 4 (b)

Aim: Sending Simple Text Messages in Realtime Mode

Objective: This program illustrate the use of Realtime Mode of sending simple text message

Procedure:

1. Start by opening the file saved in the last section.

2. Notice that the file opens in Realtime Mode. Use the Add Simple PDU tool to send a simple one-time
ping message, called an echo request, to the server. The server responds with an echo reply because
all devices have properly configured IP address settings.
3. Scroll up and down the User Created Packet Window to see the different capabilities of this ping
message, including an indication that the ping was successful.
4. Toggle the PDU List Window to see a larger display of this message. One or more of these messages
can be saved as a scenario. Scenario 0 is displayed when starting. Label this first scenario with an “i”
note. Different scenarios allow the use of the same topology for experiments with different groupings
of user created packets.
5. Click New to create a new scenario. New scenarios will initially be blank.
6. Add two packets using the Simple PDU tool, a PDU from the PC to the Server and a different PDU
from the Server to the PC. Then add an “i” note describing the scenario, to complete Scenario 1. An
example is shown below:
 7. Several scenarios can be saved with a single network. Alternate between Scenario 0 and 1.
8. Now, remove Scenario 0 using the Delete button.
9. Scenario 1 is now visible. Go to the last column in the User Created Packet Window and double-click
(delete) to remove a PDU.
10. Delete the whole scenario. Notice that the scenario list went back to the default Scenario 0.

PROGRAM NO – 4(c)
Aim: Establishing a Web Server Connection Using the PC’s Web Browser
Objective: To study the concept of receiving a web page from server, requested by a client.
Conceptual Background:
The primary function of a web server is to deliver web pages on the request of clients using the Hypertext
Transfer Protocol (HTTP). This means delivery of HTML documents and any additional content that may
be included by a document, such as images, style sheets and scripts.
A user agent, commonly a web browser or web crawler, initiates communication by making a request for
a specific resource using HTTP and the server responds with the content of that resource or an error
message if unable to do so. The resource is typically a real file on the server's secondary storage, but this
is not necessarily the case and depends on how the web server is implemented.
While the primary function is to serve content, a full implementation of HTTP also includes ways of
receiving content from clients. This feature is used for submitting web forms, including uploading of
files.
Procedure:
1. Open the file saved from the previous section.
2. Click on the PC to view the configuration window.
3. Select the Desktop tab, and then click Web Browser. Type in www.firstlab.com as the URL and
click the Go button. The Packet Tracer welcome page, shown below, appears, indicating that the
web connection has been successfully established.
4. Clear the URL, type www and click Go. Since the address entered is not complete, a “Host Name
Unresolved” message appears.
5. Type 192.168.0.105 as the URL entry and click on Go. Notice that the Packet Tracer welcome
page appears again. This is because the Server IP address can also be used to establish a web
connection.
6. Close the window and try the same steps in Simulation Mode. In this mode, the user controls time,
so the network can be viewed running at a slower pace, allowing observation of the paths packets
take and inspection of packets in detail.
7. Select the PC again and go to the Web Browser in the Desktop tab. Type www.firstlab.com as
the URL again and click Go. The welcome page should not appear right away.
8. Switch to the main interface of Packet Tracer without closing the PC configuration window.
Notice that a DNS packet is added to the event list.
9. Click Auto Capture/Play or repeatedly click the Capture/Forward button until the HTTP packet
appears on the PC. Go back to the PC configuration window. The Packet Tracer welcome page is
now shown.
10. Close the PC configuration window.
 LAB EXPERIMENT 5

OBJECTIVE: Configure network devices, such as hubs and switches within a network topology using
Packet Tracer software.

BRIEF DESCRIPTION:

ALGORITHM FOR CREATING A TOPOLOGY:

1. Open your Network Topology. Once you've opened your Network Topology on Cisco Packet
Tracer, access your network and identify the components of your network, for example; Servers,
Routers, End Devices, etc.
2. Complete the cabling. Access the cables section and connect completely and correctly the cables
between the networks in order to ensure connectivity between the devices in the network using
the connections table given.
3. Using the address table still, correctly and completely configure the IP addresses on all end devices.
This can be done by accessing the desktop platform on each device and locating the IP configuration
section. The reason for doing this is to enable the devices be on the right network.
4. After configuring the addresses, you will have to test connectivity by opening a command prompt
window on the end devices and try pinging the address which the network operates on. If it gives
you a reply, it means your network was configured correctly.

The step by procedure of creating Bus topology on Cisco Packet Tracer is shown in Figures 1-
6 below

Fig 1: Simulating network devices

 Fig 2: Simulating generic switches

Fig 3: Establish the links between the network devices and generic switches
 Fig 4: Connect the links

Fig 5: Enter the IP address to each network devices

Fig 6: Network devices connected in Bus topology
 LAB EXPERIMENT 6

OBJECTIVE: Configure network topology to implement VLANs with trunking using Packet
Tracer software.

BRIEF DESCRIPTION: the objective is to design and implement a network topology that includes
VLANs (Virtual Local Area Networks) using the Packet Tracer software. VLANs allow the logical
segmentation of a network, enabling different groups of devices to be grouped together even if they
are physically connected to the same switch. Trunking, on the other hand, is used to carry multiple
VLAN traffic across a single network link.

STEPS FOR HANDLING NETWORK :

1. Launch Packet Tracer: Start the Packet Tracer software on your computer.
2. Create the network topology: Build the network topology by dragging and dropping the
required devices from the device list onto the workspace. Include switches, routers, and PCs
as needed.
3. Connect the devices: Connect the devices using appropriate cables. Use Ethernet cables to
connect PCs to switches and switches to routers.
4. Configure VLANs: Access the switch's configuration interface by double-clicking on it.
Navigate to the VLAN configuration section and create the required VLANs. Assign VLAN
IDs and names to each VLAN.
5. Assign ports to VLANs: Assign switch ports to specific VLANs. Determine which ports
belong to which VLANs and configure them accordingly. For access ports, assign a single
VLAN. For trunk ports, configure them to allow traffic from multiple VLANs.
6. Configure trunking: Identify the trunk links between switches. Access the switch's
configuration interface and configure the trunk ports. Enable trunking and specify the
allowed VLANs on the trunk links.
7. Verify configurations: Verify that the VLANs and trunking configurations are correctly
applied. Check the status of the VLANs and trunk ports to ensure they are active and
operational.
8. Test connectivity: Test the connectivity between devices within the VLANs. Ping devices in
the same VLAN to ensure communication is successful. Ping devices in different VLANs to
 verify VLAN isolation.

9. Troubleshoot and refine: If there are any connectivity issues or misconfigurations,

troubleshoot and refine the configurations. Check VLAN assignments, trunk configurations,
and port settings to resolve any problems.
10. Document the configuration: Document the VLAN and trunking configurations for future
reference. Include details such as VLAN IDs, names, assigned ports, and trunk
configurations.
11. Monitor and maintain: Monitor the network to ensure VLANs and trunking continue to
function as expected. Regularly review the configurations and make any necessary
adjustments or updates.

EXPRIMENT SETUP : Design topology in packet tracer

In Figure the R1 GigabitEthernet 0/0/1 interface is connected to the S1 FastEthernet 0/5 port. The
S1 FastEthernet 0/1 port is connected to the S2 FastEthernet 0/1 port. These are trunk links that are
required to forward traffic within and between VLANs.
To route between VLANs, the R1 GigabitEthernet 0/0/1 interface is logically divided into three
subinterfaces, as shown in Table. The below table also shows the three VLANs that will be
configured on the switches.

G0/0/1.10 10 192.168.10.1/24

G0/0/1.20 20 192.168.20.1/24

G0/0/1.30 99 192.168.99.1/24

Table : Subinterface VLAN IP Address

Step 1 : S1 VLAN and Trunking Configuration
Step 2 : S2 VLAN and Trunking Configuration
Step 3 : R1 Subinterface Configuration
Step 4 : Verify Connectivity Between PC1 and PC2
Step 5 : Router-on-a-Stick Inter-VLAN Routing Verification
 LAB EXPERIMENT 7

OBJECTIVE : Configure and implementation of a router within Network using Packet Tracer.

BRIEF DESCRIPTION : In this experiment, participants will learn how to configure a router and
connect it to other devices within a network. They will gain hands-on experience in setting up IP
addresses, configuring routing protocols, and establishing communication between different
networks.

STEPS FOR HANDLING NETWORK HARDWARE:

1. Launch Packet Tracer: Open the Packet Tracer application on your computer.
2. Set up the network topology: Create the network topology by adding devices such as PCs,
switches, and the router onto the workspace. Connect the devices using appropriate network
cables.
3. Configure IP addresses: Assign IP addresses to each device in the network, including the PCs
and the router. Ensure that the IP addresses are within the same subnet.
4. Configure router interfaces: Access the router's configuration interface by double-clicking on
it. Configure the IP addresses of the router's interfaces, usually the FastEthernet or
GigabitEthernet ports, that connect to other devices in the network.
5. Configure default gateway: Specify the default gateway IP address on the PCs in the network.
This should be the IP address of the router interface that connects to the LAN.
6. Verify connectivity: Use the built-in tools in Packet Tracer, such as the Ping or Traceroute
commands, to verify connectivity between devices in the network. Test connectivity between
the PCs and between the PCs and the router.
7. Test routing functionality: Send network traffic between different subnets connected to the
router to ensure that the routing functionality is working correctly. Verify that the router can
forward packets between different networks.
8. Implement security measures (optional): Depending on your network requirements, you may
want to configure security features such as access control lists (ACLs), firewall rules, or VPN
settings on the router.
9. Monitor and troubleshoot: Continuously monitor the network for any issues or errors. If any
connectivity or routing problems occur, use Packet Tracer's debugging tools, such as
examining routing tables or interface statuses, to troubleshoot and resolve the issues.
 10. Document the configuration: Document the router's configuration settings, including IP
addresses, routing protocols, and any security measures implemented. This documentation
will serve as a reference for future troubleshooting or network expansion.

EXPRIMENT SETUP :

Configuration on Router:

Router>enable
Router#config t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Router(config)#host satish
satish(config)#int fa0/0
satish(config-if)#ip address 1.0.0.1 255.0.0.0
 EXPERIMENT 8

OBJECTIVE : Configure network topology and implement static routing using Packet Tracer
Software.

BRIEF DESCRIPTION : In this experiment, the objective is to design and configure a network
topology using Packet Tracer software. The network will consist of multiple devices such as routers,
switches, and PCs, connected in a specific arrangement. The experiment will focus on implementing
static routing within the network. Static routing involves manually configuring the routing tables on
the routers, specifying the next hop for each destination network. This allows for explicit control over
the network traffic flow.

STEPS FOR HANDLING NETWORK :

1. Design the Network Topology:
• Identify the devices required for your network, such as routers, switches, and PCs.
• Determine the logical layout of your network, including the IP addressing scheme for
each subnet.
• Use Packet Tracer's device palette to drag and drop the necessary devices onto the
workspace.
• Connect the devices using appropriate cables and configure their interfaces with IP
addresses.
2. Configure IP Addresses:
• Access the CLI (Command Line Interface) of each device (e.g., router or PC) in
Packet Tracer.
• Configure the IP addresses for the interfaces of each device according to the logical
layout you designed.
• Use the "ip address" command followed by the desired IP address and subnet mask
to assign IP addresses to the interfaces.
3. Enable Routing:
• Determine the routing protocol or method you want to use (in this case, static routing).
• Access the CLI of each router in Packet Tracer.
• Configure static routes on each router to direct traffic to the appropriate destination
networks.
 • Use the "ip route" command followed by the destination network address, subnet
mask, and next-hop router's IP address to configure static routes.
4. Verify Connectivity:
• Use Packet Tracer's simulation mode to test network connectivity.
• Ping from one device to another to verify that the static routes are correctly
configured.
• Ensure that the ICMP (Internet Control Message Protocol) traffic is allowed through
any firewalls or security features on the devices.
5. Monitor and Troubleshoot:
• Monitor the network for any issues or errors.
• If any connectivity or routing problems arise, use Packet Tracer's logging and
debugging features to troubleshoot.
• Check the routing tables on each router to ensure that the correct static routes are
present.
6. Document the Configuration:
• Document the network topology, including the IP addresses assigned to each device
and the configured static routes.
• Take screenshots or export the configuration files from Packet Tracer for reference
purposes.
EXPRIMENT SETUP : Design network topology

In this lab, each network has two routes to reach. We will configure one route as the main route and
another route as the backup route. If the link bandwidth of all routes is the same, we use the route
that has the least number of routers as the main route. If the link bandwidth and the number of routers
are the same, we can use any route as the main route and another route as the backup route.
If we specify two routes for the same destination, the router automatically selects the best route for
the destination and adds the route to the routing table. If you manually want to select a route that the
router should add to the routing table, you have to set the AD value of the route lower than other
routes. For example, if you use the following commands to create two static routes for network
30.0.0/8, the route will place the first route to the routing table.

#ip route 30.0.0.0 255.0.0.0 20.0.0.2 10

#ip route 30.0.0.0 255.0.0.0 40.0.0.2 20

Creating, adding, verifying static routes :

Routers automatically learn their connected networks. We only need to add routes for the networks
that are not available on the router’s interfaces. For example, network 10.0.0.0/8, 20.0.0.0/8 and
40.0.0.0/8 are directly connected to Router0. Thus, we don’t need to configure routes for these
networks. Network 30.0.0.0/8 and network 50.0.0.0/8 are not available on Router0. We have to
create and add routes only for these networks.
The following table lists the connected networks of each router.
Router Available networks on local interfaces Networks available on other routers’ interfaces
Router0 10.0.0.0/8, 20.0.0.0/8, 40.0.0.0/8 30.0.0.0/8, 50.0.0.0/8
Router1 20.0.0.0/8, 30.0.0.0/8, 50.0.0.0/8 10.0.0.0/8, 40.0.0.0/8
Router2 40.0.0.0/8, 50.0.0.0/8 10.0.0.0/8, 20.0.0.0/8, 30.0.0.0/8

Router1 configuration
Router>enable
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#ip route 10.0.0.0 255.0.0.0 20.0.0.1 10
Router(config)#ip route 10.0.0.0 255.0.0.0 50.0.0.1 20
Router(config)#ip route 40.0.0.0 255.0.0.0 20.0.0.1 10
Router(config)#ip route 40.0.0.0 255.0.0.0 50.0.0.1 20
Router(config)#exit
Router#show ip route static
S 10.0.0.0/8 [10/0] via 20.0.0.1
S 40.0.0.0/8 [10/0] via 20.0.0.1
Router#

Router2 configuration
Router>enable
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#ip route 10.0.0.0 255.0.0.0 40.0.0.1
Router(config)#ip route 30.0.0.0 255.0.0.0 50.0.0.2
Router(config)#exit
Router#show ip route static
S 10.0.0.0/8 [1/0] via 40.0.0.1
S 30.0.0.0/8 [1/0] via 50.0.0.2
Router#
 LAB EXPERIMENT 9

OBJECTIVE : Configure network topology and implement dynamic routing protocol such as RIP,
OSPF etc. using Packet Tracer.

BRIEF DESCRIPTION : In this experiment, the objective is to simulate and configure a network
topology using Packet Tracer, a network simulation tool. The focus is on implementing dynamic
routing protocols like RIP (Routing Information Protocol) and OSPF (Open Shortest Path First)
within the network.
STEPS FOR HANDLING NETWORK :
1. Understand the Experiment Requirements:
• Read and familiarize yourself with the experiment guidelines, objectives, and
requirements.
• Ensure you have a clear understanding of the network topology and the dynamic
routing protocol to be implemented (RIP, OSPF, etc.).
• Take note of any specific configurations or settings mentioned in the experiment
instructions.
2. Launch Packet Tracer:
• Open Packet Tracer on your computer.
• If required, create a new project or load the existing project provided for the
experiment.
3. Design the Network Topology:
• Use the Packet Tracer workspace to design the network topology based on the
experiment requirements.
• Place the required devices such as routers, switches, and PCs onto the workspace.
• Connect the devices using appropriate network cables to establish the desired network
connectivity.
4. Configure IP Addresses:
• Assign IP addresses to the interfaces of the devices in the network.
• Ensure that each device has a unique IP address within the same network segment.
• Verify the connectivity between devices using basic connectivity tests or the "ping"
command.
5. Implement Dynamic Routing Protocol:
• Choose the dynamic routing protocol to be implemented (RIP, OSPF, etc.).
• Configure the routers to enable the chosen routing protocol on their interfaces.
• Set up the necessary parameters for the routing protocol, such as network addresses,
timers, and authentication if required.
6. Verify Routing Protocol Functionality:
• Check the routing tables on the routers to ensure that they have learned the network
routes correctly.
• Use commands like "show ip route" or "show ip ospf database" to verify the routing
information.
• Perform connectivity tests between devices to verify that routing is functioning as
expected.
7. Test Network Resilience and Adaptability:
• Introduce changes to the network topology, such as adding or removing links or
devices.
• Observe how the dynamic routing protocol adapts to the changes and updates the
routing tables accordingly.
• Verify that devices can still communicate and that the routing protocol successfully
adjusts to the network changes.
8. Document and Analyze Results:
• Record the configurations made, including IP addresses, routing protocol settings,
and any additional configurations.
• Document the observed behavior of the network, including any issues or unexpected
outcomes.
• Analyze the results to ensure that the network topology is functioning correctly and
the dynamic routing protocol is operating as intended.
9. Troubleshooting (if necessary):
• If any issues arise during the experiment, troubleshoot the network to identify and
resolve the problems.
• Use debugging tools, log files, and relevant commands to investigate and
troubleshoot the network connectivity or routing issues.
10. Finalize the Experiment:
 • Summarize the experiment results and findings in a report or as instructed by the
experiment guidelines.
• Review the configurations, documentation, and analysis to ensure accuracy and
completeness.

EXPRIMENT SETUP : Design network topology

Router0 Configuration :

Router>en
Router#conf t
Router(config)#hostname Router0
Router0(config)#int s0/3/0
Router0(config-if)#ip add 192.168.3.1 255.255.255.252
Router0(config-if)#no shut
Router0(config-if)#desc connection to Router1
Router0(config-if)#int f0/0
Router0(config-if)#ip add 192.168.0.1 255.255.255.0
Router0(config-if)#no shut
Router0(config-if)#desc connection to LAN
Router0(config-if)#exit
Router0(config)#router RIP
Router0(config-router)#netw 192.168.0.0
Router0(config-router)#netw 192.168.3.0
Router0(config-router)#no auto
Router0(config-router)#exit
Router0(config)#exit
Router0#copy run start

Router1 Configuration :
Router>en
Router#conf t
Router(config)#hostname Router1
Router1(config)#int s0/3/0
Router1(config-if)#clock rate 64000
Router1(config-if)#ip add 192.168.3.2 255.255.255.252
Router1(config-if)#no shut
Router1(config-if)#desc connection to Router0
Router1(config-if)#int s0/2/0
Router1(config-if)#clock rate 64000
Router1(config-if)#ip add 192.168.4.1 255.255.255.252
Router1(config-if)#no shut
Router1(config-if)#desc connection to Router2
Router1(config-if)#int f0/0
Router1(config-if)#ip add 192.168.1.1 255.255.255.0
Router1(config-if)#no shut
Router1(config-if)#desc connection to LAN
Router1(config-if)#exit
Router1(config)#router RIP
Router1(config-router)#netw 192.168.1.0
Router1(config-router)#netw 192.168.3.0
Router1(config-router)#netw 192.168.4.0
Router1(config-router)#no auto
Router1(config-router)#exit
Router1(config)#exit
Router1#copy run start

Router2 Configuration :
Router>en
Router#conf t
Router(config)#hostname Router0
Router2(config)#int s0/3/0
Router2(config-if)#ip add 192.168.4.2 255.255.255.252
Router2(config-if)#no shut
Router2(config-if)#desc connection to Router1
Router2(config-if)#int f0/0
Router2(config-if)#ip add 192.168.2.1 255.255.255.0
Router2(config-if)#no shut
Router2(config-if)#desc connection to LAN
Router2(config-if)#exit
Router2(config)#router RIP
Router2(config-router)#netw 192.168.4.0
Router2(config-router)#netw 192.168.2.0
Router2(config-router)#no auto
 LAB EXPERIMENT 10

OBJECTIVE : Configure a network and implement remote login of router and Management using
Packet Trace
BRIEF DESCRIPTION : The objective of this experiment is to set up a network using Packet Tracer
and configure remote login access to a router for management purposes. This experiment focuses on
enabling secure remote access to the router using protocols such as SSH (Secure Shell) and Telnet.
Additionally, it involves configuring management features like SNMP (Simple Network Management
Protocol) to monitor and manage the network devices remotely.
STEPS FOR HANDLING NETWORK :

1. Design the network topology: Start by designing the network topology using Packet Tracer.
Determine the number and types of devices required, such as routers, switches, and PCs.
Connect the devices appropriately to create the desired network structure.
2. Configure router interfaces: Access the router's CLI (Command Line Interface) in Packet
Tracer. Configure the IP addresses and subnet masks on the router's interfaces to enable
communication with other devices in the network.
3. Enable remote login protocols: In the router's CLI, enable remote login protocols such as
Telnet or SSH (Secure Shell). This will allow you to remotely access and manage the router
from other devices.
4. Configure access credentials: Set up username and password authentication for remote login.
Create a username and password combination to ensure secure access to the router.
5. Configure IP addressing on PCs: Set the IP addresses on the PCs connected to the network.
Ensure that the PCs are on the same subnet as the router interfaces to establish
communication.
6. Test remote login: From one of the PCs, open a terminal or command prompt and attempt to
remotely log in to the router using Telnet or SSH. Use the router's IP address and the
configured username and password. Verify that remote login is successful and that you can
access the router's CLI remotely.
7. Implement remote management features: Utilize Packet Tracer's remote management
features to perform various tasks on the router, such as configuring routing protocols, setting
up VLANs, or implementing access control lists (ACLs). Use the appropriate commands in
 the router's CLI to configure and manage these features.

8. Test remote management functionality: After configuring specific features on the router, test
their functionality remotely. Verify that the changes made through remote management are
properly implemented and functional.
9. Monitor and troubleshoot: Utilize Packet Tracer's monitoring tools, such as the device
console, to monitor the router's status, logs, and debug information. Use these tools to
troubleshoot any connectivity issues, configuration errors, or other problems that may arise.
10. Document the configuration: Document the entire network configuration, including the
router's remote login settings, management features, and any additional configurations made.
This documentation will serve as a reference for future maintenance, troubleshooting, or
replication of the network setup.
EXPRIMENT SETUP :

• The “line vty” command enable the telnet and the “0″ is just let a single line or session to
the router. If you need more session simultaneously, you must type “line vty 0 10“.
• The “password” command set the “Pass123” as a password for telnet. You can set your own
password.
• The “login” command authenticate and ask you the password of telnet. If you type “no login”
command, the telnet never authenticates for the password which is not a good practice in a
real network environment.