2
Introduction
Hypervisors add a new layer of software and virtual networking that dramatically affects data center
servers and their associated network connectivity.
In the past, network administrators managed the external network infrastructure and occasionally
managed the server NICs. Server administrators managed the server, the applications running on the
server, and usually the server NICs. Hypervisors push the boundary of network infrastructure into the
physical server by their use of virtual switches (commonly referred to as soft switches or vSwitches).
This blurs the line between the domains of the server administrator and of the network administrator.
Server administrators typically configure the vSwitches but can’t see or change the external network
configurations. Network administrators can’t configure or debug the vSwitches. Challenges arising
from hypervisors include performance loss and management complexity of integrating software-based
vSwitches into your existing network management.
Industry leaders are proposing two fundamentally different approaches to deal with server-network
edge challenges and to provide more management insight into networking traffic in a virtual machine:
• Edge Virtual Bridging (EVB) with Virtual Ethernet Port Aggregator (VEPA) technology
• Port extension technology
The EVB approach uses industry-standard technologies at the server-network edge. It promotes
network management and network service provisioning as close to the edge as possible. The industry-
standard approach ensures that new technologies will work within your existing environments and
organizational roles. The goal of HP is to enable a simple migration to advanced technologies at the
server-network edge without requiring an entire overhaul strategy for your data center.
The port extension approach reflects all network traffic onto a central controlling bridge. This gives
network administrators full access and control but at the cost of bandwidth and latency.
The IEEE standards supporting networking in virtual machine (VM) environments are in the final draft
stages. It is not clear the extent to which hardware and hypervisor vendors will support these
standards. This uncertainty means that whether you are a server administrator or network
administrator, you may need to consider numerous factors when choosing new server and network
technologies.
Virtual Ethernet Bridges
A Virtual Ethernet Bridge (VEB) is a virtual Ethernet switch that you implement in a virtualized server
environment. It is anything that mimics a traditional external layer 2 (L2) switch or bridge for
connecting VMs. VEBs can communicate between VMs on a single physical server, or they can
connect VMs to the external network.
The most common implementations of VEBs are software-based vSwitches built into hypervisors. But
vendors can use the PCI Single Root I/O Virtualization (SR-IOV) standard to build hardware-based
VEBs in NICs.
Software-based VEBs – Virtual Switches
In a virtualized server, the hypervisor abstracts and shares physical NICs among multiple virtual
machines, creating virtual NICs for each virtual machine. For the vSwitch, the physical NIC acts as
the uplink to the external network. The hypervisor implements one or more software-based virtual
switches that connect the virtual NICs to the physical NICs.