Clients keep getting Disassociated from AP = Reason 8

[jason_sparrow]

Well, the on-going saga continues.

I have an R600 that for some reason disassociates clients giving 'reason 8' that i found in the web UI log.

Could someone tell me what reason 8 is please?

Also, could someone maybe explain what the AP classes as 'interference'?

I am confused as to why the AP all of a sudden starts to SmartSelect to find a clearer 5G channel when there no other rogue 5G networks anywhere nearby.

Plus, the 2.4G network is perfectly stable and that has plenty of reason to hop about as there quite a fair few nearby networks.

[monnat_systems]

is your firmware on R500 and R600 same?

[jason_sparrow]

Yes they have the very latest standalone firmware

[bill_burns_6069]

Re: "interference"
FYI: I have just over 100 Ruckus APs of various models.
Some of them have already been hard-coded to a channel to prevent "interference" messages and channel hopping.
Others are in high_density_of_AP areas where a manual channel plan is not practical or in low_density_of_AP areas where you'd think a manual channel plan wouldn't be necessary.
In the past 14 days I've gotten 390 "interference" messages about APs changing channels.
That's about 27 channel changes a day, or about 1/3 the number of APs per day.
Fairly often, the messages will show a single AP switching from one channel to another, and then right back to the original channel.

I'm not on the latest firmware but this situation has persisted through all the firmware updates I've done.

This is pretty far from the original "reason 8" topic/title.
Maybe it's time to open a new question.

[jason_sparrow]

Thanks Bill,

Wow, thats a lot of hopping and that seems to be the same thing that is happening to me, albeit with only three AP's with standalone firmware!

I reverted back to the standalone, purely for the fact that that Unleashed does not facilitate the option to create separate 2.4 & 5 G networks with separate SSID & PW.

The official rep did ask why it would be wanted and i gave a reason, so i don't know if it will be included in the next update or not.

Its strange as the standalone firmware allows this to be configured (along with a few other manufacturers), so it was odd that it wasn't implemented in the Unleashed firmware.

Anyway, yes, this is way off topic now so ill post a new question.

🙂

[bill_burns_6069]

FYI: I don't think you're causing yourself any extra channel hopping problems by running standalone firmware. Current generations of ZD firmware don't seem to do anything to coordinate what channels get selected by what APs. I would assume that "unleashed" also does not coordinate these things. (at least, not beyond what's hard coded in your config)

I *am* surprised to hear that unleashed doesn't allow for separate SSIDs per radio, since this is the solution that's often recommended by support reps when there are roaming issues.

I believe the only thing that a ZD (or unleashed) gives you is a single point of management. (and maybe logging)
If you're not going to be overly bothered by having to update firmware and configs once for each of your (3) APs, you should be OK.