<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Do x690's and X590s with EXOS support vxlan? in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97158#M22072</link>
    <description>&lt;P&gt;VXLAN is supported on the Summit X770, X670-G2, and ExtremeSwitching X870, X690 series switches, and stacks with X770, X670-G2, X870, and X690 slots only. Extreme seems to have gone somewhat down the vxlan path and have maybe abandoned it, or kept it limited in favor of&lt;/P&gt;&lt;DIV class=""&gt;&lt;H2&gt;Limitations&lt;/H2&gt;&lt;P class=""&gt;The following capabilities are not supported in ExtremeXOS:&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Layer 3 gateways&lt;/LI&gt;&lt;LI&gt;Multicast VXLAN&lt;/LI&gt;&lt;LI&gt;Ability to assign more than one VNI to a virtual network&lt;/LI&gt;&lt;LI&gt;IPv6 addresses for local and remote VTEPs&lt;/LI&gt;&lt;LI&gt;Assigning source IP for VXLAN gateway encapsulation:&lt;UL class=""&gt;&lt;LI&gt;Per &lt;A title="In the Extreme Networks implementations, virtual routers allow a single physical switch to be split into multiple virtual routers. Each virtual router has its own IP address and maintains a separate logical forwarding table. Each virtual router also serves as a configuration domain. The identity of the virtual router you are working in currently displays in the prompt line of the CLI. The virtual routers discussed in relation to Extreme Networks switches themselves are not the same as the virtual router in VRRP.In VRRP, the virtual router is identified by a virtual router (VRID) and an IP address. A router running VRRP can participate in one or more virtual routers. The VRRP virtual router spans more than one physical router, which allows multiple routers to provide redundant services to users." href="https://documentation.extremenetworks.com/exos_22.3/GUID-A10F4BB8-780D-4CDF-9F4C-DA5C83150E16.shtml" target="_blank" rel="noopener"&gt;virtual router (VR)&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Per virtual network or VNI&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Support for adding more than one tenant VLAN/VMAN per VNI&lt;/LI&gt;&lt;LI&gt;A physical port being part of both a tenant VLAN/VMAN and an underlay (Network) VLAN&lt;/LI&gt;&lt;LI&gt;Routing in and out of tunnels&lt;/LI&gt;&lt;LI&gt;Support for heterogeneous stack environments where at least one of the stack nodes is not VXLAN capable&lt;/LI&gt;&lt;LI&gt;More than one next-hop on a (network) port&lt;/LI&gt;&lt;LI&gt;Multicast underlay IP network, including PIM-Bidir&lt;/LI&gt;&lt;LI&gt;Multiple VRs&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;P&gt;Otherwise, they could act as fabric attach, but you would need fabric capable switches for them to connect to. Fabric is vxlan on steroids.&lt;/P&gt;&lt;P&gt;&lt;A title="Extreme Fabric" href="https://www.extremenetworks.com/solutions/network-fabric" target="_blank" rel="noopener"&gt;https://www.extremenetworks.com/solutions/network-fabric&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Honestly we looked into doing exactly what you are, discovered fabric and went HOOLYSHEET and rolled fabric out across our nation wide network. There's even a case study: &lt;A title="Case Study" href="https://www.extremenetworks.com/resources/case-study/fabric-helps-fuel-growth-at-fastcom" target="_blank" rel="noopener"&gt;https://www.extremenetworks.com/resources/case-study/fabric-helps-fuel-growth-at-fastcom&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 13 Sep 2023 22:21:40 GMT</pubDate>
    <dc:creator>Brent_Addis</dc:creator>
    <dc:date>2023-09-13T22:21:40Z</dc:date>
    <item>
      <title>Do x690's and X590s with EXOS support vxlan?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97149#M22068</link>
      <description>&lt;P&gt;Curious if the x690 and x590s support vxlan, like an overlay network.&lt;/P&gt;&lt;P&gt;Have a project where an HQ and DR datacenter would be connected via these switches and a 10gig wan.&amp;nbsp; Do not just want to span layer 2 over it, even though its only about 60 mile fiber run.&amp;nbsp; Would like servers in vmware cluster in one DC to be moved back and forth with servers in a vmware cluster in the other DC without re-ip and changing DNS on everything.&lt;/P&gt;&lt;P&gt;Is it possible or is this the wrong kind of switch platform for it?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2023 20:54:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97149#M22068</guid>
      <dc:creator>Keith9</dc:creator>
      <dc:date>2023-09-12T20:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: Do x690's and X590s with EXOS support vxlan?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97158#M22072</link>
      <description>&lt;P&gt;VXLAN is supported on the Summit X770, X670-G2, and ExtremeSwitching X870, X690 series switches, and stacks with X770, X670-G2, X870, and X690 slots only. Extreme seems to have gone somewhat down the vxlan path and have maybe abandoned it, or kept it limited in favor of&lt;/P&gt;&lt;DIV class=""&gt;&lt;H2&gt;Limitations&lt;/H2&gt;&lt;P class=""&gt;The following capabilities are not supported in ExtremeXOS:&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Layer 3 gateways&lt;/LI&gt;&lt;LI&gt;Multicast VXLAN&lt;/LI&gt;&lt;LI&gt;Ability to assign more than one VNI to a virtual network&lt;/LI&gt;&lt;LI&gt;IPv6 addresses for local and remote VTEPs&lt;/LI&gt;&lt;LI&gt;Assigning source IP for VXLAN gateway encapsulation:&lt;UL class=""&gt;&lt;LI&gt;Per &lt;A title="In the Extreme Networks implementations, virtual routers allow a single physical switch to be split into multiple virtual routers. Each virtual router has its own IP address and maintains a separate logical forwarding table. Each virtual router also serves as a configuration domain. The identity of the virtual router you are working in currently displays in the prompt line of the CLI. The virtual routers discussed in relation to Extreme Networks switches themselves are not the same as the virtual router in VRRP.In VRRP, the virtual router is identified by a virtual router (VRID) and an IP address. A router running VRRP can participate in one or more virtual routers. The VRRP virtual router spans more than one physical router, which allows multiple routers to provide redundant services to users." href="https://documentation.extremenetworks.com/exos_22.3/GUID-A10F4BB8-780D-4CDF-9F4C-DA5C83150E16.shtml" target="_blank" rel="noopener"&gt;virtual router (VR)&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;Per virtual network or VNI&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Support for adding more than one tenant VLAN/VMAN per VNI&lt;/LI&gt;&lt;LI&gt;A physical port being part of both a tenant VLAN/VMAN and an underlay (Network) VLAN&lt;/LI&gt;&lt;LI&gt;Routing in and out of tunnels&lt;/LI&gt;&lt;LI&gt;Support for heterogeneous stack environments where at least one of the stack nodes is not VXLAN capable&lt;/LI&gt;&lt;LI&gt;More than one next-hop on a (network) port&lt;/LI&gt;&lt;LI&gt;Multicast underlay IP network, including PIM-Bidir&lt;/LI&gt;&lt;LI&gt;Multiple VRs&lt;/LI&gt;&lt;/UL&gt;&lt;/DIV&gt;&lt;P&gt;Otherwise, they could act as fabric attach, but you would need fabric capable switches for them to connect to. Fabric is vxlan on steroids.&lt;/P&gt;&lt;P&gt;&lt;A title="Extreme Fabric" href="https://www.extremenetworks.com/solutions/network-fabric" target="_blank" rel="noopener"&gt;https://www.extremenetworks.com/solutions/network-fabric&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Honestly we looked into doing exactly what you are, discovered fabric and went HOOLYSHEET and rolled fabric out across our nation wide network. There's even a case study: &lt;A title="Case Study" href="https://www.extremenetworks.com/resources/case-study/fabric-helps-fuel-growth-at-fastcom" target="_blank" rel="noopener"&gt;https://www.extremenetworks.com/resources/case-study/fabric-helps-fuel-growth-at-fastcom&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2023 22:21:40 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97158#M22072</guid>
      <dc:creator>Brent_Addis</dc:creator>
      <dc:date>2023-09-13T22:21:40Z</dc:date>
    </item>
    <item>
      <title>Re: Do x690's and X590s with EXOS support vxlan?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97185#M22075</link>
      <description>&lt;P&gt;Thanks, I'll have to look into that.&lt;/P&gt;&lt;P&gt;I have a HQ with x690's as core switching.&lt;/P&gt;&lt;P&gt;I have a DR colo with x590's brought into our network via layer 3 ospf, 10gig wan.&lt;/P&gt;&lt;P&gt;Next year want to move the servers out of the HQ into yet another colo, was looking at getting more x690s.&amp;nbsp; Adding the site to our 10 gig wan that the existing sites have.&lt;/P&gt;&lt;P&gt;Will initially have to L2 span VLAN172 for voice for a little because sip voice equipment terminates at HQ but would be moving all the servers to the colo (which includes the vm's for the phone system).&amp;nbsp; That is until we move phone systems which is another 2024 project.&amp;nbsp; Started down the rabbit hole of vxlan and kind of was interested in a l2 stretched overlay on a l3 ospf multi-path underlay.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 18:55:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/do-x690-s-and-x590s-with-exos-support-vxlan/m-p/97185#M22075</guid>
      <dc:creator>Keith9</dc:creator>
      <dc:date>2023-09-15T18:55:18Z</dc:date>
    </item>
  </channel>
</rss>

