<?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: Odd AP Authorization issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619510#M136125</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, I'm an idiot -- based on the suggestions here, I looked outside of the local network and back to my core and found that MAC address.&amp;nbsp; After tracing it down and getting the IP from the core's ARP table I found the crux of the problem - it's my location appliance.&amp;nbsp; The same location appliance that I have an open TAC case with because it's not communicating with this WLC (LOL, ya think the two are realated???).&amp;nbsp; I think my issue has to due with not having the WLC configured to accept SSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ugh, somedays you're the pidgeon, somedays you're the statue ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help guys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;EDIT&lt;/STRONG&gt; - It's definately a SSC issue, will take care of it tonight.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Mar 2011 15:21:00 GMT</pubDate>
    <dc:creator>Ryan Curry</dc:creator>
    <dc:date>2011-03-30T15:21:00Z</dc:date>
    <item>
      <title>Odd AP Authorization issue</title>
      <link>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619507#M136122</link>
      <description>&lt;P&gt;About 2 weeks ago I installed a 2125 controller in one of our remote sites that had 4 LWAPP aps.&amp;nbsp; Prior to the controller install, the APs were tunneling across the WAN to our main campus.&amp;nbsp; Once the controller was installed, I started to get the following critical alarm in WCS and I can't figure out what I need to do to take care of it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="padding-left: 30px;"&gt;Failed to authorize AP '&amp;lt;MAC&amp;gt;' with certificate type&amp;nbsp; 'Unknown' on controller '&amp;lt;Remote Site's Controller&amp;gt;'. 'AP Authorization entry does not&amp;nbsp; exist in the Controllers AP Authorization List.'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From what I've seen, the reported AP is not a Cisco radio MAC and the existing APs are running fine.&amp;nbsp; Aside from taking my Air Magnet laptop over there and hunting down (and turning off) the device I'm at a loss on what action I can take.&amp;nbsp; Does anyone have a suggestions on this scenario?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks all!&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:00:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619507#M136122</guid>
      <dc:creator>Ryan Curry</dc:creator>
      <dc:date>2021-07-04T03:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: Odd AP Authorization issue</title>
      <link>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619508#M136123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ryan,&lt;/P&gt;&lt;P&gt;&amp;nbsp; You could try to chase the mac address/ apr entry down and find the port it's connected to.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2011 17:01:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619508#M136123</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2011-03-29T17:01:15Z</dc:date>
    </item>
    <item>
      <title>Re: Odd AP Authorization issue</title>
      <link>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619509#M136124</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;yes seems to be an attack if&amp;nbsp; the ip address does not belong to a cisco ap. Is it happening only in one remote site?&amp;nbsp; Btw do the trace on the wired site at first by checking the mac address table&amp;nbsp; or arp table&amp;nbsp;&amp;nbsp; Regards&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Posted from my mobile device.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 08:15:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619509#M136124</guid>
      <dc:creator>dmantill</dc:creator>
      <dc:date>2011-03-30T08:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: Odd AP Authorization issue</title>
      <link>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619510#M136125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, I'm an idiot -- based on the suggestions here, I looked outside of the local network and back to my core and found that MAC address.&amp;nbsp; After tracing it down and getting the IP from the core's ARP table I found the crux of the problem - it's my location appliance.&amp;nbsp; The same location appliance that I have an open TAC case with because it's not communicating with this WLC (LOL, ya think the two are realated???).&amp;nbsp; I think my issue has to due with not having the WLC configured to accept SSC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ugh, somedays you're the pidgeon, somedays you're the statue ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help guys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;EDIT&lt;/STRONG&gt; - It's definately a SSC issue, will take care of it tonight.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 15:21:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/odd-ap-authorization-issue/m-p/1619510#M136125</guid>
      <dc:creator>Ryan Curry</dc:creator>
      <dc:date>2011-03-30T15:21:00Z</dc:date>
    </item>
  </channel>
</rss>

