0% found this document useful (0 votes)
162 views9 pages

Implement Basic Connectivity

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
162 views9 pages

Implement Basic Connectivity

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Computer Engineering Department

College of Computer and Information Systems


Umm Al-Qura University
Makkah, Saudi Arabia
2020-2021

Implement Basic Connectivity


Abdulrahman Hani Khaledi

Group 2, 439009881

Computer Networks

Report 4

Dr. Amar Jaffar

Oct 5, 2021
Introduction
In this report, we will use the Cisco IOS to perform an initial configuration to a router, including host
name, passwords, a message-of-the-day (MOTD) banner, and other basic settings, that we verified on
the last report. Next, you will apply connectivity by perform basic configuring IP addressing on switches
and PCs.

Equipment and tools


• IOS terminal
• IP configuration
• Command prompt

Addressing Table
Device Interface IP Address Subnet Mask
S1 VLAN 1 192.168.1.253 255.255.255.0
S2 VLAN 1 192.168.1.254 255.255.255.0
PC1 NIC 192.168.1.1 255.255.255.0
PC2 NIC 192.168.1.2 255.255.255.0
Table 1 Addressing tracer

1 Perform a Basic Configuration on S1 and S2


Complete the following steps on switch1 and switch2.

1.1 Configure S1 with a hostname


Click S1 and then click the CLI tab. Enter the correct command to configure the hostname as S1:
Switch> enable
Switch# configure terminal
Switch(config)# hostname S1

1.2 Configure the console and encrypted privileged EXEC mode passwords
Use cisco for the console password. Use class for the privileged EXEC mode password:
S1(config)# line console 0
S1(config-line)# password cisco
S1(config-line)# login
S1(config-line)# exit
S1(config)# enable secret class
1.3 Verify the password configurations for S1.
How can you verify that both passwords were configured correctly? Use an appropriate banner text to
warn unauthorized access. The following text is an example:
Authorized access only. Violators will be prosecuted to the full extent of the law.
S1(config)# banner motd “Authorized access only. Violators will
be prosecuted to the full extent of the law.”

1.4 Save the configuration file to NVRAM.


Which command do you issue to accomplish this step?
S1(config)# exit
S1# copy running-config startup-config

1.5 Repeat Steps 1 to 5 for S2.


Switch> enable
Switch# configure terminal
Switch(config)# hostname S2
S2(config)# line console 0
S2(config-line)# password cisco
S2(config-line)# login
S2(config-line)# exit
S2(config)# enable secret class
S2(config)# banner motd “Authorized access only. Violators will
be prosecuted to the full extent of the law.”
S2(config)# exit
S2# copy running-config startup-config
2 Configure the PCs
Configure PC1 and PC2 with IP addresses.

2.1 Configure both PCs with IP addresses.


Click PC1 and then click the Desktop tab. Click IP Configuration. In the Addressing Table above, you can
see that the IP address for PC1 is 192.168.1.1 and the subnet mask is 255.255.255.0. Enter this information
for PC1 in the IP Configuration window. Repeat steps for PC2.

Figure 1 IP Configuration

2.2 Test connectivity to switches


Click PC1. Close the IP Configuration window if it is still open. In the Desktop tab, click Command
Prompt. Type the ping command and the IP address for S1 and press Enter. Packet Tracer PC Command
Line 1.0
PC> ping 192.168.1.253

Question:

Q Were you successful? Explain.


It should not be successful because the switches have not been configured with an IP address.

3 Configure the Switch Management Interface


Configure S1 and S2 with an IP address.

3.1 Configure S1 with an IP address


Switches can be used as plug-and-play devices. This means that they do not need to be configured for
them to work. Switches forward information from one port to another based on MAC addresses.
Question:

Q If this is the case, why would we configure it with an IP address?


An IP address is required to connect to a switch remotely. The switch is managed through
VLAN1 by default.

Use the following commands to configure S1 with an IP address:


S1# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
S1(config)# interface vlan 1
S1(config-if)# ip address 192.168.1.253 255.255.255.0
S1(config-if)# no shutdown
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed
state to up
S1(config-if)#
S1(config-if)# exit
S1#

Question:

Q Why do you enter the no shutdown command?


The no shutdown command enables the interface to an active state.

3.2 Configure S2 with an IP address


Use the information in the Addressing Table to configure S2 with an IP address.
S2# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
S2(config)# interface vlan 1
S2(config-if)# ip address 192.168.1.254 255.255.255.0
S2(config-if)# no shutdown
%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed
state to up
S2(config-if)#
S2(config-if)# exit
S2#
3.3 Verify the IP address configuration on S1 and S2
Use the show ip interface brief command to display the IP address and status of all the switch ports and
interfaces. You can also use the show running-config command.
S1:

Figure 2 S1 IP address and status

S2:

Figure 3 S2 IP address and status


3.4 Save configurations for S1 and S2 to NVRAM.
Which command is used to save the configuration file in RAM to NVRAM?
S2# copy running-config startup-config

3.5 Verify network connectivity


Network connectivity can be verified using the ping command. It is very important that connectivity
exists throughout the network. Corrective action must be taken if there is a failure. Ping S1 and S2 from
PC1 and PC2.

a. Click PC1 and then click the Desktop tab.

b. Click Command Prompt.

c. Ping the IP address for PC2.


C:\>ping 192.168.1.2

Pinging 192.168.1.2 with 32 bytes of data:

Reply from 192.168.1.2: bytes=32 time<1ms TTL=128


Reply from 192.168.1.2: bytes=32 time=2ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128
Reply from 192.168.1.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.2:


Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 0ms

d. Ping the IP address for S1.


C:\>ping 192.168.1.253

Pinging 192.168.1.253 with 32 bytes of data:

Reply from 192.168.1.253: bytes=32 time<1ms TTL=255


Reply from 192.168.1.253: bytes=32 time<1ms TTL=255
Reply from 192.168.1.253: bytes=32 time<1ms TTL=255
Reply from 192.168.1.253: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.1.253:


Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
e. Ping the IP address for S2.
C:\>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:

Request timed out.


Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
Reply from 192.168.1.254: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.1.254:


Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Note: You can also use the ping command on the switch CLI and on PC2.

All pings should be successful. If your first ping result is 80%, try again. It should now be 100%. You will
learn why a ping may sometimes fail the first time later in your studies. If you are unable to ping any of
the devices, recheck your configuration for errors.

Check Result

Conclusion
As we did in the previous lab, we configure both switches with a hostname, added a password for console
and privileged EXEC mode, then we wrote appropriate banner text to warn unauthorized access, and
saved the configuration file. After that we configured both PCs and switches with IP addresses, saved
configuration, and finally, verified our network connectivity.
Table of Contents
INTRODUCTION........................................................................................................................................................ 1
EQUIPMENT AND TOOLS ......................................................................................................................................... 1
ADDRESSING TABLE ................................................................................................................................................. 1
1 PERFORM A BASIC CONFIGURATION ON S1 AND S2 ....................................................................................... 1
1.1 CONFIGURE S1 WITH A HOSTNAME................................................................................................................... 1
1.2 CONFIGURE THE CONSOLE AND ENCRYPTED PRIVILEGED EXEC MODE PASSWORDS ....................................................... 1
1.3 VERIFY THE PASSWORD CONFIGURATIONS FOR S1. ............................................................................................... 2
1.4 SAVE THE CONFIGURATION FILE TO NVRAM. ..................................................................................................... 2
1.5 REPEAT STEPS 1 TO 5 FOR S2. ......................................................................................................................... 2
2 CONFIGURE THE PCS........................................................................................................................................ 3
2.1 CONFIGURE BOTH PCS WITH IP ADDRESSES. ....................................................................................................... 3
2.2 TEST CONNECTIVITY TO SWITCHES..................................................................................................................... 3
3 CONFIGURE THE SWITCH MANAGEMENT INTERFACE ..................................................................................... 3
3.1 CONFIGURE S1 WITH AN IP ADDRESS ................................................................................................................ 3
3.2 CONFIGURE S2 WITH AN IP ADDRESS ................................................................................................................ 4
3.3 VERIFY THE IP ADDRESS CONFIGURATION ON S1 AND S2 ....................................................................................... 5
3.4 SAVE CONFIGURATIONS FOR S1 AND S2 TO NVRAM. .......................................................................................... 6
3.5 VERIFY NETWORK CONNECTIVITY ...................................................................................................................... 6
CHECK RESULT.......................................................................................................................................................... 7
CONCLUSION............................................................................................................................................................ 7

You might also like