Network Virtualisation Explained: VLANs, VXLAN,...

In a nutshell: Network virtualisation separates logical network behaviour from the exact physical topology underneath. It lets teams create segments, overlays and policies in software, but it still depends on a well-designed physical underlay.

What network virtualisation means

Network virtualisation creates logical networks on top of shared physical infrastructure. Instead of every application needing dedicated switches and cables, software can define segments, routing, firewall rules, load balancing and connectivity between virtual machines, containers, clouds and sites.

Classic VLANs are one form of logical separation. Modern overlays such as VXLAN extend the idea across larger data-centre and cloud environments.

Main building blocks

Component	What it does	Buyer question
Underlay	The real IP network carrying overlay traffic.	Is it simple, resilient and observable?
Overlay	Logical network built over the underlay, often using tunnelling.	Which encapsulation and MTU are required?
Virtual switch	Connects virtual workloads inside hosts.	How are policies enforced and logged?
Controller	Central policy, automation and state management.	What happens if the controller is unavailable?
Gateway	Connects virtual networks to physical networks, WAN or internet.	Where is north-south traffic inspected?

Why teams use it

Virtualised networks make it easier to create environments quickly, segment applications, move workloads, support multi-tenant platforms and automate security policy. In private cloud and large virtualised data centres, this removes a lot of ticket-driven network changes.

It is also important for hybrid cloud because cloud networks are already virtualised. The enterprise network team needs a model that maps on-premises segmentation, cloud VPC/VNet design and security inspection consistently.

Common risks

The biggest mistake is hiding complexity instead of managing it. Overlays can make troubleshooting harder if teams cannot see the path across virtual switches, tunnel endpoints, gateways and physical links. MTU mismatches, asymmetric routing and unclear ownership between network and platform teams are common problems.

Security also needs care. Microsegmentation only works when applications are mapped accurately and rules are maintained as workloads change.

Network virtualisation buyer checklist

Is the physical underlay designed for predictable ECMP, MTU and failure behaviour? Which teams own overlay policy, gateways, firewalls and troubleshooting? Can the platform show flow logs across virtual and physical boundaries? How are workloads discovered for microsegmentation policy? Are cloud VPC/VNet designs aligned with on-premises segmentation? What is the rollback plan for controller or policy mistakes?

Sources and further reading

Find vendors: use the TechDirectory company directory to compare telecom providers, system integrators, data-centre operators, IoT specialists and managed service providers in Singapore.

Network Virtualisation Explained: VLANs, VXLAN, Overlays and SDN