Access your Pro+ Content below.
vSphere VLAN: Understanding 802.1Q VLAN tagging
This article is part of the Network Evolution issue of June 2011 Vol. 2, No. 3
Configuring vSphere VLANs can be more complicated than establishing VLANs in a typical physical network and therefore requires a different approach – 802.1Q VLAN tagging. In a physical network, servers all have their own physical Network Interface Cards (NICs) that are connected to a physical switch port. As a result, VLANs are usually controlled by setting the VLAN ID on the physical switch port and then setting the server's IP address to correspond to that NIC's VLAN. But in a virtual environment, dedicating a physical NIC (pNIC) to each VM that resides on the host doesn't work. In fact, a host physical NIC may service many VMs, which may all need to be connected to different VLANs. Consequently, the old method of setting a VLAN ID on the physical switch port doesn't work. That's where 802.1Q VLAN tagging comes in. VLANs primer VLANs for networking professionals: In this guide learn everything from basic VLAN configuration to setting up VLANs in virtual environments. Networking for virtualization: The basics Before we explain ...
Access this PRO+ Content for Free!
Features in this issue
Virtual desktop infrastructure is seeing speedy uptake, but desktop virtualization network challenges mean investing in load balancing, traffic prioritization and even more bandwidth to support real-time applications to the desktop.
vSphere VLANs have requirements different from those of VLANs in physical environments because VMs are fluid and can't be assigned to one physical NIC. So 802.1Q VLAN tagging offers a new approach to configuring and managing VLANs in vSphere.
Running network diagnostics for virtualization requires a new set of strategies that involve virtual switches, virtual network probes and rerouting traffic for analysis.
News in this issue
In order to implement virtualization, enterprises must go beyond old-school network documentation for a full IT infrastructure audit that shows resources across silos.
One virtualization architect explains the miscommunications between systems and network engineers and how his teams worked together toward managing virtualization more effectively.