Hey folks--this is the second of three posts looking a little more closely at VXLAN. If you missed the first post, you can find it here. In this installment we are going to look at the some of the other options out there. Two of the most common questions we see are ”why do I need yet another protocol?” and “can I now get rid of X?” This should help you answer these questions.So, let’s dig in… Read More »
Yes, I am still talking about VXLAN, rather you folks are still talking about VXLAN, so I thought its worthwhile digging deeper into the topic since there is so much interest out there. There also still seem to be a fair number of misconceptions around VXLAN, so let’s see what we can do to clear things up.
This time around, I have some partners in crime for the discussion:
Larry Kreeger is currently a Principal Engineer at Cisco Systems’ SAVTG working on Nexus 1000V architecture. Larry has a wide ranging background in networking accumulated from over 25 years of experience in developing networking products. His recent focus is data center networking, especially as it relates to data center virtualization.
Ajit Sanzgiri has worked on various networking technologies at Cisco and other bay area networking companies over the last 16 years. His interests include hardware based switching and routing solutions, Ethernet and wireless LANs and virtual networking. Currently he works on the Nexus1000v and related network virtualization products.
So, Larry and Ajit have put together this VXLAN primer--its fairly dense stuff, so we are breaking this into three posts. In this initial post, we’ll cover the basics--why VXLANs and what is VXLAN. I know I’ve covered this to some degree already, but Larry and Ajit are going to dig a little deeper, which will hopefully help clarify the lingering questions and misconceptions. In the next post, we’ll discuss how VXLAN compares with the other tools in your networking arsenal, and, in the final post, we’ll cover more of the common questions we are seeing.
So, the recent VXLAN announcement we made with some of our partners (including VMware, Citrix, and RedHat) certainly generated a lot of questions.
So let me cover some of the most common ones I have heard.
Why do we need a new protocol? We already have VLANs, MPLS, OTV, LISP and a whole host of other acronyms to contend with!
From my perspective, Cisco continues to be a fun place to work for a couple of reasons. First of all, we have a company full of really smart geeks with networking chops second to none. Second, we have the freedom to push boundaries and find ways to make our customers’ lives easier.
Bring those two together and you get some interesting results, like the new VXLAN technology we announced at VMworld today. Working with industry notables, Cisco contributed our networking smarts to help develop a technology that will make a big difference for our customers who want to build clouds. VXLAN is the basis of a scalable cloud network where lots of logical networks (over 16M, courtesy of a 24 bit of logical network identifier) can be created instantly to meet the needs of the even the most complex and dynamic cloud. Indeed, the technology even pushes the boundary of virtual machine migration beyond a layer 2 domain. A group of networking and server virtualization companies have submitted a joint proposal to the IETF to have the VXLAN technology standardized.
To read the IETF submittal, click here. To learn more about why VXLAN should be part of you cloud plans, read this white paper. If you are at VMworld, by all means, swing by the Cisco or VMware booth to see a demo and get your questions answered.
If you are interested in putting VXLAN to test, stay tuned for the upcoming 1.5 release of Nexus 1000V (entering beta in September 2011).
Look for more posts on the topic, but, in the interim, if you have questions, post them here and we’ll get them answered.