vCloud and VEPA: Neither answer is a winner

vCloud and VEPA: Neither answer is a winner

Rivka Gewirtz Little, Senior Site Editor

Lots of vendors say they have the answer for managing network traffic between virtual machines, but users don't seem to think there is one solid strategy.

VMware released the vCloud director, which implements switching, routing, firewalling, NAT and even DHCP servers within the VMware framework. Cisco took a stab at virtualization networking with its virtual switch, the Nexus 1000V. Other vendors are going with Virtual Ethernet Port Adapters (VEPA), which pull all the traffic out of the hypervisor and let the first-hop switch handle all the necessary aspects of bridging, VLANs, routing, QoS and security.

According to Fast Packet blogger, Ivan Pepelnjak, vCloud and Cisco's VN Tag approach are both proprietary, which limits their use, and VEPA still needs hypervisor support.

    Requires Free Membership to View

    By submitting your registration information to SearchNetworking.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchNetworking.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

These limitations make all of the above solutions “half-baked.”

Read Ivan's “vCloud and VEPA both lack a real network virtualization solution” blog.

Next up, virtualization problems are plentiful, so what's the solution?


This was first published in December 2011

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.