<?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: AP6522 Log comprehensions in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20538#M1309</link>
    <description>For me it sound like a client problem or a wifi design problem.&lt;BR /&gt;
&lt;BR /&gt;
Capturing is running like this:&lt;BR /&gt;
remote-debug live-pktcap rf-domain &lt;YOUR-RF&gt; write tftp://&lt;TFTP-SERVER&gt;/filename.pcap radio all count 1000 filter ether host &lt;CLIENT-MAC&gt;&lt;BR /&gt;
&lt;BR /&gt;
This write 1000 packages to your TFTP Server for the client &lt;CLIENT-MAC&gt; include all wireless packages with the client mac.&lt;BR /&gt;
&lt;BR /&gt;
With this pcap you can check what happens.&lt;BR /&gt;&lt;/CLIENT-MAC&gt;&lt;/CLIENT-MAC&gt;&lt;/TFTP-SERVER&gt;&lt;/YOUR-RF&gt;</description>
    <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
    <dc:creator>Timo1</dc:creator>
    <dc:date>2017-10-11T12:33:00Z</dc:date>
    <item>
      <title>AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20529#M1300</link>
      <description>Hello,&lt;BR /&gt;
&lt;BR /&gt;
        We have 12 AP6522  and a RFS4000 Wireless Controller. All of them are in version 5.5.1.0-017R. The  peripherals connected to the AP are 25 MC90XX.&lt;BR /&gt;
&lt;BR /&gt;
    Since september, we  started to check the logs of the AP and I need some help to understand some  message or to solve some alerts.&lt;BR /&gt;
&lt;BR /&gt;
    There are the  message : &lt;BR /&gt;
&lt;BR /&gt;
    &lt;OL&gt; 
&lt;LI&gt;KERN-3-ERR: 0| bridge.c:1598       Warning: Filtering MAC address 00-00-00-00-00-00 on vlan 1 port up1 from       FDB.  
&lt;/LI&gt;&lt;LI&gt;DOT11-5-WPA_WPA2_FAILED:       Client 00-23-68-00-00-00 failed group key handshake on wlan       TerminauxMobiles radio ap6522-AP1:R1  
&lt;/LI&gt;&lt;LI&gt;DOT11-6-CLIENT_DISASSOCIATED:       Client 00-23-68-00-00-00 disassociated from wlan TerminauxMobiles radio       ap6522-AP9:R1: client initiated (reason code:3)  
&lt;/LI&gt;&lt;LI&gt;DOT11-6-CLIENT_DISASSOCIATED:       Client 00-23-68-00-00-00 disassociated from wlan TerminauxMobiles radio       ap6522-AP3:R1: dot11i 4way handshake timeout (reason code:15)  
&lt;/LI&gt;&lt;LI&gt;DOT11-6-CLIENT_DISASSOCIATED:       Client 00-23-68-00-00-00 disassociated from wlan TerminauxMobiles radio       ap6522-AP8:R1: dot11i group handshake timeout (reason code:16) &lt;/LI&gt;&lt;/OL&gt;        I found in the FAQ a  similar message for KERN-3-ERR but it's slighty different.&lt;BR /&gt;
&lt;BR /&gt;
    I understand with  the second message that there is a problem between the AP and the peripheral.&lt;BR /&gt;
&lt;BR /&gt;
    In the  manual for the Wing Wireless Reason Code, reason code says "station has left ess" but it doesn't help me.&lt;BR /&gt;
&lt;BR /&gt;
    For the  reason code 15 &amp;amp; 16, the manual says that the problem come from the AP or  the client. But the wireless cover is excellent and this messages concern all  peripheral.&lt;BR /&gt;
&lt;BR /&gt;
        Some  peripherals are in 2,4GHz and some in 5GHz. The AP are at 10m high. I think the  height may be the problem.&lt;BR /&gt;
&lt;BR /&gt;
        Can you  help me with this alerts ?&lt;BR /&gt;
&lt;BR /&gt;
        Best  regards.&lt;BR /&gt;
&lt;BR /&gt;
    &lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20529#M1300</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:15:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20530#M1301</link>
      <description>The dissass reason codes are per 802.11 standard - here a list of a KB article with the list....&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/What-s-mean-of-802-11-Deauth-Reason-Codes" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/What-s-mean-of-802-11-Deauth-Reason-Codes&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20530#M1301</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20531#M1302</link>
      <description>Thank you, I had a file but I don't look at the FAQ for the reason code. It 's similar to my file content. &lt;BR /&gt;
Could you give some explanation of some terms like "group-key handshake" or "ess" ? I search for "group-key handshake". I see it's a communication protocol between 2 systems.&lt;BR /&gt;
Thanks.</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20531#M1302</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20532#M1303</link>
      <description>&lt;A href="https://en.wikipedia.org/wiki/IEEE_802.11i-2004" target="_blank" rel="nofollow noreferrer noopener"&gt;https://en.wikipedia.org/wiki/IEEE_802.11i-2004&lt;/A&gt;\&lt;BR /&gt;
The group key is for broadcast/multicast messages between the AP-client.&lt;BR /&gt;
&lt;BR /&gt;
I'd recommend to read this book to get a better unterstanding..&lt;BR /&gt;
&lt;A href="https://www.amazon.fr/Cwna-Certified-Wireless-Administrator-Official/dp/1118893700/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.amazon.fr/Cwna-Certified-Wireless-Administrator-Official/dp/1118893700/&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20532#M1303</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20533#M1304</link>
      <description>Thanks for additional information.&lt;BR /&gt;
&lt;BR /&gt;
Do you know this alert : KERN-3-ERR: 0| bridge.c:1598      Warning: Filtering MAC address 00-00-00-00-00-00 on vlan 1 port up1 from      FDB ?&lt;BR /&gt;
I can't find a good explanation. I see a similar message in the FAQ but it's diffrent.&lt;BR /&gt;
&lt;BR /&gt;
Thanks.&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20533#M1304</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20534#M1305</link>
      <description>I get the same 00-00-00-00-00-00 MAC message with a RFS6000 and WiNG 5.8.4. But don't see any of this packages.&lt;BR /&gt;
&lt;BR /&gt;
For the reason code 15 and 16 you can do a packet capture to understand the problem. Maybe do a spectrum analyst, of the signal strength is perfect.</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20534#M1305</guid>
      <dc:creator>Timo1</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20535#M1306</link>
      <description>We get an intervention to check the Wifi signal and the strengh is good on the entire warehouse. The AP cover very well the building.&lt;BR /&gt;
&lt;BR /&gt;
For the pocket capture, did you advice me a soft in particular ?&lt;BR /&gt;
Thanks.&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20535#M1306</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20536#M1307</link>
      <description>Do you also check the warehouse for SNR, Channel plan and CCI?&lt;BR /&gt;
&lt;BR /&gt;
Just checking for Signal say's mostly nothing</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20536#M1307</guid>
      <dc:creator>Timo1</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20537#M1308</link>
      <description>Yes, the channel plan and CCI are good.&lt;BR /&gt;
For the SNR too. There a pertubation an AP and the controller. For the rest of the AP, there is no noise.&lt;BR /&gt;
The intervention was carry out by a Wireless specialist. &lt;BR /&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20537#M1308</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20538#M1309</link>
      <description>For me it sound like a client problem or a wifi design problem.&lt;BR /&gt;
&lt;BR /&gt;
Capturing is running like this:&lt;BR /&gt;
remote-debug live-pktcap rf-domain &lt;YOUR-RF&gt; write tftp://&lt;TFTP-SERVER&gt;/filename.pcap radio all count 1000 filter ether host &lt;CLIENT-MAC&gt;&lt;BR /&gt;
&lt;BR /&gt;
This write 1000 packages to your TFTP Server for the client &lt;CLIENT-MAC&gt; include all wireless packages with the client mac.&lt;BR /&gt;
&lt;BR /&gt;
With this pcap you can check what happens.&lt;BR /&gt;&lt;/CLIENT-MAC&gt;&lt;/CLIENT-MAC&gt;&lt;/TFTP-SERVER&gt;&lt;/YOUR-RF&gt;</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20538#M1309</guid>
      <dc:creator>Timo1</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: AP6522 Log comprehensions</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20539#M1310</link>
      <description>I'll try that and reply if I need help. Thanks for your help.</description>
      <pubDate>Wed, 11 Oct 2017 12:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/ap6522-log-comprehensions/m-p/20539#M1310</guid>
      <dc:creator>tech_ori</dc:creator>
      <dc:date>2017-10-11T12:33:00Z</dc:date>
    </item>
  </channel>
</rss>

