<?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: AP Aware not working in ExtremeControl</title>
    <link>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120292#M2124</link>
    <description>&lt;P&gt;I found a fix for my issue but it may be unique.&amp;nbsp; Prior to using NAC to set up ports for our APs we had other methods that left the config having tagging on ports for the APs.&amp;nbsp; I found that the issue was not happening on our new AP ports which only had an untagged VLAN on them before NAC added the tagging.&amp;nbsp; I tried powering down the AP, removing the tagging that was still there, and powering it back up.&lt;/P&gt;&lt;P&gt;That seems to have done the trick.&amp;nbsp; After that change we no longer have extra devices showing up on the ports.&amp;nbsp; I did find however that in some cases (model 505 APs for example) if the device was in End Systems already then they show up on the wired port but as Disconnected.&amp;nbsp; I was able to remove the extra devices from our End Systems and that fixed that problem as well.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Sep 2025 12:33:14 GMT</pubDate>
    <dc:creator>Robert_Fredette</dc:creator>
    <dc:date>2025-09-16T12:33:14Z</dc:date>
    <item>
      <title>AP Aware not working</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120035#M2113</link>
      <description>&lt;P&gt;Has anyone seen AP Aware stop working just on one switch?&amp;nbsp; Is there a cli command I can try or something?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Aug 2025 14:12:48 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120035#M2113</guid>
      <dc:creator>troy_alan</dc:creator>
      <dc:date>2025-08-21T14:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: AP Aware not working</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120220#M2119</link>
      <description>&lt;P&gt;Yes, I have seen AP Aware stop working on several switches.&amp;nbsp; No fix yet though, sorry.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 15:27:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120220#M2119</guid>
      <dc:creator>Robert_Fredette</dc:creator>
      <dc:date>2025-09-05T15:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: AP Aware not working</title>
      <link>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120292#M2124</link>
      <description>&lt;P&gt;I found a fix for my issue but it may be unique.&amp;nbsp; Prior to using NAC to set up ports for our APs we had other methods that left the config having tagging on ports for the APs.&amp;nbsp; I found that the issue was not happening on our new AP ports which only had an untagged VLAN on them before NAC added the tagging.&amp;nbsp; I tried powering down the AP, removing the tagging that was still there, and powering it back up.&lt;/P&gt;&lt;P&gt;That seems to have done the trick.&amp;nbsp; After that change we no longer have extra devices showing up on the ports.&amp;nbsp; I did find however that in some cases (model 505 APs for example) if the device was in End Systems already then they show up on the wired port but as Disconnected.&amp;nbsp; I was able to remove the extra devices from our End Systems and that fixed that problem as well.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Sep 2025 12:33:14 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremecontrol/ap-aware-not-working/m-p/120292#M2124</guid>
      <dc:creator>Robert_Fredette</dc:creator>
      <dc:date>2025-09-16T12:33:14Z</dc:date>
    </item>
  </channel>
</rss>

