0% found this document useful (0 votes)
61 views10 pages

Project Specifications s1 2023

Uploaded by

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

Project Specifications s1 2023

Uploaded by

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

CPIS 370

FINAL PROJECT-S1-2023
Due Date 19 Nov 2023

Group members:

Sulaiman Alahyawi 2043802

Wesam Qaffas 2139895

Rayan Alzibali 2135733

Final Project Checklist


Tasks (report submission) Submission status
date
Phase 1
Phase 2
Phase 3
Phase 4
Final draft submission(report +Packet
tracer file)
Presentation /DISCUSSION

Marking criteria

PHASE # TASKS Max. Obtained


MARKS Marks
Phase 1 Network Address 3
Planning
Phase 2 Network topology 2
design
Phase 3 Implementation 10
Phase 4 Final document 3
Presentation Presentation 2

Total 20

Project Practical Skills


This Project contains skills that relate to the following objectives:
• Interpret network diagrams.
• Select the components required to meet a network specification.
• Select the appropriate media, cables, ports, and connectors to connect switches
to other network devices and hosts.
• Perform and verify initial switch and router configuration tasks.
• Describe how VLANs create logically separate networks and the need for
routing between them.
• Configure, verify, and troubleshoot VLANs.
• Configure, verify, and troubleshoot inter-VLAN routing.

Network diagram:
The Diagram shows the network layout at Building. Analyze, Investigate, Plan,
Design and implements and test the underlying network as per requirements specified
in Blue Print (Architecture Diagram). The building is basic reference for the network
design.
There is PEK University. They have currently many functional departments ( HR, IT
etc.) which are in the same building A. Each floor in building A has users from
different departments. The servers of the university and few users from HR
department are in Building B.
The users on each floor from each department are divided according to table 1 below:
Floor Department No of users Building

1st Students 300 A


Student Affairs 14
2nd Faculty 42
Students 90
IT Tech 15
3rd Faculty 62
Admin 30
IT Tech 14
1ST Server 4 B
HR 20
BUILDING A

3rd Floor BUILDING B


Servers
Room
2nd Floor
HR

1st Floor

Figure 1: Network Layout

Phase 1:

Network Address Planning

Table: 1 Calculate subnet addresses using VLSM and record them along with the
range for each subnet. You could use the following IP address 172.30.0.0/23.
Table 2
VLAN VLAN name No of Subnet address Subnet mask First usable Last usable Broadcast
number hosts address address address
required
VLAN 10 Student 390 172.39.0.0/23 255.255.254.0 172.39.0.1 172.39.1.254 172.39.1.255
VLAN 20 Faculty 104 172.39.2.0/25 255.255.255.128 172.39.2.1 172.39.2.126 172.39.2.127
VLAN 40 Admin 30 172.39.2.192/27 255.255.255.224 172.39.2.193 172.39.2.222 172.39.2.223
VLAN 30 IT TECH 29 172.39.2.224/27 255.255.255.224 172.39.2.225 172.39.2.254 172.39.2.255

VLAN 50 HR 20 172.39.3.0/27 255.255.255.224 172.39.3.1 172.39.3.30 172.39.3.31


VLAN 60 Student 14 172.39.3.32/28 255.255.255.240 172.39.3.33 172.39.3.46 172.39.3.47
Affairs
VLAN 70 Server 6 172.39.3.48/29 255.255.255.248 172.39.3.49 172.39.3.54 172.39.3.55
VLAN 99 Management 35 172.39.2.128/26 255.255.255.192 172.39.2.129 172.39.2.190 172.39.2.191

Phase 2:
Task 1: Design the network topology for the company using the Simulator Packet
tracer.
Given below is incomplete topology as many connections, devices, user end
devices are missing. Also few device connectivity is wrong.
You need to trouble shoot the given topology and then complete the topology.

Task 2: Select devices


Below is the reference table, shows devices and other equipment’s that
is used in the network topology.
 Number of switches.
 Number of end devices (like Printer, Laptops, PCs) also calculated.
 Features of cables are considered for
cable selection. Table: 3 Required devices

Device Quantity
Switch 15

Router 1
Twisted pair: cross 13
over cable
Straight through cable 18

Fiber optic cable 0

Servers 3

Serial cable(optional) 0

Wireless access 0
points(if requirement)
PCs/laptops 12

Resources (printer, 1
scanner, projector
etc.)
Phase 3:
Task 1: Implementation
Configure the devices in the network using the Simulator Packet Tracer.

• Basic configurations(on switch and router)


• VLAN Configurations (on switches)
• Intervlan routing (on Router)
The topology will be provided with few configurations done on selected Devices. You
need to complete the configurations and make the successful communication between
all devices.

The following configurations are supposed to be done on the devices in the network
topology.
Table 4
Device VLAN(s) Management Ports Ports
IP Address assignment assignment
(access (trunk mode)
mode)
Student_S1  Student 172.39.2.131 Fa0-fa0/23 Fa0/1
Management
Student_S2  Student 172.39.2.132 Fa0-fa0/23 Fa0/1
Management
Student_S3  Student 172.39.2.133 Fa0-fa0/23 Fa0/1
Managemen
t
IT TECH_S1  IT Tech 172.39.2.134 Fa0-fa0/23 Fa0/1
Management
Student_Affair_S1  IT Tech 172.39.2.135 Fa0-fa0/5 Fa0/1
 Student_Affair Fa0/6-fa0/24
Managemen
t
Faculty_S1 Faculty 172.39.2.136 Fa0-fa0/23 Fa0/1
Management
Faculty_S2 Faculty 172.39.2.137 Fa0-fa0/23 Fa0/1
Management
Faculty_S3 Faculty 172.39.2.138 Fa0-fa0/17 Fa0/1
Admin Fa0/18-
fa0/24
Managemen
t
ADMIN Admin 172.39.2.139 Fa0- fa0/23 Fa0/1
Management
Basic configurations:
All Switches and PEK Router:
• Hostname of the device (main switches and PEK router ; change the
hostname to match the display name)
• Console password on switches as "cisco"(only main switches in both
buildings)
• Privileged mode password as "project"(only main switches in both buildings)
• Login Banner on BUILDING A_SWITCH and BUILDING B_SWITCH as
“Welcome to PEK Company. Unauthorized access to devices is prohibited " 
Save all configurations to NVRAM. (copy run start command)

Router: Configure router with InterVlan routing concept.


Sub interface are created. (Already done)
Encapsulation of the sub interfaces. (Already done)
IP address configuration on sub interfaces (required to be done) VLANs
(on switches):
• All required VLANs are supposed to be configured on switches.
• Management VLAN should be configured on all switches.  Management IP
address is to be configured on all devices.
Note: you are required to configure only switches highlighted in table 4.but other
switches need to be troubleshoot if VLANs configured on them are correct?

User End devices configurations:


• All user end devices are to be configured with IP address according to its
subnet address.
Describe how VLANs create logically separate networks and the need for routing
between them.

VLANs create separate networks logically rather than physically by grouping


devices based on their network requirements and needs, Inter-VLAN routing
enables communication between devices in different VLANs by forwarding
packets based on their Layer 3 information, such as IP addresses. This improves
network security, optimal performance, and logical segmentation of network
resources.

Task 2: Troubleshooting
Troubleshoot the network topology and state your findings in the table.
Table 5
S.no Device Problem Solution How the problem effects the
business

1 Student_S1 VLANs not configured Configure VLANs: Missing VLAN configuration may
- Student fa0/1 prevent students from accessing
- Management fa0/1 necessary resources.
2 Student_S2 VLANs not Configure VLANs: Missing VLAN configuration may
configured - Student fa0/1 prevent students from accessing
- Management fa0/1 necessary resources.
3 IT TECH_S1 VLANs not Configure VLANs: Missing VLAN configuration may
configured - IT Tech fa0/1 limit the IT Tech's access to necessary
- Management fa0/1 resources.
4 IT TECH_S2 VLANs not Configure VLANs: Missing VLAN configuration may
configured - IT Tech fa0/1 limit the IT Tech's access to necessary
- Management fa0/1 resources.
5 ADMIN 1- Wrong Ports assignments: 1- Any access or trunk
assignment assignments not following the
- access mode for intended configuration may lead to
Fa0/2- fa0/23 connectivity and authorization
2- VLANs not issues for administration purposes.
configured -trunk mode for
Fa0/1

Configure VLANs: 2- Misconfigured VLANs may


result in limited or incorrect access
- Admin fa0/1 for administrative tasks.
- Management fa0/1
Task 3: Testing the connectivity
Check the accessibility from all departments to the server in the other building.
And also Administrator should be able to remotely access the network devices i.e.
Switches and routers (in building A) from building B.
Table 6:
Source Device Destination device Connectivity
status(successful OR no)
PC1 PC_STUDENT AFFAIR successful
PC1 DNS SERVER successful
PC1 Laptop_HR successful
PC1 PC2 successful
Laptop_IT TECH HTTP SERVER successful
Laptop_IT TECH Laptop2_HR successful
Laptop_IT TECH Laptop_ADMIN successful
Laptop_IT TECH PC3 successful

Phase 4: Final document

Write a brief report about what have you done in respect to the above
three phases. Max 1 page.

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

In Phase 1 of the project, the network address planning was performed using the
VLSM (Variable Length Subnet Mask) technique. The given IP address range of
172.39.0.0/23 was utilized to calculate subnet addresses. Each subnet address was
recorded in conjunction with its comparing extend. This information was then used
within the subsequent phases to plan and configure the network.
In Phase 2, Task 1 involved designing the network topology for the company using
the Simulator Packet Tracer. The initial topology given was incomplete, with missing
connections, devices, and user end devices. A few device connectivity was also
incorrect. The objective was to create a complete and accurate topology that reflects
the company's network infrastructure.

Task 2 in Phase 2 required selecting the appropriate devices and equipment for the
network topology. The number of switches and end devices (such as printers, laptops,
and PCs etc..) were calculated. Moreover, the features of the cables utilized in the
network were taken into consideration.

Phase 3 focused on the implementation of the network. Task 1 involved configuring


the devices using the Simulator Packet Tracer. This included performing basic
configurations on the switches and router, configuring VLANs on the switches and
setting up inter-VLAN routing on the router. The objective was to set up successful
communication between all devices.

The basic configurations included setting the hostname and console password on the
main switches and PEK router (hostname only), as well as a privileged mode
password. A login banner (MOTD message ) was also configured on the BUILDING
A_SWITCH and BUILDING B_SWITCH devices. All configurations are saved in
NVRAM on all switches and routers .

For the PEK router, sub -interfaces were already created and encapsulated. However,
IP address configuration on the sub-interfaces was required. VLANs were configured
on the switches, with a check to troubleshoot any potential issues with VLAN
configurations on other switches .

User end devices were configured with IP addresses according to their respective
subnet addresses.

Task 2 in Phase 3 involved troubleshooting the network topology and documenting


any findings in a table. This is done to identify and resolve any issues or errors that
may affect network performance or connectivity.

Finally, in Task 3 of Phase 3, connectivity was tested. Verified that all departments
can access the server in the other building. It is also confirmed whether the
administrator can remotely access the network devices (Switches) in Building A from
Building B.

What problems were encountered and how were they solved:

1 - A message in the CLI of the switch "%CDP-4-NATIVE_VLAN_MISMATCH:


Native VLAN mismatch discovered on FastEthernet0/4 (1), with Switch
FastEthernet0/1 (99)."
The problem is caused by a native VLAN mismatch between FastEthernet0/4 with
native VLAN = 1 on one switch and FastEthernet0/1 with native VLAN = 99 on
another switch.

To solve these problems, the native VLAN in both ports that connect the two switches
must be equal (FastEthernet0/4 (99) and FastEthernet0/1 (99)).

2 - When try to access the switch remotely, this message appears "[Connection to
172.39.2.130 closed by foreign host]"

This issue is caused by not setting the remote access password for the Switch. At least
a password must be set for remote access on the Switch.

You might also like