Essential Guide

How VMware NSX network virtualization could change networking -- or not

A comprehensive collection of articles, videos and more, hand-picked by our editors

VCE Vblock won't die in the Cisco-VMware network virtualization war

With the launch of NSX, the Cisco-VMware network virtualization battle is on, but that won't spell death for VCE Vblock because users need simplicity.

The VMware NSX launch at VMworld last week may have been the official start of the Cisco-VMware network virtualization battle, but this won't necessarily mean an end to VCE and its Vblock products.

VCE, the coalition of Cisco, VMware and EMC, builds and sells Vblocks, which combine switches, servers, virtualization and storage into one package with management software that stretches across the ecosystem.

In my view, the decision to buy a Vblock isn't a hardware decision; it's a resource decision. Although you get a few racks of expensive equipment, what you are really purchasing is a professional services package. Someone has already done the work to integrate all of the storage, compute and networking pieces for you, even down to VCE the cables and performing assembly. So Vblock will exist as long as VCE can convince customers to pay for those professional services and put revenue on the bottom line.

More on VMware network virtualization

That won't be a difficult sell for VCE as IT management gets deeper into building private clouds, which change internal funding models and make technology integration post-acquisition very difficult.

Building and operating a cloud management platform such as VMware vCloud, OpenStack or Hyper-V take so much project time and so many resources for implementation that few people have the time to argue over the details of a hardware system. VMware works on just about any hardware, so why waste time deciding which hardware is best? VCE's Vblock allows you to just pick something and get started with your cloud planning.

Plus, with Vblock you don't need a lot of equipment. I've been through the numbers, and 20 racks of converged hardware can easily run thousands of virtual machines. At this point, the difference between varying brands of server architecture and storage arrays is quite small.

In my last role, I was building an overlay network with an orchestration system. I found that I cared very little about what hardware was running the system. In fact, the entire hardware provided little value to the solution. Buying Vblocks was cheaper overall when factoring in design, purchasing and negotiation costs. What I appreciated most about Vblocks was that I didn't waste any time discussing storage, compute or network hardware. I spent a day picking out the stock-keeping units for the Vblock package, and then we got on with delivering network services.

So while VMware and Cisco might compete in the public market, VCE is a separate company, with professional services that provide the customer the ability to deploy VMware with the least possible hassle. Nothing about that has changed. VMware and Cisco have entered a new relationship where they compete in networking, but they'll still partner for cloud platforms. While that is new for Cisco and VMware, that isn't new in the industry. Move on, and now let's debate how SDN can change your operational issues.

Read Greg's Ethereal Mind blog

PRO+

Content

Find more PRO+ content and other member only offers, here.

Essential Guide

How VMware NSX network virtualization could change networking -- or not

GUIDE SECTIONS

  1. News
  2. NSX opinions
  3. Video

Join the conversation

5 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

VCE vBlock won't die, because its already dead
Cancel
Many of the VBlocks in the market have become V + C + E or even C + E- this is due to the lack of flexibility within the architecture that leads to 'uncoupling' - thus the "integration value" is lost along the way. when this happens and thus it now becomes very high cost. If you stick with the architecture you lack the flexibility and get locked into the ongoing high cost paradigm without the innovation choice- catch 22. Not "dead"- but needs to be applied to the correct business opportunity with clearly defined scope of opportunity that matches the value. NP
Cancel
Really? Cisco's acquisition of Whiptail is certainly another nail in the coffin
Cancel
I work for VCE. Man, the comments are rabid here. Clearly if you think the Vblock is dead you're holding the chart sideways.

As for the fact that there are many V+C+E Pblox (psuedo Vblocks), many folks think they can do the same for less cost. They can't, but imitation is the sincerest form of flattery. Many of these are sold by resellers who piggyback on the design but can't match the quality, service, or integrated software in the system.

As for Whiptail, our engineering EVP had a response out within hours of the news release. Business as usual. Great, it's in UCS. We'll use it if we need it. Just like everything else at VMware, Cisco, and EMC.

I'm @jellers and I approve this comment. Who are the rest of you?
Cancel
This is no more than what system integrators have been doing for a lot longer than VCE has been in existence and they simply can't deliver on many of those unique requirements a client may have.
Cancel

-ADS BY GOOGLE

SearchNetworking

SearchEnterpriseWAN

SearchCloudProvider

SearchUnifiedCommunications

SearchSecurity

SearchDataCenter

Close