2.12. Virtualization Fundamentals
💡 First Principle: Virtualization is abstraction—separating the logical from the physical. A virtual server doesn't know or care which physical CPU is running it. This abstraction enables flexibility, efficiency, and isolation—but it also hides what's happening from traditional network tools.
Consider this troubleshooting scenario: You're told that Server A can't reach Server B. You check switch ports, run show mac address-table, verify VLAN assignments—everything looks fine. The problem? Both servers are VMs on the same physical host, connected through a virtual switch that your physical switch can't see. Traffic between them never touches a physical cable. Without understanding virtualization, you'd troubleshoot the wrong layer entirely.
What happens when you ignore the virtual layer: A VM gets migrated to another host for maintenance. Its MAC address suddenly appears on a different switch port. STP sees the topology change and recalculates. Port security (if configured) blocks the "new" MAC. Without understanding vMotion and VM mobility, these events look like attacks or failures instead of normal operations.
Why network engineers must understand virtualization:
- Virtual switches connect VMs and are easy to miss: a VMware vSwitch can participate in CDP (and a distributed switch in LLDP), but it is not on by default, so the virtual layer stays invisible in
show cdp neighborsuntil someone enables it - vNIC bandwidth isn't limited by physical ports—oversubscription happens invisibly
- VM mobility means a server can move between physical hosts without changing IP
- Containers create thousands of network endpoints on a single host
The network impact: When a VM moves from one physical host to another, the MAC address moves too. The network must handle this without dropping packets. Technologies like VXLAN exist specifically to solve virtualization-related networking challenges.
