<?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: Device tags used in legacy hivemanager in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68803#M4111</link>
    <description>&lt;P&gt;Hi Mike,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is possible in NG through two methods:&lt;/P&gt;&lt;P&gt;Cloud Configuration Groups - You create "groups" of AP and apply classification rules to the VLANs to the AP for management and also client profiles. &lt;A href="https://blog.aerohive.com/cloud-configuration-groups/" alt="https://blog.aerohive.com/cloud-configuration-groups/" target="_blank"&gt;https://blog.aerohive.com/cloud-configuration-groups/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Classification rules - Similar to the above, you skip creating the CCG and instead apply classification rules, based on the AP locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2019 21:16:52 GMT</pubDate>
    <dc:creator>ashley_finch</dc:creator>
    <dc:date>2019-05-09T21:16:52Z</dc:date>
    <item>
      <title>Device tags used in legacy hivemanager</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68800#M4108</link>
      <description>&lt;P&gt;Hi we used device tags and user policies with multiple vlans to direct devices to correct vlan for every site in hivemanager. I would like to know how i can solve this in NG. Im currently in prosess of creating the config as is from legacy. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ex: &lt;/P&gt;&lt;P&gt;If we call a VLAN : multiVLAN  , og this has VLAN 2: device tag New york, VLAN 2: device tag texas&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When an AP in texas is connected to VLAN 2 is supplied to client ... &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 16:38:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68800#M4108</guid>
      <dc:creator>volkan</dc:creator>
      <dc:date>2018-10-24T16:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: Device tags used in legacy hivemanager</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68801#M4109</link>
      <description>&lt;P&gt;this is from my legacy&lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 17:05:14 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68801#M4109</guid>
      <dc:creator>volkan</dc:creator>
      <dc:date>2018-10-24T17:05:14Z</dc:date>
    </item>
    <item>
      <title>Re: Device tags used in legacy hivemanager</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68802#M4110</link>
      <description>&lt;P&gt;Shoulda bought Brocade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have this same issue. Looks like no solves.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 19:41:12 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68802#M4110</guid>
      <dc:creator>michael_thompso</dc:creator>
      <dc:date>2019-05-08T19:41:12Z</dc:date>
    </item>
    <item>
      <title>Re: Device tags used in legacy hivemanager</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68803#M4111</link>
      <description>&lt;P&gt;Hi Mike,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is possible in NG through two methods:&lt;/P&gt;&lt;P&gt;Cloud Configuration Groups - You create "groups" of AP and apply classification rules to the VLANs to the AP for management and also client profiles. &lt;A href="https://blog.aerohive.com/cloud-configuration-groups/" alt="https://blog.aerohive.com/cloud-configuration-groups/" target="_blank"&gt;https://blog.aerohive.com/cloud-configuration-groups/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Classification rules - Similar to the above, you skip creating the CCG and instead apply classification rules, based on the AP locations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 21:16:52 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/device-tags-used-in-legacy-hivemanager/m-p/68803#M4111</guid>
      <dc:creator>ashley_finch</dc:creator>
      <dc:date>2019-05-09T21:16:52Z</dc:date>
    </item>
  </channel>
</rss>

