<?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: APs reboot due to high number of clients per radio in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074918#M15111</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, look for a crash dump in the controller.&amp;nbsp; Management &amp;gt; Tech Support &amp;gt; AP Crash Log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is NONE, then try the following commands: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; debug ap enable &lt;WAP name=""&gt;;&lt;/WAP&gt;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; debug ap command "sh version"; and &lt;/P&gt;&lt;P&gt;3.&amp;nbsp; debug ap disable &lt;WAP name=""&gt;&lt;/WAP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Post the output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As what Scott has mentioned, there are alot of reason why a WAP reboots without any intervention and faulty cabling could also be the culprit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Nov 2012 02:04:45 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2012-11-09T02:04:45Z</dc:date>
    <item>
      <title>APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074913#M15106</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone problems with accesspoints reboots at high client count (50+ associations per radio)&lt;/P&gt;&lt;P&gt;We have a 5508 WLC with 7.3 Code and 3600 AP´s.&lt;/P&gt;&lt;P&gt;Our problem is that sometimes accesspoints reboots. And this only if a lot of clients are connected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks in advance for your help&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:59:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074913#M15106</guid>
      <dc:creator>Dieter Prinesdoma</dc:creator>
      <dc:date>2021-07-04T05:59:37Z</dc:date>
    </item>
    <item>
      <title>Re:APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074914#M15107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it is possible that the access points will reboot. There could be a couple different reasons why, most noticeable would be interference caused by so many clients (clients themselves can cause co-channel interference). Is the AP actually rebooting or is the radios resetting due to some reason?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 00:45:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074914#M15107</guid>
      <dc:creator>Damon Garner</dc:creator>
      <dc:date>2012-11-08T00:45:38Z</dc:date>
    </item>
    <item>
      <title>APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074915#M15108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;Has anyone problems with accesspoints reboots at high client count (50+ associations per radio)&lt;/PRE&gt;&lt;P&gt;50 clients???&amp;nbsp; Per RADIO???? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Seriously?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 00:52:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074915#M15108</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2012-11-08T00:52:17Z</dc:date>
    </item>
    <item>
      <title>Re:APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074916#M15109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don´t know the reason why the ap reboot. This is the problem. We monitor the Ap with nagios and we see that the ap is offine for a few minutes. So I believe the ap reboot.&lt;/P&gt;&lt;P&gt;We found no logs on the wlc for the reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem area is a congress center a so sometimes we have really a lot of users. (like a Cisco Networkers)&lt;/P&gt;&lt;P&gt;We have all the typical problems at high density WLAN. (a lot of Rouge Ap´s, high channel&amp;nbsp; utilization, interference …)&lt;/P&gt;&lt;P&gt;But could that the reason why a accesspoint reboot?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 07:48:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074916#M15109</guid>
      <dc:creator>Dieter Prinesdoma</dc:creator>
      <dc:date>2012-11-08T07:48:51Z</dc:date>
    </item>
    <item>
      <title>APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074917#M15110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Take a look at the ap uptime and the ap join, that will tell you if the ap has rebooted and or if it lost connection with the WLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt; &lt;BR /&gt;Scott &lt;BR /&gt; &lt;BR /&gt;Help out other by using the rating system and marking answered questions as "Answered"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Nov 2012 13:42:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074917#M15110</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2012-11-08T13:42:10Z</dc:date>
    </item>
    <item>
      <title>Re: APs reboot due to high number of clients per radio</title>
      <link>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074918#M15111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok, look for a crash dump in the controller.&amp;nbsp; Management &amp;gt; Tech Support &amp;gt; AP Crash Log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If there is NONE, then try the following commands: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; debug ap enable &lt;WAP name=""&gt;;&lt;/WAP&gt;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; debug ap command "sh version"; and &lt;/P&gt;&lt;P&gt;3.&amp;nbsp; debug ap disable &lt;WAP name=""&gt;&lt;/WAP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Post the output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As what Scott has mentioned, there are alot of reason why a WAP reboots without any intervention and faulty cabling could also be the culprit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 02:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/aps-reboot-due-to-high-number-of-clients-per-radio/m-p/2074918#M15111</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2012-11-09T02:04:45Z</dc:date>
    </item>
  </channel>
</rss>

