CP1402/CP1802 Assignment
Networking Case Study
Introduction
This case study consists of five components.
You are to design a network, research and source appropriate devices justifying choices (feasibility, efficiency, etc.), subnet the network, assign IP addresses to the appropriate devices, and provide an executive summary of the project. You are also to provide a proposal for incorporating cloud computing.
Note: This is not a group project. Each student must individually complete all parts of their submission.
Students must start with a new document and they must not have another person’s file in their possession at any time. Students may discuss the task with each other, but each student must write their assignment independently and not show their work to other students.
James Cook University takes academic misconduct very seriously, and penalties will apply both for copying another student’s work, and providing work to another student.
Deliverables
A single Word document (.docx) – containing all parts
Assignment breakdown
Scenario
A European software development company has asked you to assess and redesign their network. They are opening new branches in Porto and Riga, which will require new equipment. They have existing contracts and hardware to maintain fibre optic leased line WAN links between sites.
PART 1 – Executive summary
PART 2 – Network diagram
PART 3 – Subnet the network and assign IP addresses to the appropriate devices
PART 4 – Research and source appropriate devices justifying choices (feasibility, efficiency, etc.) with a Weighted Scoring Model (WSM)
PART 1 – Executive summary
Describe the purpose, scope, and objectives of the project for each of parts 2, 3 and 4. Why is it important to produce a well-designed network diagram? What goals are you trying to achieve with the hardware you select for the procurement project?
· Purpose
The first thing you need to do when starting on a project is ask “why”? What problem are you trying to solve? Once you explicitly define the problem, it becomes easier to evaluate possible solutions.
· Scope
A project’s scope defines the outputs or deliverables of a project. What is the overall outcome of the project? How will the output of the project solve the problem? What features will the end result have?
· Objectives
The objectives are areas of focus of the project, and can be listed as discrete goals. Projects are usually constrained by an overall budget and time-frame. Objectives can break down the overall constraints of the project and apply them to individual aspects. Typically, good objectives follow the SMART principle, in that goals must be:
o Specific – well-defined and clear output
o Measurable – You know when the goal has been accomplished, or how much progress has been made
o Attainable – Goals are realistic and can be achieved within the project’s constraints o Relevant – The goals are worthwhile and make sense in the context of the project o Time-bound – Goals should have a time limit
The executive summary should be well-articulated: clear, concise, and use correct spelling and grammar. The intended audience for the executive summary can be assumed to have basic technical knowledge, but are not networking experts. You should aim for 200 to 300 words.
PART 2 – Network specifications and diagram Network Specifications
You have been given a rough sketch of the network topology below. You are to draw the network using Visio, subnet the network (see case study part 3), and assign router interfaces and IP addresses to router interfaces and servers.
Network Structure
Hardware
· Only include one switch in your diagram for each LAN or WLAN
· The Internet router port address is 31.167.22.43/30
· The Aarhus router is connected to the Internet, and provides access to the public backbone containing a web server and a mail server.
PART 3 – Subnet the network and assign IP addresses to the appropriate devices.
Each location has the following number of hosts Aarhus, Dublin, and Riga all have WLANs.
Location |
Workstations |
Expected Peak Wi-fi Users |
Aarhus |
600 |
50 |
Dublin |
300 |
35 |
Milan |
100 |
n/a |
Oslo |
200 |
n/a |
Porto |
20 |
n/a |
Riga |
65 |
15 |
Subnetting
Create subnets for the LANs and WLANs using a public class B network. Create subnets for the WANs using a public class C network. You are to use the table format below to provide the subnet details.
Table 1. LAN & WLAN Subnets
Spreadsheet Columns: Subnet name, subnet address, subnet mask (in slash format), first useable address, broadcast address, static address range, and DHCP address range (all addresses to be in dotted decimal notation)
Table 2. WAN Subnets
Spreadsheet Columns: Subnet name, subnet address, subnet mask (in slash format), first useable address, broadcast address (all addresses to be in dotted decimal notation)
Table 3. Router Interfaces
Spreadsheet Columns: Location, interface, IP address, subnet mask (in slash format) Table 4. Servers
Spreadsheet Columns: Location, server name, IP address, subnet mask (in slash format)
Additional requirements:
· Servers at a given location should be placed within a “server subnet” rather than as part of the same subnet used for workstations.
· Wi-fi at the Riga location is intended for use by clients, not employees.
· The size of your subnets should be large enough to satisfy the required number of hosts, but no larger. As we are using static subnetting in this subject, all LANs and WLANs should have the same size. (If you wish to create VLSM subnets, you are welcome, but the onus will be on you to teach yourself the technique and create a correct solution and there will be no additional marks.)
· DHCP will to be used for IP address allocation for hosts in each subnet and these ranges are to be allocated for each LAN. You may assume that DHCP will be provided by the router.
· Static IP addresses are to be allocated where appropriate.
· The ISP has given us an IP address of 31.167.22.43/30 for the Internet connection at Aarhus.
PART 4 – Research and source appropriate devices justifying choices (feasibility, efficiency, etc.)
You are to research and submit a project procurement plan for the new Oslo and Riga networks. The devices you must include are routers, switches, and wireless access points. Make sure the devices you select can handle the number of workstations required at each site, and provide a good quality of service to wired and wireless users.
The Riga offices include a meeting area for clients. It is only necessary to provide wi-fi access within this area, which is an open space that measures 10 × 20m. Choose your wireless access point/s accordingly.
Your project plan and final recommendations should be based on a Weighted Decision Matrix (similar to the WDM you completed in the Procurement Practical). You are to compare five (5) devices from each category and to base the decision on (at least 4) reasonable and well-justified attributes.
You are to justify the choices of attributes on which you compare your devices, and the scores that you give each device.
Note that Oslo and Riga have differing requirements, and therefore you should produce different WDMs for the devices at each site; although you may choose the same models of devices to compare, the criteria may differ.
The client would like to keep the budget for all procurement under $10,000. You may exceed this amount if you can justify it well. All hardware should be available new and still supported by the manufacturer.
This section should include:
For each Weighted Decision Matrix
· Table 1 indicating the attributes chosen for comparison and the justification for these attributes
· Table 2 outlining the devices to be compared, their prices, links to where they can be purchased, and justifications for the scores you’ve given each attribute
· Table 3 the WDM itself
· Create your WDMs in Excel and copy and paste them into your Word doc
· Each table should be well presented and easy to read
Budget
· Create a well-presented table of the prices of all devices and the total cost
· Include hardware only, not labour
Marking Scheme
Ensure that you follow the processes and guidelines taught in class to produce high quality work. This assessment rubric provides you with the characteristics of exemplary, good, satisfactory, and unacceptable work in relation to task criteria
Criteria |
Exemplary 100% |
Good 80% |
Satisfactory 60% |
Limited 40% |
Very Limited 20% |
Absent 0% |
|||||||||
Part 1 |
Consistently logical and |
Generally logical and relevant |
Presents reasonable |
Provides basic articulation |
Executive summary contains |
Incomprehensible |
|||||||||
relevant articulation of the |
purpose, scope, and objectives |
articulation of the purpose, |
of purpose, scope, or |
some relevant articulation of |
executive summary, |
||||||||||
Executive |
|||||||||||||||
Summary |
purpose, scope, and objectives |
of the project, aimed at a semi- |
scope, and objectives of the |
objectives. |
purpose, scope or objectives. |
negligible attempt, or |
|||||||||
Purpose, Scope, |
of the project. |
technical audience. |
project. |
not done. |
|||||||||||
and Objectives |
|||||||||||||||
Suitable for a semi-technical |
Generally suitable for a semi- |
||||||||||||||
/15 |
audience. |
technical audience. |
|||||||||||||
Quality of |
1. |
Well-structured into |
Most of the criteria are |
Over half of the criteria are |
Under half of the criteria |
Attempt at executive |
Negligible attempt or |
||||||||
Writing |
paragraphs. |
satisfactory (See criteria under |
satisfactory (See criteria |
are satisfactory (See criteria |
summary, but contains many |
not done. |
|||||||||
/5 |
2. |
Correct grammar. |
"exemplary") but some minor |
under "exemplary") but some |
under "exemplary") or |
significant issues with |
|||||||||
3. |
Correct spelling. |
issues. |
minor issues. |
significant issues in some |
grammar, spelling. |
||||||||||
areas. |
|||||||||||||||
Part 2 |
1. |
Created in MS Visio using |
Most of the criteria are |
Over half of the criteria are |
Under half of the criteria |
Many problems (e.g. not done |
Negligible attempt or |
||||||||
Cisco icon set, and the |
satisfactory (See criteria under |
satisfactory (See criteria |
are satisfactory (See criteria |
in Visio, inconsistent |
not done. |
||||||||||
Topology |
|||||||||||||||
Design |
diagram is: |
"exemplary") but some minor |
under "exemplary") but some |
under "exemplary") or |
formatting, diagram does not |
||||||||||
issues. |
minor issues. |
significant issues in some |
align to subnetting scheme, |
||||||||||||
Diagram |
2. |
Neat and Professional |
|||||||||||||
appearance |
3. |
All lines at set angles |
areas. |
etc). |
|||||||||||
(multiples of 30, 45, 90 |
|||||||||||||||
/10 |
degrees) |
||||||||||||||
4. |
Lines do not end short |
||||||||||||||
5. |
Lines do not appear over |
||||||||||||||
the top of devices |
|||||||||||||||
6. |
Lines align if on same |
||||||||||||||
level |
|||||||||||||||
Diagram Labels |
Topology is accurate and the |
Most of the criteria are |
Over half of the criteria are |
Under half of the criteria |
Many problems (e.g. topology |
Negligible attempt or |
|||||||||
and Devices |
diagram |
satisfactory (See criteria under |
satisfactory (See criteria |
are satisfactory (See criteria |
is inaccurate; devices are not |
not done. |
|||||||||
1. |
Includes device names |
"exemplary") but some minor |
under "exemplary") but some |
under "exemplary") or |
named, etc). |
||||||||||
/10 |
2. |
Interface names |
issues. |
minor issues. |
significant issues in some |
||||||||||
3. |
Interface IP addresses |
areas. |
|||||||||||||
4. |
Masks in slash format |
||||||||||||||
5. |
Text neatly placed and |
||||||||||||||
sized |
|||||||||||||||
Part 3 |
1. |
LANs and WLANs are the |
Most of the criteria are |
Most of the criteria are |
Some LANs and WANs are |
Few LANs and WANs are |
Negligible attempt or |
||||||||
correct size and allocated |
satisfactory (See criteria under |
satisfactory (See criteria |
documented. |
correctly identified. |
not done. |
||||||||||
Subnetting |
|||||||||||||||
Scheme |
from a public class B |
"exemplary") but one or two |
under "exemplary") but |
||||||||||||
/10 |
block. |
minor issues, such as a missing |
several minor issues (e.g |
Sizes are correct, or at least |
Nonsensical subnet size |
||||||||||
2. |
All required LANs and |
LAN, or incorrect address block |
multiple missing LANs or |
not outlandishly incorrect. |
chosen. |
||||||||||
WLANs are documented. |
choice. |
WANs) or a significant issue |
Page 7 of 9
3. |
WANs are the correct size, |
such as incorrect size. |
||||||||
and allocated from a public |
||||||||||
class C block. |
||||||||||
4. |
All required WANs are |
|||||||||
documented. |
||||||||||
Subnet Tables |
Based on the chosen subnetting |
Most of the criteria are |
Most of the criteria are |
Tables are presented and |
Tables are presented, but |
Tables are |
||||
/10 |
scheme, the following |
satisfactory (See criteria under |
satisfactory (See criteria |
contain most of the correct |
contain major issues such as |
incomprehensible, or |
||||
specifications are available and |
"exemplary") but some minor |
under "exemplary") but |
columns, and some correct |
impossible subnet bounds. |
negligible attempt, or |
|||||
correct for LANs and WLANs |
lapses. |
several minor issues, or a |
entries. |
not done. |
||||||
table, and WANs table: |
significant issue such as |
|||||||||
1. |
Subnet address |
missing a column. |
||||||||
2. |
Subnet mask |
|||||||||
3. |
Broadcast address |
|||||||||
4. |
First usable address |
|||||||||
5. |
Static address range |
|||||||||
(LANs and WLANs only) |
||||||||||
6. |
DHCP address range |
|||||||||
(LANs and WLANs only) |
||||||||||
Router Table |
Based on the chosen subnetting |
Most of the criteria are |
Over half of the criteria are |
Table is presented, but |
Table is presented, but |
Table is |
||||
/10 |
scheme, the following |
satisfactory (See criteria under |
satisfactory (See criteria |
contains several significant |
generally incomplete or |
incomprehensible, or |
||||
specifications are available and |
"exemplary") but a few minor |
under "exemplary") but some |
errors such as mismatched |
incorrect. |
negligible attempt, or |
|||||
correct in the router interface |
issues or missing interfaces. |
minor issues. |
IP addresses or missing |
not done. |
||||||
table: |
columns. |
|||||||||
1. |
Location |
|||||||||
2. |
Interface |
|||||||||
3. |
IP address |
|||||||||
4. |
Subnet mask |
|||||||||
Server Table |
Based on the chosen subnetting |
Most of the criteria are |
Over half of the criteria are |
Table is presented, but |
Table is presented, but |
Table is |
||||
/5 |
scheme, the following |
satisfactory (See criteria under |
satisfactory (See criteria |
contains several significant |
generally incomplete or |
incomprehensible, or |
||||
specifications are available and |
"exemplary") but a few minor |
under "exemplary") but some |
errors such as mismatched |
incorrect. |
negligible attempt, or |
|||||
correct in the server table: |
issues. |
minor issues. |
IP addresses or missing |
not done. |
||||||
1. |
Location |
columns. |
||||||||
2. |
Name |
|||||||||
3. |
IP address |
|||||||||
4. |
Subnet mask |
|||||||||
Part 4 – |
1. |
All required WDMs |
As per “exemplary”, but some |
As per “exemplary”, but |
Some WDMs are available, |
Major issues with WDMs, |
Negligible attempt, |
|||
Procurement |
available. |
minor lapses. |
several minor lapses, or some |
but justifications are |
justifications, and hardware |
nonsensical, or not |
||||
Weighted |
2. |
WDMs have been |
significant issues, such |
generally poor, and |
choices. |
done. |
||||
Decision |
formatted as per the |
missing WDMs, formatting |
hardware choices generally |
|||||||
Matrices |
practical example |
issues, some poor |
inappropriate. |
|||||||
/30 |
3. |
Clear, concise, and |
justifications, or some |
Page 8 of 9
reasonable justifications |
inappropriate hardware |
||||||
for priorities and attributes |
choices. |
||||||
given in the matrix. |
|||||||
4. Appropriate hardware |
|||||||
choices. |
|||||||
Budget |
Professional, detailed, accurate, |
As per “exemplary”, but some |
Generally accurate and |
Several inaccuracies. |
Generally inaccurate. |
Negligible attempt or |
|
/5 |
and visually appealing. |
minor lapses. |
visually appealing. |
not done. |
|||
代写计算机编程类/金融/高数/论文/英文
本网站支持淘宝 支付宝 微信支付 paypal等等交易。如果不放心可以用淘宝或者Upwork交易!
E-mail:850190831@qq.com 微信:BadGeniuscs 工作时间:无休息工作日-早上8点到凌晨3点
如果您用的手机请先保存二维码到手机里面,识别图中二维码。如果用电脑,直接掏出手机果断扫描。