<?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: Flapping/Intermittent Access Points in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764538#M250893</link>
    <description>&lt;P&gt;In future get some console logs (especially since you were there doing factory reset) - that really is the ONLY way to 100&amp;amp; accurately diagnose these problems!&lt;BR /&gt;Sometimes a packet capture of the CAPWAP packets may show you something useful - like missing board info which confirms hardware (radios) failed.&lt;BR /&gt;But like Leo says we've been RMAing an average of 20 x 1832 per month for about 2 years now.&amp;nbsp; We don't use 1852 but probably safe to assume similar quality issues with 1852.&amp;nbsp; Cisco still consider this to be within expected MTBF.&lt;BR /&gt;Just RMA the 3 APs.&lt;/P&gt;</description>
    <pubDate>Sun, 29 Jan 2023 01:16:28 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2023-01-29T01:16:28Z</dc:date>
    <item>
      <title>Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764212#M250860</link>
      <description>&lt;P&gt;Has anyone seen this issue with the 1852i APs? We have 3 APs that flap all day everyday. The LED cycles red, amber, green continuously and never joins the WLC. The cables tested out fine and we attempted a factory reset on the APs.&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Jan 27 12:06:10: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Jan 27 12:06:12: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Jan 27 12:15:11: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Jan 27 12:15:15: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Jan 27 12:16:18: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to down&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;Jan 27 12:16:21: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/5, changed state to up&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 18:28:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764212#M250860</guid>
      <dc:creator>jdparsons</dc:creator>
      <dc:date>2023-01-27T18:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764260#M250864</link>
      <description>&lt;P&gt;That is because LWAP looking for WLC to join, since its not joined that is reboot process common, connect console and post complete boot log here ?&lt;/P&gt;
&lt;P&gt;how are you expecting AP to join WLC?&lt;/P&gt;
&lt;P&gt;what option?&lt;/P&gt;
&lt;P&gt;same Layer 2 domain ?&lt;/P&gt;
&lt;P&gt;Option 43 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 20:31:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764260#M250864</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-01-27T20:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764300#M250865</link>
      <description>&lt;P&gt;I am unable to connect a console to the AP as I am no longer onsite and will not be again for a month or two.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I expect the AP to join via CAPWAP.&lt;/P&gt;&lt;P&gt;Option 82&lt;/P&gt;&lt;P&gt;Same Layer 2 domain&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 21:51:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764300#M250865</guid>
      <dc:creator>jdparsons</dc:creator>
      <dc:date>2023-01-27T21:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764303#M250866</link>
      <description>&lt;P&gt;So you mean to say AP join WLC and disconnect or keep rebooting with out joining?&lt;/P&gt;
&lt;P&gt;if you have WLC you can enable debug&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 22:03:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764303#M250866</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-01-27T22:03:54Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764305#M250867</link>
      <description>&lt;P&gt;The AP connects to the switch and either it reboots or the interface goes down and comes back up. There is no log of the AP joining the WLC at all.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 22:05:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764305#M250867</guid>
      <dc:creator>jdparsons</dc:creator>
      <dc:date>2023-01-27T22:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764331#M250873</link>
      <description>&lt;P&gt;I would rather not bother wasting any time troubleshooting any issue(s) with the 1800s.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I suspect the 1800 have a very poor "build" quality whereby the components were not designed to last this long.&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/244975"&gt;@Rich R&lt;/a&gt;, how many 1800s have you been RMAing per month?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 23:18:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764331#M250873</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2023-01-27T23:18:56Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764420#M250880</link>
      <description>&lt;P&gt;issue with only 1800 AP, do you have any other AP in and working ?&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2023 10:44:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764420#M250880</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-01-28T10:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764425#M250881</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;U&gt;&lt;FONT color="#FF6600"&gt;&lt;EM&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;gt;...&lt;/EM&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;SPAN&gt;&lt;U&gt;&lt;FONT color="#FF6600"&gt;&lt;EM&gt;continuously and never&lt;FONT color="#FF0000"&gt; joins&lt;/FONT&gt; the WLC&lt;/EM&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;BR /&gt;&amp;nbsp; Can you see anything in the controller &lt;STRONG&gt;logs&lt;/STRONG&gt; when these ap's are trying to join ? (Also include controller model and software version) ,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;M.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2023 11:43:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764425#M250881</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-01-28T11:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: Flapping/Intermittent Access Points</title>
      <link>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764538#M250893</link>
      <description>&lt;P&gt;In future get some console logs (especially since you were there doing factory reset) - that really is the ONLY way to 100&amp;amp; accurately diagnose these problems!&lt;BR /&gt;Sometimes a packet capture of the CAPWAP packets may show you something useful - like missing board info which confirms hardware (radios) failed.&lt;BR /&gt;But like Leo says we've been RMAing an average of 20 x 1832 per month for about 2 years now.&amp;nbsp; We don't use 1852 but probably safe to assume similar quality issues with 1852.&amp;nbsp; Cisco still consider this to be within expected MTBF.&lt;BR /&gt;Just RMA the 3 APs.&lt;/P&gt;</description>
      <pubDate>Sun, 29 Jan 2023 01:16:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flapping-intermittent-access-points/m-p/4764538#M250893</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-01-29T01:16:28Z</dc:date>
    </item>
  </channel>
</rss>

