<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Vxlan on The IT Hollow</title>
    <link>https://theithollow.com/tags/vxlan/</link>
    <description>Recent content in Vxlan on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 03 Sep 2012 11:00:48 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vxlan/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Quick Thought on VXLANs</title>
      <link>https://theithollow.com/2012/09/03/vxlans-a-good-idea/</link>
      <pubDate>Mon, 03 Sep 2012 11:00:48 +0000</pubDate>
      <guid>https://theithollow.com/2012/09/03/vxlans-a-good-idea/</guid>
      <description>&lt;p&gt;After attending VMworld this year, I decided I needed to try to understand VXLANs a little better.  Based off of the basic concept that it stretches a layer two broadcast domain over layer three networks, I was worried that I knew how this was accomplished.&lt;/p&gt;
&lt;h2 id=&#34;what-is-vxlan&#34;&gt;What is VXLAN?&lt;/h2&gt;
&lt;p&gt;VXLAN stands for Virtual Extensible LAN and is a fairly new method of making the datacenter network elastic.  Suppose for example that you want to be able to move your virtual machines from your own server room to a co-location and then to a public cloud depending on what the load was on your environment.  In order to do this without causing downtime, you&amp;rsquo;d need a way for your layer two ethernet frames to continue getting from your clients to your servers even, if a router is in that path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
