<?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: Remote management fabric switches VOSS in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/remote-management-fabric-switches-voss/m-p/95642#M2117</link>
    <description>&lt;P&gt;If your fabric switches only carries L2VSN services, I would use mgmt VLAN IP on a dedicated separate mgmt L2VSN I-SID.&lt;/P&gt;&lt;P&gt;If your fabric switches carry L3VSN (IPVPN) services, then allocate a VRF for mgmt and set mgmt CLIPs on that mgmt VRF. In this case it makes most sense to use the default VRF-0 (GRT) as mgmt (L3VSN over VRF-0(GRT) = IP Shortcuts). And create VRFs 1,2,3.etc.. (L3VSNs) as services.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 27 Apr 2023 12:38:30 GMT</pubDate>
    <dc:creator>Ludovico_Steven</dc:creator>
    <dc:date>2023-04-27T12:38:30Z</dc:date>
    <item>
      <title>Remote management fabric switches VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/remote-management-fabric-switches-voss/m-p/95638#M2115</link>
      <description>&lt;P&gt;What is the recommended solution for managing fabric switches 7400, 5420, from a remote network? The fabric network is being used in a managed WAN solution,&amp;nbsp; I would like to keep customer traffic separate from management traffic. The ISP can extend a VLAN back to the monitoring location. Sounds like the text book application for the CLIP but haven't been successful so far.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 16:47:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/remote-management-fabric-switches-voss/m-p/95638#M2115</guid>
      <dc:creator>PatrickW</dc:creator>
      <dc:date>2023-04-26T16:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: Remote management fabric switches VOSS</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/remote-management-fabric-switches-voss/m-p/95642#M2117</link>
      <description>&lt;P&gt;If your fabric switches only carries L2VSN services, I would use mgmt VLAN IP on a dedicated separate mgmt L2VSN I-SID.&lt;/P&gt;&lt;P&gt;If your fabric switches carry L3VSN (IPVPN) services, then allocate a VRF for mgmt and set mgmt CLIPs on that mgmt VRF. In this case it makes most sense to use the default VRF-0 (GRT) as mgmt (L3VSN over VRF-0(GRT) = IP Shortcuts). And create VRFs 1,2,3.etc.. (L3VSNs) as services.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Apr 2023 12:38:30 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/remote-management-fabric-switches-voss/m-p/95642#M2117</guid>
      <dc:creator>Ludovico_Steven</dc:creator>
      <dc:date>2023-04-27T12:38:30Z</dc:date>
    </item>
  </channel>
</rss>

