It is the same as the first deployment where we moved to a company that had a wireless solution in their warehouse. In warehouses, you need to accommodate for heat. They had a lot of problems with access points dying and communicating, and they couldn't operate in the heat. The solution was to buy access points capable of being deployed outside, which have better shielding and are designed to handle higher and lower temperatures. We deployed those in the warehouse and that fixed all the communication problems. The need was to fix a warehouse's bad Wi-Fi. In the process, I replaced all of the Wi-Fi. The building consists of 75% warehouse and 25% office. I replaced everything and put outside access points only in the warehouse. On the office side, we put the normal conventional Ruckus Wireless WAN access points.
In Cisco, there is a configuration where it automatically switches from the 2.4 GHz to 5.2 GHz frequency. But with Ruckus, usually, we need to manually define whether we want to use the 2.4 GHz or 5.2 GHz. Another point is that its penetration power is low when we are using it in any location with more walls, as the signal strength diminishes. So, the signal strength and the penetration power of the signal should be improved. It is not like Cisco. We are using Cisco APs also, but Cisco APs perform better when we compare them with Ruckus. In future releases, I would like to see automatic switching between 2.4 GHz and 5.2 GHz frequencies. We should not have to set it manually. It should automatically change its frequency based on the load. For example, if the number of users increases, then its frequency should change automatically, switching to the less congested band.
