<?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 Arrghhh aparently I was in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826007#M98494</link>
    <description>&lt;P&gt;Arrghhh aparently I was hitting two errors.&lt;/P&gt;
&lt;P&gt;MAC address AND the primary WLCs certificate had run out &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;So all APs joined WLC 2 &lt;SPAN&gt;(this WLC has a newer manufacturing date)&amp;nbsp;&lt;/SPAN&gt;after being denied on WLC 1 &amp;nbsp;- AP Fallback was enabled on WLC2, ... sooo ... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Still no word on the MAC address problem. Workaround was to disable LAG on the WLCs.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Nov 2015 20:23:20 GMT</pubDate>
    <dc:creator>Thomas Obbekaer Thomsen</dc:creator>
    <dc:date>2015-11-25T20:23:20Z</dc:date>
    <item>
      <title>Old 4402s reporting its own MAC address in duplicated IP log.</title>
      <link>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826005#M98492</link>
      <description>&lt;P&gt;Both 4402 has all of a sudden started to output this message:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;"Warning: Controller has detected its IP Address 10.75.86.16 being used by a machine with MAC Address 00:0b:85:46:1e:c7."&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The trouble is MAC address&amp;nbsp;&lt;SPAN&gt;00:0b:85:46:1e:c7 is the controllers OWN address ??!?!?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;10.75.86.16 is the management interface of the WLC. (.15 AP manager).&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;The other controller has a similar message in its log, just containing its IP .14 and its own MAC address. (.13 AP manager)&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;At the same time APs starts to disconnect from the WLC.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Any suggestions ?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We have disabled one port of on each WLC in case it was some kind of LAG / Portchannel problem.&lt;/P&gt;
&lt;P&gt;But still nothing.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The controllers had a fine uptime of a couple of years, and nothing like this has happend before.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We have tried rebooting and also upgarded to the newest 7.0.252 but still the problem exists.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:18:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826005#M98492</guid>
      <dc:creator>Thomas Obbekaer Thomsen</dc:creator>
      <dc:date>2021-07-05T11:18:31Z</dc:date>
    </item>
    <item>
      <title>Hmmm when we disable LAG on</title>
      <link>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826006#M98493</link>
      <description>&lt;P&gt;Hmmm when we disable LAG on the WLCs the error never returns in the log.&lt;/P&gt;
&lt;P&gt;(This is still with only one port connected from the WLCs to the switch)&lt;/P&gt;
&lt;P&gt;APs are still disconnected after a short while &lt;span class="lia-unicode-emoji" title=":confused_face:"&gt;😕&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Of course now the WLC has a different MAC address -&amp;nbsp;Hmmmmm clear arp somthing on a switch ?&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2015 19:20:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826006#M98493</guid>
      <dc:creator>Thomas Obbekaer Thomsen</dc:creator>
      <dc:date>2015-11-25T19:20:43Z</dc:date>
    </item>
    <item>
      <title>Arrghhh aparently I was</title>
      <link>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826007#M98494</link>
      <description>&lt;P&gt;Arrghhh aparently I was hitting two errors.&lt;/P&gt;
&lt;P&gt;MAC address AND the primary WLCs certificate had run out &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;So all APs joined WLC 2 &lt;SPAN&gt;(this WLC has a newer manufacturing date)&amp;nbsp;&lt;/SPAN&gt;after being denied on WLC 1 &amp;nbsp;- AP Fallback was enabled on WLC2, ... sooo ... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Still no word on the MAC address problem. Workaround was to disable LAG on the WLCs.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2015 20:23:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/old-4402s-reporting-its-own-mac-address-in-duplicated-ip-log/m-p/2826007#M98494</guid>
      <dc:creator>Thomas Obbekaer Thomsen</dc:creator>
      <dc:date>2015-11-25T20:23:20Z</dc:date>
    </item>
  </channel>
</rss>

