VMware vSphere 5.0: Networking Gets Only "also starring" Role

 
 
Cameron Sturdevant Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.
By Cameron Sturdevant  |  Posted 2011-08-24 Email Print this article Print
 
 
 
 
 
 
 

netAP

Creating a vSphere Distributed Switch is much easier than migrating existing vNetwork Standard Switches.

VMware vSphere 5.0 marks a step forward for the vNetwork Distributed Switch (vDS) with the addition of a SPAN monitoring port and user-definable network resource pools, and virtual-to-physical configuration of QoS using 802.1 tagging.

These are all advances in virtual switch infrastructure. The next step is to make networking as easy to implement as creating a VM.

I'll admit that lab networking architecture (whether in eWEEK Labs or in your own test environment) isn't stringently planned out. Nor is it subject to the kind of rigorous change controls that would apply to a production network. Further, our existing virtual switches provided "good enough" networking and weren't maintained much beyond making sure that all the VMs could see each other and the storage.

Having said all that, it's pretty clear that networking is still an "also starring" technology at VMware. During my tests, one of the chief headaches of my time in the trenches was caused by the migration of the existing, virtual standard switches associated with each of my ESX host systems. There are a variety of ways to go from every-host-has-it's-own-switch to one big switch. The point is that it was very difficult to even get a handle on the process. And once I had adopted the simplest method (given my small environment and quiescent VMs) it was still tricky to both migrate the switch and maintain connectivity to the management port via vCenter.

I would like to see more automation built into the vDS creation process. At the end of the day, adding and removing physical host network resources should be about as easy as standing up and pulling down a VM.

 
 
 
 
del.icio.us | digg.com
 
 
 
 
 
 

Submit a Comment

Loading Comments...

 
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel