Wow are they late to this market. We have been using the Microsoft SDN solution (based around standards like GRE - so works with all your existing network stuff) for well over a year now....
If you visit VMware's certifications portal you may notice there's something missing: Virtzilla currently offers no courses for its NSX network virtualisation product. The only entry under NSX is for a forthcoming “Associate” level certification, the very lowest of VMware certifications that ask candidates to prove familiarity …
Oh, ye of little education. Firstly, VMware's offering is a combination of the older vCNS solution and Nicira following the acquisition in 2012. So in effect, the offering goes way back beyond your 'over a year' - not exactly "Wow are they late to this market".
Oh, and being first isn't necessarily the best - the line Microsoft often say about server virtualization - I seem to recall they were rather late to the party when it comes to the server side?
Secondly, Microsoft's SDN solution is highly proprietary - Server 2012 or bust. NSX comes in two flavours, one purely for vSphere, however the other is multi-hypervisor. Both are based on Open vSwitch (hence the multi-platform support).
And as for standards support, well, so long as you can do a basic VLAN or two and up the MTU size, you're pretty much good to go with NSX. After all, isn't moving up from the tin rather the point of being 'Software Defined'?
Open vSwitch alone doesn't provide you the ability to create a virtual network that's topology independent that supports L2 and L3
Microsoft does this using standards based transmission methods. VMWare uses a proprietary solution.
Not sure what you're getting at here - how would you define a VMware vSwitch then if not SDN? So, saying that they're late to the market is a little odd...
Re: RE: AC
A VMware vSwitch alone is not SDN. You clearly have no idea what SDN is.
What exactly is NSX?
Ok... it looks a little like VXLAN. There's nothing on VMware's site that explains how this integrates with the non-virtualized network. It looks just like a layer-2 over layer-3 solution. How does it handle multicast? Does this mean I have to use their specialized "yet another inconsistent" web gui? Is there integration with vSphere?
Does it comply with any standards? Can I for example make use of a Cisco/HP/Juniper gateway when linking with non-NSX networks?
It seems to me like VMware doesn't know this or you would think they'd make it pretty clear on their web page.
Don't fear Technofobes - Microsoft has got you covered!
It has been a very strange one, seamingly this battle has suppose to have been between Cisco and VMware, yet both have still not made it out of the starting block, no doubt due to the many variants they have out there in the wild.
Neither should you be suprised by Microsoft seizing the initiative, not only do they have a seat at the top table within both the ONF and OpenDaylight, their Azure cloud is already battling with the likes of Amazon & Google, their SDN strategy is based on two very simple plays Windows Server and Systems Center, unlike Cisco and VMware access to training is FREE and easily accessible through the Microsoft Virtual Academy.