Network Design Documentation

This documentation is about network design using a top-down design methodology. It includes project goals, business goals and constraints, technical goals and trade-offs, project scope, project requirements, network design, switching and routing protocols, and security mechanisms.

[Document title]

[Document title]
Contents
introduction......................................................................................................................................3
Project goal......................................................................................................................................3
Business goals and constraints.....................................................................................................3
Technical goals and trade-off.......................................................................................................3
Project scope....................................................................................................................................4
Project requirements........................................................................................................................4
Hardware requirements................................................................................................................4
Software requirements.................................................................................................................5
Network design................................................................................................................................6
Logical design and addressing.....................................................................................................6
Physical design.............................................................................................................................6
Switching and routing protocols......................................................................................................7
Security mechanism.........................................................................................................................7
Conclusion.......................................................................................................................................7
References........................................................................................................................................8

[Document title]
Introduction
This documentation is about network design using a top-down design methodology. This
approach subdivides the task at hand into smaller simpler stages of coming up with a solution. In
this documentation, we are creating a wireless network design for a home delivery service in
Parramatta in Australia for OZ dispatch. OZ dispatch is one of the clients being granted a
network design solution. It has its main office at Parramatta and other 20 collection and delivery
centers. OZ dispatch deals with customer delivery and controls the payment process through a
website. OZ will be operating using office desktops and smartphones as the end devices in the
design network.
Project goal
The aim of this project is to come up with a suitable design of the organization that will aid in the
daily operations of the orders and delivery services to the customers. The network should also
create a favorable working environment for both the manager and the delivery officers. This will
be achieved by creating an efficient and scalable network in the OZ dispatch organization
considering its business goals and ts constraints together with the traffic goals and the trade-offs
as explained below.
Business goals and constraints
The business goals are customer and staff oriented (DiMicco, Millen, Geye, Dugan, Brownholtz and
Muller, 2009). The following are the goals.
 The customers of the OZ dispatch should be able to navigate through the web and place
orders in the system.
 The orders made by the customers should be dispatched to the CDCs accordingly.
 The orders made by the customers should be collected separately in the CDCs.
The following are the consideration of the constraints in the whole process of the design and the
delivery services.

[Document title]
 Time is a major constraint following the evolution in technology and the competitors
also. From this, before putting up a workable design, the analysis should be done on the
same scenarios and a report generated to guide on the construction of network design
(Singh and Chaudhuri, 2009).
 Cost is another constraint in that the expenditure of hosting an independent network with
its servers is a bit expensive although there is a need for the same in the OZ dispatch
organization.
 Another constraint on the same is the allocation of available resources as is a must for the
project’s success.
Technical goals and trade-off
Technical goals mostly rely on the network behavior, the efficiency and quality of the
networking devices and the security of the network from the information security to device and
equipment security (Hvolby and Steger-Jensen, 2010). This may include the following.
 Providing topmost security and installing access control features in the network.
 Availability of the network all along to ensure a smooth flow of daily activities in the
organization.
 Network efficiency providing efficiency in communication and data transfer among the
organization.
 The network scalability should be more scalable to give room for expansion even in the
future.
On the trade-offs aspects, we shall have the following in the OZ dispatch organization.
 Security.
In order to achieve a high-level security detail on the network, the employees and the
users must be restricted from unwanted performances in the network. The employees
should not download any unnecessary files from the internet.
 Network performances
This can be increased by increasing the bandwidth of the network.
 Network availability.
The network availability can be achieved by adding additional back up lines to the
network.

[Document title]
 Installation of quality networking devices and equipment to support more users and
support network expansion.
Project scope
This project aim as pointed out earlier is to come up with a network design for the OZ dispatch
organization. The OZ organization wants to put up a network that will serve its daily activities.
OZ organization offers home delivery services to its customers after order placement and
payment from the customer through the web. This company wants a design that will host it
independently. The organization has a main office in Parramatta, Australia, and other 20
collection and delivery centers (CDCs). The organization has a manager who is also the data
analyst, the sales and marketing personnel, the accountant and the owner of the OZ. The main
office hosts all the servers, also the manager, and the 20 delivery officers each having a
smartphone. Each CDC has a wireless access point and office desktops are available in the main
office connected through the cables (Zouganeli, Tyssø, Feng, Arnesen and Kapetanovic, 2014).
Project requirements
Hardware requirements
The table below shows the hardware requirements and their description and cost (Pfaff, Pettit.,
Amidon, Casado, Koponen and Shenker, 2009).
Device Description Cost Seller Quantity Total cost
Switch 24- port cisco
switch
$250 Cisco
sellers
24 $6000
Router 24 gigabit cisco
ASR 9000 series
router
$200 Cisco
sellers
24 $4800
Server 360 power edge
server
$400 Hp dealers 2 $800
RJ45 Connectors $20 Cisco
sellers
21 $420

[Document title]
Cable Cat 8 Ethernet
cable
$150 Cisco
sellers
10 $1500
Desktop  Hp
 4gb
RAM
 500 GB
Hard disk
storage
 Intel core
i3
 32inch
screen
 Window
10 pro.
Operating
system
$210 Hp dealers 25 $5250
Mobile phone  WPA2
enabled
 WiFi
enabled
$280 Smart
phone
dealers
21 $5880
TOTAL $24650
The devices use is as follows:
Switch –used for outsourcing and expanding a network.
Sever – used for storage of the information and data circulating in the network.
Cables – used for connecting networking devices.
RJ45 – used as connectors at the ends of the cable.
Mobile phone (Smartphone) – used to access the network.

[Document title]
Computers – these are the end devices in a network.
Software requirements
Below are the required software.
 Operational software – windows 10 professional OS for the desktops and Android
version for the smartphones.
 System software.
- Microsoft Windows.
 Application software
- Web application software; Firefox Mozilla, chrome, opera mini.
- Microsoft office, Adobe
The user communities, data stores, network application, and traffic flow table (Van Lamsweerde,
2009).
User communities Data stores Network application Traffic flows
Customers and
manger
Application server Web application High
Data analyst,
accountant, sales, and
marketing executive.
DHCP server Application server Medium
Employees Application server Microsoft outlook low
Employees DNS server, FTP
server
FTP in windows Low

[Document title]
Network design
Logical design and addressing
The OZ network will include a hybrid topology i.e ring and star topology. The network will have
a firewall to control inputs in the network. Routers will be installed to ensure wireless access and
servers to allocate and store user facilities. Below is a diagram.
The addresses and naming will be as follows;
 The subnet mask: 255.255.252.0
 The network address: 191.2.68.0
 The broadcast address: 191.2.71.252 – 191.2.71.259
 The default gateway: 191.2.71.1
 The IP addresses will range from: 191.2.68.3 – 191.2.68.30
 Subnet name- CDC1-CDC20
Physical design
This is the actual layout of the network structure including the arrangement of the networking
devices in the OZ premises. In this case, we shall use the hybrid topology of two physical
designs, the ring, and star topology (Singla, Hong, Popa and Godfrey, 2012). The servers will
connect to the ring from a switch and the access/workstations connect via a ring topology.
Below is a diagram showing the logical and physical design of the OZ network.

[Document title]
Switching and routing protocols
Switching protocols are for maintaining automatic connections and helps in processing a packet
from one device to another. The protocols include; the trunking protocol, RSTP, PortFast, and
UplinkFast (Kompella and Rekhter, 2015). The routing protocols offer an easy configuration as
well as the use of simpler methods to forward packets. The protocols used are; the Open Shortest
Path Fast, Border Gateway Protocol, and the Routing Information Protocol.
Security mechanism
This is the mechanisms to be implemented to make sure the network facilities are all secure.
They include; authorization, account, packet filters, firewall, data encryption, and port security
are all implemented in the network.

[Document title]
Test plans
We shall use the cisco packet tracer to verify the connection. Then the command prompt will be used to
ping the address of the device and check the availability of the internet.
All the devices should be able to communicate within the network
Pinging among the devices

[Document title]

[Document title]
Pinging the dhcp server.
Communication among the different departments.

[Document title]
Communication among the same departments.
Conclusion
The description above contained in this document can serve as a solution to the OZ organization
network design. The network should be implemented as per the protocols and security
mechanism should be comprehended with regular network updates and troubleshooting should
be performed regularly.

[Document title]
References
DiMicco, J., Millen, D.R., Geyer, W., Dugan, C., Brownholtz, B. and Muller, M., 2009,
November. Motivations for social networking at work. In Proceedings of the 2009 ACM
conference on Computer supported cooperative work (pp. 711-720). ACM.
Hvolby, H.H. and Steger-Jensen, K., 2010. Technical and industrial issues of Advanced Planning
and Scheduling (APS) systems. Computers in Industry, 61(9), pp.845-851.
Kompella, K. and Rekhter, Y., 2015. OSPF extensions in support of generalized multi-protocol
label switching (GMPLS)(No. RFC 4203).
Pfaff, B., Pettit, J., Amidon, K., Casado, M., Koponen, T. and Shenker, S., 2009, October.
Extending networking into the virtualization layer. In Hotnets.
Singh, S.K. and Chaudhuri, A., 2009. The reality of India: folding constraints into business
strategy. Journal of Business Strategy, 30(4), pp.5-16.
Singla, A., Hong, C.Y., Popa, L. and Godfrey, P.B., 2012. Jellyfish: Networking data centers
randomly. In Presented as part of the 9th {USENIX} Symposium on Networked Systems Design
and Implementation ({NSDI} 12) (pp. 225-238).
Van Lamsweerde, A., 2009. Sofwtare Requirements: From system goals to UML models to
software (Vol. 10). Chichester, UK: John Wiley & Sons.
Zouganeli, E., Tyssø, V., Feng, B., Arnesen, K. and Kapetanovic, N., 2014. Project-based
learning in programming classes–the effect of open project scope on student motivation and
learning outcome. IFAC Proceedings Volumes, 47(3), pp.12232-12236.