Logical Network Design for OZ Dispatch

This document provides a logical network design for OZ Dispatch, a small business enterprise specializing in home delivery service. It includes information about the network requirements, user communities, and traffic flows. The goal is to create a secured and scalable network for real-time data transfer between the head office and remote branches. The document also discusses business goals, technical goals, and trade-offs, as well as the implementation plan and test plan.

COIT20264, HT1-2019
Network Design
Assessment 1- Logical Network Design
OZ Dispatch

OZ Dispatch
Logical Network Design
Executive Summary
OZ Dispatch is a small business enterprise that specializes in the home delivery service. The
organization’s headquarters are is located in Parramatta NSW, of Australia. In the Parramatta office,
data analyst, accountant, managing director, marketing and sales executive are in this office. Data
analyst is doing a lot of data analysis. Due to this, there is need for a lot of data sharing within the office.
OZ Dispatch customer base consists of individuals who are located in different remote areas. The
customers should be able to place orders at the comfort of their zones. This will be through the web.
Furthermore, they should be able to make payments using the web interface. This will require WAN
system that is secured due to the sensitive transactions that are to be done.
Note that once customers have made their orders, these orders are collected form the suppliers and
taken to the distribution points near to the customers. OZ Dispatch has a total of 20 distribution points
with two employees. Once the products are collected, there is a need for these products to be uploaded
in the ERP system for the purpose of tracking. The twenty remote offices will require to have access to
this ERP system hosted at the head office. VPN will be the best solution for this dilemma.
1 | P a g e

OZ Dispatch
Logical Network Design
Table of Contents
Executive Summary.....................................................................................................................................1
List of Tables................................................................................................................................................3
List of Figures...............................................................................................................................................3
Project Goal.................................................................................................................................................4
Project Scope...............................................................................................................................................4
List of Business Goals and Constraints.........................................................................................................4
Business Goals ........................................................................................................................................4
Expansion in market share...................................................................................................................4
Increased profit and revenue collection..............................................................................................5
Reduced operational costs..................................................................................................................5
Exploration of new markets.................................................................................................................5
Increased employee productivity........................................................................................................5
Provision of superior customer support..............................................................................................5
Business Constraints:...............................................................................................................................5
Finance................................................................................................................................................5
Staffing and management...................................................................................................................6
Government Regulations.....................................................................................................................6
List of Technical Goals and Trade-offs.........................................................................................................6
Availability...............................................................................................................................................6
Scalability.................................................................................................................................................6
Security....................................................................................................................................................6
Performance............................................................................................................................................7
Adaptability.............................................................................................................................................7
Table of User Communities, Data Stores, Network Applications and Traffic Flows.....................................8
User Community Table............................................................................................................................8
Network Application................................................................................................................................9
MODEL FOR ADDRESSING AND NAMING..................................................................................................11
The explanation and justification of your logical network design..............................................................14
LOGICAL NETWORK DIAGRAM(S) INCLUDING ADDRESSING AND NAMING..............................................15
The list of routing and switching protocols, and security mechanisms.....................................................17
OSPF PROTOCOL....................................................................................................................................17
2 | P a g e

OZ Dispatch
Logical Network Design
BGP PROTOCOL.....................................................................................................................................17
HSRP PROTOCOL....................................................................................................................................17
SWITCHING PROTOCOL.........................................................................................................................17
STP.........................................................................................................................................................18
VTP........................................................................................................................................................18
8. DISCUSSION OF SECURITY MECHANISMS..................................................................................18
VPN tunnelling end-points.....................................................................................................................19
Access Control Lists...............................................................................................................................19
VLANs....................................................................................................................................................19
WPA.......................................................................................................................................................19
The physical network diagram...................................................................................................................20
The table of networking & communication devices and applications required.........................................20
The explanation and justification of 12 above...........................................................................................22
A test plan that can be used to test the new network...............................................................................22
One detailed test script for your test plan.................................................................................................22
References.................................................................................................................................................24
3 | P a g e

OZ Dispatch
Logical Network Design
Project Goal
The project goal is to allow for a secured and scalable network which allows real-time data transfer
between the head office and the remote twenty offices. During the design of network for OZ Dispatch,
there are considerations which we take into account. Some of the considerations include accessibility
and integrity of data over the public network. Scalability is also another factor that we consider. This
factor measure the ability of a network to grow without interfering with business operations. Along
these factors, it is required that the printers, scanners, are to be shared on the network.
Project Scope
The network to be designed is to serve OZ dispatch head office and twenty of its branches. The network
design process covers the following areas
i. List of Business Goals and Constraints
ii. List of Technical Goals and Trade-offs
iii. Table of User Communities, Data Stores, Network Applications and Traffic Flows
iv. Model for addressing and naming
v. Explanation and justification of the logical network design
vi. Logical network diagram(s) including addressing and naming
vii. Discussion of routing and switching protocols
viii. Discussion of security mechanisms
List of Business Goals and Constraints
IT any business organization that would want to satisfy its internal and external customers, it
must integrate IT Infrastructure services. These services include but are not limited to email,
internet access, contentment management system, system applications such as the ERP, print, file
storage, and sharing, systems security, etc. OZ Dispatch Company would want to improve on its
service delivery to its customers by the integration of IT infrastructure services in its business
processes. This article seeks to outline top-down approach activities necessary to Implement IT
services in OZ Dispatch. In the top-down technique, users of the system are engaged so much
before infrastructure services are the rolling wheel of every business enterprise. Of late, statics
show that ground breaking. This is aimed at getting exactly what the client is in need
(Oppenheimer, 2014). The project is intended to take a maximum of 4 weeks with a minimum of
three weeks. The implementation process is set to begin on the 10th of June 2019.
4 | P a g e

OZ Dispatch
Logical Network Design
Business Goals
Note that business enterprises that are in existence have a list of goals that they are to achieve
them to consider their business viable. Below is a list of business goals for OZ Dispatch
Company;
Expansion in market share
Extended market share can only be achieved by going out there in the market and convincing
customers or potential buyers on how you can satisfy their needs. This can be done in a number
of ways. For OZ Dispatch Company, we choose the deployment of Information technology in
convincing our customers. Will be using emails, website, and use of flyers.
Increased profit and revenue collection
Collection of revenue in terms of sales of huge volumes of products or is a goal every profit-
making business enterprise. OZ Dispatch Company aims to rise in the area of revenue collection
and profits.
Reduced operational costs
Operational costs if not managed appropriately, they can bring down the business enterprise.
History has it that there are business organizations which have closed down due to
mismanagement of operational costs. While on other hand business enterprises who are capable
to manage their operational costs, they have long-term survival.
Exploration of new markets.
One may feel that markets outside there they are flooded, this is not true because there are
markets which are still very raw, and they have not been exploited. Deployment of IT
infrastructure may speed-up the process.
Increased employee productivity
Once OZ employees have been furnished with relevant technology, their out level will increase
significantly. This is the target for OZ Dispatch Company.
5 | P a g e

OZ Dispatch
Logical Network Design
Provision of superior customer support
Customers who are served beyond their expectations will leave OZ Dispatch premises smiling
and it is obvious that they will come again, or they may refer someone. This is what our client
company expects.
Business Constraints:
A business constraint refers to the limitations which interfere with the profitability of a business
enterprise endeavour. To improve the profitability of the business, it is required that this
limitation be reduced or be removed completely. Like any other business organization, OZ
Dispatch has the following business constraints.
Finance
Financial factors are often interfering for business processes. These constraints can range from
excessive salaries to inadequate budget allocation or overhead expenditures. A good example is
when more employees are required but the allocated budget provided cannot allow, this will limit
the growth.
Staffing and management
Since businesses change and grow, their management and staffing needs change too. This factor
can constraint business productivity and growth especially when employees are not able to
conform to the new business requirements.
Government Regulations
Sometimes, business enterprise’ regulations constrain profitability. More so, government-
imposed laws can be a business constraint. For example, laws concerning imports and exports
can directly affect business operations.
Having identified the above constraints that would affect OZ Dispatch business operations
negatively, OZ management should find a way of dealing with these constraints that can be
managed. For them that are beyond OZ, then an alternative has been used.
List of Technical Goals and Trade-offs
A technical goal refers to an objective milestone that will get a business project closer to its
achievement. Some of the technical goals for OZ Company IT infrastructure project are:
6 | P a g e

OZ Dispatch
Logical Network Design
Availability
Availability is the measure of the run time of a system without failures. OZ network is expected
to be uptime at a percentage of 99.97% so as to eliminate standstills due to unavailability of the
network system.
Scalability
Scalability measures how well a system can allow expansion and growth without disrupting
business processes. OZ network to be designed will be scalable allowing future growth.
Security
It is important to have a secure networking system because there are intruders who would want
to access our networking system due to reasons known to them. We cannot claim that we will
develop a totally secure network system. However, our network will be developed in a manner
that will slow down the activities of an intruder.
Performance
Network performance measures the service quality of a network as observed by a client. Our
costs and upgrade.
Adaptability
A network that is adaptable is one that can be introduced to a business enterprise and it does not
constraint business operations. The network being developed will fit into OZ business activities
without holding any of the operations.
The trade-off is a technique of balancing between two desirable opposing qualities, factors or
situations with an aim of obtaining another desirable outcome. According to Mariño, it is
desirable to trade-off one factor against another as long as the outcome will be of better results
(Mariño, 2016). It, therefore, implies that finance, space and project delivery will be a trade-off
to performance, availability, and scalability. Furthermore, implementation of one a high
throughput for one critical application program interprets the sacrifice of another application.
7 | P a g e

OZ Dispatch
Logical Network Design
Table of User Communities, Data Stores, Network Applications and Traffic Flows
User Community Table
A user community of a network refers to the users of a computing system together with the
applications that they use. Table of user communities for OZ Dispatch is as below
Table of user communities
User community name Number of users Location of the
community
Applications used
Head office 5 Parramatta All
Remote offices 40 (20 offices each with
2 users)
Remote locations All
Customers Variable Remote location Web and mobile
payment application
Suppliers Variable Remote location ERP
Network applications, data store and Traffic flows
Application
name
Type of Traffic
Flow
Technological Protocol(s)
used
Approximate
Bandwidth
needed (Kb)
Database
update
Server/Server CDN 100000
E-mail Client/Server SMTP 10
8 | P a g e

OZ Dispatch
Logical Network Design
Remote
access
Terminal/host RDP 600
Web
browsing
Client/Server HTTP,HTTPS 60
File transfers Peer/Peer FTP 100
IP telephony Client/Server RTP,SCCP,SGCP,MGCP,SIP 10000
Network Application
Applicat
ion
Name
Traffic flow Type Protocol
s used
by
Applicat
ion
Bandwidt
h
Requirem
ents by
Applicatio
ns
Data
Store
User
Communi
ties
QoS
FTP
(File
Transfe
r
Protocol
)
Data (Client/Server) FTP,
SFTP
2 Mbps File
Server
Employee
s –
managing
director,
sales and
marketing
executive,
data
analyst
and an
accountan
t
Reserved
traffic
rate.
Email Data (Client/Server,
Server/Client)
SMTP,
POP3,
IMAP
1024kbps Email
Server
and
Web
mail
Storage
Employee
s –
managing
director,
sales and
marketing
executive,
data
Reserved
Traffic
Rate
9 | P a g e

OZ Dispatch
Logical Network Design
analyst
and an
accountan
t
VOIP Audio (Peer to Peer) SIP,
SRTP
128 kbps Cisco
Router
Configu
red with
VOIP
Server
Employee
s –
managing
director,
sales and
marketing
executive,
data
analyst
and an
accountan
t, CDC
employees
Transmis
sion
delay<11
0 ms,
Web
Services
Data
(Client/Server,Server
/Client)
HTTP,
HTTPS
1024 kbps Backup
on
storage,
Web
Server
Employee
s –
managing
director,
sales and
marketing
executive,
data
analyst
and an
accountan
t, CDC
employees
,
customers
Reserved
Traffic
Rate
Remote
Termina
l Access
Data (Terminal/Host) SSH,
Telnet,
VPN
256 Kbps Applicat
ion
Server
Systems
Administr
ator
Isolated
traffic
10 | P a g e

OZ Dispatch
Logical Network Design
Table of data store
Data Stores Location Applications
File Server Head office FTP (File
Transfer
Protocol)
Mail Server Head office Email
Server Head office VOIP
Web server Head office Web Services
MODEL FOR ADDRESSING AND NAMING
Network component naming refers to the giving of a name to a networking device. Naming
should be done in a way that makes it easier to identify a networking component. Computer
networking components should be given a name following the below naming scheme
Location name, component generic name, let’s say we want to name a router at Parramatta
office, it will be, Parramatta Router.
Addressing refers to the allocation of an IP address to a networking device. This can be done
manually or by use of a DHCP server. Static/manual IP address suits best for small business
enterprises of a population less than 10 people. This technique will be the best for the CDCs
sites. For Parramatta office where the population may be higher and frequent visits, we will
recommend the use of DHCP. This will relieve the systems administrator the struggle of
mastering IP addresses assigned computing devices and those to be assigned (Velte & Velte,
2013).
11 | P a g e

OZ Dispatch
Logical Network Design
Assuming that we have been provided with an IP address of 192.168.7.71/19 our addressing
scheme table will look like the one below.
Note that we are using classless subnetting to avoid wastage of IP addresses
Location
Name
Require
d IP
Hosts
Reserve
d IP
address
es
Network
Address
Mask Starting
and ending
address
(address
range)
Broadcast
Parramat
ta
100 26 192.168.0.0 255.255.255.1
28
192.168.0.1
-
192.168.0.1
26
192.168.0.1
27
CDCs1 50 12 192.168.0.1
28
255.255.255.1
92
192.168.0.1
29 -
192.168.0.1
90
192.168.0.1
91
CDCs2 50 12 192.168.0.1
92
255.255.255.1
92
192.168.0.1
93 -
192.168.0.2
54
192.168.0.2
55
CDCs3 50 12 192.168.1.0 255.255.255.1
92
192.168.1.1
-
192.168.1.6
2
192.168.1.6
3
CDCs4 50 12 192.168.1.6
4
255.255.255.1
92
192.168.1.6
5 -
192.168.1.1
26
192.168.1.1
27
CDCs5 50 12 192.168.1.1
28
255.255.255.1
92
192.168.1.1
29 -
192.168.1.1
91
12 | P a g e

OZ Dispatch
Logical Network Design
192.168.1.1
90
CDCs6 50 12 192.168.1.1
92
255.255.255.1
92
192.168.1.1
93 -
192.168.1.2
54
192.168.1.2
55
CDCs7 50 12 192.168.2.0 255.255.255.1
92
192.168.2.1
-
192.168.2.6
2
192.168.2.6
3
CDCs8 50 12 192.168.2.6
4
255.255.255.1
92
192.168.2.6
5 -
192.168.2.1
26
192.168.2.1
27
CDCs9 50 12 192.168.2.1
28
255.255.255.1
92
192.168.2.1
29 -
192.168.2.1
90
192.168.2.1
91
CDCs10 50 12 192.168.2.1
92
255.255.255.1
92
192.168.2.1
93 -
192.168.2.2
54
192.168.2.2
55
CDCs11 50 12 192.168.3.0 255.255.255.1
92
192.168.3.1
-
192.168.3.6
2
192.168.3.6
3
CDCs12 50 12 192.168.3.6
4
255.255.255.1
92
192.168.3.6
5 -
192.168.3.1
26
192.168.3.1
27
CDCs13 50 12 192.168.3.1 255.255.255.1 192.168.3.1 192.168.3.1
13 | P a g e

OZ Dispatch
Logical Network Design
28 92 29 -
192.168.3.1
90
91
CDCs14 50 12 192.168.3.1
92
255.255.255.1
92
192.168.3.1
93 -
192.168.3.2
54
192.168.3.2
55
CDCs15 50 12 192.168.4.0 255.255.255.1
92
192.168.4.1
-
192.168.4.6
2
192.168.4.6
3
CDCs16 50 12 192.168.4.6
4
255.255.255.1
92
192.168.4.6
5 -
192.168.4.1
26
192.168.4.1
27
CDCs17 50 12 192.168.4.1
28
255.255.255.1
92
192.168.4.1
29 -
192.168.4.1
90
192.168.4.1
91
CDCs18 50 12 192.168.4.1
92
255.255.255.1
92
192.168.4.1
93 -
192.168.4.2
54
192.168.4.2
55
CDCs19 50 12 192.168.5.0 255.255.255.1
92
192.168.5.1
-
192.168.5.6
2
192.168.5.6
3
CDCs20 50 12 192.168.5.6
4
255.255.255.1
92
192.168.5.6
5 -
192.168.5.1
26
192.168.5.1
27
14 | P a g e

OZ Dispatch
Logical Network Design
(Bianco & Neri, 2013)
The explanation and justification of your logical network design
A logical network design denotes to the virtualized representation of a network that appears to the user
as a separate whole self-contained network. This may be a physically a portion of the larger network or
the LAN. The diagrams in the next section shows the logical design of both the head office and the
branch. From the diagram, it is depicted that hierarchical network design technique is used. This is
implied by the access layer, distribution layer and the core layers of the network.
A hierarchical network design entails division of the discrete layers. Every tier or layer in the hierarchy
performs specified duties which define its role within the network. The three tier layers include:
Access layer – which offers user access to the network
Distribution layer – the distribution layer offers policy-based controls and connectivity and it acts as the
boundary between the access layer and core layer.
Core layer – offer fast transmission between distributions within the campus network
We apply this kind of approach in our network design since it divides the larger network into smaller
manageable blocks. Note that only traffic that is destined for other networks is transported to the higher
layers of the hierarchy.
For designing of OZ network, architecture Top-down network methodology is used. In this
approach, three layers are used such as distribution, core, access layer. In addition to it, in the
network architecture we can see that between the Internet network and router, a firewall is
installed in order to secure the network from unauthorized access.
In below Network logical design of the OZ, dispatch company shows that ISP (Internet Service
Provider) is connected to a router which is situated to main office Parramatta. From this router,
the switch is connected to pc or laptop, printer, mobile phone, and wireless access point. The
main router relates to branch router at CDs. All 20 collection and distributed centres, routers are
connected to switch and switches are connected to printers, computers, mobile phones or phones,
and wireless access points.
LOGICAL NETWORK DIAGRAM(S) INCLUDING ADDRESSING AND NAMING
A logical network diagram gives the architecture of the network. It shows the VLANs
architecture and geographic spread of the network. More so, the main interconnection of
computing devices is shown
15 | P a g e

OZ Dispatch
Logical Network Design
16 | P a g e

OZ Dispatch
Logical Network Design
The list of routing and switching protocols, and security mechanisms
A routing protocol denotes to the set of rules and algorithms that will be used in the forwarding of
packets within our network. Sample routing protocols include OSPF, static routing, default routing,
EIGRP routing, BGP, EGP and RIP in our network design for OZ dispatch, we will purely use OSPF routing
protocol. This is the protocol will allow route summary. Furthermore, the protocol will support our
VLSM network design. Another thing that makes us to choose this protocol is that it industry standard
and it does not tie us to one vendor, that is cisco. Most important is that the protocol is capable of
reconstructing the routing table just in case there changes made in the network topology or failure.
OSPF PROTOCOL
In our routing, we will be using Open Shortest Path First (OSPF) routing protocol. We select this
routing protocol because it supports classless routing and can discover new routes just in case
there is a change in the network. It requires no administrator. The network is connected through
routers which include the router protocols such as OSPF that aims to provide the best path to the
packets. It manages the traffic in the enterprise networks in which many networks (local) are
connected via routers.
BGP PROTOCOL
The Border Gateway Protocol (BGP) controls packets that are forwarded over the internet and it
provides stability. It is a standard Exterior gateway protocol made to exchange reachability and
routing info between autonomous systems as the path vector protocol. Our network autonomous
systems will be managed by this protocol. This protocol will manage the packets sent on the
internet and is managed by the network administrator.
HSRP PROTOCOL
The Hot Standby Routing Protocol (HSRP) provides the way to achieve maximum network
uptime by ensuring the coverage of the failure of the hops in the network (Duggan, 2014). This a
routing protocol which offers a backup system to the routers just in case of a failure event. We
will deploy this protocol on our routers to ensure that in case of a failure of one of the routers,
another router – standby router picks the roles of an active router until the failure is resolved.
SWITCHING PROTOCOL
Switching is a technique to avoid looping of the network. Network loops may be daunting so
much in any given network. There exist several switching techniques but, in our network, will be
using Per-VLAN Spanning Tree Protocol and VLAN Trunking Protocol. This approach is
17 | P a g e

OZ Dispatch
Logical Network Design
selected because it has a capability to converge so fast, minimizing time wasted waiting for
convergence (Carthern & Wilson, 2016).
STP
The switches with Spanning Tree Protocol (STP) are categorized as listening, blocking, disabling
and forwarding ports. In the network design, it is very important to eliminate the loops to prevent
the broadcast propagation around it. This protocol allows to include backup in network design so
that if any link fails, it is tolerable.
VTP
The VLAN Trunking Protocol (VTP) provides the ease of configuration and VLAN management
protocols and policies (Oppenheimer, 2014). This protocol is implemented the switch to switch
and switch to the router. Network design for OZ dispatch should fulfil the requirements and
technical goals, the network needs to consider the configuration protocols so that it is easy to
manage, delete, add and rename the VLAN automatically. If the network needs to add the new
switch, this protocol automatically will configure the new switch to the router.
8. DISCUSSION OF SECURITY MECHANISMS
Every networked system requires appropriate security to be put in place. This is because there
are enormous intruders on the internet who are waiting for the weak networked system so that
can they break in. The following are the security techniques that we will be using.
 Physical Security, Authentication and Authorisation
The organization needs to implement the physical security mechanisms, authentication, and
authorization policies to limit access to protect the network equipment. The delivery staff at
CDC’s are provided with the smartphones and the Wi-Fi’s, so the devices should be secured
from the theft like physical vulnerabilities or the internal threats such as misuse of the devices.
 Firewalls
The firewalls are the set of rules that monitors the traffic that should be allowed to move in and
out (Oppenheimer, 2014). As indicated earlier our firewall is positioned strategically to ensure
18 | P a g e

OZ Dispatch
Logical Network Design
every single packet that is either leaving or entering ore network is filtered. This will also block
the threats from various applications used in this network design.
VPN tunnelling end-points
In our network, we will configure VPNs to allow users from the branches to access ERP and
other applications remotely in a secure manner. The tunnelling secures the data that is transferred
from one to another end. The encapsulation of data in VPN tunnelling enhance the security
features of the network design.
Access Control Lists
The authorization and authentication policies will be implemented to protect the data. An access-
lists refers to a set of statements that when applied on the router will take effect by either permit
or deny access to some resources. The staff should be given the minimal permissions to access
the system which can be further protected by the authorisation policies such as login id and
passwords.
VLANs
A VLAN is a logical segmentation of the network. A network is divided into divisions by the
subnetting process. Once the network is segmented each segment appears as a separate entity
from one another. This will improve the security of our networking system (Hooper, 2012).
WPA
Wireless Security is important for OZ Dispatch’s network design as each CDC has Wi-Fi and
internet connection and each of them has servers at Paramatta. The Wi-Fi protected access is
used for data encryption and authentication by providing access control and management in a
centralized manner (Oppenheimer, 2014).
19 | P a g e

OZ Dispatch
Logical Network Design
The physical network diagram
Figure 1: The physical network diagram
The table of networking & communication devices and applications required
Below table provides networking and communication devices and applications
Name of the
network
device/Application
Manufacturer Features Quantity Cost for
each
Item ($)
Approximate
Total cost
Switch D-link switch 48 port fast Ethernet port,
1 console, 1 usb port.
21 210 4410
Router Dell router Dell router, 1gb ram, 2gig
ports, 2 Serial slots
21 920 19320
Firewall Sophos Sophos XG5 Firewall, 8
Ethernet ports, 1 USB
port, 1console port
1 840 840
20 | P a g e

OZ Dispatch
Logical Network Design
Wireless access-
point
D-Link EAP120, 2 Gigabit
Ethernet Port
21 154 3234
Patch panel Patch Panels-48Ports 3 52 156
Laptop computers Dell HP 330, 500 gb hdd, 8th
Gen Intel® Core i7-8550U,
Windows 10 Pro 64 bit, 4
gb on-board DDR4 + 8 GB
DIMM, 15.6” FHD (1920 x
1080) IPS
55 750 41250
RJ-45 RJ-45 Connector 30 packs
of 100 rjs
9 900
Desktop
computers
Dell Dell Latitude E5250 12.5"
Laptop, 8 gb RAM , i5,
Windows 10 64 bit Pro, 1
TB hdd storage
150 75 11250
Server Dell Dell poweredge r730, 64
gb ram, Quad Core 6tb
hdd, windows 2012R 64
bit Pro,
2 1020 2040
Operating System Microsoft Server: Windows 2012 R
64 bit.
1 23 250
Operating System Cisco Internet Operating System 1 170 170
Operating System Microsoft Client: Windows 10 64 bit 1 100 100
Applications Microsoft Microsoft Office 2012. 1 40 40
Approximate total 0
Table 1: The networking & communication devices and applications
21 | P a g e

OZ Dispatch
Logical Network Design
The explanation and justification of 12 above
Switch – switch hardware component is a networking device that is used to add functionality of the
network. In our network, it will used to attach workstations to the network.
Router – the router will be used in the forwarding of the packets between our networks and the outside
world.
Firewall – the firewall will be used as a security device. It will be filtering the traffic that enters and
leaves our network.
Wireless access points- the Aps will be used by handheld devices to allow them to be attached on the
network.
Laptop computers and Desktop computers – laptop and desktop computers will be used by the staff to
perform their work related duties.
Operating system – server operating system is required to provide services such as dns, dhcp and file
sharing and storage.
Server – server hardware will be used to host services such as the dhcp, dns and file sharing
A test plan that can be used to test the new network
The table below shows a test plan matrix that will be used for the testing of our networking
Ping test PC 1 PC 2 PC 3 Server 0 Server 1 Where test
done
PC 1 Done at
head office
and all
branches
PC 2 Done at
head office
and all
branches
PC 3 Done at
head office
and all
branches
22 | P a g e

OZ Dispatch
Logical Network Design
Ping test PC 1 PC 2 PC 3 Server 0 Server 1 Where test
done
Server 0 Done at
head office
Server 1 Done at
head office
Table 2: test plan that can be used to test the new network
One detailed test script for your test plan
A network test script refers to the scripts that are run to test network connectivity and verification of
the network. The table below show the test scripts to be used on router, switch and PCs
Network Device Script Explanation
Router Show running Shows the running
configurations
Show ip inter brie Shows the configured ip address
of the router interfaces and
interface status
Show ip route Show the routing table
Switch Show vla brief Shows the available vlans and
interfaces configured to access
particular vlan
Show interface trunk Shows the trunking interfaces
Show vtp status Shows the virtual trunking
status
Show span Shows the spanning tree of the
of the switch
PC and Servers Ping Used to test connectivity
Traceroute Used to show the route that is
taken by a packet from source
computer to destination
23 | P a g e

OZ Dispatch
Logical Network Design
Ipconfig Verifies the configured IP
address on the interface of the
PC or server.
Table 3: Detailed test script for your test plan
Acceptance Criteria
Functionality Requirement Validation Checks Network
Acceptance(YES/N
O)
Subnetting All workstations to be
placed in their correct
VLANs
Workstations checked to have been
assigned IP addresses as per the
VLANs
YES
DHCP It is required that PCs
have IP addresses
automatically
Devices have been assigned IP
address by the DHCP
YES
Security PCs from head office
should be able to
access all devices at
the branch level and
vice versa
Ping to all other branches is
successful
YES
24 | P a g e

OZ Dispatch
Logical Network Design
References
Bianco, A. & Neri, F., 2013. Addressing. In: Next Generation Optical Network Design and Modelling. New
York City: Springer, pp. 92-99.
Carthern, C. & Wilson, W., 2016. OSI layers. In: Cisco Networks: Engineers' Handbook of Routing,
Switching, and Security. New York City: Apress, pp. 35-46.
Duggan, M., 2014. Cisco CCIE Routing and Switching v5.0 Configuration and Troubleshooting. In: Cisco
CCIE Routing and Switching. Indianapolis: Cisco Press, pp. 321-3330.
Hooper, H., 2012. CCNP Security VPN 642-648 Official Cert Guide. Indiana Polis: Cisco Press.
Lammle, T. & Swartz, J., 2013. CCNA Data Center - Introducing Cisco Data Center Networking Study
Guide. 6th ed. Hoboken, New Jersey: John Wiley & Sons.
Mariño, P. P., 2016. Optimization of Computer Networks: Modeling and Algorithms: A Hands-On
Approach. 3rd ed. Hoboken, New Jersey: John Wiley & Sons.
Oppenheimer, P., 2014. Top-down Network Design. 2nd ed. Indianapolis: Cisco Press.
Sequeira, A., 2013 . Interconnecting Cisco Network Devices, Part 1 (ICND1) Foundation Learning. 3rd ed.
Indianapolis: Cisco Press.
Velte, T. & Velte, ., 2013. Cisco A Beginner's Guide. New York City: McGraw Hill Professional.
25 | P a g e