<?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 Stuck Beacon Messages in Wireless Questions and Best Practices</title>
    <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Stuck-Beacon-Messages/m-p/38592#M1860</link>
    <description>I am seeing alot of stuck beacon messages, what do they mean
&lt;BR /&gt;
How can I get rid of these messages?
&lt;BR /&gt;
I have checked for PHY errors, although to be honest I am not sure why. Any advice, would be appreciated
&lt;BR /&gt;&lt;BR /&gt;
Oct 23 13:21:19 WAP002 user.warn kernel: wifi0: 1113001497 : stuck beacon (missed 11) action=0, scanning 0, syncbeacon 0, sc_beacons 1
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 0  measured latest ctl:-107 ext:-50  capped median ctl:-108 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 1  measured latest ctl:-106 ext:-50  capped median ctl:-107 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 2  measured latest ctl:0 ext:0  capped median ctl:-88 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: wifi0: 1113002716 : stuck beacon (missed 11) action=0, scanning 0, syncbeacon 0, sc_beacons 1
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 0  measured latest ctl:-107 ext:-50  capped median ctl:-108 ext:-88
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 1  measured latest ctl:-106 ext:-50  capped median ctl:-107 ext:-88
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 2  measured latest ctl:0 ext:0  capped median ctl:-88 ext:-88
&lt;BR /&gt;&lt;BR /&gt;
Histogram of PHY errors per second (pcttime in each range)
&lt;BR /&gt;
   0  1-500 ..1K  ..2K  ..5K ..10K ..20K ..50K .100K  more
&lt;BR /&gt;
   0     1     1     1     1     0     1    84    11     0
&lt;BR /&gt;&lt;BR /&gt;
 Running 9.0.0.0.56</description>
    <pubDate>Wed, 23 Oct 2013 14:00:38 GMT</pubDate>
    <dc:creator>simon_young_604</dc:creator>
    <dc:date>2013-10-23T14:00:38Z</dc:date>
    <item>
      <title>Stuck Beacon Messages</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Stuck-Beacon-Messages/m-p/38592#M1860</link>
      <description>I am seeing alot of stuck beacon messages, what do they mean
&lt;BR /&gt;
How can I get rid of these messages?
&lt;BR /&gt;
I have checked for PHY errors, although to be honest I am not sure why. Any advice, would be appreciated
&lt;BR /&gt;&lt;BR /&gt;
Oct 23 13:21:19 WAP002 user.warn kernel: wifi0: 1113001497 : stuck beacon (missed 11) action=0, scanning 0, syncbeacon 0, sc_beacons 1
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 0  measured latest ctl:-107 ext:-50  capped median ctl:-108 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 1  measured latest ctl:-106 ext:-50  capped median ctl:-107 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: NF Channel 2462 Chain 2  measured latest ctl:0 ext:0  capped median ctl:-88 ext:-88
&lt;BR /&gt;
Oct 23 13:21:20 WAP002 user.warn kernel: wifi0: 1113002716 : stuck beacon (missed 11) action=0, scanning 0, syncbeacon 0, sc_beacons 1
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 0  measured latest ctl:-107 ext:-50  capped median ctl:-108 ext:-88
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 1  measured latest ctl:-106 ext:-50  capped median ctl:-107 ext:-88
&lt;BR /&gt;
Oct 23 13:21:22 WAP002 user.warn kernel: NF Channel 2462 Chain 2  measured latest ctl:0 ext:0  capped median ctl:-88 ext:-88
&lt;BR /&gt;&lt;BR /&gt;
Histogram of PHY errors per second (pcttime in each range)
&lt;BR /&gt;
   0  1-500 ..1K  ..2K  ..5K ..10K ..20K ..50K .100K  more
&lt;BR /&gt;
   0     1     1     1     1     0     1    84    11     0
&lt;BR /&gt;&lt;BR /&gt;
 Running 9.0.0.0.56</description>
      <pubDate>Wed, 23 Oct 2013 14:00:38 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Stuck-Beacon-Messages/m-p/38592#M1860</guid>
      <dc:creator>simon_young_604</dc:creator>
      <dc:date>2013-10-23T14:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Stuck Beacon Messages</title>
      <link>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Stuck-Beacon-Messages/m-p/38593#M1861</link>
      <description>9.4.3 corrects an issue where stuck beacons occur in high-noise environments. 
&lt;BR /&gt;&lt;BR /&gt;
&lt;A href="https://support.ruckuswireless.com/documents/263-zoneflex-release-9-4-mr3-release-notes/download" rel="nofollow"&gt;https://support.ruckuswireless.com/do...&lt;/A&gt; 
&lt;BR /&gt;&lt;BR /&gt;
Stuck beacon is a driver-level error indicating the chipset couldn't complete a TX.
&lt;BR /&gt;&lt;BR /&gt;
Your histogram indicates a LOT of interference (can be non-wifi sources that won't show in a normal scan)</description>
      <pubDate>Wed, 23 Oct 2013 16:44:22 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Wireless-Questions-and-Best/Stuck-Beacon-Messages/m-p/38593#M1861</guid>
      <dc:creator>keith_redfield</dc:creator>
      <dc:date>2013-10-23T16:44:22Z</dc:date>
    </item>
  </channel>
</rss>

