Network Design For Malcom Technologies

Non-functional requirements

In this project we will be providing a network design to Malcom Technologies. Malcom Technologies is an upcoming business enterprises that is a main distributor of wheel-bearings. This is not only attributed its hard working marketing and sales team, but also quality services they offer their customers. Due to increased growth, Malcom Technologies management has decided to redesign its network infrastructure in support of its business activities.

Save Time On Research and Writing
Hire a Pro to Write You a 100% Plagiarism-Free Paper.
Get My Paper

Non-functional requirement refers to those requirements that will specify the criteria that is used to provide a judgement of operations of a system. For our network project design, the following are the non-functional requirements:

Scalability: our designed network should be scalable in a manner that in case of a need of expansion, the expansion should be done without any form of interruptions to the current network structure.

Performance: the performance of our designed network should have a high work performance without laxity in the network flow.

Reliability: the designed network will be reliable and minimal downtimes will be experienced.

Save Time On Research and Writing
Hire a Pro to Write You a 100% Plagiarism-Free Paper.
Get My Paper

Functional requirements are the requirements that defines what the system should perform. For instance, in our network design, the designed network should be able to do the following as described by the administration:

Engineering and sales department should have access to print services

Finance, Human Resource and Admin departments should have access to all network infrastructure resources.

Sales and engineering should not access finance department at no single time. 

Hardware requirements

Item name

Features

How much required

Justification

Cost in US Dollar

Firewall

Model: Sophos xg

1

Sophos firewall will be used to filter both incoming and outgoing traffic

2420.54

Router

 Interface Card Slots: 4. each supports HWIC, WIC, and VWIC type modules.

 Fixed USB 1.1 Ports : 2

DRAM: 512 MB

Compact Flash: 64 MB

ü  Network slot module : 1

One

The router will enable communication between the VLANS. In addition, it routes information to and fro the network

1591

Server

Processor core: 28

Processor speed:3.6 GHz

Processor family: Intel

Processors number: 2

Memory slots: 20 DIMM

Maximum Memory: 2TB, 128 GB DDR# RAM

Cache level: L3 38.50

Network controller: HPE 1 GB 321i 4 adapter-ports

1

The server will be used for hosting DNS, DHCP, Print and file sharing services

26644

Wireless router

DRAM : 512 MB

LAN interface: 4 fast Ethernet ports.

Mini-USB port: 1

Auxiliary port: RJ 45 Single Port

Model: Cisco router 3500 series.

WAN interface: 1 gigabit Ethernet 0 and 1 Serial interfaces

Flash memory: 256 MB

2

Wireless handheld devices will be supported with the wireless router to access the internet

65*2=130

Switch

Flash memory: 64 MB

Model: Cisco Switch 2900 series

RJ 45 ports: 48

DRAM: 128 MB

3

Switches are required for the expansion of the network

2481*3=7543

IP Addressing

Area

IP address range

Sub netmask

Engineering Department

172.16.6.1 – 172.16.6.254

255.255.255.0

Admin department

172.16.2.1 – 172.16.2.254

255.255.255.0

Sales Department

172.16.5.1 – 172.16.5.254

255.255.255.0

HR department

172.16.3.1 – 172.16.3.254

255.255.255.0

Finance Department

172.16.4.1 – 172.16.4.254

255.255.255.0

User Centric design

The network design being developed will based on UCA approach, for instance our designed network will be simple and easy to learn.

Router configuration

Router>

Router>ena

Router#confi ter

Enter configuration commands, one per line.  End with CNTL/Z.

Router(config)#username admin123 pass admin123

Router(config)#service password-encryption

Router(config)#enabl se admin123

Router(config)#banner motd !You are in our Core Router!

Router(config)#line vty 0 4

Router(config-line)#password admin123

Router(config-line)#logg synchronous

Router(config-line)#login

Router(config-line)#line c 0

Router(config-line)#pass admin123

Router(config-line)#logi

Router(config-line)#logg sy

Router(config-line)#exi

Router(config)#inter fa0/0

Router(config-if)#no shut

Router(config-if)#description This is the physical interface, no need for IP address

Router(config-if)#inter f0/0.2

Router(config-subif)#ip add 172.16.2.2 255.255.0.0

Router(config-subif)#no ip add 172.16.2.2 255.255.0.0

Router(config-subif)#ip add 172.16.2.1 255.255.0.0

Router(config-subif)#inter fa0/0.3

Router(config-subif)#ip add 172.16.3.1 255.255.0.0

172.16.0.0 overlaps with FastEthernet0/0.2

Router(config-subif)#inter f0/0.2

Router(config-subif)#ip add 172.16.2.1 255.255.255.0

Router(config-subif)#inter fa0/0.3

Router(config-subif)#ip add 172.16.3.1 255.255.255.0

Router(config-subif)#inter fa0/0.4

Router(config-subif)#ip add 172.16.4.1 255.255.255.0

Router(config-subif)#inter fa0/0.5

Router(config-subif)#ip add 172.16.5.1 255.255.255.0

Router(config-subif)#inter fa0/0.6

Router(config-subif)#ip add 172.16.6.1 255.255.255.0

Router(config-subif)#ena

Router(config-subif)#encapsulation dot1q 6

Router(config-subif)#inter fa0/0.5

Router(config-subif)#encapsulation dot1q 5

Router(config-subif)#inter fa0/0.4

Router(config-subif)#encapsulation dot1q 4

Router(config-subif)#inter fa0/0.3

Functional requirements

Router(config-subif)#encapsulation dot1q 3

Router(config-subif)#inter fa0/0.2

Router(config-subif)#encapsulation dot1q 2

Router(config-subif)#exi

Router(config)#end

Router#copy run start

 [OK]

[4], [5]  

Switch 2 configuration

Switch>ena

Switch#confi ter

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#inter ra f0/1-3

Switch(config-if-range)#switchport mode trunk

Switch(config-if-range)#switchport trunk encapsulation dot1q

Switch(config-if-range)#exi

Switch(config)#inter f0/1

Switch(config-if)#switchport trunk allowed vlan all  

Switch(config-if)#inter f0/2

Switch(config-if)#switchport trunk allowed vlan all  

Switch(config-if)#inter f0/3

Switch(config-if)#switchport trunk allowed vlan all  

Switch(config-if)#inter fa0/4

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 4

Switch(config-if)#inter fa0/5

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 5

% Access VLAN does not exist. Creating vlan 5 

Switch(config-if)#inter f0/6

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 6

% Access VLAN does not exist. Creating vlan 6 

Switch(config-if)#end

Switch#copy run star 

Switch 1 configuration

Switch>ena

Switch#conf ter

Enter configuration commands, one per line.  End with CNTL/Z.

Switch(config)#inter fa0/1

Switch(config-if)#switchport mode tr

Switch(config-if)#swi trunk encapsulation dot1q

Switch(config-if)#switchport trunk allowed vlan all

Switch(config-if)#exi

Switch(config)#inter f0/2

Switch(config-if)#switchport mode acc

Switch(config-if)#switchport access vlan 3

Switch(config-if)#inter f0/3

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 2

% Access VLAN does not exist. Creating vlan 2

Switch(config-if)#inter f0/4

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 2

Switch(config-if)#end

Switch#copy run start

 [OK]  

[6]

Configuration of switch 3

Switch>

Switch>ena

Switch#confi ter

Switch(config)#inter f0/1

Switch(config-if)#switchport mode trunk

Switch(config-if)#switchport trunk encapsulation dot1q

Switch(config-if)#switchport trunk allowed vlan all

Switch(config-if)#inter f0/2

Switch(config-if)#switchport mode access

Switch(config-if)#switchport access vlan 6

Switch(config-if)#inter fa0/3

Switch(config-if)#switchport mode acc

Switch(config-if)#switchport access vlan 2

Switch(config-if)#end

Switch#copy run star

DHCP configuration

DHCP will be done on the router. The commands are issued on the router

Router#

Router#

Router#ena

Router#conf ter

Router(config)#service dhcp

Router(config)#ip dhcp excluded-address 172.16.2.1 172.16.2.10

Router(config)#ip dhcp pool malcom

Router(dhcp-config)#network 172.16.2.0 255.255.255.0

Router(dhcp-config)#leas 2 12 45

Router(dhcp-config)#default-router 172.16.2.1

Router(dhcp-config)#domain-name malcom.com

Router(dhcp-config)#end

Router#copy run star  

We will be using access lists to provide security for our network. In addition, Sophos firewall device will be deployed to filter the incoming and outgoing traffic.

Access list commands are as issued below:

 Router>ena

Password:

Router#confi ter

Router(config)#access-list 117 deny tcp 172.16.5.0 0.0.0.255 172.16.4.0 0.0.0.255

Router(config)#access-list 117 deny tcp 172.16.6.0 0.0.0.255 172.16.4.0 0.0.0.255

Router(config)#access-list 117 permit tcp any any  

Router(config)#inter fa0/0

Router(config-if)#ip access-group 117 in 

Steps to configure wireless router

  1. Open the Access Point’s web-based setup page. Access it by entering in your browse default IP ie 192.168.0.1. Press “Enter”.
  2. In the web-page setup, click ‘Wireless’.
  • Enter network Name SSID. For instance Malcom_WiFi. Note that Broadcast SSID should be enabled.
  1. Click “Wireless Security”. Pick desired security type.
  2. Enter secret word in “Passphrase” field.
  3. In the “internet setup”, type default gateway, one of the LAN IP addresses and dns server address.  
  • In the “Network Setup Area”, type Local Area Network IP address which will be the default gateway to PCs, Enable the DHCP server, type the “Start IP Address”.
  • Click “Save Settings”.

Assigning IP address to client with aid of DHCP

C:>ipconfig /ip dhcp

%DHCP-6-ADDRESS_ASSIGN: Interface Ethernet0 assigned DHCP address 172.16.2.11, mask 255.255.255.0, hostname C:

Assigning IP address to client Machine

C:>ipconfig /ip 172.16.2.2 255.255.255.0

C:>ipconfig /dg 172.16.2.1

Demonstration of dynamic issued IP address

C:>ipconfig /all

        Connection-specific DNS Suffix  . : malcom.com

Hardware requirements

        IP Address. . . . . . . . . . . . : 172.16.2.11

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 172.16.2.1

    Description . . . . . . . . . . . : Realtek RTL8139/810X Family PCI FastEthernet NIC

    Physical Address. . . . . . . . . : 000C.8741.9931

    DHCP Enabled. . . . . . . . . . . : Yes

    Link-local IPv6 Address . . . . . : FE80::20C:87FF:FE41:9931%1

    DHCPv6 IAID . . . . . . . . . . . : 53808830769 

To demonstrate the working of our network, we are going to ping client devices from different departments

Ping from admin department to HR department 

C:>ping 172.16.3.2 

Pinging 172.16.3.2 with 32 bytes of data:

Reply from 172.16.3.2: bytes=32 time=65ms TTL=241

Reply from 172.16.3.2: bytes=32 time=60ms TTL=241

Reply from 172.16.3.2: bytes=32 time=69ms TTL=241

Reply from 172.16.3.2: bytes=32 time=65ms TTL=241

Reply from 172.16.3.2: bytes=32 time=60ms TTL=241

Ping statistics for 172.16.3.2:

     Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

     Minimum = 60ms, Maximum =  69ms, Average =  64ms 

Ping from admin department to finance department device

C:>ping 172.16.4.2 

Pinging 172.16.4.2 with 32 bytes of data:

Reply from 172.16.4.2: bytes=32 time=72ms TTL=241

Reply from 172.16.4.2: bytes=32 time=59ms TTL=241

Reply from 172.16.4.2: bytes=32 time=48ms TTL=241

Reply from 172.16.4.2: bytes=32 time=63ms TTL=241

Reply from 172.16.4.2: bytes=32 time=55ms TTL=241 

Ping statistics for 172.16.4.2:

     Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

     Minimum = 48ms, Maximum =  72ms, Average =  59ms 

Ping from admin department to sales department device

C:>ping 172.16.5.2 

Pinging 172.16.5.2 with 32 bytes of data:

Reply from 172.16.5.2: bytes=32 time=51ms TTL=241

Reply from 172.16.5.2: bytes=32 time=69ms TTL=241

Reply from 172.16.5.2: bytes=32 time=51ms TTL=241

Reply from 172.16.5.2: bytes=32 time=53ms TTL=241

Reply from 172.16.5.2: bytes=32 time=55ms TTL=241 

Ping statistics for 172.16.5.2:

     Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

     Minimum = 51ms, Maximum =  69ms, Average =  56ms 

Ping from admin department device to engineering device

C:>ping 172.16.6.2  

Pinging 172.16.6.2 with 32 bytes of data:

Reply from 172.16.6.2: bytes=32 time=57ms TTL=241

Reply from 172.16.6.2: bytes=32 time=50ms TTL=241

Reply from 172.16.6.2: bytes=32 time=71ms TTL=241

Reply from 172.16.6.2: bytes=32 time=50ms TTL=241

Reply from 172.16.6.2: bytes=32 time=64ms TTL=241 

Ping statistics for 172.16.6.2:

     Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

     Minimum = 50ms, Maximum =  71ms, Average =  58ms 

Our network designed above can be handed over to Malcom Technologies. The design was mainly human centred design where we did the design on the basis of human use. It is kept simple and not complicated nor with a lot of jargon.

The configurations in our devices are kept simple and easy to understand. Additionally, comments are included to enable whoever is studying the network should not find it difficult. The devices are configured in Netsim Boson simulation software. Configured devices include the following together with their configurations:

Router- router is configured with Router-On-a-stick technology to enable inter-vlan communication.

For our server, we use windows server 2012R to host our DHCP and DNS server services.  We opt for windows server 2012 R version as it is not complicated and supports the latest technology. This technology more so, supports virtual interfaces to allow more devices to appear as if they are directly connected to the router.

The switches are configured with five vlans.  Each vlan represent a department. Vlans are virtual LANs that support segmentation of a network in logical manner.

Wireless access points in our topology are used to support wireless handheld computing devices for them to access the internet.

In our network design, we assume our ISP provided address is class B address that we use for IP addressing. We therefore subnet into five subnets each subnet hosting a maximum of 254 devices. 

References

[1]

P. Ciccarelli, ‎. Faulkner and ‎. FitzGerald, Introduction to Networking Basics, Hoboken: John Wiley & Sons, 2012.

[2]

T. Szigeti, ‎. Hattingh and ‎. Barton, End-to-End QoS Network Design: Quality of Service for Rich-Media & Cloud, Indinapolis: Cisco Press, 2013.

[3]

S. Noble, Building Modern Networks, Birmingham: Packt Publishing Ltd, 2017.

[4]

Kavian and Y. S., Intelligent Systems for Optical Networks Design: Advancing Techniques, Hershey: IGI Global, 2013.

[5]

M. Jacot, ‎. Jacot and ‎. Bali, Advanced Tuning for JD Edwards EnterpriseOne Implementations, New York City: McGraw Hill Professional, 2013 .

[6]

T. Lammle and ‎. Montgomery, CCNA Data Center: Introducing Cisco Data Center Technologies Study Guide, Hoboken: John Wiley & Sons, 2016 .

[7]

M. Duggan, Cisco CCIE Routing and Switching v5.0 Configuration and Troubleshooting, Indiana Polis: Cisco Press, 2014.

[8]

G. Tomsho, MCSA Guide to Networking with Windows Server 2016, Exam 70-741, Boston: Cengage Learning, 2017.

[9]

TP-Link, “How to Setup a TP-Link WiFi Router,” 23 September 2018. [Online]. Available: https://www.youtube.com/watch?v=k9zyKOI-AGs.

[10]

R. Nobel, ‎. Ziliotto and ‎. Lovison, CCIE Wireless Exam (350-050) Quick Reference: CCIE Wirel Quick Ref ePub _1, Indianapolis: Cisco Press, 2012.