Download What are the Advantages and Disadvantages of a Policy

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Wake-on-LAN wikipedia , lookup

Remote Desktop Services wikipedia , lookup

Computer network wikipedia , lookup

Wireless security wikipedia , lookup

Zero-configuration networking wikipedia , lookup

Lag wikipedia , lookup

Distributed firewall wikipedia , lookup

Spanning Tree Protocol wikipedia , lookup

Network tap wikipedia , lookup

Telephone exchange wikipedia , lookup

Cracking of wireless networks wikipedia , lookup

Airborne Networking wikipedia , lookup

List of wireless community networks by region wikipedia , lookup

Piggybacking (Internet access) wikipedia , lookup

Virtual LAN wikipedia , lookup

Transcript
Analytical summary
(ENG653) (2013/2014)
427951
427951 ENG653
Table of Contents
1.0
Introduction ........................................................................................................................................... 2
2.0
Network Topology .................................................................................................................................. 2
3.0
Implementation and Requirements ........................................................................................................ 4
METHODOLOGY .....................................................................................................................................................................4
DESIRABLE FEATURES ............................................................................................................................................................4
FUTURE REQUIRMENTS AND REJECTED REQUIREMENTS .....................................................................................................4
4.0 Conclusion ................................................................................................................................................... 5
PAGE 1
427951 ENG653
1.0 Introduction
In this short report I will be discussing the proposed network design, analyzing its key strengths and
weaknesses, the method used to implement the design of the proposed multilayer switched network.
2.0 Network Topology
The network topology chosen has a router with access to the internet connected to two core switches
which are in turn connected to five access switches. The two core switches are also connected to both
the customer server and the company server, as shown in figure 2.1. The five access switches can only
access either the customer server or company server once permitted by the core switches. Two core
switches are needed in the topology as to reduce risk of network failure, as one will act as a backup
core should the other fail.
Figure 2.1
The access switches provide ports to each department in order to give them access to a server
depending on the department’s VLAN ID. The IDs were carefully distributed between departments as
shown in Figure 2.2.
PAGE 2
427951 ENG653
Figure 2.2
Switches
Accounting
Employees
VLAN 40
Administrative
VLAN 50
Accounting
Partners
VLAN 30
Customer
Service
Employees
VLAN 60
Meeting
Room
VLAN 70
Total
Switch 3
12
6
2
20
Switch 4
8
4
6
18
Switch 5
6
4
4
6
Switch 6
3
2
2
10
Switch 7
12
6
2
Total
41
22
16
20
3
20
20
16
3
98
Each access switch is connect to both core switch 1 and core switch 2 through link aggregation to
increase reliability and reduce link failure. The servers are connected directly to the core switches,
this is to prevent departments from accessing the servers without the correct permission.
After distributing the departments between the access switches, IP allocation was plotted out to
organize and give a clear understanding which IP addresses the departments and VLANs will utilize.
Figure 2.3
VLAN Name
VLAN
Core1
Core2
Virtual VLAN
IP Allocation
Customer_Server
10
10.1.10.1
10.1.10.2
10.1.10.3
Server IP Add 10.1.10.4
Company_Server
20
10.1.20.1
10.1.20.2
10.1.20.3
Server IP Add 10.1.20.4
Accounting_Partners
30
10.1.30.1
10.1.30.2
10.1.30.3
User IP Add 10.1.30.4-250
Accounting_Employees
40
10.1.40.1
10.1.40.2
10.1.40.3
User IP Add 10.1.40.4-250
Adminstrative_Support_Employees
50
10.1.50.1
10.1.50.2
10.1.50.3
User IP Add 10.1.40.4-250
Customer_Service
60
10.1.60.1
10.1.60.2
10.1.60.3
User IP Add 10.1.40.4-250
Meeting_Room
70
10.1.70.1
10.1.70.2
10.1.70.3
User IP Add 10.1.40.4-250
PAGE 3
427951 ENG653
3.0 Implementation and Requirements
Firstly, I will discuss the network design’s implementation core requirements. Thirteen steps were
taken to ensure that the network’s core requirements were met.
METHODOLOGY
The project began by enabling STP on all devices, STP will safeguard a network that uses redundant
paths from loops which can be detrimental to a network.
The router, the core switches and the access switches were then connected, the core switch was
connected to the router and the core switch was physically connected to the access switches using
redundant paths. The core switches would also be connected using trunking.
The customer server was then implemented by creating a VLAN which would later connect to the core
switches, this is the same scenario for the company server, and the only difference would be that the
VLAN would have a separate ID. Once the customer server and company server have their VLANs set
up, implementation of the VLANs on each access switch for accounting partners, accounting
employees, administrative support employees, meeting room and customer service were
administered. The access switches were then configured using terminal to connect to the core as
trunk ports.
On the router device, the next step was to configure the ISP for the entire network by configuring the
loopback interface. At this stage, it was found through testing, the access switches could not ping the
loopback but it could be pinged from the core switch.
DESIRABLE FEATURES
In the process of designing the network, desirable features were also discussed and some
implemented. In particular, defining ACL to filter network traffic and restriction. This was one of few
desirable features that was implemented into the network design, as ACL can specify which VLANs are
granted access to the server.
Introducing additional VLANs would increase the performance, security and management of the
network by using ACL. Providing network redundancy would ensure network availability and counter
network failure. Link aggregation was used as a more reliable throughput for redundancy.
FUTURE REQUIRMENTS AND REJECTED REQUIREMENTS
Future requirements were discussed in the process of designing the network, these include the
following:




Upgrading hardware
Deploying improved protocols
Upgrading network cables to wireless
Implementing a network scheduler program
PAGE 4
427951 ENG653
Rejected requirements include the following:



Additional core and access switches
VPN
VoIP
4.0 Conclusion
Regrettably, the routing could only work as far as allowing the core switch to ping the loop back but
not the router and the client could ping the router but not the loopback. Regardless, I felt that I have
gained a great deal of knowledge in designing and configuring a network topology.
PAGE 5