Documentation Downloads Knowledge How-To Hub Forums Cases Assets Warranty
Skip to main content
atma_tiwana

17 Messages

 • 

326 Points

Thu, Sep 24, 2020 3:09 PM

R600 unleashed dropping 2.4ghz

R600 unleashed dropping 2.4ghz connection.

Hi. I have unleashed running on 2 R600's that are wired into a switch. Mesh option is off.

Very 3ish days the 2.4ghz connection drops. The only reason I know this is because I have a google nest doorbell which is constantly uploading video to the cloud.

Anybody got any pointers before I sell the Ruckus system. Ive had this before with a Zyxel Multy X, but never an issue with all other systems ive tried including my ISP router.

Question

 • 

Updated 

4 months ago

34

5

Responses

david_black_5940365

113 Messages

 • 

2.4K Points

4 months ago

The R600 is one of the best APs Ruckus has shipped. You’re problem could be any number of things including the thermostat, router, ISP, internet circuit, Nest servers, interference. Why are you using the 2.4 band anyway? 5 would be a much better choice.

3

atma_tiwana

17 Messages

 • 

326 Points

Unfortunately in the U.K google do not allow the nest hello doorbell to run at 5ghz.

As far as I know all the 5ghz devices had no issues but as stated the nest hello doorbell has a 24/7 upload stream and when I tried to connect to the other 2.4ghz devices which are wyze cams they had disconnected and 3 of the 4 had reconnected and one did not connect.

This leads me to believe the issue is not the devices but something to do with the 2.4ghz frequency dropping out.

When I realised the provlem I was able to log in remotely using the unleashed mobile app so I know the network was up and running.

Strange things going on

Like

4 months ago

0

syamantak_omer

Official Rep

 • 

733 Messages

 • 

11.4K Points

Hi Atma,

You may need to log a case to check this issue, as it is specific to doorbell over 2.4GHz radio.

For some quick check ups, refer below points:
  • Check if other devices are also dropping on 2.4GHz radio.
  • How far doorbell is connected from the nearest AP?
  • Check on Unleashed event logs, if device is dropping or it is just loosing internet connection. May be flag the doorbell as favorite client in the Unleashed GUI.
  • Pull the AP support logs and see what it shows when client disconnect (AP log will indicate the disconnection reason, but you have to be quick to pull the logs as soon as you see the disconnection, because logs may get overwrite by new logs).
  • If disconnection is too frequent, run the troubleshoot utility in Unleashed GUI for this client and it will show you why client is getting disconnection.
  • It is good idea to check if there is high interference on 2.4 radio. Also check if there is a USB 3.0 device or any other electronic device is located which can impact 2.4G radio.
Regards,
Syamantak Omer

Regards,

Syamantak Omer

Like

4 months ago

atma_tiwana

17 Messages

 • 

326 Points

Just checked and nest had an issue the same day as my issue so that would possibly explain the issue. But still concerned that my wyze cams went offline (possibly)

Like

4 months ago

0

atma_tiwana

17 Messages

 • 

326 Points

4 months ago

Here is a copy of the log if anyone can help.

The outage hapened at 11:02 but this is the closest info I can find

ntroller connecting error, errno: 2 No such file or directory
Sep 24 11:47:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:47:23 Ruckus-Unleashed meshd[13928]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:47:23 Ruckus-Unleashed meshd[13924]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:47:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:46:53 Ruckus-Unleashed meshd[13840]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:46:53 Ruckus-Unleashed meshd[13836]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:46:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:46:23 Ruckus-Unleashed meshd[13767]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:46:23 Ruckus-Unleashed meshd[13763]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:46:20 Ruckus-Unleashed ntpclient[13758]: Skew 40.1mS, freq adjust 0
Sep 24 11:46:20 Ruckus-Unleashed ntpclient[13758]: Time set from remote server
Sep 24 11:46:20 Ruckus-Unleashed ntpclient[13758]: Using server: ntp.ruckuswireless.com
Sep 24 11:46:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:45:53 Ruckus-Unleashed meshd[13684]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:45:52 Ruckus-Unleashed meshd[13680]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:45:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:45:24 Ruckus-Unleashed kernel: FWLOG: [106174147] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Sep 24 11:45:24 Ruckus-Unleashed kernel: FWLOG: [106173906] WAL_DBGID_STA_VDEV_XRETRY ( 0x40 )
Sep 24 11:45:22 Ruckus-Unleashed meshd[13595]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:45:22 Ruckus-Unleashed meshd[13591]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:45:16 Ruckus-Unleashed syslog: sqlited, sta count = 13
Sep 24 11:45:07 Ruckus-Unleashed kernel: v54cf: v54cf_open: inode=8f56b368, filp=89dcf2c0
Sep 24 11:45:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:45:00 Ruckus-Unleashed kernel: ol_rc_update_handler: WARNING: handler called without transmit attempts
Sep 24 11:45:00 Ruckus-Unleashed kernel:  Keydata=0x78 0x8d 0xf2 0x63 0x4d 0x5e 0xed 0x9e 0xf1 0x2a 0x9b 0xe5 0xb9 0x0 0x61 0x49
Sep 24 11:45:00 Ruckus-Unleashed kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=4
Sep 24 11:45:00 Ruckus-Unleashed kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress:0x5cae8904a9dc
Sep 24 11:45:00 Ruckus-Unleashed kernel: net80211_tac_cfg_sta_set_param(): set station dc:a9:04:89:ae:5c vlan_id = 1
Sep 24 11:44:52 Ruckus-Unleashed meshd[13503]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:44:52 Ruckus-Unleashed meshd[13499]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:44:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:44:22 Ruckus-Unleashed meshd[13419]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:44:22 Ruckus-Unleashed meshd[13415]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:44:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:43:52 Ruckus-Unleashed kernel: FWLOG: [106080201] WAL_DBGID_TX_SCH_REGISTER_TIDQ ( 0xff, 0x1 )
Sep 24 11:43:52 Ruckus-Unleashed stamgr: tac_del_arp:dev=br0 SIOCDARP failed, errno=6
Sep 24 11:43:52 Ruckus-Unleashed kernel:  Keydata=0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Sep 24 11:43:52 Ruckus-Unleashed kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=0
Sep 24 11:43:52 Ruckus-Unleashed kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress:0x5cae8904a9dc
Sep 24 11:43:52 Ruckus-Unleashed meshd[13342]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:43:51 Ruckus-Unleashed meshd[13338]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:43:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:43:29 Ruckus-Unleashed kernel: v54cf: v54cf_open: inode=8f56b9a8, filp=89b959c0
Sep 24 11:43:21 Ruckus-Unleashed meshd[13264]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:43:21 Ruckus-Unleashed meshd[13256]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:43:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:42:51 Ruckus-Unleashed meshd[13171]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:42:51 Ruckus-Unleashed meshd[13167]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:42:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:42:21 Ruckus-Unleashed meshd[13097]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:42:21 Ruckus-Unleashed meshd[13093]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:42:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:41:51 Ruckus-Unleashed meshd[12997]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:41:50 Ruckus-Unleashed meshd[12993]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:41:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:41:31 Ruckus-Unleashed kernel: Reached buffer limit
Sep 24 11:41:30 Ruckus-Unleashed syslog: bba: STAs from 2.4g to 5g.
Sep 24 11:41:30 Ruckus-Unleashed syslog: bba: sta-2g=7 sta-5g=2 perc=25 sta-2g-expect=2
Sep 24 11:41:20 Ruckus-Unleashed meshd[12936]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:41:20 Ruckus-Unleashed meshd[12932]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:41:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:40:50 Ruckus-Unleashed meshd[12836]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:40:50 Ruckus-Unleashed meshd[12832]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:40:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:40:20 Ruckus-Unleashed meshd[12776]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:40:20 Ruckus-Unleashed meshd[12772]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:40:16 Ruckus-Unleashed syslog: sqlited, sta count = 13
Sep 24 11:40:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:39:50 Ruckus-Unleashed meshd[12662]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:39:49 Ruckus-Unleashed meshd[12658]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:39:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:39:19 Ruckus-Unleashed meshd[12601]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:39:19 Ruckus-Unleashed meshd[12597]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:39:19 Ruckus-Unleashed kernel: ol_rc_update_handler: WARNING: handler called without transmit attempts
Sep 24 11:39:19 Ruckus-Unleashed kernel:  Keydata=0xa7 0x91 0xdf 0x19 0x2e 0x45 0x4 0xa0 0xb0 0x41 0xba 0xaa 0x99 0xa3 0x80 0xe2
Sep 24 11:39:19 Ruckus-Unleashed kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=4
Sep 24 11:39:19 Ruckus-Unleashed kernel: wmi_unified_vdev_install_key_send Setting Key for Macaddress:0x5cae8904a9dc
Sep 24 11:39:19 Ruckus-Unleashed kernel: net80211_tac_cfg_sta_set_param(): set station dc:a9:04:89:ae:5c vlan_id = 1
Sep 24 11:39:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:38:49 Ruckus-Unleashed meshd[12511]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:38:49 Ruckus-Unleashed meshd[12507]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:38:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:38:19 Ruckus-Unleashed meshd[12440]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:38:19 Ruckus-Unleashed meshd[12436]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:38:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:37:49 Ruckus-Unleashed meshd[12351]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:37:48 Ruckus-Unleashed meshd[12347]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:37:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:37:18 Ruckus-Unleashed meshd[12265]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:37:18 Ruckus-Unleashed meshd[12261]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:37:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:36:48 Ruckus-Unleashed meshd[12172]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:36:48 Ruckus-Unleashed meshd[12168]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:36:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:36:18 Ruckus-Unleashed meshd[12101]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:36:18 Ruckus-Unleashed meshd[12097]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:36:06 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:35:48 Ruckus-Unleashed meshd[12025]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:35:47 Ruckus-Unleashed meshd[12021]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:35:36 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Sep 24 11:35:17 Ruckus-Unleashed meshd[11951]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory
Sep 24 11:35:17 Ruckus-Unleashed meshd[11934]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory


Any help would be appreciated.  I like my 4 Ruckus R600's and would like to keep them.

1

0

syamantak_omer

Official Rep

 • 

733 Messages

 • 

11.4K Points

This has no information related to the client. Most of these logs are related to controller - AP functions.

Try pulling the AP support information which will give us more info.




Or add the doorbell's MAC address to Diagnostics and enable below debugs and open a case with support. Collect and provide the debug logs with client MAC when you see the issue next time.



Regards,
Syamantak Omer

Regards,

Syamantak Omer

Like

4 months ago

atma_tiwana

17 Messages

 • 

326 Points

4 months ago

Thank you Syamantak Omer. I've done that and downloaded the logs.

Where should I be looking and what for?  Is this something I can look at now or is it too late? Or do I have ito look immediatley when the problem happens again?

TIA

0

0

sanjay_kumar_gols5p74yq7mn

Official Rep

 • 

246 Messages

 • 

4.2K Points

4 months ago

Hi Atma,

If you set the debug logs enabled under the Diagnostics tab.
Then you can download the Debug logs and the AP Support logs as soon as the issue occurs.

You can open the AP Support logs and check for the client MAC address to see the disconnection events.
However, to open the debug logs, it can be done only from the TAC support.

So if you have these 2 logs downloaded at the time of issue, please open a support case so that the TAC can help you.

0

atma_tiwana

17 Messages

 • 

326 Points

4 months ago

So just an update.


Looking into it further I check the google nest service status and there was a issue on the same day.


So that could ecplain the nest camera but not happened to my wyze cams.


I'll now keep a closer eye on it.


Is there a way to get notified when a certain clients disconnect via the app ideally or any other method ?

My setup is router to switch, switch to 2 R600's and other wired devices. The router is the DHCP server.

I may change the setup to router to 1 r600, same r600 to switch, switch to 2nd r600. Leave DHCP server on router. That way all devices can be seen on the Ruckus network?

Finally is there a way to switch b&g off on the 2.4ghz. I have 2 wireless SSIDs. One for 5ghz only and the other for 2.4ghz.

6

0

syamantak_omer

Official Rep

 • 

733 Messages

 • 

11.4K Points

Hi Atmas

Is there a way to get notified when a certain clients disconnect via the app ideally or any other method ?
[Omer] Mark your client as Favorite.



My setup is router to switch, switch to 2 R600's and other wired devices. The router is the DHCP server.

I may change the setup to router to 1 r600, same r600 to switch, switch to 2nd r600. Leave DHCP server on router. That way all devices can be seen on the Ruckus network?
[Omer] I do NOT suggesting changing this. your current setup is fine.

Finally is there a way to switch b&g off on the 2.4ghz. I have 2 wireless SSIDs. One for 5ghz only and the other for 2.4ghz.
[Omer] 

Regards,

Syamantak Omer

Like

4 months ago

atma_tiwana

17 Messages

 • 

326 Points

Thanks Omar, I've marked my cameras as favourite so I can keep an eye on them.

Like

4 months ago

syamantak_omer

Official Rep

 • 

733 Messages

 • 

11.4K Points

I am not sure why but some part of my last comment is missing. Please refer below.

Finally is there a way to switch b&g off on the 2.4ghz. I have 2 wireless SSIDs. One for 5ghz only and the other for 2.4ghz.
[Omer] You can disable it, refer below screenshots. However, I do NOT suggest disabling it. Set the background scan internval from default 20 seconds to 600 or 1000 seconds.




Regards,
Syamantak Omer

Regards,

Syamantak Omer

Like

4 months ago

0

atma_tiwana

17 Messages

 • 

326 Points

Hi Omar,

Does that not just switch 2.4ghz off completely? I want 2.4ghz to work but on the n only and switch off the b&g protocols.

Regards

Like

4 months ago

0

syamantak_omer

Official Rep

 • 

733 Messages

 • 

11.4K Points

No, it will just disable the background scanning for 2.4GHz radio.

You can enable "n Only" mode on 2.4GHz radio from the AP group settings.



Regards,
Syamantak Omer

Regards,

Syamantak Omer

Like

4 months ago

Was this helpful?