Skip to main content

7 Messages

 • 

150 Points

Sat, Dec 29, 2018 7:10 AM

R600 regular disconnects

I purchased a R600 for home use and I am experiencing regular disconnects that can only be resolved by a reboot of the device. Happens almost every day or every few days. Initially I thought it may have something to do with my internet providers router, but I just upgraded to the latest router. I'm not too familiar with this device, is there something I should be looking into?

Responses

69 Messages

 • 

1.1K Points

2 years ago

You should check the network connectivity during these interruptions first.
Such a problem look like not the Ruckus problem.
Secondary read logs оf APs & controller.
Sometimes this Encryption option: "802.11w MFP" should be disabled.
Software version should be updated.

7 Messages

 • 

150 Points

2 years ago

Alexey, 
Looking at the logs it looked like my son's XBox may have been causing the issue. Maybe the load from streaming was doing something. I've hard wired it to see if it resolves the issue. I looked at the logs and I keep seeing timeouts. Also, I couldn't find the 802.11w MFP to check if it was disabled. 
Here is a small snippet of the latest logs. I'm trying to find out what new-host-11 is.

Dec 31 20:39:39 new-host-11 daemon.err wsgclient[601]: registration:594 Failed to init socket! ret:124 url:https://RuckusController/wsg/ap

Dec 31 20:39:40 new-host-11 user.warn kernel: FWLOG: [59552084] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:40 new-host-11 user.warn kernel: FWLOG: [59552504] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:41 new-host-11 user.warn kernel: FWLOG: [59552818] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:41 new-host-11 user.warn kernel: FWLOG: [59553133] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:41 new-host-11 user.warn kernel: FWLOG: [59553448] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:42 new-host-11 user.warn kernel: FWLOG: [59553762] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:47 new-host-11 user.warn kernel: FWLOG: [59558900] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:47 new-host-11 user.warn kernel: FWLOG: [59559424] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:48 new-host-11 user.warn kernel: FWLOG: [59560788] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:49 new-host-11 user.warn kernel: FWLOG: [59561102] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:52 new-host-11 user.warn kernel: FWLOG: [59564248] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:52 new-host-11 user.warn kernel: FWLOG: [59564563] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:52 new-host-11 user.warn kernel: FWLOG: [59564877] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:53 new-host-11 user.warn kernel: FWLOG: [59565192] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:53 new-host-11 user.warn kernel: FWLOG: [59565506] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:54 new-host-11 user.warn kernel: FWLOG: [59566240] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:54 new-host-11 user.warn kernel: FWLOG: [59566555] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:55 new-host-11 user.warn kernel: FWLOG: [59567184] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:55 new-host-11 user.warn kernel: FWLOG: [59567499] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:55 new-host-11 user.warn kernel: FWLOG: [59567813] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:56 new-host-11 user.warn kernel: FWLOG: [59568128] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:56 new-host-11 user.warn kernel: FWLOG: [59568442] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:56 new-host-11 user.warn kernel: FWLOG: [59568757] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:57 new-host-11 user.warn kernel: FWLOG: [59569176] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:57 new-host-11 user.warn kernel: FWLOG: [59569491] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:57 new-host-11 user.warn kernel: FWLOG: [59570015] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:58 new-host-11 user.warn kernel: FWLOG: [59570539] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:58 new-host-11 user.warn kernel: FWLOG: [59570854] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:59 new-host-11 user.warn kernel: FWLOG: [59571169] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:59 new-host-11 user.warn kernel: FWLOG: [59571483] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:59 new-host-11 user.warn kernel: FWLOG: [59571798] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:39:59 new-host-11 user.warn kernel: FWLOG: [59572112] WAL_DBGID_DEV_TX_TIMEOUT ( 0x9 )

Dec 31 20:40:00 new-host-11 daemon.err wsgclient[601]: crSocketConn:70 Connection Timeout!

Dec 31 20:40:00 new-host-11 daemon.err wsgclient[601]: crSocketInit:243 crSocketConn failed ret = 125

36 Messages

 • 

868 Points

2 years ago

What OS are you running on this? Unleashed? ZoneDirector? Smartzone?
Are you running the standalone firmware? 

If using standalone, I suggest downloading the Unleashed firmware for your AP, more options, more feature sets, more robust performance vs standalone. 

7 Messages

 • 

150 Points

2 years ago

I'm not all that familiar with the device, but I can tell you I'm running software version 104.0.0.0.1347
What firmware is compatible with the R600?
Can I use one of these updates?
Ruckus Unleashed AP 200.6.10.1.312 (GA Refresh2) Software for R60
ZoneFlex Solo Access Point 110.0.0.0.675 (GA) Software Release (R600)
Ruckus Unleashed AP 200.6.10.1.308 (GA) Software for R600
Brand User

2.6K Messages

 • 

44.8K Points

I could not find any clearly matching bug for the output, and would recommend the 110.0 Solo AP image upgrade.
https://support.ruckuswireless.com/software/1726-zoneflex-solo-access-point-110-0-0-0-675-ga-softwar...

7 Messages

 • 

150 Points

Thank you Michael. I actually installed The Ruckus Unleashed (latest) last night as I was getting desperate. Should I keep it or revert and install the zoneflex solo you recommended?
Brand User

2.6K Messages

 • 

44.8K Points

Not a worry, and more flexible. You can add additional R600s with Unleashed, and they will Mesh to extend coverage.Unleashed is based on ZoneDirector code, and a very popular platform.  Let us know how your testing/experience goes.

7 Messages

 • 

150 Points

Thank you again Michael ( and everyone else who chimed in). I'll monitor it closely and see if there are any other hiccups. 
Hopefully this resolves the dropped connections.

7 Messages

 • 

150 Points

2 years ago

Update: As of right now, I haven't noticed any dropped connections, at least not like I was before. I do however receive notifications of the following:

2019/01/07  00:18:25AP Has JoinedHighAP[[email protected]:b0:52:21:8d:00] joins with uptime [259224] s and last disconnected reason [Heartbeat Loss]
2019/01/06  00:18:07AP Has JoinedHighAP[[email protected]:b0:52:21:8d:00] joins with uptime [172807] s and last disconnected reason [Heartbeat Loss
2019/01/05  00:18:19AP Has JoinedHighAP[[email protected]:b0:52:21:8d:00] joins with uptime [86420] s and last disconnected reason [Heartbeat Loss]

This appears on a consistent basis. Not sure if this is common or if there is something I should be looking at.
Brand User

2.6K Messages

 • 

44.8K Points

APs share "heartbeats" to communicate that they are active.  This msg indicates some possible network connectivity issue between this AP and others/controller.  Does anything usually occur on your network at this time, ie server backups/regular downloads/file transfers, etc?

7 Messages

 • 

150 Points

Michael, nothing that I know of occurs at that time. This is a home network and I don't have anything running at any specific time.  As of right now, the last time this happened was on Jan. 7th. Odd how it comes and goes. 

388 Messages

 • 

5.9K Points

2 years ago

When I had met this msg, and TAC tell me "WAL_DBGID_DEV_TX_TIMEOUT" is happend when there is very congested.

That means because there is very congested, AP don't transmit any packet.

As a result I had found there is WIPS solution.

Atfer we turned off the WIPS, a condition was very very better.

Try it.