07-08-2019 01:21 PM
07-08-2019 07:05 PM
In that case, urging clients to 5GHz is likely a good step to take. It won't prevent the older clients from connecting to 2.4GHz, so as long as those aren't the majority of your client traffic then it still makes sense to use this setting. This guide has some other setting suggestions for dealing with interference in HiveManager Classic: https://thehivecommunity.aerohive.com/s/article/Radio-Frequency-Interference-Troubleshooting
07-08-2019 06:43 PM
Hi Sam,
thanks for replying. We are using Hive Manager Classic 8.2R2.
We are getting a lot of interference on our 2.4 GHz radio and less on 5Ghz which sometimes causes devices not being able to connect to the AP.
Our APs are designed for guests which can have old devices sometimes.
07-08-2019 04:35 PM
I wouldn't recommend implementing that setting if you have a lot of older client devices on the network as they'd work better with 2.4GHz instead. This also does technically slow the connection process down, but usually only by milliseconds. You'd also want to take client count in to consideration. Depending on what AP models you're using, each radio can host either 100 clients or 255 (depending on the chip set in the AP in use), so if you're going to exceed this number of clients then you may not want to try to urge them all to one radio.
Generally I recommend this setting when we see heavy interference on the 2.4GHz radio and less on the 5GHz radio. If you can tell me which HiveManager platform you're using, I can provide a guide that reviews how to check for interference on your network to see if this is needed. This guide will walk you through how to determine which HiveManager you are using, for reference: https://thehivecommunity.aerohive.com/s/article/Which-HiveManager-Platform-am-I-using