代写INFT 3019 Network Architecture 2023 Assignment 1: Network Implementation帮做R语言
- 首页 >> C/C++编程INFT 3019 Network Architecture 2023
Assignment 1: Network Implementation (25%)
Due: As per course site
Individual Assignment
Submission: via the course website
Overview
The following assignment will require you to demonstrate skills you have learnt in the course INFT 3019 Network Architecture. The scenario has you as a network consultant brought into work on a new network design for the company. Each deliverable has been listed below to assist you in
planning the report. For full marks,a professional report meeting all deliverables must be submitted before the due date. In summary, this assignment requires you to create an IP Addressing Scheme, and implement the scheme into the provided Packet Tracer file.
Do not be concerned if you do not knowhow to complete all required features in Week 1! You are taught the content to help you complete this assignment.
Deliverables
This assignment requires you to complete multiple deliverables:
• Develop an IP Addressing Scheme,
• Implement network using Packet Tracer
Justifications and assumptions for the deliverables should be included when relevant.
You should upload to Learnonline the following files:
• A Word document containing the IP addressing scheme along with relevant justifications. Supplementary Excel files are also allowed, but a core project word document should be provided.
• A Packet Tracer file containing the implementation made in Packet Tracer Version 8 .2 or above.
Weighting
The assignment is worth 15% of your overall grade for this course. The following table breaks down each component of the assignment, giving it a percentage out of the 25% for this assignment.
|
IP addressing scheme |
11.5% |
|
Implementation in Packet Tracer |
11.5% |
|
Presentation, style, grammar, and spelling |
2% |
Scenario
Fast Track Express (abbreviated as FTX) is a renowned delivery and logistics company that has decided to relocate its entire operations from the Bahamas to Adelaide, South Australia, due to regulatory reasons. To support this transition, the company is constructing two new offices in
Adelaide, including a state-of-the-art headquarters located in the Adelaide CBD. The other office is in Mawson Lakes’ technology park.
The Adelaide CBD office, which will serve as the company's new headquarters, will be the primary hub for FTX's operations in the region. The other office will be used as a branch location to support the company's growing presence in Adelaide.
FTX's new headquarters will be connected directly to Telstra Business, the company's ISP. This will ensure that the company's operations run smoothly, and that their customers receive the best possible service.
The company has provided below you,a consulted with Jim’s IT Consulting, with a detailed list of requirements outlining each office, along with the number of people who will be working in each floor/room. Your task is to create an initial IP addressing scheme for the new offices and to
implement the IP addressing scheme into a demo simulation of the network infrastructure.
Adelaide CBD (Headquarters):
|
Floor/Room Staff Size Comments |
||
|
L1-01 |
30 |
Each staff member will have a workstation that requires the use of a wall port. |
|
L1-02 |
45 |
Each staff member will have a workstation that requires the use of a wall port. |
|
L1-03 |
80 |
Each staff member will have a workstation that requires the use of a wall port. This room will not have Staff Members initially but must be included in the IP Addressing Scheme (including WiFi) for future expansion purposes. |
|
L2-01 |
10 |
Each staff member will have a workstation that requires the use of a wall port. |
|
L2-02 |
16 |
Each staff member will have a workstation that requires the use of a wall port. |
|
L2-03 |
5 |
Each staff member will have a workstation that requires the use of a wall port. This room will not have Staff Members initially but must be included in the IP Addressing Scheme (including WiFi) for future expansion purposes. |
Mawson Lakes Branch:
|
Floor/Room Staff Size Comments |
||
|
GF-01 |
5 |
Each staff member will have a workstation that requires the use of a wall port. |
|
GF-02 |
15 |
Each staff member will have a workstation that requires the use of a wall port. |
|
GF-03 |
8 |
Each staff member will have a workstation that requires the use of a wall port. |
|
GF-04 |
6 |
Each staff member will have a workstation that requires the use of a wall port. |
|
WAREHOUSE |
150 |
No wall ports. All Staff Members are connected via WiFi. |
Additional Assumptions
• Unless specified otherwise, each staff member has one (1) workstation that is connected directly to a wall port.
• Wireless access is required at both offices.
o There should be a dedicated WiFi network (and subsequent VLAN) at both locations.
• Each staff member may have up to 3 devices extra using the Wi-Fi.
o This does not include the Mawson Lakes Warehouse Staff, who are only permitted to use the WiFi for their company Tablet.
• The network address given to the ISP <-> Adelaide CBD connection is 200.162.125.8/29 (ISP has .9,Adelaide has .10).
• The base network for all other address on the network is 10.0.0.0/8. This means that all addresses should fall under the range of 10.0.0.0-10.255.255.255.
• Adelaide has a server room that consists of two servers and a singular terminal PC.
o The server room should be able to fit a total capacity of 30 hosts.
• No additional networking devices (i.e., routers/switches) are expected to be added to the
network, what you see in the Packet Tracer file is all that should be considered.
Out of Scope
• Considerations for additional networking equipment, or buildings/rooms.
• Subnetting of the ISP Router/ISP Test Server, IP Addresses are already allocated.
Deliverable 1 - IP Addressing Scheme
Use the knowledge you have gained so far in this course to create an IP addressing scheme that
provides a scalable solution that FTX can use for the coming 5 years.
Your IP Addressing Scheme must :
• Encompass each of the branch locations.
• Include Network Device Link IP Addresses (i.e., WAN Link between locations, Router/Distribution switch links, etc.).
You do not need to:
• Make considerations for future networking/server equipment. Assume that the number of switches you see in the Packet Tracer is the max amount they will always have.
• Reserve IP Addresses for future growth. The future growth considerations should be factored into the current network sizes, it’s not expected for you to further reserve IP Addresses to accommodate for future branches/rooms
Your IP Addressing Scheme deliverable should consist of five main aspects:
• Network table – Shows all the networks in the network network infrastructure.
• Supernet table - Shows logical summaries of a block of addresses.
o Each office location should have its own supernet.
o You must waste as few addresses as possible given the requirements. This means you cannot have Adelaide’s supernet be 10.1.0.0/16, and Mawson Lakes’s as
10.2.0.0/16 unless you really need that size of a supernet.
• VLAN table – Shows all the VLAN’s being used,as well as the network they correlate to.
• IP Assignment table – Shows all the IP Addresses used in the Packet Tracer file, based on your network table.
• Justifications – Include any justifications that you see fit (i.e., additional networks that were included, WiFi network size, etc.).
Multiple appendixes have been provided as an example. Appendix A/B/C show the expected tables, and Appendix D shows the diagram the appendix tables are intended to represent.
Subnetting
The IP Addressing Scheme must be developed using VLSM. You should make use of supernets to allocate a range of addresses per location, meaning that all addresses for each area should have their own range.
You should not do VLSM in a manner where the network table looks like this:
• Network: 10.<branch>.<vlanid>.0/24
Doing so will result in a major loss of marks.
Refer to Appendix B for an example.
VLAN
Ensure each room also has its own VLAN. Additional VLAN’s outside of those used for rooms may also be required (i.e., servers, printers, management, blackhole, native, etc.).
Deliverable 2 - Implementation in Packet Tracer
Using the provided Packet Tracer file found on the Assignment 1 tab in Learnonline, implement FTX’s network as per the below specifications. DO NOT make your own Packet Tracer file or modify the provided one.
If you cannot open the Packet Tracer file because of version incompatibility, update your Packet Tracer on Netacad.com.
It’sa requirement that you use the same IP Addressing scheme you made in the first deliverable when implementing the network. You might need to adapt it to suit the Packet Tracer.
You do not need to complete the following steps in the below order if you feel confident enough to make your own order, but it’s recommended that you do so. Treat it like a checklist!
Step 1 - Basic Configuration
On all switches and routers perform. the following steps:
• Give hostname and domain name (fasttrack.com.au).
• Disable IP domain lookup.
• Ensure secure passwords are used for the console and VTY lines on all devices (use “cisco” for Console and VTY).
• Ensure an enable secret is present on all devices, use “class” for this.
• Create an RSA Key.
• Only allow SSH connections.
• Encrypt all passwords.
Step 2 - Implement VLANs & STP
• Use your VLAN table to assist you in creating VLANson the switches.
• Ensure the switch ports are in the correct VLAN.
• Shutdown all unused ports and move them into a blackhole/unused VLAN.
• Configure a management SVI on each switch.
• Configure trunk links where appropriate, change the native VLAN.
• Change all switches to use Rapid STP.
Step 3 - Implement IP addressing
• Use your IP addressing scheme and implement all IP addressing according to it.
o This includes configuration for rooms that may not be needed as yet.
• Configure Inter-VLAN routing on each router, using router-on-a-stick for Mawson Lakes, and SVI’s for the Adelaide CBD.
• The WAN links should use private IP addressing, except for the link to the ISP.
• The ISP router is already configured, you do not need to configure it. Simply align your IP addressing with it for the WAN link to it.
• End devices (PCs, Laptops, …) need IP addressing too, give them each an IP address. This includes servers and printers.
• Place the “TERMINAL” PC in the Management VLAN.
Step 4 - Implement Basic Routing
• Configure static routes to relevant networks at all company locations (you do not need to configure the ISP).
• Minimise the number of static routes required per L3 device by using default and summary static routes.
o If you create the supernet table correctly this will greatly save you time.
• DO NOT USE DYNAMIC ROUTING PROTOCOLS LIKE OSPF.