Skip to content

Redundant Network Implementation

Use of duplicate components to enhance reliability and fault tolerance

Redundant network implementation project overview:

Redundant network implementation project aims to provision or upgrade the LAN, WAN network, taking into account the following: 

• High availability of network devices with dual connections between switches

• Link aggregation to devices/services such as high availability firewalls, clusters where the network also has a double connection (link aggregation)

• Ensure the proper bandwidth is distributed to the network consumers and network devices are scaled properly

• Comply with the business requirements that will be agreed upon during the pre-design phase (VLANs, SWITCH level routing, L1, L2, L3 needs)

• Assure required network topology pre-requirements are met

This project considers implementing a redundant network to a site/location where the network equipment is stacked and is used by highly available services (highly available Sophos Firewall, Hyper-V Clusters) with link aggregation and endpoint devices.  

This project refers to a network setup with duplicate or backup components, such as routers, switches, or links, to provide fault tolerance and resilience against failures. Redundant networks often employ load balancing and failover techniques to ensure uninterrupted service even if one component fails.

Redundant network implementation project approach:

We assess the business requirements, including the current network topology, and prepare a detailed plan, including the final approach, tools, technologies, and connections for building a redundant network, including double physical connections. If existing network devices need to be updated/replaced, we make as many settings as possible on the new devices without connecting them to the old devices. Our colleagues create customized scripts based on which we can test the operation of the devices connected to the network equipment. 

We connect the new devices to the old devices (also using the link aggregation method) and reconnect the endpoints at the given times according to the plan. We usually start with your workstations/simple endpoints until we reach about 50% utilization of the new device, constantly monitoring the used bandwidth on the up-links. Based on this approach, we aim to avoid burdening your old and new devices with high bandwidth usage on the up-links. 

In the next step, we begin moving one node of the clusters in the new devices to the final configured ports during a period when data traffic is minimized (weekend, night). In the case of a Hyper-V cluster, virtual servers running on one node are moved to other nodes, and then LAN link aggregation is transferred to the new switch devices. After successful tests, we migrate the running virtual machines back to the Hyper-V node. 

During the last phase, we transfer network devices/connections with low availability to new devices with downtime that cannot be avoided.

Redundant network implementation project in-scope activities:

  • Topology and detailed plan preparation
  • Order necessary hardware (Switch, router, cables, accessories)
  • Perform basic settings
  • Installation of devices in a rack and connect to the appropriate equipment
  • Creation of the scripts for checking the devices connected to the network
  • Preparation of a detailed migration plan
  • Configure the new network equipment
  • Cabling and physical connections change during weekends or business hours

Redundant network implementation project needed hardware and software:

The necessary hardware and licenses will be defined during the project analysis phase, as this varies from case to case.

Redundant network implementation project pre-requirements:
  • Free space in the rack cabinets (details will be provided during the analysis phase)
  • Free ports in current network devices during the transition period until both old and new devices operate simultaneously
  • Providing access to the server room
  • Securing operations teams (Hyper-V Cluster, SQL cluster, Windows servers)
  • Providing connection and configuration of monitoring systems
We provide “high available network” and “network high availability” implementation projects for medium and large organizations
  • “High available network” typically refers to a network infrastructure that is designed to maintain high availability or uptime, ensuring that network services remain accessible and operational with minimal downtime.
  • “Network high availability” refers to a network’s capability to remain operational and accessible even in the face of failures or disruptions. It can include redundant components, failover mechanisms, and other strategies to minimize downtime and ensure continuous operation.