R500 "random" disassociations

unknown

Hi, I have two Ruckus R500 installed with the latest unleashed firmware. I'm experiencing a behavior where one of my laptops with Windows 10 frequently gets disassociated from the AP:s.

The system log during the time of disassociation:

Mar 22 22:21:21 ArnasPrastgard kernel: ath_get_radio_stats:Add counters, tx_errors=3431 rx_errors=1 tx_dropped=0 rx_dropped=0
Mar 22 22:21:04 ArnasPrastgard kernel: ol_rc_update_handler: WARNING: handler called without transmit attempts
Mar 22 22:21:04 ArnasPrastgard kernel:  Keydata=0x1d 0xb9 0x35 0x92 0x11 0x89 0xaa 0xad 0x17 0x9c 0x8e 0x78 0x79 0x6c 0xf8 0xc4 
Mar 22 22:21:04 ArnasPrastgard kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=4 
Mar 22 22:21:04 ArnasPrastgard kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress:0x5ff2ae815670 
Mar 22 22:21:04 ArnasPrastgard kernel: net80211_tac_cfg_sta_set_param(): set station 70:56:81:ae:f2:5f vlan_id = 1
Mar 22 22:21:04 ArnasPrastgard kernel: ol_ath_mute_dfs;1907: Muting DFS
Mar 22 22:21:02 ArnasPrastgard Eved: STA-DISASSOC-REASON [ieee80211_input(),2024,received IEEE80211_FC0_SUBTYPE_DISASSOC] 70:56:81:ae:f2:5f rx_rssi=34,ack_rssi=0,reason=8,freq=2437,chan=6,rx pkt,byte;tx pkt,byte=(21296,1827092,42248,56107480)
Mar 22 22:20:56 ArnasPrastgard clusterD[859]: clusterd_threadForTacmon:2101 clusterD reply the tacmon message.
Mar 22 22:20:56 ArnasPrastgard ZD-APMgr: IPC_thread rcv ping from TACMON 
Mar 22 22:20:52 ArnasPrastgard kernel: ath_get_radio_stats:Add counters, tx_errors=3431 rx_errors=1 tx_dropped=0 rx_dropped=0
Mar 22 22:20:26 ArnasPrastgard clusterD[859]: clusterd_threadForTacmon:2101 clusterD reply the tacmon message.


The frequency and the interval of the disassociations seem almost random to me. In some cases several hours can pass before a disassociation, while sometimes I get disassociated every few minutes.

I'm not seeing this behavior on other clients connected to the same AP:s which could suggest an issue with the actual client machine. However, that specific machine does not show these symptoms at all when connecting to other AP:s.

Has anyone experienced something similar?

/John

michael_brado

Hello John,


     The message says the AP received a STA disassociation, for reason=8, or Client has Roamed away. 


Is this Win10 perhaps equidistant between two APs, that it keeps deciding to bounce between?  All roaming


behavior is controlled by the client radio/drivers, who have some algorithm that looks at signal strength,


interference, and other factors.  Ruckus Unleashed APs do not have Load Balancing or Band Balancing


enabled by default.  Check Admin&Services, Services, Radio Control, where each service has a tab.