<?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 how to read log analysis tool &amp;quot;clients sections&amp;quot; in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/how-to-read-log-analysis-tool-quot-clients-sections-quot/m-p/11379#M2631</link>
    <description>Hi,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I am new to the ruckus, and I need an information about the log.&lt;BR /&gt;I need to know about the interval time about client uptime&amp;nbsp;and any others detail about my client behavior.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Below I've just found it the ruckus support website which it has a tool to create a few report about the AP or ZD. Here is the link I use&amp;nbsp;&lt;A href="https://loganalyzer1.ruckuswireless*com/Rowdy/" rel="nofollow" target="_blank" title="Link https//loganalyzer1ruckuswirelesscom/Rowdy/"&gt;https://loganalyzer1.ruckuswireless*com/Rowdy/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;So, lucky to find that tools. Thank you for the support.&amp;nbsp;&lt;BR /&gt;But I have a question about it. I really know how to read the log, especially for clients log.&lt;BR /&gt;Is there any help/guide so I can be able to read the log?&lt;BR /&gt;&lt;BR /&gt;I still don't know how to exactly read&amp;nbsp;the detail about the log information, like below:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/522i2F71A84D9C993298/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528" alt="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;May I get the answer?&lt;BR /&gt;Thank you,&amp;nbsp;</description>
    <pubDate>Thu, 10 Dec 2015 13:04:33 GMT</pubDate>
    <dc:creator>alvinp</dc:creator>
    <dc:date>2015-12-10T13:04:33Z</dc:date>
    <item>
      <title>how to read log analysis tool "clients sections"</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/how-to-read-log-analysis-tool-quot-clients-sections-quot/m-p/11379#M2631</link>
      <description>Hi,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I am new to the ruckus, and I need an information about the log.&lt;BR /&gt;I need to know about the interval time about client uptime&amp;nbsp;and any others detail about my client behavior.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Below I've just found it the ruckus support website which it has a tool to create a few report about the AP or ZD. Here is the link I use&amp;nbsp;&lt;A href="https://loganalyzer1.ruckuswireless*com/Rowdy/" rel="nofollow" target="_blank" title="Link https//loganalyzer1ruckuswirelesscom/Rowdy/"&gt;https://loganalyzer1.ruckuswireless*com/Rowdy/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;So, lucky to find that tools. Thank you for the support.&amp;nbsp;&lt;BR /&gt;But I have a question about it. I really know how to read the log, especially for clients log.&lt;BR /&gt;Is there any help/guide so I can be able to read the log?&lt;BR /&gt;&lt;BR /&gt;I still don't know how to exactly read&amp;nbsp;the detail about the log information, like below:&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528"&gt;&lt;img src="https://community.ruckuswireless.com/t5/image/serverpage/image-id/522i2F71A84D9C993298/image-size/large?v=v2&amp;amp;px=999" role="button" title="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528" alt="Image_ images_messages_5f91c3e1135b77e2478c4def_8058c388351531ca55a03c0c4e1ada01_RackMultipart201512105780x3zc8-d97f3604-bc41-472d-9e77-9cfe66a28017-1450841070.jpg1449752528" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;May I get the answer?&lt;BR /&gt;Thank you,&amp;nbsp;</description>
      <pubDate>Thu, 10 Dec 2015 13:04:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/how-to-read-log-analysis-tool-quot-clients-sections-quot/m-p/11379#M2631</guid>
      <dc:creator>alvinp</dc:creator>
      <dc:date>2015-12-10T13:04:33Z</dc:date>
    </item>
    <item>
      <title>Re: how to read log analysis tool "clients sections"</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/how-to-read-log-analysis-tool-quot-clients-sections-quot/m-p/11380#M2632</link>
      <description>The top is Transmit and Receive packets specific to your wireless client, so I think you might&lt;BR /&gt;&lt;BR /&gt;
appreciate greater explanation of the four QOS stacks and what the columns stand for and mean.&lt;BR /&gt;&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
AP CLI command: get mqstats.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
Client media queue and station information, in packets, accumulated&lt;BR /&gt;
since STA associates and discarded when client roams.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
# enq = original data packets queued for transmission.&amp;nbsp; # deq = the number of packets&lt;BR /&gt;
transmitted.&amp;nbsp; # reenq = number of packets&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
that are attempted to be transmitted again (re-enqueued).&amp;nbsp; # deact is related to transmission&lt;BR /&gt;
scheduling, and is not meaningful.&lt;BR /&gt;&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
qued:&amp;nbsp; # of packets currently in&lt;BR /&gt;
this queue. &amp;nbsp;Will usually be 0 but sometime you can catch it with a few&lt;BR /&gt;
packets.&lt;BR /&gt;&lt;BR /&gt;
ovrflw: # packets dropped from tail of&lt;BR /&gt;
queue due to the queue being ‘full’ (at the max limit for this packet class)&lt;BR /&gt;&lt;BR /&gt;
enq: # of packets enqueued to the tail&lt;BR /&gt;
of the queue&lt;BR /&gt;&lt;BR /&gt;
deq: # of packets dequeued from the head&lt;BR /&gt;
of the queue (includes retries)&lt;BR /&gt;&lt;BR /&gt;
reenq: # of packet re-enqueued to head&lt;BR /&gt;
of the queue (due to retries)&lt;BR /&gt;&lt;BR /&gt;
deact: # of times this queue was&lt;BR /&gt;
deactivated from the scheduler due to being empty (usually not important)&lt;BR /&gt;&lt;BR /&gt;
XRetries:&amp;nbsp; # of packets dropped due&lt;BR /&gt;
to excessive number of retries (usually 20). &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
--- MQ Stats ---&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;-- wlan0 --&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;STA:&lt;BR /&gt;
00:40:96:a8:f7:86 AID:1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
-----------------------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
Qued&amp;nbsp; ovrflw&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;&amp;nbsp;&amp;nbsp;enq&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
deq&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; reenq&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; deact&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
XRetries XTlimits AirtimeCrd&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;voice(0) X:&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 118&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 166&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 48&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 166&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
4000&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;video(2) X:&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 316&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 479&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 163&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
6115&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;44&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp; data(4) X:&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 201&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 322&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 121&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
2875&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
4000&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;bkgnd(6) X:&amp;nbsp;&amp;nbsp; 0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1601&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2134&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 533&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
7556&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 68&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;BR /&gt;
3880&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;
XTlimits indicates how many times packets exceeded the&lt;BR /&gt;
holding time limit. If the AP can't dequeue the packet before holding time&lt;BR /&gt;
expires (these holding time limits are different for different types of traffic&lt;BR /&gt;
meaning, data, background, video, voice) it will drop it.&lt;BR /&gt;&lt;BR /&gt;XTlimit value is significant in the support info. All queue columns showing&lt;BR /&gt;
some major figures, usually indicates too much interference or too much&lt;BR /&gt;
incoming data from the wire side.&lt;BR /&gt;&lt;BR /&gt;Look for too much broadcast traffic on the network, and how big is the&lt;BR /&gt;
broadcast domain, and what type of clients are on the network?&lt;BR /&gt;&lt;BR /&gt;If interference on the radio band doesn’t look bad, it may be wire traffic&lt;BR /&gt;
driving client queue limits to max.</description>
      <pubDate>Thu, 10 Dec 2015 19:18:57 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/how-to-read-log-analysis-tool-quot-clients-sections-quot/m-p/11380#M2632</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-12-10T19:18:57Z</dc:date>
    </item>
  </channel>
</rss>

