<?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: Log assistance in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30119#M8410</link>
    <description>Michael,&lt;BR /&gt;&lt;BR /&gt;Thank you for the info and your help with this!!&lt;BR /&gt;&lt;BR /&gt;Kevin</description>
    <pubDate>Wed, 17 Oct 2018 18:23:39 GMT</pubDate>
    <dc:creator>k_cr</dc:creator>
    <dc:date>2018-10-17T18:23:39Z</dc:date>
    <item>
      <title>Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30117#M8408</link>
      <description>Over All Problem: We have an AP that is causing us issues. &amp;nbsp;Randomly, when you connect to it, one of 3 things will happen...&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;1. Connects, no problems&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;2. No IP address, but you're able to connect to the AP&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;3. The user is told that their password is incorrect and they need to input the correct password&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Scenario:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- We are utilizing a Zone Director 3025 appliance (Ver: 10.0.1.0, UpTime: 24d)&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- We have approx 75 AP's (r7982, r700, r510...All restarted within the past 24 days)&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- We are utilizing PSK's&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- We are utilizing dynamic vlans where users are placed on one of 5 vlans based upon conditions setup in RADIUS&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Troubleshooting&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- I have been unable to narrow down the AP(s) causing the issue&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- The issue doesn't happen all the time, it seems to happen randomly to random devices at random intervals of the day.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- All switch ports have been verified&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Things we know&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- There isn't a known DHCP issue. &amp;nbsp;If the user wanders to a different AP, then they will receive a valid IP address.&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;- The user's PSK is good. &amp;nbsp;If the user wanders to another AP, it connects to the AP &amp;amp; network with no issues&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;Requested Assistance:&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;I am looking at AP's that are around the affected area in an attempt to narrow down what may be causing this. &amp;nbsp;We had an issue with a device and I captured the log from one of the AP's the user connected to, but I can't find any information on interpreting the AP log data. &amp;nbsp;Any help interpreting the logs below would be greatly appreciated!! &amp;nbsp;Thanks!!&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Kevin&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;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:03:04 EW-A-1171-O local2.err syslog: lwapp_proc_add_mobile_apend_dvc_type: send device type to zd, rc 26, station 5c:f7:e6:bb:41:5e&amp;nbsp;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:03:04 EW-A-1171-O local2.err syslog: lwapp_update_role_based_access_pcy_me: error: attached role based policy_id :0, policy6_id :0 to station ,rc = 255 me_type=6 5c:f7:e6:bb:41:5e&amp;nbsp;&lt;/P&gt;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:03:04 EW-A-1171-O user.info kernel: net80211_tac_cfg_sta_set_param(): set station 5c:f7:e6:bb:41:5e vlan_id = 600&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:03:28 EW-A-1171-O daemon.warn Eved: STA-DISASSOC-REASON [ieee80211_input(),2076,received IEEE80211_FC0_SUBTYPE_DISASSOC] 5c:f7:e6:bb:41:5e rx_rssi=15,ack_rssi=0,reason=8,freq=2412,chan=1,rx pkt,byte;tx pkt,byte=(524,65243,686,557786)&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:03:38 EW-A-1171-O user.info kernel: net80211_tac_cfg_sta_set_param(): set station 5c:f7:e6:bb:41:5e vlan_id = 600&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;&amp;nbsp;Oct 17 14:04:56 EW-A-1171-O local2.err syslog: lwapp_proc_add_mobile_apend_dvc_type: send device type to zd, rc 26, station 5c:f7:e6:bb:41:5e&amp;nbsp;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:04:56 EW-A-1171-O local2.err syslog: lwapp_update_role_based_access_pcy_me: error: attached role based policy_id :0, policy6_id :0 to station ,rc = 255 me_type=6 5c:f7:e6:bb:41:5e&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:04:56 EW-A-1171-O user.info kernel: net80211_tac_cfg_sta_set_param(): set station 5c:f7:e6:bb:41:5e vlan_id = 600&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;
&lt;P alt="" name="" rel="" target="" title="" type="" value=""&gt;Oct 17 14:05:03 EW-A-1171-O daemon.warn Eved: MLME-REPLAYFAILURE.indication(wlan0 AES-CCM keyid=101 unicast RA:addr=e0:10:7f:3b:63:38 TA:addr=5c:f7:e6:bb:41:5e) (pkt-rsc:54 k-&amp;gt;rsc[1]:56&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;/P&gt;&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;</description>
      <pubDate>Wed, 17 Oct 2018 16:35:12 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30117#M8408</guid>
      <dc:creator>k_cr</dc:creator>
      <dc:date>2018-10-17T16:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30118#M8409</link>
      <description>The STA Dissassociation for reason=8, indicates that the client roamed away from the AP it was on.I don't know what MLME-REPLAYFAILURE relates too...</description>
      <pubDate>Wed, 17 Oct 2018 17:11:31 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30118#M8409</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-17T17:11:31Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30119#M8410</link>
      <description>Michael,&lt;BR /&gt;&lt;BR /&gt;Thank you for the info and your help with this!!&lt;BR /&gt;&lt;BR /&gt;Kevin</description>
      <pubDate>Wed, 17 Oct 2018 18:23:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30119#M8410</guid>
      <dc:creator>k_cr</dc:creator>
      <dc:date>2018-10-17T18:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30120#M8411</link>
      <description>Another grouping of logs to consider....&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;Oct 17 14:04:59 matrix: Adding peer AP.58:B6:33:0F:89:D0 (10.0.17.196) for PID 525 (func=avpd_roam_sync_req, line=994) ...&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:59 kernel:&amp;nbsp;&amp;nbsp;Keydata=0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0&amp;nbsp;&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:59 kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=0&amp;nbsp;&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:59 kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress:0x14cbb33da3d4&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:55 kernel: ieee80211_vlan_clr_filter 146 wlan2 del vlan 255&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:55 Eved: SMARTROAM-KICKOFF: addr=5c:f7:e6:bb:41:5e&amp;nbsp;rx_tot_cnt=149&amp;nbsp;rx_rssilo_cnt=150&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:55 kernel: Mac 0 - 5c:f7:e6:bb:41:5e&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;2147436400&amp;nbsp;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;&lt;BR alt="" name="" rel="" target="" title="" type="" value="" /&gt;Oct 17 14:04:55 kernel: ProbeMac filter List: used 1</description>
      <pubDate>Wed, 17 Oct 2018 22:43:45 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30120#M8411</guid>
      <dc:creator>k_cr</dc:creator>
      <dc:date>2018-10-17T22:43:45Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30121#M8412</link>
      <description>My user name and password will not work even did a factory hard reset using super and sp-admin cany do anything</description>
      <pubDate>Thu, 18 Oct 2018 05:23:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30121#M8412</guid>
      <dc:creator>electa_smith</dc:creator>
      <dc:date>2018-10-18T05:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30122#M8413</link>
      <description>Electa,&lt;BR /&gt;&lt;BR /&gt;I think you may have meant to post this in the forum as opposed to this conversation. &amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Kevin</description>
      <pubDate>Thu, 18 Oct 2018 17:46:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30122#M8413</guid>
      <dc:creator>k_cr</dc:creator>
      <dc:date>2018-10-18T17:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30123#M8414</link>
      <description>If you have held the indented hard reset button for 8 seconds after letting it fully power up, it should go to factory default.&lt;BR /&gt;If you cannot login to an AP that has been factory defaulted with userid = super, password = sp-admin, it may be an OEM model of our AP, that cannot be accessed except with the OEM company uid/pw.</description>
      <pubDate>Thu, 18 Oct 2018 18:11:41 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30123#M8414</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-18T18:11:41Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30124#M8415</link>
      <description>What's a OEM company uid/pw</description>
      <pubDate>Fri, 19 Oct 2018 20:39:56 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30124#M8415</guid>
      <dc:creator>electa_smith</dc:creator>
      <dc:date>2018-10-19T20:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30125#M8416</link>
      <description>They are private licensed ISPs who have the right to configure the APs soley for use of their customers who sign up for local service.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;If these are purchased on eBay/Amazon they are not supported by Ruckus, and because of the OEM proprietary configurations, can only be administered with their provided username/password.&lt;BR /&gt;Only buy Ruckus products from Ruckus resellers.</description>
      <pubDate>Fri, 19 Oct 2018 20:54:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30125#M8416</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-19T20:54:44Z</dc:date>
    </item>
    <item>
      <title>Re: Log assistance</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30126#M8417</link>
      <description>Hi Craig, please open a ticket with our Tech Support, and ask them to investigate your issues against bug ER-6341.We may need a deeper look at the logs, and a TSE can assist best over our Forums replies.</description>
      <pubDate>Fri, 19 Oct 2018 21:01:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Log-assistance/m-p/30126#M8417</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2018-10-19T21:01:15Z</dc:date>
    </item>
  </channel>
</rss>

