Network Design Steps

1. Outline the requirements

Before designing any network we must be aware of the purpose of the network and it should be efficiently conveyed to everyone working on the design so that they stick to the purpose.

2. Draw out the network topology

Network topology plays a big part in the implementation of the network as it informs the network administrator about the network components, segments, and connections between different segments of the network.

<script async src=""

3. Keep a register of the hardware

We should note down all the hardware components used and keep a record of how they are connected and configured within the network. We should also keep a backup of the configurations on remote devices, in case of an outage in the network.

4. Label the hardware

Labeling the hardware correctly helps us in differentiating between the hardware which would otherwise look identical. The labels should be based on the network device role and configuration used in the network.

5. Keep a record of the software used

We should keep a record of all the software, along with the versions, used on all the devices, and also the proof of licenses for that software to avoid future copyright infringement litigation if any. 

6. IP addresses and subnets

The IP addresses for individual components and subnets for the segments of the networks must be carefully assigned and documented for future references. The network diagram should identify the hardware with their hostnames and IP addresses.

7. Test the network

Before transitioning the network into production, we must always test the network by running a prototype of the network in a test environment to confirm everything works as intended.

8. Allow room for redundancy

Adding redundant components in a network helps in case of a failure or a security breach. It helps increase the availability of the network.

9. Network security

Security is a major component for everything in the world these days, and every possible step should be taken to keep the network secure and save it from malicious attacks. Network security should be a part of the network design and not an afterthought. 

10. Plan for the future

All networks become slow more and more devices are put onto the network. Planning for network expansion while designing the network is a must.

This section will be explained based on the cloud solution for migrated applications along with the on-prem solution.

Figure1: Preliminary Network Design

The above pictorial representation shows the architecture of the cloud-side application migrations. There will be a load balancer that will receive the connection requests from the on-prem or BYOD devices via the internet to access the applications hosted in the cloud such as Moodle LMS. The load balancer can also act as a web application firewall to stop certain IP ranges while directing the traffic accordingly to the application instance. Maria DB will be used as the database server to store sensitive data such as credentials and will work with an Active Directory if required. Instance will be created under a scaling policy such as increment server by one if usage of server is over 80% and decrement if usage is less than 80 percent. 

The instance will be used to host the applications that are migrated. Redis cache will make sure that the ram of the instances is shared and people on different instances cannot differentiate from the server they are connected to. Blob storage will be useful to store all high storage artifacts such as images, videos, etc. the entire setup will be hosted on VNET in the Sydney region of Azure services.

<script async src=""

Some assumptions before describing the on-prem of SaveTheChildren organization are as follows:

  • Here is one HQ
  • There will be one central office
  • There will be 2 other offices
  • They use systems and phones in their office
  • They have switches and media servers, and other local server in their on-prem offices
Figure2: Office COnstruction

IP Addressing for the corporate office will be private Ip addresses assigned by their local intranet Admins. range of class B addressing with 4 hosts for office locations with a maximum of 16382 users per host. This will be sufficient enough for the entirety of the operations based on our assumptions.