Virtual Switches and Networks

When many VMs live on one physical server, they still need to talk to each other and the outside world. A virtual switch (vSwitch) is software inside the hypervisor that does the job of a physical switch, but for virtual machines.

It forwards Ethernet frames between VMs and out through the host physical network cards, so the network now reaches inside the server itself.

Each VM is given one or more virtual NICs (virtual network interface cards). To the guest OS, a vNIC looks exactly like a real Ethernet adapter with its own MAC address (Media Access Control hardware address).

The vNIC connects to a port on the virtual switch. From there the hypervisor decides whether traffic stays inside the host or exits onto the physical LAN.

A virtual switch works like its physical cousin: it learns which MAC address sits on which virtual port and forwards frames only where they belong. Traffic between two VMs on the same host never touches a physical cable, so it is extremely fast.

When a VM needs to reach a different host or the internet, the vSwitch sends the frame out through an uplink, the host real network adapter.

An uplink is the physical NIC on the host that connects the virtual switch to the real network. You can bind several physical NICs to one vSwitch for more bandwidth and redundancy, a technique called NIC teaming or link aggregation.

If one uplink cable fails, the others keep the VMs online. Without an uplink, a vSwitch becomes isolated and VMs can only talk among themselves.

Virtual switches support VLANs (Virtual Local Area Networks) just like hardware switches. You can place VMs into separate VLANs so, for example, web servers and database servers are isolated even on the same host.

The vSwitch tags frames with VLAN IDs and passes them over a trunk uplink to the physical network, keeping segmentation consistent from the virtual world to the physical one.

Hypervisors offer several vSwitch connection modes:

• External: bound to a physical NIC, so VMs reach the LAN and internet.
• Internal: VMs talk to each other and the host, but not the outside network.
• Private: VMs talk only to each other, fully isolated even from the host.

Choosing the right mode controls exactly how far a VM traffic can travel.

Many desktop hypervisors offer a NAT (Network Address Translation) mode. The VMs sit on a private virtual network and share the host single IP address to reach the internet, just like home devices share one public address.

NAT is convenient for labs because VMs get internet access without needing their own address on the real LAN, but inbound connections require port forwarding.

In large data centers, a distributed virtual switch spans many physical hosts and is managed as one logical switch. VMware vDS and similar tools let admins configure network policy once and apply it everywhere.

This keeps settings consistent when a VM live-migrates between hosts, since the network configuration follows the VM automatically rather than being set per host.

SDN (Software-Defined Networking) separates the control plane (decisions about where traffic goes) from the data plane (actual forwarding). A central controller programs the network through software, making it flexible and automated.

Virtual switches are a natural fit for SDN: the entire network can be defined, changed, and scaled in code rather than by plugging cables, which is essential at cloud scale.

Modern troubleshooting often ends inside a host. A VM with no connectivity might have its vNIC attached to the wrong vSwitch, the wrong VLAN, or an uplink that is down. Understanding the virtual layer saves hours of chasing physical cables that are fine.

The same concepts (switches, VLANs, MAC addresses) apply, just implemented in software within the hypervisor.

A VM vNIC plugs into a vSwitch port; the vSwitch forwards local traffic instantly and sends external traffic out an uplink to the physical LAN, optionally tagged with a VLAN. Choosing external, internal, private, or NAT modes controls reach, and distributed switches plus SDN scale this design across whole data centers.

Test your understanding of virtual networking modes.

A virtual switch forwards frames between VMs using their virtual NICs and connects to the physical network through an uplink. vSwitches support VLANs and offer external, internal, private, and NAT modes to control reach. Distributed switches and SDN scale this design across data centers, so network troubleshooting now extends inside the host.