<?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: Fabric - Segmented Management VLAN coesxistence mode in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-segmented-management-vlan-coesxistence-mode/m-p/121443#M3181</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Requires user to configure the same IP manually under both “interface vlan” and “mgmt vlan. Allows routing and management functions to work together on the same VLAN with the same IP. Packets received by data path will be duplicated to both mgmt and routing stacks.&lt;/P&gt;&lt;P&gt;Useful for FE (Fabric extent) case in particular on the XA1400 where FE tunnel source IP must belong to the routing stack and user wants to manage switch from underlay IP network using same IP.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Roopesh K Rajan&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2026 04:23:18 GMT</pubDate>
    <dc:creator>rkaruvanrajan</dc:creator>
    <dc:date>2026-04-08T04:23:18Z</dc:date>
    <item>
      <title>Fabric - Segmented Management VLAN coesxistence mode</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-segmented-management-vlan-coesxistence-mode/m-p/121206#M3172</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;Could someone please explain the reasons and use cases for configuring coexistence mode?&lt;/P&gt;&lt;P&gt;Specifically, it would be helpful to understand the key benefits, typical scenarios where it is recommended.&lt;/P&gt;&lt;P&gt;Thank you in advance for your support.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;EF&lt;/P&gt;</description>
      <pubDate>Thu, 12 Feb 2026 13:01:03 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-segmented-management-vlan-coesxistence-mode/m-p/121206#M3172</guid>
      <dc:creator>EF</dc:creator>
      <dc:date>2026-02-12T13:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Fabric - Segmented Management VLAN coesxistence mode</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-segmented-management-vlan-coesxistence-mode/m-p/121443#M3181</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Requires user to configure the same IP manually under both “interface vlan” and “mgmt vlan. Allows routing and management functions to work together on the same VLAN with the same IP. Packets received by data path will be duplicated to both mgmt and routing stacks.&lt;/P&gt;&lt;P&gt;Useful for FE (Fabric extent) case in particular on the XA1400 where FE tunnel source IP must belong to the routing stack and user wants to manage switch from underlay IP network using same IP.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Roopesh K Rajan&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 04:23:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-segmented-management-vlan-coesxistence-mode/m-p/121443#M3181</guid>
      <dc:creator>rkaruvanrajan</dc:creator>
      <dc:date>2026-04-08T04:23:18Z</dc:date>
    </item>
  </channel>
</rss>

