Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

Lab Assignment 2018-2019

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 15

Laboratory Experiments in Computer Networks

University of Rwanda (UR) /College o Science and Technology (CST)

School of Engineering/Department: Electrical and Electronic Engineering

Module: ETE 4163, Computer Networks

Description

Networking is one of the fastest-growing and important fields in the computer industry today.
The Internet, interconnecting millions of computers, provides a global communication and
resource-sharing infrastructure which elicits many changes in the workplace and in working
style. These changes create a growing need for small business and home networks. No
computerized office today is able to be productive without some sort of networking technology.
Working from home over a network during both business and non-business hours is now
currently standard. Realizing these various types of networks requires professionals who are
familiar with a variety of networking technologies. Students cannot be expected to compete in
the current job market unless they can demonstrate to prospective employers that they have data
communication and networking experience that goes beyond the purely theoretical.

The objective of the laboratory experiments is to fully prepare students to be able to set up or
maintain networks using current and emerging networking technologies. This document
contains two main parts: Lab assignments (1&2) and reports. Lab assignments will be done into
two different ways: using packet tracer and in labs for hands-on practice.

Reporting

You will prepare a report which summarizes the main tasks and output results of the labs. Your
report will include codes and answers to questions given in the lab protocols.

Note: You will need install the Cisco Packet Tracer software for configuration. In class, the
lecturer will guide the basics configuration. In addition to the configuration in Cisco Packet
Tracer, students will perform themselves the same configuration in the lab for hands-on
practices. Assistance will be provided if needed.

LAB 1: SMALL HOME NETWORK CONFIGURATION USING PACKET TRACER

This Lab1 recapitulates the presentation you learned in class. We will walk through the essentials
of setting up a basic home network that consists of a router and a few computers. Setting up an
actual network takes time, so we're going to use Cisco Packet Tracer. Packet Tracer is a powerful
tool that allows you to virtually simulate network setup just by interacting on your computer.

Step 1. Open Packet Tracer> for example, Go to Start. Type "Cisco Packet Tracer" and click the
application to open it.

Step 2. Physical Setup. To make a network, we first need a source such as a network hub. For
this example, we will use a router>

a) Go ahead and click the Router section and choose the 1841 Router (as example, it may
be another router from your choice).
b) Move your mouse to the white space, and click to place the router on the workspace.
c) Click End Devices and click Generic PC.
d) Move your mouse to the white space, and click once to place the PC on the workspace.
e) Repeat, and add a second Generic PC.
f) Now we are going to connect them together. Click Connections.
g) Choose the Copper Cross-Over cable.
h) Click on PC-0 and select FastEthernet.
i) Click on the other side to Router and select the FastEthernet0/0. (or
GigabitEthernet0/0)
j) Repeat and connect PC-1 to the FastEthernet interface.
k) Connect PC-1 to the Router and select FastEthernet0/1 (or GigabitEthernet0/1)

Step 3. Router configuration

1) Click Router0. A window will come up. Go to the CLI tab.


2) Type no when asked to continue with configuration dialog.
3) Type enable to go to "privileged execution mode".
4) Type config t, to enter "global configuration mode".
5) Type hostname Router0, to name the router.
6) Type enable secret class, to password protect the "privileged execution mode".
7) Configure the password for the console line. Type line con 0. Then type password cisco,
to set the password as cisco.
8) Type login to enable password prompting.
9) Type exit to return to "global configuration mode".
10) To configure the password for the "virtual terminal lines". Type in line vty 0 4. Type in
password cisco.
11) To enable the password requirement. Type in login.
12) Type exit to return to "global configuration mode".
13) We connected the computers (PCs) to the router using the FastEthernet interface. We are
going to set up the router to work with those interfaces. Type in interface (int)
GigabitEthernet0/0 (gig 0/0)
14) Type in ip address 192.168.1.1 255.255.255.0 (This will set the IP address and Subnet
mask of the first FastEthernet Interface)
15) To set a description on the router for later reference. To do this, we will type in
description Router0 FastEthernet0/0 (or GigabitEthernet0/0)
16) To start the interface, we are going to type no shutdown.
17) Type exit to return to "global configuration mode".
18) Repeat this process with FastEthernet0/1 (GigabitEthernet0/1). Type in interface
FastEthernet0/1 (or GigabitEthernet0/1).
19) This time, type ip address 192.168.2.1 255.255.255.0
20) Type in description Router0 FastEthernet0/1 (or GigabitEthernet0/1).
21) To start the interface, type no shutdown.
22) Type exit to exit from "interface configuration mode".
23) Type exit to return to "global configuration mode".
24) Hit the Enter key, and we will be back at the "privileged execution mode" when we first
started the command line.
25) To check the information that we entered into the system. To do this, type show running-
config. Continuously hit Enter to scroll down the list. You will see all the configurations
you just set. 27. We want the router to run these configurations when it starts up. To do
this, we need to copy the configuration files into the Router's NV RAM. To do this, we
type in copy running-config startup-config. Hit Enter to confirm.
The router configuration is now complete.

Step 4. PC configuration

We are now going to configure the computers to connect to the network

1) First, click on PC-0. A configuration window will come up.

2) Go to the Desktop tab and click IP Configuration.

3) We will set a Static IP.

4) Set the IP Address to 192.168.1.2

5) Set the Subnet Mask to 255.255.255.0

6) Set the Default Gateway to 192.168.1.1

7) Close the PC-0 configuration window.

8) Repeat with PC-1, except use 192.168.2.2 for the IP Address.

9) Set the Subnet Mask to 255.255.255.0

10) Set the Default Gateway to 192.168.2.1

11) Close the PC-1 configuration window.

By now, you should see green dots on the cables connected to the devices.
Step 5. Testing connectivity:

We are going to test for a valid connection by pinging PC-1 from PC-0.

1) To do this, click PC-0. Go to the Desktop tab and click Command Prompt. This acts
very similar to a DOS prompt in a Windows OS.

2) To see the details of the computer's local network, we can type in ipconfig.

3) To ping PC-1 by typing in ping 192.168.2.2 At first, the request might time-out, but you
should get a reply after that.

Step 6. Testing for Connectivity using Simulation Mode

1) At the bottom right corner, click the "stopwatch" icon to activate Simulation Mode.

2) Click Edit Filters. Clear the selections. Select only ICMP.

3) Click anywhere to get out.

4) Look at the bar of items on the right hand side. Click the Closed Envelope + button.
This will allow us to choose a source to test our network.

5) Click PC-0 and then click PC-1.

6) Click Auto Capture/Play to begin simulation. You should now see an envelope going
from PC-0 to the Router to PC-1 and back.

After that, you have successfully completed your network setup

LAB 2: BASIC NETWORK DEVICES CONFIGURATION

Learning Objectives:

Upon completion of this lab, you will be able to:

 Cable a network according to the topology diagram.


 Perform basic configuration tasks on a router.
 Configure and activate Ethernet interfaces.
 Test and verify configurations.
 Reflect upon and document the network implementation.

Scenario:

In this lab activity, you will create a network that is similar to the one shown in the below
topology diagram. Begin by cabling the network as shown in the topology diagram. You will
then perform the initial router configurations required for connectivity. Use the IP addresses that
are provided in the topology diagram to apply an addressing scheme to the network devices.
When the network configuration is complete, examine the routing tables to verify that the
network is operating properly.

I. Topology Diagram

II. Addressing Table

TASK 1: CABLE THE NETWORK.

Cable a network that is similar to the one in the Topology Diagram. The output used in this lab is
from 1841 routers. You can use any current router in your lab as long as it has the required
interfaces as shown in the topology. Be sure to use the appropriate type of Ethernet cable to
connect from host to switch, switch to router, and host to router. Be sure to connect the serial
DCE cable to router R1 and the serial DTE cable to router R2.

Answer the following questions:

a) What type of cable is used to connect the Ethernet interface on a host PC to the Ethernet
interface on a switch? ________________________

b) What type of cable is used to connect the Ethernet interface on a switch to the Ethernet
interface on a router? __________________________
c) What type of cable is used to connect the Ethernet interface on a router to the Ethernet
interface on a host PC? _________________________

TASK 2: PERFORM BASIC CONFIGURATION OF ROUTER R1.

Step 1: Establish a HyperTerminal session to router R1.

Step 2: Enter privileged EXEC (execute) mode.

Router>enable

Router#

Step 3: Enter global configuration mode.

Router#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#

Step 4: Configure the router name as R1.

Enter the command hostname R1 at the prompt.

Router(config)#hostname R1 R1(config)#

Step 5: Disable DNS lookup. Disable DNS lookup with the no ip domain-lookup command.

R1(config)#no ip domain-lookup

R1(config)#

Answer these questions:

a) Why would you want to disable DNS lookup in a lab environment?


______________________________________________________________________________
______________________________________________________________________________

b) What would happen if you disabled DNS lookup in a production environment?


______________________________________________________________________________
______________________________________________________________________________

Step 6: Configure the EXEC mode password.

Configure the EXEC mode password using the enable secret password command. Use class for
the password.
R1(config)#enable secret class

R1(config)#

Answer this question:

Why is it not necessary to use the enable password password command?


______________________________________________________________________________
______________________________________________________________________________

Step 7: Configure a message-of-the-day banner.

Configure a message-of-the-day banner using the banner motd command.

R1(config)#banner motd &

Enter TEXT message. End with the character '&'.

********************************

!!!AUTHORIZED ACCESS ONLY!!!

********************************

&

R1(config)#

Answer these questions:

a) When does this banner display?


______________________________________________________________________________

b) Why should every router have a message-of-the-day banner?


______________________________________________________________________________

Step 8: Configure the console password on the router.

Use cisco as the password. When you are finished, exit from line configuration mode.

R1(config)#line console 0

R1(config-line)#password cisco

R1(config-line)#login

R1(config-line)#exit

R1(config)#
Step 9: Configure the password for the virtual terminal lines.

Use cisco as the password. When you are finished, exit from line configuration mode.

R1(config)#line vty 0 4

R1(config-line)#password cisco

R1(config-line)#login

R1(config-line)#exit R1(config)#

Step 10: Configure the FastEthernet0/0 interface.

Configure the FastEthernet0/0 interface with the IP address 192.168.1.1/24.

R1(config)#interface fastethernet 0/0

R1(config-if)#ip address 192.168.1.1 255.255.255.0

R1(config-if)#no shutdown

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up

R1(config-if)#

Step 11: Configure the Serial0/0/0 interface. Configure the Serial0/0/0 interface with the IP
address 192.168.2.1/24. Set the clock rate to 64000.

R1(config-if)#interface serial 0/0/0

R1(config-if)#ip address 192.168.2.1 255.255.255.0

R1(config-if)#clock rate 64000

R1(config-if)#no shutdown

R1(config-if)#

Note: The interface will be activated until the serial interface on R2 is configured and activated

Answer the following question:

What is the purpose of the clock rate command?

Step 12: Return to privileged EXEC mode. Use the end command to return to privileged EXEC
mode.
R1(config-if)#end

R1#

Step 13: Save the R1 configuration. Save the R1 configuration using the copy running-config
startup-config command.

R1#copy running-config startup-config

Building configuration...

[OK]

R1#

Answer this question:

What is a shorter version of this command? ________________________

TASK 3: PERFORM BASIC CONFIGURATION OF ROUTER R2.

Step 1: For R2, repeat Steps 1 through 9 from Task 2.

Step 2: Configure the Serial 0/0/0 interface.

Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24.

R2(config)#interface serial 0/0/0

R2(config-if)#ip address 192.168.2.2 255.255.255.0

R2(config-if)#no shutdown

%LINK-5-CHANGED: Interface Serial0/0/0, changed state to up


%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up
R2(config-if)#

Step 3: Configure the FastEthernet0/0 interface.

Configure the FastEthernet0/0 interface with the IP address 192.168.3.1/24.

R2(config-if)#interface fastethernet 0/0

R2(config-if)#ip address 192.168.3.1 255.255.255.0

R2(config-if)#no shutdown

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up


%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
R2(config-if)#

Step 4: Return to privileged EXEC mode.

Use the end command to return to privileged EXEC mode.

R2(config-if)#end

R2#

Step 5: Save the R2 configuration. Save the R2 configuration using the copy running-config
startup-config command.

R2#copy running-config startup-config

Building configuration... [OK]

R2#

TASK 4: CONFIGURE IP ADDRESSING ON THE HOST PCs.

Step 1: Configure the host PC1.

Configure the host PC1 that is attached to R1 with an IP address of 192.168.1.10/24 and a default
gateway of 192.168.1.1.

Step 2: Configure the host PC2.

Configure the host PC2 that is attached to R2 with an IP address of 192.168.3.10/24 and a default
gateway of 192.168.3.1.

TASK 5: VERIFY AND TEST THE CONFIGURATIONS.

Step 1: Verify that routing tables have the following routes using the show ip route command.

You can see that both R1 and R2 have two routes. Both routes are designated with a C. These are
the directly connected networks that were activated when you configured the interfaces on each
router. If you do not see two routes for each router as shown in the following output, proceed to
Step 2.

R1#show ip route

Codes:

C - connected, S - static, R - RIP, M - mobile, B - BGP


D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1,
N2 - OSPF NSSA external type 2
E1 - OSPF external type 1,
E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C 192.168.1.0/24 is directly connected, FastEthernet0/0


C 192.168.2.0/24 is directly connected, Serial0/0/0
------------------------

R2#show ip route

Codes:

C - connected, S - static, R - RIP, M - mobile, B - BGP


D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set

C 192.168.2.0/24 is directly connected, Serial0/0/0


C 192.168.3.0/24 is directly connected, FastEthernet0/0

Step 2: Verify interface configurations.


Another common problem is router interfaces that are not configured correctly or not activated.
Use the show ip interface brief command to quickly verify the configuration of each router’s
interfaces. Your output should look similar to the following:

R1#show ip interface brief

R2#show ip interface brief


If both interfaces are up and up, then both routes will be in the routing table. Verify this again by
using the show ip route command

Step 3: Test connectivity.


Test connectivity by pinging from each host to the default gateway that has been configured for
that host.
Questions:
From the host attached to R1, is it possible to ping the default gateway? __________
From the host attached to R2, is it possible to ping the default gateway? __________
If the answer is no for any of the above questions, troubleshoot the configurations to find the
error using the following systematic process
1) Check the PCs.
Are they physically connected to the correct router? (Connection could be through a switch or
directly.) ____________
Are link lights blinking on all relevant ports? ____________

2) Check the PC configurations.


Do they match the Topology Diagram? ____________

3) Check the router interfaces using the show ip interface brief command. Are the interfaces up
and up? ____________

If your answer to all three steps is yes, then you should be able to successfully ping the default
gateway.

Step 4: Test connectivity between router R1 and R2.


From the router R1, is it possible to ping R2 using the command ping 192.168.2.2?
____________
From the router R2, is it possible to ping R1 using the command ping 192.168.2.1?
____________
If the answer is no for the questions above, troubleshoot the configurations to find the error using
the following systematic process:
1) Check the cabling.
Are the routers physically connected? ____________
Are link lights blinking on all relevant ports? ____________

2) Check the router configurations.


Do they match the Topology Diagram? ____________
Did you configure the clock rate command on the DCE side of the link? ____________
3) Check the router interfaces using the show ip interface brief command.
Are the interfaces “up” and “up”? ____________
If your answer to all three steps is yes, then you should be able to successfully ping from R2 to
R1 and from R2 to R3.

TASK 6: REFLECTION

Step 1: Attempt to ping from the host connected to R1 to the host connected to R2.
This ping should be unsuccessful.

Step 2: Attempt to ping from the host connected to R1 to router R2.


This ping should be unsuccessful.

Step 3: Attempt to ping from the host connected to R2 to router R1. This ping should be
unsuccessful. What is missing from the network that is preventing communication between these
devices?

TASK 7: DOCUMENTATION

On each router, capture the following command output to a text (.txt) file and save for your
report ( to be included in your lab report)
• show running-config
• show ip route
• show ip interface brief

LAB3: CONFIGURING WIRELESS LAN ACCESS

Scenario:
In this activity, you will configure a Linksys wireless router, allowing for remote access from
PCs as well as wireless connectivity with WPA2 security. You will manually configure PC
wireless connectivity by entering the Linksys router SSID and password.

Objectives of Lab:
 Part 1: Configure a Wireless Router
 Part 2: Configure a Wireless Client
 Part 3: Verify Connectivity

1. Topology
2. Addressing Table

Part 1: Configure a Wireless Router


 Step 1: Connect the Internet interface of WRS2 to S1.
Connect the WRS2 Internet interface to the S1 F0/7 interface.
 Step 2: Configure the Internet connection type.
a) Click WRS2 > GUI tab.
b) Set the Internet Connection type to Static IP.
c) Configure the IP addressing according to the Addressing Table.
 Step 3: Configure the network setup.
a) Scroll down to Network Setup. For the Router IP option, set the IP address to
172.17.40.1 and the subnet mask to 255.255.255.0.
b) Enable the DHCP server.
c) Scroll to the bottom of the page and click Save Settings.
 Step 4: Configure wireless access and security.
a) At the top of the window, click Wireless. Set the Network Mode to Wireless-N
Only and change the SSID to WRS_LAN.
b) Disable SSID Broadcast and click Save Settings.
C) Click the Wireless Security option.
d) Change the Security Mode from Disabled to WPA2 Personal.
e) Configure cisco123 as the passphrase.
f) Scroll to the bottom of the page and click Save Settings

Part 2: Configure a Wireless Client

 Step 1: Configure PC3 for wireless connectivity.

Because SSID broadcast is disabled, you must manually configure PC3 with the
correct SSID and passphrase to establish a connection with the router.

a) Click PC3 > Desktop > PC Wireless.


b) Click the Profiles tab.
c) Click New.
d) Name the new profile Wireless Access.
e) On the next screen, click Advanced Setup. Then manually enter the SSID of
WRS_LAN on
Wireless Network Name. Click Next.
f) Choose Obtain network settings automatically (DHCP) as the network settings,
and then
click Next.
g) On Wireless Security, choose WPA2-Personal as the method of encryption and
click Next.
h) Enter the passphrase cisco123 and click Next.
i) Click Save and then click Connect to Network.
 Step 2: Verify PC3 wireless connectivity and IP addressing configuration. The
Signal Strength and Link Quality indicators should show that you have a strong
signal. Click More Information to see details of the connection including IP
addressing information. Close the PC Wireless configuration window.

Part 3: Verify Connectivity

All the PCs should have connectivity with one another.

You might also like