<?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 L3VSN MGMT in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-l3vsn-mgmt/m-p/122212#M3250</link>
    <description>&lt;P&gt;Mgmt VLAN and Mgmt CLIP are both inband management options.&lt;/P&gt;&lt;P&gt;If your switch is acting as a L3 Router for (some if not all) fabric services, use mgmt CLIP on it.&lt;/P&gt;&lt;P&gt;If your switch is acting as a L2 access switch for all fabric services, use mgmt VLAN IP on it.&lt;/P&gt;&lt;P&gt;Then we do have some customers who like to do everything either with mgmt VLAN or with Mgmt CLIP, it is possible, but there are issues if you enable mgmt VLAN IP on L3 router + you want to hit that mgmt IP if you are coming from a different subnet on that same L3 router (here you need the Mgmt VLAN-L3 type interface which was introduced in VOSS 9.3.0.0); and on the flip side, if you wanted to use Mgmt CLIP everywhere even on L2 access switches, you need to globally IP enable ISIS for that to work, which is not normally a setting that needs enabling on a L2 access switch.&lt;/P&gt;&lt;P&gt;Mgmt OOB should always work, but you will need to provide a valid static route on it (not a default route please, a static towards the management stations reachable over OOB only; OOB is supposed to Out-of-Band!)&lt;/P&gt;&lt;P&gt;The mgmt interfaces (CLIP,VLAN,OOB) are designed to reply on the same interface for any TCP/UDP traffic originating from the management stations.&lt;/P&gt;&lt;P&gt;But for switch initiated traffic (SNMP Traps, RADIUS requests, etc..) the mgmt (default) route precedence in the Mgmt IP routing table will apply. That is why it is not a good idea to slap a default route on the Mgmt OOB interface; or if you do, make sure it has lower pref than inband default routes.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Jul 2026 07:02:27 GMT</pubDate>
    <dc:creator>Ludovico</dc:creator>
    <dc:date>2026-07-27T07:02:27Z</dc:date>
    <item>
      <title>Fabric L3VSN MGMT</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-l3vsn-mgmt/m-p/122197#M3248</link>
      <description>&lt;P&gt;I configured a management VLAN interface and can successfully access the Fabric Web GUI using the IP address and data port assigned to that VLAN.&lt;/P&gt;&lt;P&gt;In addition, I have configured out-of-band (OOB) management. However, I can't access the Fabric Web GUI through the dedicated MGMT port.&lt;/P&gt;&lt;P&gt;I also configured a CLIP address, but I'm not sure whether the CLIP is supposed to be accessible through the dedicated MGMT port or whether it is only used for routing and communication within the fabric.&lt;/P&gt;&lt;P&gt;Has anyone successfully configured OOB and Clip management on Extreme?&lt;/P&gt;&lt;P&gt;Any guidance would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kriss&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jul 2026 08:10:50 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-l3vsn-mgmt/m-p/122197#M3248</guid>
      <dc:creator>Kriss</dc:creator>
      <dc:date>2026-07-24T08:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: Fabric L3VSN MGMT</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-l3vsn-mgmt/m-p/122212#M3250</link>
      <description>&lt;P&gt;Mgmt VLAN and Mgmt CLIP are both inband management options.&lt;/P&gt;&lt;P&gt;If your switch is acting as a L3 Router for (some if not all) fabric services, use mgmt CLIP on it.&lt;/P&gt;&lt;P&gt;If your switch is acting as a L2 access switch for all fabric services, use mgmt VLAN IP on it.&lt;/P&gt;&lt;P&gt;Then we do have some customers who like to do everything either with mgmt VLAN or with Mgmt CLIP, it is possible, but there are issues if you enable mgmt VLAN IP on L3 router + you want to hit that mgmt IP if you are coming from a different subnet on that same L3 router (here you need the Mgmt VLAN-L3 type interface which was introduced in VOSS 9.3.0.0); and on the flip side, if you wanted to use Mgmt CLIP everywhere even on L2 access switches, you need to globally IP enable ISIS for that to work, which is not normally a setting that needs enabling on a L2 access switch.&lt;/P&gt;&lt;P&gt;Mgmt OOB should always work, but you will need to provide a valid static route on it (not a default route please, a static towards the management stations reachable over OOB only; OOB is supposed to Out-of-Band!)&lt;/P&gt;&lt;P&gt;The mgmt interfaces (CLIP,VLAN,OOB) are designed to reply on the same interface for any TCP/UDP traffic originating from the management stations.&lt;/P&gt;&lt;P&gt;But for switch initiated traffic (SNMP Traps, RADIUS requests, etc..) the mgmt (default) route precedence in the Mgmt IP routing table will apply. That is why it is not a good idea to slap a default route on the Mgmt OOB interface; or if you do, make sure it has lower pref than inband default routes.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jul 2026 07:02:27 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/fabric-l3vsn-mgmt/m-p/122212#M3250</guid>
      <dc:creator>Ludovico</dc:creator>
      <dc:date>2026-07-27T07:02:27Z</dc:date>
    </item>
  </channel>
</rss>

