Assignment 2 1619 Networking, Assignments of Computer Networks

The CEO Mr. Nguyen is happy with your first report and now he has asked you to analyse the specification from the institution, as given earlier. You need to design and implement the networking project within a given timeframe

Typology: Assignments

2021/2022

Uploaded on 05/11/2022

hien-tran-6523
hien-tran-6523 🇻🇳

4.7

(35)

23 documents

1 / 26

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Higher National in Computing
Unit 2: Networking Infrastructure
ASSIGNMENT 2
Learner’s name: Tran Quang Hien
ID: GCS210109
Class: GCS1003A
Subject code: 1619
Assignment due: Assignment submitted:
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a

Partial preview of the text

Download Assignment 2 1619 Networking and more Assignments Computer Networks in PDF only on Docsity!

Higher National in Computing

Unit 2 : Networking Infrastructure

ASSIGNMENT 2

Learner’s name: Tran Quang Hien ID: GCS Class: GCS1003A Subject code: 1619 Assignment due: Assignment submitted:

ASSIGNMENT 2 FRONT SHEET Qualification BTEC Level 5 HND Diploma in Computing Unit number and title Unit 2: Networking Infrastructure Submission date 06/03/2022 Date Received 1st submission Re-submission Date Date Received 2nd submission Student Name Tran Quang Hien Student ID GCS Class GCS1003A Assessor name Nguyen Xuan Sam Student declaration I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that making a false declaration is a form of malpractice. Student’s signature Grading grid

P 5 P 6 P 7 P 8 M 3 M 4 D 2 D 3

Assignment Brief 2 (RQF)

Higher National Certificate/Diploma in Computing

Student Name/ID Number: Tran Quang Hien/ GCS Unit Number and Title: Unit 2: Networking Academic Year: 2022 Unit Assessor: Sam X. Nguyen Assignment Title: Networking Infrastructure Issue Date: April 1st, 2021 Submission Date: Internal Verifier Name: Date: Submission Format: Format: The submission is in the form of an individual written report. This should be written in a concise, formal business style using single spacing and font size 12. You are required to make use of headings, paragraphs and subsections as appropriate, and all work must be supported with research and referenced using the Harvard referencing system. Please also provide a bibliography using the Harvard referencing system. Submission ● Students are compulsory to submit the assignment in due date and in a way requested by the Tutor. ● The form of submission will be a soft copy posted on http://cms.greenwich.edu.vn/. ● Remember to convert the word file into PDF file before the submission on CMS. Note: ● The individual Assignment must be your own work, and not copied by or from another student. ● If you use ideas, quotes or data (such as diagrams) from books, journals or other sources, you must reference your sources, using the Harvard style. ● Make sure that you understand and follow the guidelines to avoid plagiarism. Failure to comply this requirement will result in a failed assignment. Unit Learning Outcomes:

LO 3 Design efficient networked systems. LO 4 Implement and diagnose networked systems. Assignment Brief and Guidance: Assignment scenario (cont.) The CEO Mr. Nguyen is happy with your first report and now he has asked you to analyse the specification from the institution, as given earlier. You need to design and implement the networking project within a given timeframe: Task 2 Design efficient networked systems:

  • Prepare a written step-by-step plan of how you are going to design a Local Area Network including a blueprint of your LAN.
  • Justify your choice of devices for your network design.
  • Produce a test plan to evaluate this design for the requirements of bandwidth and cost constraints as per user specifications.
  • Justify the security requirements and quality of services needed for selection of accessories.
  • Suggest a maintenance schedule to support the networked system. Task 3 Implement test and diagnose networked systems:
  • Implement a networked system based on your prepared design.
  • Conduct verification with, e.g., Ping, extended ping, trace route, telnet, SSH, etc.
  • Record the test results and analyse these against expected results.
  • Investigate what functionalities would allow the system to support device growth and the addition of communication devices.
  • Discuss the significance of upgrades and security requirements in your recommendations.

Table Content

  • P5. Provide a logical/physical design of the networked system with a clear explanation and address table
      1. Discuss the difference between logical and physical design
      • 1.1 Logical Design
      • 1.2 Physical Design
      • 1.3 Compare physical & logical design:
      1. Discuss and explain the user requirements for general network design
      • 2.1 Requirements for general
      1. Logical design of network based on the specific requirements
      1. Physical design of network based on the specific requirements
      1. The IP address table
  • P6. Evaluate the design to meet the requirements
      1. Test Plan
      1. Evaluate My Network Design Advantages:
  • P7. Implement a networked system based on a prepared design
      1. Network Implementation
      1. Diagram
  • P8. Document and analyse test results against expected results
      1. Log book
      1. Network test results
      • Test case 1:
      • Test case 2:
      • Test case 3:
      • Test case 4:
      • Test case 5 :
      • Test case 6:

ASSIGNMENT 2 ANSWER Introduction This is my second project, so I'll do everything I can to get Merit. In the first assignment, I had introduce to you about networking. So in this second assignment, I will going to design a Local Area Network including a blueprint of LAN, implement and diagnose networked systems. P 5. Provide a logical/physical design of the networked system with a clear explanation and address table

1. Discuss the difference between logical and physical design 1.1 Logical Design The way data passes through a network is described by logical network architecture. A logical design will often depict the following features of your logical network architecture: •Subnets (such as: IP addresses, VLAN IDs, and subnet masks,) •Network objects (routers and firewalls) •Specific routing protocols •Routing domains •Voice gateways •Traffic flow •Network segment Figure 1: Logical Design Because the information contained therein belongs to the L3 (Layer 3) of the OSI model, L2 devices (such as switches) are not represented in an L3 or logical network diagram. While physical network diagrams are necessary, logical network diagrams aid network management in the following ways: Troubleshooting: If service is down between two IP addresses, a logical network diagram can quickly rule out a firewall issue. Firewalls: Using logical network diagrams, you can maintain your firewall rulebases up to date. Eliminate redundancies: You can quickly understand what is and isn't redundant using logical network diagrams.

The physical design layout defines the portions of the logical design network that exist in a certain network architecture. It also refers to the organization of computers and other physical components. Among the components are fiber, ISDN, and Ethernet. The logical design network takes a particular aspect of a network's conceptual design and assigns it a logical role within that framework. IP network architecture, such as Class A, B, or C address schemes, are among its components. Figure 3: Compare physical & logical design

**2. Discuss and explain the user requirements for general network design

  1. 1 Requirements for general** In our generic system's system component model, the user component is the topmost layer. The term "user" refers to the system's end users, but it may also apply to anybody who uses the system, such as network and system administrators and management. User requirements are a set of needs derived from user input that users require to properly execute their tasks on the system. Everyone who is connected to the network is typically regarded a potential user while gathering requirements. In general, the system should adapt to individuals and their situations, provide rapid and reliable access to and transfer of information, and provide excellent customer service. The following are the general requirements:
  • Timeliness
  • Interactivity
  • Reliability
  • Presentation quality
  • Adaptability
  • Security
  • Affordability
  • Functionality
  • Supportability
  • Future growth User criteria are the least technical and the most subjective. When seen in Figure 4, as consumers'

requirements proceed to the network, they get more technological. All of these requirements will be described in further detail as we go through the application, device, and network components. Figure 4: Requirements become more technical as we move closer to network devices The idea is to use them as a springboard for more objective and technical requirements in other components. These sample requirements are presented as a starting point for determining network requirements, and they may differ depending on the circumstances of the user.

3. Logical design of network based on the specific requirements Figure 5: Logical Design in my system

Test case Action Description 1 Check the port status (^) Click interface and then make sure all ports is on 2 Configure DHCP for first floor (^) Open DHCP Server and configure it 3 Configure HTTP for first floor Open FTP Server and configure it 4 Configure FTP for first floor (^) Open FTP Server and configure it 5 Ping PC0 to DNS Server Open Network Administrator, click desktop then click command prompt Use command “ping 192.168.2.2” 6 Ping Laptop to DNS Server Open Network Administrator, click desktop then click command prompt Use command “ping 192.168.2.2” 7 Ping PC0 to HTTP Server Open Network Administrator, click desktop then click command prompt Use command “ping 192.168.2.3” 8 Ping Laptop0 to FTP server Open Network Administrator, click desktop then click command prompt Use command “ping 192.168.2.4”

2. Evaluate My Network Design Advantages:

  • Simple design but work effectively. The structure is clearly which divided into 2 floors: Ground floor include Laptop, PC and Printer. First Floor include DNS Server, HTTP Server and FTP Server.
  • Each PCs are be able to ping each other
  • The ground and the first floors include student computer labs. From the machines in these 2 rooms can access DNS, HTTP, FTP
  • The server can be easy to fixed if there are any problems Disadvantages:
  • Missing some servers
  • Need to improve security
  • It’s hard to build a servers
  • If we are not careful with DHCP server – everything is down

Solutions:

  • Upgrade a security system like firewall
  • Add more switches to expand the layout network
  • Reduce cost **P7. Implement a networked system based on a prepared design
  1. Network Implementation** Step 1: Configure DNS server To set up a networked system, make sure that the (on mode) port is linked to all servers, switches, routers, and PCs. We must first build a server before configuring a DNS server. Then: Services - > DNS - > Server Figure 7: Configure DNS(1) After that, I provide domain name translation and turn on DNS service

Type config - > Setting in GLOBAL - > Configure IP address Figure 10 : Configure DNS( 4 ) Type FastEthernet0 in INTERFACE - > Configure IP address (IPv4, Subnet Mask) Figure 11 : Configure DNS( 5 )

Try to ping DNS server by click on the desktop mode on pc0. Then, continue to type the IP address of DNS server: ping 192.168.2.2. 0% loss prove that I have already successfully configured the DNS server: Figure 12: Successfully ping DNS Server from PC Figure 1 3 : Successfully ping DNS Server from Laptop

Step 4: Configure static Interfaces at routers and admin labs Interface FastEthernet0/0: The IP address is 192.168.1.1 and the subnet mask is 255.255.255.0. This one used to connect to the switch with DNS_Server Figure 1 6 : FastEthernet0/0 (Router 0) Interface Serial 2/0: The IP address is 10.0.0.1 and the subnet mask is 255.255.255.0. This one used to connect to the Internet_Router. Figure 17 : Serial 2/0 (Router 0)

PC

The IP address is 192.168.1.2; the subnet mask is 255.255.255.0; the Default Gateway is 192.168. 1 .1and the DNS server is 192.168.2. Figure 18 : PC Laptop 0 The IP address is 192.168.1. 3 ; the subnet mask is 255.255.255.0; the Default Gateway is 192.168. 1 .1and the DNS server is 192.168.2. Figure 1 9: Laptop 0