1

The Ministry of Education and Science of Ukraine

Odessa National Academy of Telecommunications

them. AS Popov
______________________________________________________________

DEPARTMENT OF COMMUNICATION NETWORK

GUIDELINES
For laboratory work number 1

regulatory discipline

"Сomputer networks"
 
educational and vocational training programs
in the direction of higher education

0924 - "TELECOMMUNICATIONS"

Odessa -2019
 2

Laboratory work №1

Analysis of TCP/IP network configuration and status using Cisco

Packet Tracer software simulator

1 Objectives

1.1 Study of methods for configuring hosts on a TCP/IP network.

1.2 Acquisition of practical skills in the software shell Cisco Packet Tracer.
.
2 Key points

2.1 Cisco Packet Tracer Input Interface

This initial interface contains ten components. If you are unsure of what a particular
interface item does, move your mouse over the item and a help balloon will explain the item.
The Cisco Packet Tracer input interface contains ten components listed in Table 1 (fig.1).

Table 1 – Cisco Packet Tracer Input Interface Components

This bar provides the File, Edit, Options, View, Tools, Extensions,
and Help menus. You will find basic commands such as Open, Save,
1 Menu Bar
Save as Pkz, Print, and Preferences in these menus. You will also be
able to access the Activity Wizard from the Extensions menu.
This bar provides shortcut icons to the File and Edit menu commands.
This bar also provides buttons for Copy, Paste, Undo, Redo, Zoom,
the Drawing Palette, and the Custom Devices Dialog. On the right,
2 Main Tool Bar
you will also find the Network Information button, which you can use
to enter a description for the current network (or any text you wish to
include).
This bar provides access to these commonly used workspace tools:
Select, Move Layout, Place Note, Delete, Inspect, Resize Shape,
3 Common Tools Bar
Add Simple PDU, and Add Complex PDU. See "Workspace Basics"
for more information.
You can toggle between the Physical Workspace and the Logical
Workspace with the tabs on this bar. In Logical Workspace, this bar
also allows you to go back to a previous level in a cluster, create a New
Logical/Physical
Cluster, Move Object, Set Tiled Background, and Viewport. In
4 Workspace and
Physical Workspace, this bar allows you to navigate through physical
Navigation Bar
locations, create a New City, create a New Building, create a New
Closet, Move Object, apply a Grid to the background, Set
Background, and go to the Working Closet.
This area is where you will create your network, watch simulations, and
5 Workspace
view many kinds of information and statistics.
You can toggle between Realtime Mode and Simulation Mode with the
tabs on this bar. This bar also provides buttons to Power Cycle Devices
Realtime/Simulation
6 as well as the Play Control buttons and the Event List toggle button in
Bar
Simulation Mode. Also, it contains a clock that displays the relative
Time in Realtime Mode and Simulation Mode.
7 Network This box is where you choose devices and connections to put into the
 3
workspace. It contains the Device-Type Selection Box and the Device-
Component Box
Specific Selection Box.
This box contains the type of devices and connections available in
Device-Type
8 Packet Tracer. The Device-Specific Selection Box will change
Selection Box
depending on which type of device you choose.
Device-Specific This box is where you choose specifically which devices you want to
9
Selection Box put in your network and which connections to make.
This window manages the packets you put in the network during
User Created Packet
10 simulation scenarios. See the "Simulation Mode" section for more
Window*
details.

You can freely resize the User Created Packet Window (UCPW) by placing the cursor
near the left edge of the window (it will turn into a "resize" cursor) and then drag the cursor left
or right. You can hide the window from view by dragging the edge all the way to the right. When
the UCPW is hidden, you can bring it back by placing the cursor on the edge (notice when the
resize cursor appears) and then dragging the edge back.
 4
2.2 Connections/Links

Packet Tracer supports a wide range of network connections. Each cable type can only be
connected to certain interface types.

Cable Type Description

Console connections can be made between PCs and routers or switches.
Certain conditions must be met for the console session from the PC to
work: the speed on both sides of the connection must be the same, the data
Console bits must be 7 for both or 8 for both, the parity must be the same, the stop
bits must be 1 or 2 (but they do not have to be the same), and the flow
control can be anything for either side.
This cable type is the standard Ethernet media for connecting between
devices that operate at different OSI layers (such as hub to router, switch
Copper to PC, router to hub). It can be connected to the following port types: 10
Straight-through Mbps Copper (Ethernet), 100 Mbps Copper (Fast Ethernet), and 1000
Mbps Copper (Gigabit Ethernet).
This cable type is the Ethernet media for connecting between devices that
operate at the same OSI layer (such as hub to hub, PC to PC, PC to
Copper Cross- printer). It can be connected to the following port types: 10 Mbps Copper
over (Ethernet), 100 Mbps Copper (Fast Ethernet), and 1000 Mbps Copper
(Gigabit Ethernet).
Fiber media is used to make connections between fiber ports (100 Mbps or
Fiber 1000 Mbps).
Phone line connections can only be made between devices with modem
ports. The standard application for modem connections is an end device
Phone (such as a PC) dialing into a network cloud.
Coaxial media is used to make connections between coaxial ports such as a
Coaxial cable modem connected to a Packet Tracer Cloud.
Serial connections, often used for WAN links, must be connected between
serial ports. Note that you must enable clocking on the DCE side to bring
up the line protocol. The DTE clocking is optional. You can tell which end
of the connection is the DCE side by the small “clock” icon next to the
Serial port. If you choose the Serial DCE connection type and then connect two
DCE and DTE devices, the first device will be the DCE side and the second device will be
automatically set to the DTE side. The reverse is true if you choose the
Serial DTE connection type.

2.3 Important Terminology

1. ICMP ping: command consisting of an echo request message from one device to another,
and the returning echo reply.
2. IP address: 32-bit address assigned to devices as identification in the network.
3. Ethernet: one of the most common LAN standards for hardware, communication and
cabling.
4. Fast Ethernet Interface: 100 Mbps Ethernet port. In Packet Tracer, a GUI may be used to
configure such interfaces.
5. OSI model: 7-layer framework for looking at network protocols and devices, consisting
of the application, presentation, session, transport, network, data link, and physical
layers.
 5
6. PDU: protocol data unit, a grouping of data appropriate to a given layer in the OSI
model.
7. Packets: OSI Layer 3 protocol data units. Represented by envelopes in Packet Tracer
Simulation Mode.
8. Device Tables: includes ARP, switching, and routing tables. They contain information
regarding the devices and protocols in the network.
9. ARP Table: Address Resolution Protocol (ARP) table, stores pairings of IP Addresses
and Ethernet MAC addresses.
10. Scenario: one topology with a set of PDUs placed in the network to be sent at specific
times. Using different scenarios, experiment with different combinations of packets using
the same base topology.

2.4 Creating Devices

To place a device onto the workspace, first choose a device type from the Device-Type
Selection box. Then, click on the desired device model from the Device-Specific Selection box.
Finally, click on a location in the workspace to put your device in that location. If you want to
cancel your selection, press the Cancel icon for that device. Alternatively, you can click and
drag a device from the Device-Specific Selection box onto the workspace. You can also click
and drag a device directly from the Device-Type Selection box and a default device model will
be chosen for you.
To quickly create many instances of the same device, press and hold the Ctrl button,
click on the device in the Device-Specific Selection box, and then release the Ctrl button. The
device is now locked and you can click on the workspace multiple times to add multiple copies
of the device. Cancel this operation by pressing the Cancel icon for that device. To duplicate
devices, you can press and hold the Ctrl button and then drag a device on the workspace or
select the devices and then use the Copy and Paste buttons.

2.5 Adding Modules

Most Packet Tracer devices have modular bays or slots into which you can insert
modules. In the workspace, click on a device to bring up its configuration window. By default,
you will be in the Physical Device View sub-panel of the device. An interactive picture of the
device is on the right of the panel, and a list of compatible modules is on the left. You can resize
the picture with the Zoom In, Original Size, and Zoom Out buttons. You can also resize the
entire configuration window by dragging its borders with the mouse. Alternatively, you can
undock the window so that you can move it around and freely resize it. You can browse (by
clicking) through the list of modules and read their description in the information box at the
bottom. When you have found the module you want to add, simply drag it from the list into a
compatible bay on the device picture. You can remove a module by dragging it from the device
back into the list.
You must turn off a device (by clicking its power button) before you can add or remove
modules, and you should turn the device back on after you are done.

2.6 Making Connections

To make a connection between two devices, first click the Connections icon from the
Device-Type Selection box to bring up the list of available connections. Then click the
appropriate cable type. The mouse pointer will change into a "connection" cursor. Click on the
first device and choose an appropriate interface to which to connect. Then click on the second
device and do the same. A connection cable will appear between the two devices, along with link
lights showing the link status on each end (for interfaces that have link lights). If you made a
 6
mistake by connecting to an incorrect interface or you want to change the connection to a
different interface, click on the link light near the device to unplug the connection from the
device. Click on the device again and select the desired interface to reconnect the device. For a
full list of connections supported in Packet Tracer, please read the "Connections/Links" help
page.
To quickly make many connections of the same type, press and hold the Ctrl button,
click on a cable type in the Device-Specific Selection box, and release the Ctrl button. The
connection cursor is now locked and you can repeatedly make the same connection type between
devices. Cancel this operation by pressing the Cancel icon for the cable type.

3 Key questions

1. Describe the components of the Cisco Packet Tracer input interface.

2. What is the purpose of the Cisco Packet Tracer interface workspace?
3. Specify the functionality of the logical and physical workspaces of the Cisco Packet
Tracer interface.
4. What is the purpose of Simulation mode?
5. How to create a device in the Cisco Packet Tracer workspace?
6. What needs to be done to create multiple copies of devices?
7. How to select multiple devices in the Cisco Packet Tracer workspace?
8. How to remove a device or multiple devices in the Cisco Packet Tracer workspace?
9. Describe the types of cables used to connect devices on the network.
10. What are the conditions for the correct connection of devices using a console cable?
11. Describe the type of connection Serial
12. Describe the type of connection Copper Straight-through
13. Describe the type of connection Copper Cross-over.

4 Homework

4.1 Learn, using the recommended literature, as well as this methodological manual, the
main components, areas and modes of operation of the Cisco Packet Tracer input interface, as
well as the types of connections used to create the network topology.
4.2. Prepare for an interview on key questions of p.3.
4.3 Make a plan for the implementation of laboratory work, guided by paragraph 5.

5 Lab assignment

5.1 Creating a First Network

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:
 7

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.
 8
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.

Congratulations on creating your first network!

5.2 Sending Simple Test Messages in Realtime Mode

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:
 9

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 Scena-
rio 0.

Congratulations on being able to send and organize simple test messages in Realtime Mode!
 

5.3 Establishing a Web Server Connection Using the PC’s Web Browser

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 (packet tracing!).
 10
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.

Congratulations on successfully establishing a web server connection!

5.4 Capturing Events and Viewing Animations in Simulation Mode

1. Open the previously saved file.

2. In Realtime Mode, send a simple PDU from the PC to the Server.
3. Delete the PDU by using the method learned in the previous section.
4. Switch to Simulation Mode.
5. Click Edit Filters and click All/None to uncheck all fields. Then click ICMP to only view
ICMP packets in the animation.
6. Add a simple PDU from the PC to the Server. Notice that the newly created PDU is
added to the User Created PDU List. This packet has been captured as the first event in
the event list and a new packet icon (envelope) appears in the workspace. The eye icon to
the left of the event list indicates that this packet is currently displayed.
7. Click the Capture/Forward button once. This simulates a network sniffing program,
capturing the next event that occurs on the network. Note that after clicking
Capture/Forward, the packet in the workspace moves from one device to another (this is
the ICMP echo request message from the PC to the Server). Another event is added in the
event list – this reflects the change in the workspace. The first time through an animation,
the meaning of the Capture/Forward is capture; after resetting the simulation, the
meaning is forward.
8. Adjust the speed of the animation by dragging the Play Speed slider to the right making it
go faster. Dragging the speed slider in the opposite direction (to the left) will slow down
the animation.
9. Click the Capture/Forward button a second time. This captures the next network event
(this is the echo reply from the Server to the PC, shown as successful with a green check
mark on the envelope).
10. Click Capture/Forward button again. The Server has already sent an echo reply to the PC
therefore, there are no more ICMP events left to capture.
 11

11.

Congratulations on successfully capturing events and viewing animations in Simulation

Mode!

5.5 Looking Inside Packets in Simulation Mode

1. Continuing from the last activity, click Reset Simulation. This clears the entries in the
event list except for the original packet.
2. Select the packet envelope on the workspace to show the PDU Information window like
the one shown in the screenshot below. This window contains the OSI Model tab, which
shows how the packet is processed at each layer of the OSI model by the current device.
Close this window, noting that this packet is indicated in the event list by the eye icon.
The whole row in the event list is also highlighted. Clicking on the color square in the
Info column is equivalent to clicking directly on the packet envelope (try it!).
 12

3. Use the Next Layer and Previous Layer buttons to see details of the packet processing at
the relevant OSI layers. Note that only the Out Layers can be viewed in the case of this
original echo request message.
4. Click on the Outbound PDU Details tab. This tab shows exactly what makes up the PDU
headers. It is organized into header type and the individual fields in each header.
5. Close the PDU Information window. Click on Capture/Forward button once.
6. Click on the packet in the workspace again to open the PDU Information window. Notice
that this time, information regarding both the In Layers and Out Layers can be viewed.
7. Click on the Inbound PDU Details tab. This shows the details of the inbound echo
request packet from the PC to the Server. The Outbound PDU Details tab, shows similar
information, but for the echo reply packet from the Server to the PC.
8. Click on Reset Simulation again. Now click on Auto Capture/Play. The echo request and
echo reply are automatically captured. Click on the Back Button to rewind the animation
one step at a time. Now click on the Capture/Forward button to forward the packet
through the animation. Note the change in the event list and the workspace. Remember
that at any time, a PDU Information Window can be opened by clicking directly on the
envelope on the workspace, or by clicking the Info column in the Event List.
9. Click on the Back Button twice to rewind the animation. Now click Auto Capture/Play
and the packet animation will automatically occur.

Congratulations on being able to manipulate the Play Controls and PDU Information
Window to understand more about packet processing details!
 13
5.6 Viewing Device Tables and Resetting the Network

1. Open the file saved from the previous section.

2. Open the ARP Tables for both devices by clicking them with the Inspect tool. The ARP
tables always appear on the same spot. Reposition them to make them both visible. You
can also resize the tables for better viewing.

In Realtime Mode, send a simple PDU from the PC to the Server. Notice that the ARP tables
are filled in automatically, as shown here:

3. Delete the PDU using the method covered in the previous sections. Notice that the entries
in the ARP tables are NOT cleared. ARP entries for both devices have already been
learned. Deleting the user created PDUs does not reset events what has already occurred
in the network.
4. Click Power Cycle Devices. ARP tables are cleared because the Power Cycle Devices
button turns the devices off and back on again therefore, losing temporary information
like the ARP table entries.
5. Go to Simulation Mode. In the event list filters, make sure that ICMP and ARP are
checked so that you can view ICMP and ARP packets in the animation.
6. Create a new simple PDU from the Server to the PC.
7. Notice that since the devices were power cycled earlier, the ARP tables are empty. ARP
request packets need to be issued before the ICMP ping packets, so that the devices in the
network can learn about each other. Click on Auto Capture/Play to watch the animation.
8. Click Reset Simulation. Notice that even though the event list is cleared (except for the
user created PDU), the ARP tables remain full. Click Auto Capture/Play. This time, since
the ARP tables are full, there are no new ARP packets issued.
9. Click Power Cycle Devices. Doing so will empty the tables. Notice that new ARP request
packets appear automatically in the event list.
 14
Congratulations! You can now view device tables, reset a simulation, and reset the
network!

5.7 Reviewing Your New Skills

 Single-clicking on the Delete button removes the entire scenario including all the PDUs
associated with it.
 Double-clicking on (delete) in the far right column in the PDU List window deletes
individual PDUs.
 The Reset Simulation button clears all entries in the Event List, except for User Created
PDUs, and allows the animation to restart. This, however, does not reset the device
tables.
 The Power Cycle Devices button turns all of the devices in the network off and on so the
tables that the devices built are lost along with configurations and other information not
saved.
 Saving work periodically prevents lost configurations and state changes in the network.

Congratulations on being ready to build and analyze many different networks in Packet
Tracer! Be aware that there are many other features that were not covered in this lab.

6 Protocol content

The protocol must provide the title of this work, its purpose, the results of the homework,
the results of the laboratory assignment, the conclusions.
 15

Figure 1 – Cisco PT interface