<?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: PHY Errors, Noise Floor, Airtime interpretation in ZD in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13919#M3416</link>
    <description>Hi Jelle ,
&lt;BR /&gt;&lt;BR /&gt;
Here are our numbers as seen on a 7762AC deployed indoors, during a tech conference. At the moment we recorded these numbers, it was almost impossible to get a reliable connection on the 2.4 GHz frequency.
&lt;BR /&gt;&lt;BR /&gt;
Radio: 802.11g/n
&lt;BR /&gt;
# of Aurhorized Client Devices: 69
&lt;BR /&gt;
Noise Floor: -88
&lt;BR /&gt;
PHY Errors: 831
&lt;BR /&gt;
% AirTime (total/busy/RX/TX): 87/47/33/8
&lt;BR /&gt;&lt;BR /&gt;
%Retries/%Drops: 7.14 / 0.00
&lt;BR /&gt;
TX Power: Min
&lt;BR /&gt;
Background scanning: enabled</description>
    <pubDate>Tue, 18 Mar 2014 13:54:59 GMT</pubDate>
    <dc:creator>the_event_engin</dc:creator>
    <dc:date>2014-03-18T13:54:59Z</dc:date>
    <item>
      <title>PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13917#M3414</link>
      <description>I would like to find out what values for PHY Errors, Noice Floor, Airtime total, busy, RX, TX are good and what values are bad?
&lt;BR /&gt;&lt;BR /&gt;
If I'm correctly informed, this is what I know:
&lt;BR /&gt;
PHI Errors of &amp;lt; 20000 is acceptable, 
&lt;BR /&gt;
Noise Floor above -85 is bad, below -110 is excellent. 
&lt;BR /&gt;
Total Airtime 100% would be great since that means the capacity is fully used, total airtime of &amp;lt; 20 could mean there is a lot of interference, or hardly any users. 
&lt;BR /&gt;&lt;BR /&gt;
Is this correct? 
&lt;BR /&gt;
What can I learn from the other Airtime values (busy, rx, tx)? Are the values different for 2.4 and 5 GHz? (i.e 2.4GHz NF should be below -90, 5GHz NF should be below -85?)
&lt;BR /&gt;&lt;BR /&gt;
I'm basically looking for an answer on this question: what values of which fields of the monitoring page in the ZD indicate that an AP is doing great or needs attention?</description>
      <pubDate>Fri, 14 Mar 2014 14:48:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13917#M3414</guid>
      <dc:creator>jelle_alten_606</dc:creator>
      <dc:date>2014-03-14T14:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13918#M3415</link>
      <description>You've asked a great question and I hope for a nice discussion on this.
&lt;BR /&gt;&lt;BR /&gt;
It's a bit subjective and it's not quite clear cut what is acceptable and what not. Maybe just one of many clients will cause most of the errors and others will do less and work fine.
&lt;BR /&gt;&lt;BR /&gt;
But in any case I would not consider PHY errors of s a good compromise between price/performance.</description>
      <pubDate>Mon, 17 Mar 2014 07:39:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13918#M3415</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2014-03-17T07:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13919#M3416</link>
      <description>Hi Jelle ,
&lt;BR /&gt;&lt;BR /&gt;
Here are our numbers as seen on a 7762AC deployed indoors, during a tech conference. At the moment we recorded these numbers, it was almost impossible to get a reliable connection on the 2.4 GHz frequency.
&lt;BR /&gt;&lt;BR /&gt;
Radio: 802.11g/n
&lt;BR /&gt;
# of Aurhorized Client Devices: 69
&lt;BR /&gt;
Noise Floor: -88
&lt;BR /&gt;
PHY Errors: 831
&lt;BR /&gt;
% AirTime (total/busy/RX/TX): 87/47/33/8
&lt;BR /&gt;&lt;BR /&gt;
%Retries/%Drops: 7.14 / 0.00
&lt;BR /&gt;
TX Power: Min
&lt;BR /&gt;
Background scanning: enabled</description>
      <pubDate>Tue, 18 Mar 2014 13:54:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13919#M3416</guid>
      <dc:creator>the_event_engin</dc:creator>
      <dc:date>2014-03-18T13:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13920#M3417</link>
      <description>Well you've got low retry rate which is good, also your Air Time is at 87% but the Air Time declared as busy is at 47% and the noise floor is at -88dBm. 
&lt;BR /&gt;&lt;BR /&gt;
I guess there are quite a few other (or your) networks around your AP that keep triggering this APs and the STAs connected to it CCA.
&lt;BR /&gt;&lt;BR /&gt;
This could also be from people bringing their MiFis. How many networks do are there?
&lt;BR /&gt;&lt;BR /&gt;
You could try using a higher directional antenna or 7762-AC-S and stop transmitting 802.11b rates. Those travel far and cause a lot of issues. You do that over CLI.</description>
      <pubDate>Wed, 19 Mar 2014 08:08:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13920#M3417</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2014-03-19T08:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13921#M3418</link>
      <description>So if I zoom in on Airtime: 
&lt;BR /&gt;
High "total" is good, if "busy" is not a big part of it? 
&lt;BR /&gt;
Or even: if busy &amp;lt; rx + tx, the AP is doing ok?</description>
      <pubDate>Wed, 19 Mar 2014 22:55:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13921#M3418</guid>
      <dc:creator>jelle_alten_606</dc:creator>
      <dc:date>2014-03-19T22:55:26Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13922#M3419</link>
      <description>Uh uh, now I have an AP that has no clients, but %Airtime of 66.3/9.7/52.3/4.3  (total/busy/RX/TX) . Why is it RXing 52 % while there are no clients, no meshing APs? Anybody a clue? 
&lt;BR /&gt;
The Noise Floor is -90, with quite some PHY Errors.
&lt;BR /&gt;&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c407135b77e247926013_705fcdfe2258a2b230f70cdbec3c55f3_Schermafbeelding20140325om20.3-b5bf3ca1-b582-4557-98c3-7a6e4b97877a-544279920.png1395776030"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/583i66060AD14FF6725E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c407135b77e247926013_705fcdfe2258a2b230f70cdbec3c55f3_Schermafbeelding20140325om20.3-b5bf3ca1-b582-4557-98c3-7a6e4b97877a-544279920.png1395776030" alt="Image_ images_messages_5f91c407135b77e247926013_705fcdfe2258a2b230f70cdbec3c55f3_Schermafbeelding20140325om20.3-b5bf3ca1-b582-4557-98c3-7a6e4b97877a-544279920.png1395776030" /&gt;&lt;/span&gt;</description>
      <pubDate>Tue, 25 Mar 2014 19:32:58 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13922#M3419</guid>
      <dc:creator>jelle_alten_606</dc:creator>
      <dc:date>2014-03-25T19:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13923#M3420</link>
      <description>Well you have no clients currently, but the history shows the AP has transferred 74MB in the 5GHZ and 179MB in the 2,4GHz bands and the calculations are done on those data.
&lt;BR /&gt;&lt;BR /&gt;
I'd say the AP is in good condition. On the 2,4GHz you've got only 5,5% of retries and no drops, the noise floor is OK and AT looks good.</description>
      <pubDate>Tue, 25 Mar 2014 22:04:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13923#M3420</guid>
      <dc:creator>primoz_marinsek</dc:creator>
      <dc:date>2014-03-25T22:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13924#M3421</link>
      <description>Thanks for your reply. It seems that the values of the AirTime are pinned to the last values they had when there was a client. Or at least the value doesn't go down very fast.
&lt;BR /&gt;
Either it is an average over a longer time interval than I expected, or it is registered the same way the RF Pollution is: when there is no traffic anymore, it will keep the last known value since no new values can be registered without traffic.
&lt;BR /&gt;&lt;BR /&gt;
Can anybody confirm this?
&lt;BR /&gt;&lt;BR /&gt;
Here are screen shots of last night (all left the building) and this morning (nobody in yet). I confirmed that there were no stations by checking the event logs of the AP. What I find interesting is that the AirTime is still pretty high, even RX is 42% after a silent night. And the fairies obviously downloaded 5 MB during the night, while uploading 800 MB, bypassing the event logs. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; That might also explain the airtime...
&lt;BR /&gt;&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c408135b77e2479278de_7a58723b3e8cc97f07bf93d6c258767d_WifiDifs_inline-3bf32bca-ebd2-4abf-b816-945d268e8f57-957795747.png1395868465"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/584i8EFAA3C4B9D5308D/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c408135b77e2479278de_7a58723b3e8cc97f07bf93d6c258767d_WifiDifs_inline-3bf32bca-ebd2-4abf-b816-945d268e8f57-957795747.png1395868465" alt="Image_ images_messages_5f91c408135b77e2479278de_7a58723b3e8cc97f07bf93d6c258767d_WifiDifs_inline-3bf32bca-ebd2-4abf-b816-945d268e8f57-957795747.png1395868465" /&gt;&lt;/span&gt;</description>
      <pubDate>Wed, 26 Mar 2014 21:18:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13924#M3421</guid>
      <dc:creator>jelle_alten_606</dc:creator>
      <dc:date>2014-03-26T21:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13925#M3422</link>
      <description>hey, &lt;BR /&gt;&lt;BR /&gt;how could I troubleshoot the noise floor ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c410135b77e2479439ac_5c6e67d32af5ed808429ea20e097611c_RackMultipart20150316293468vx8-2f4804a4-bbcf-41d5-b012-8669364732e9-1663709439.png1426509889"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/585i92613A950C42A2B8/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c410135b77e2479439ac_5c6e67d32af5ed808429ea20e097611c_RackMultipart20150316293468vx8-2f4804a4-bbcf-41d5-b012-8669364732e9-1663709439.png1426509889" alt="Image_ images_messages_5f91c410135b77e2479439ac_5c6e67d32af5ed808429ea20e097611c_RackMultipart20150316293468vx8-2f4804a4-bbcf-41d5-b012-8669364732e9-1663709439.png1426509889" /&gt;&lt;/span&gt;&lt;B&gt;&lt;/B&gt;</description>
      <pubDate>Mon, 16 Mar 2015 12:45:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13925#M3422</guid>
      <dc:creator>abed_al_r_b</dc:creator>
      <dc:date>2015-03-16T12:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13926#M3423</link>
      <description>That looks fantastic. Your noise floors are much lower (remember that dBm's are powers of 10, so the more negative the number, the lower the noise floor). You have a moderate number of PHY errors on 2.4 and none on 5GHz, but that's fairly impressive. Airtime utilization is almost all tx/rx and very little "busy".&lt;BR /&gt;&lt;BR /&gt;I live in a residential area and my numbers are worse than yours. Are you having performance issues?</description>
      <pubDate>Mon, 16 Mar 2015 15:45:38 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13926#M3423</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2015-03-16T15:45:38Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13927#M3424</link>
      <description>First, thanks for the reply.&lt;BR /&gt;Second, yes , I do have a performance issue .&lt;BR /&gt;I understand the following, If my TX power is Full and the noise is -118 , is that a good statistics ? 'casue i thought the noise should be between -85 &amp;lt;-&amp;gt; -110 .&lt;BR /&gt;I do have a lot of packet lost .</description>
      <pubDate>Wed, 18 Mar 2015 07:48:35 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13927#M3424</guid>
      <dc:creator>abed_al_r_b</dc:creator>
      <dc:date>2015-03-18T07:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13928#M3425</link>
      <description>No, I think you might be misinterpreting the original post. The noise floor, loosely speaking, represents the minimum signal strength that the AP could "hear" over ambient noise. So the lower this number (or rather, the bigger the negative number), the better. So a noise floor of -120 is better than -118, for example. Anything better than -100 is really really good.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I see in your case most of your clients are connected to 2.4GHz, but you've only transferred 300MB of data or so in total. It might be more useful to look at these stats with some more data transferred (e.g. more uptime or speed tests between reboots). It might also be helpful to open a support ticket, where you can attach support info taken from the ZoneDirector or from the AP. Those contain more detailed breakdown of performance metrics which may be more useful. From the glance that you showed, everything seems healthy to me.</description>
      <pubDate>Wed, 18 Mar 2015 15:43:35 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13928#M3425</guid>
      <dc:creator>john_d</dc:creator>
      <dc:date>2015-03-18T15:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13929#M3426</link>
      <description>Somehow before I made some changes to the Ruckus controller, the PHY Errors value from all AP were a lot lower while the users experienced bad connection.&amp;nbsp; After the change, the PHY Errors value jumped to xxxx which is way higher, but the users got better connection and better network access. &amp;nbsp; I wonder why ?&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c469135b77e247a6ea47_d401ce8556e92b5e168b07cba9b87310_RackMultipart20180824115720qt7-c697298d-b2f6-4dcd-89e7-0950d4e2353b-697623022.jpg1535135073"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/586i52CFF4BCF4378BC3/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c469135b77e247a6ea47_d401ce8556e92b5e168b07cba9b87310_RackMultipart20180824115720qt7-c697298d-b2f6-4dcd-89e7-0950d4e2353b-697623022.jpg1535135073" alt="Image_ images_messages_5f91c469135b77e247a6ea47_d401ce8556e92b5e168b07cba9b87310_RackMultipart20180824115720qt7-c697298d-b2f6-4dcd-89e7-0950d4e2353b-697623022.jpg1535135073" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c469135b77e247a6ea47_b05e77409f4d606ec30fdfe55edf6b6b_RackMultipart20180824100075rf8-0b3f7b05-a9a5-47fe-91f1-1aae9c7b3eac-780691941.jpg1535135081"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/587i6E4DE5DDB2E84E87/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c469135b77e247a6ea47_b05e77409f4d606ec30fdfe55edf6b6b_RackMultipart20180824100075rf8-0b3f7b05-a9a5-47fe-91f1-1aae9c7b3eac-780691941.jpg1535135081" alt="Image_ images_messages_5f91c469135b77e247a6ea47_b05e77409f4d606ec30fdfe55edf6b6b_RackMultipart20180824100075rf8-0b3f7b05-a9a5-47fe-91f1-1aae9c7b3eac-780691941.jpg1535135081" /&gt;&lt;/span&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;</description>
      <pubDate>Fri, 24 Aug 2018 18:36:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13929#M3426</guid>
      <dc:creator>rick_buthsombat</dc:creator>
      <dc:date>2018-08-24T18:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: PHY Errors, Noise Floor, Airtime interpretation in ZD</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13930#M3427</link>
      <description>@RICK BUTHSOMBAT: Do you still remember what changes you made in the controller?</description>
      <pubDate>Tue, 02 Apr 2019 14:41:09 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/PHY-Errors-Noise-Floor-Airtime-interpretation-in-ZD/m-p/13930#M3427</guid>
      <dc:creator>leon_broer</dc:creator>
      <dc:date>2019-04-02T14:41:09Z</dc:date>
    </item>
  </channel>
</rss>

