<?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 joining issue 4404 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334010#M62384</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have reset the controller another time and everything worked out fine. The AP's were joining also via port 1 again.&lt;/P&gt;&lt;P&gt;Nevertheless a strange occurrence, I will upgrade the firmware.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Sep 2009 12:07:36 GMT</pubDate>
    <dc:creator>torex-hiscom</dc:creator>
    <dc:date>2009-09-09T12:07:36Z</dc:date>
    <item>
      <title>AP joining issue 4404</title>
      <link>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334008#M62382</link>
      <description>&lt;P&gt;I have one 4404 controller running version 5.1.151.&lt;/P&gt;&lt;P&gt;There are 74 AP's which are divided between interface ap-manager 1(on port 1) and ap-manager 2 (on port 2). LAG is disabled.&lt;/P&gt;&lt;P&gt;After a controller reset the AP's wouldn't join port 1 anymore, only port 2. So a maximum of 48 AP's were joined on port 2, while the other 26 AP's kept trying but showed the messages:&lt;/P&gt;&lt;P&gt;Message: 22: AP:001d.e554.f42a: %LWAPP-3-CLIENTERRORLOG: Join Timer: did not recieve join response (controller - xxx-4400)&lt;/P&gt;&lt;P&gt;Message: 23: AP:001d.e554.f42a: %LWAPP-3-CLIENTERRORLOG: Set Transport Address: no more AP manager IP addresses remain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Port 1 and 2 are configured exactly the same way. After I configured an ap-manager interface on port 3 all the remaining AP's joined via that interface. &lt;/P&gt;&lt;P&gt;So the ap-manager interface on port 1 doesn't seem to work. It looks a bit like bug CSCsq30980, but the circumstances are not exactly the same.&lt;/P&gt;&lt;P&gt;Any ideas what's wrong?&lt;/P&gt;&lt;P&gt;I plan to reset the controller again in some time, but for the coming weeks I'll leave it running.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Albert&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 01:01:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334008#M62382</guid>
      <dc:creator>torex-hiscom</dc:creator>
      <dc:date>2021-07-04T01:01:30Z</dc:date>
    </item>
    <item>
      <title>Re: AP joining issue 4404</title>
      <link>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334009#M62383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Albert,&lt;/P&gt;&lt;P&gt;i haved a similar issue on a 4402 and it was the optical cable or the fsp module.(i don't remember very well)&lt;/P&gt;&lt;P&gt;Try to change this component and try again.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Sep 2009 14:34:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334009#M62383</guid>
      <dc:creator>daysleeper</dc:creator>
      <dc:date>2009-09-08T14:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: AP joining issue 4404</title>
      <link>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334010#M62384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have reset the controller another time and everything worked out fine. The AP's were joining also via port 1 again.&lt;/P&gt;&lt;P&gt;Nevertheless a strange occurrence, I will upgrade the firmware.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Sep 2009 12:07:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-joining-issue-4404/m-p/1334010#M62384</guid>
      <dc:creator>torex-hiscom</dc:creator>
      <dc:date>2009-09-09T12:07:36Z</dc:date>
    </item>
  </channel>
</rss>

