<?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: VSAs for VOSS Switches in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97965#M2210</link>
    <description>&lt;P&gt;Thanks James, my issue is that I want only one of those VLANs to come in untagged and the rest to be tagged.&amp;nbsp; So that essentially the WAP boots up, gets DHCP via the untagged VLAN then connects to it's controller.&amp;nbsp; Once it gets it's controller config it bridges two VLANS tagged (two separate SSIDs) so a total of 3 VLANs on the switch port, 1 untagged and 2 tagged.&amp;nbsp; With ERS I was able to use the following VSA's to accomplish this:&lt;BR /&gt;FA-VLAN-Create=1&lt;BR /&gt;FA-VLAN-PVID=&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 16 Nov 2023 14:34:40 GMT</pubDate>
    <dc:creator>Configterminal</dc:creator>
    <dc:date>2023-11-16T14:34:40Z</dc:date>
    <item>
      <title>VSAs for VOSS Switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97953#M2208</link>
      <description>&lt;P&gt;Hi - does anyone have the VSAs needed to push down to VOSS switches to configure multiple VLANs on a port after a client authenticates. &amp;nbsp;We are using XMC to assign dynamic vlans. &amp;nbsp;The use case is when we plug in an Aruba WAP we need to assign a default VLAN ID plus 3 additional VLANs to be allowed on that port? &amp;nbsp;I have it down for ERS switches running BOSS but not for VOSS. &amp;nbsp;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 16 Nov 2023 00:44:17 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97953#M2208</guid>
      <dc:creator>Configterminal</dc:creator>
      <dc:date>2023-11-16T00:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: VSAs for VOSS Switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97965#M2210</link>
      <description>&lt;P&gt;Thanks James, my issue is that I want only one of those VLANs to come in untagged and the rest to be tagged.&amp;nbsp; So that essentially the WAP boots up, gets DHCP via the untagged VLAN then connects to it's controller.&amp;nbsp; Once it gets it's controller config it bridges two VLANS tagged (two separate SSIDs) so a total of 3 VLANs on the switch port, 1 untagged and 2 tagged.&amp;nbsp; With ERS I was able to use the following VSA's to accomplish this:&lt;BR /&gt;FA-VLAN-Create=1&lt;BR /&gt;FA-VLAN-PVID=&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;BR /&gt;FA-VLAN-ISID =&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Nov 2023 14:34:40 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97965#M2210</guid>
      <dc:creator>Configterminal</dc:creator>
      <dc:date>2023-11-16T14:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: VSAs for VOSS Switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97995#M2213</link>
      <description>&lt;P&gt;Thank you!!!! This worked like a charm&lt;/P&gt;</description>
      <pubDate>Fri, 17 Nov 2023 17:20:45 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/vsas-for-voss-switches/m-p/97995#M2213</guid>
      <dc:creator>Configterminal</dc:creator>
      <dc:date>2023-11-17T17:20:45Z</dc:date>
    </item>
  </channel>
</rss>

