There’s so much great material being written on VXLAN and NVGRE that I decided to write a separate post listing the best of it (if you still can’t decide whether you should care about VXLAN, register for my Introduction to Virtual Networking webinar).
Omar Sultan published a three-part series on Cisco’s Data Center blog: In-depth VXLAN description, Comparison with OTV, MAC-in-GRE and LISP and More FAQ (including relationship between VN-Tag and VXLAN). The information in these posts is pretty much spot-on and accurate.
Denton Gentry @ Coding Relic wrote another great series: Introduction, Encapsulation and Learning, and Transition and Gateways. He also did a deep dive (as far as one could go given the current fuzzy state of the pseudo-draft) on NVGRE (I simply couldn’t be bothered after figuring out how much of the real stuff is still missing).
Martin Casado eloquently pointed to the elephant in the room – lack of control plane – and suggested (what else) OpenFlow as the solution (it’s also nice to see you can get bonus points by not figuring out what needs to be done).
Last but definitely not least, there are two masterpieces from vendors
marketing departments to make you laugh: HP claims VXLAN uses more power than EVB (no wonder, as the latter probably only works in PowerPoint) while Dell promises to support VXLAN, NVGRE, OpenFlow and unicorn tears.
Vishwas Manral rightfully pointed out that he does not work in HP marketing. Fixed the last paragraph.