Comments on: VMware tries to expand virtual networks with VXLAN http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/ Wed, 22 May 2013 02:49:20 +0000 hourly 1 http://wordpress.com/ By: media http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/#comment-652873 Mon, 05 Sep 2011 06:26:36 +0000 http://gigaom.com/?p=399244#comment-652873 VMware has yet again won the hearts of its clients because of regularly updating and upgrading their features and services.
http://v12ntoday.com/blogposts/vmware-plans-on-strengthening-the-storage-department-after-altering-their-computing-model.html

]]> By: Ashish Shah http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/#comment-652000 Wed, 31 Aug 2011 17:47:33 +0000 http://gigaom.com/?p=399244#comment-652000 Derrick,

Your comment about OTV being limited Layer 2 is incorrect. OTV is meant to extend L2 over L3 (IP) networks.

Cisco white paper on VXLAN has a comparison on VXLAN vs. OTV and LISP:
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-685115.html

Quote:
“Working with OTV and LISP
VXLAN is intended for creating more logical networks in a cloud environment. Overlay Transport Virtualization (OTV) while using similar frame format as VXLAN, is a data center interconnect technology extending Layer 2 domains to different data centers over Layer-3. Unlike VXLAN, OTV has simpler deployment requirements since it does not mandate multicast-enabled transport network. Locator ID Separation Protocol (LISP) goes a step further by providing IP address mobility between data centers with dynamic routing updates. While VXLAN, OTV, and LISP may share similar frame format, they serve very different networking purposes and are hence complimentary to each other.”

]]> By: Ashish Shah http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/#comment-651995 Wed, 31 Aug 2011 17:39:21 +0000 http://gigaom.com/?p=399244#comment-651995 Derrick,

Your comment about OTV being limited to a Layer 2 environment is incorrect. OTV is meant to extend Layer 2 over Layer 3 (IP) networks.

Cisco VXLAN white paper has a section on VXLAN vs. OTV and LISP.
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-685115.html

“Working with OTV and LISP
VXLAN is intended for creating more logical networks in a cloud environment. Overlay Transport Virtualization (OTV) while using similar frame format as VXLAN, is a data center interconnect technology extending Layer 2 domains to different data centers over Layer-3. Unlike VXLAN, OTV has simpler deployment requirements since it does not mandate multicast-enabled transport network. Locator ID Separation Protocol (LISP) goes a step further by providing IP address mobility between data centers with dynamic routing updates. While VXLAN, OTV, and LISP may share similar frame format, they serve very different networking purposes and are hence complimentary to each other.”

]]> By: Juan Lage http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/#comment-651878 Wed, 31 Aug 2011 07:49:28 +0000 http://gigaom.com/?p=399244#comment-651878 Yes, but it is non-standard. This is isn’t new indeed, but the relevant thing is that it comes from the biggest virtualization player and networking player together, and it comes as IETF standard proposal backed by other vendors (incl. Citrix, not mentioned on the article).

]]> By: Juergen Brendel http://gigaom.com/2011/08/30/vmware-tries-to-expand-virtual-networks-with-vxlan/#comment-651756 Tue, 30 Aug 2011 19:44:34 +0000 http://gigaom.com/?p=399244#comment-651756 This is nothing new, though. Companies like vCider ( http://vcider.com ) are offering this as a service already. And contrary to a vendor specific solution, you can actually set up networks that span different cloud, from different providers (EC2, Rackspace and machines in your data center all on the same LAN).

]]>