HP ProLiant DL288 ISS Technology Focus, Volume 10, Number 2 - Page 2

What is EVB?

Get HP ProLiant DL288 PDF manuals and user guides View all HP ProLiant DL288 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 2 highlights

There is agreement within the industry that we need to standardize the management of these virtual networks. There is also agreement that we should base the mechanism on some iteration of the EVB standard. Disagreement occurs over: The implementation techniques The effect on physical assets (cost, performance, reliability) Whether server administrators or network administrators should control these virtual network systems What is EVB? The authors of the 802.1Qbg project within IEEE 802.1were also responsible for creating an Edge Virtual Bridging ad-hoc industry group. Together, these groups address the following components of EVB: Virtual Ethernet Port Aggregator (VEPA) Virtual Station Interface (VSI) Discovery Support for multiple channels on one physical link Virtual Ethernet Port Aggregator HP is leading development of the VEPA for virtual network switching as part of EVB. The VEPA standard ensures that new technologies will work within existing IT environments and organizational roles. Our goal is to give you a simple way to migrate to advanced technologies at the server-to-network edge without requiring an entire overhaul strategy for your data center. VEPA works with an adjacent, external bridge to support bridging between multiple VMs and external networks (Figure 1). VEPA forwards all VM-originated frames to the adjacent bridge for frame processing and reflective relay (also commonly known as "hairpin‟ forwarding). VEPA steers and replicates frames from the VEPA uplink to the appropriate destinations. You can implement VEPA in software or with embedded hardware. Figure 1. Comparison of VEB and VEPA models. VEPA forwards VM frames to an external bridge and uses reflective relay for VM-to-VM traffic. VEPA is a simple extension to VEB with similar port configuration and address tables. It requires only minor changes to frame forwarding behavior and no changes to existing frame formats. Migration between VEB and VEPA is straightforward, and you can deploy both in the same station (server) and over the same physical link. To do this, VEB and VEPA must operate on separate channels. 2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
2
There is agreement within the industry that we need to standardize the management of these virtual networks. There is also
agreement that we should base the mechanism on some iteration of the EVB standard. Disagreement occurs over:
The implementation techniques
The effect on physical assets (cost, performance, reliability)
Whether server administrators or network administrators should control these virtual network systems
What is EVB?
The authors of the 802.1Qbg project within IEEE 802.1were also responsible for creating an Edge Virtual Bridging ad-hoc
industry group. Together, these groups address the following components of EVB:
Virtual Ethernet Port Aggregator (VEPA)
Virtual Station Interface (VSI) Discovery
Support for multiple channels on one physical link
Virtual Ethernet Port Aggregator
HP is leading development of the VEPA for virtual network switching as part of EVB. The VEPA standard ensures that new
technologies will work within existing IT environments and organizational roles. Our goal is to give you a simple way to
migrate to advanced technologies at the server-to-network edge without requiring an entire overhaul strategy for your data
center.
VEPA works with an adjacent, external bridge to support bridging between multiple VMs and external networks (Figure 1).
VEPA forwards all VM-originated frames to the adjacent bridge for frame processing and reflective relay (also commonly
known as
“hairpin
‟
forwarding). VEPA steers and replicates frames from the VEPA uplink to the appropriate destinations.
You can implement VEPA in software or with embedded hardware.
Figure 1.
Comparison of VEB and VEPA models. VEPA forwards VM frames to an external bridge and uses reflective relay for VM-to-VM
traffic.
VEPA is a simple extension to VEB with similar port configuration and address tables. It requires only minor changes to frame
forwarding behavior and no changes to existing frame formats. Migration between VEB and VEPA is straightforward, and
you can deploy both in the same station (server) and over the same physical link. To do this, VEB and VEPA must operate on
separate channels.