The Cisco 5520 Series Wireless LAN Controller is a highly scalable, service-rich, resilient, and flexible platform that is ideal for medium-sized to large enterprise and campus deployments.
N/A
Cisco 8540 Wireless Controller
Score 7.9 out of 10
N/A
The Cisco 8540 Wireless Controller is a highly scalable, service-rich, resilient, and flexible platform. It provides centralized control, management, and troubleshooting for high-scale deployments in service provide, enterprise, and large campus deployments.
The Cisco 8540 Wireless Controller is an upgrade from the 5520. It has only one RU appliance when compared to the Cisco 8540 Wireless Controller, which has two. The Cisco 8540 Wireless Controller connects to more access points and is a higher speed network than the 5520.
At this point the Cisco 5520 Wireless Controllers are end of life as a Cisco product, so I would not recommend them to anyone looking to purchase a wireless controller for an enterprise. However, many people are still using these, and they do work reliably, even if they are a bit long in the tooth now.
[Cisco 8540 Wireless Controller's] software quality has been shed in recent years. The only problem I have with it is its inability to work with older Cisco Access Points. However, that's to be expected for any deployment. While the controller's UI works well, some areas could be improved. API integrations lack flexibility. [I feel] it's time for policy redesign. It can be a little difficult to determine coding quality.
The GUI on the Cisco 8540 WLC is much better designed than other Cisco products. Its easy to navigate between the different settings to find what is needed.
The AP groups allows touching multiple APs at one time.
It also allows us to create standard SSIDs that can be used at all sites that connect back to it, this saves a lot of time instead of hitting each site with a local controller.
We have had some issues with access points losing their configurations and going offline. This is not a common issue and we are not entirely certain if it is a fault of the controller or the individual APs. That said, the controller does not appear to retain the knowledge of the offline AP which can be a management headache.
Code quality is a bit hit and miss. This will be great for a while, then things will be bad for a while, then we'll do it again. The UI of the controller works, but could do with a refresh, and I would like to see some improvement on layout and organization.
The constant code/firmware upgrades and the QA of new code could be better.
Maybe the compatibility with old Cisco Access Points could be improved, but it's normal in all kinds of deployments.
This equipment from Cisco has been dependable and we are able to easily continue to add access points or make changes easily to the Wi-Fi password settings.
We have been operating this equipment for a number of years and it does not give us any issues.
Overall the usability is ok. The centralized management reduces complexibility and offers bulk features like adding access points to specific groups which automatically applies linked configurations.
On the other hand the GUI is very outdated and some features are not displayed correctly on new browsers. Also automation possibilities are very limited compared to the new 9800 series controller.
Very feature rich, easy enough for beginners to understand layout and initial setup. Need a good training (online, Cisco Leaning Network, etc.) to fully understand all features and product capabilities. Strict power requirements for APs are only major drawback for our specific implementation.
Cisco support is always ready to support and engage in any problem or issue. Starting from the implementation support, troubleshooting any software issue or hardware. Their engineers are engaging whenever we ask for support, keep following up with us, and troubleshoot any problem till we find a solution and be satisfied [with] the service.
Just take your time when setting up the HA pairs as those can be tricky. Also take your time setting up AP groups and make sure they are on all the SSIDs you need to be on.
Cisco Identity Services Engine is well integrated on Cisco 5520 Wireless Controller because the WLC supports a lot of authentication methods and security protocols (such as PEAP, EAP-TLS, Captive Portal redirect). They perform very well with ISE. Cisco ISE is able to manage centrally the AAA sessions from all the WLCs keeping a central point of management for wireless infrastructure.
We have [done] some work before with the Cisco 3504 product, but the more recent Cisco 8540 Wireless Controller provides a wider range of capabilities for managing the wireless network and each individual device [and] also being able to handle more users. Unfortunately, we didn't test and deploy equivalent products from other concurrent companies.
Implementing the [Cisco] 5520 [Wireless] Controllers offered us a huge improvement in administrative time over our previous Cisco 3850 deployment. Being able to see all of our APs on a single controller as well as centrally manage them is a great benefit. This also removed the need to deploy specific equipment in different IDFs throughout our Industrial locations and instead only requiring switches with Power Over Ethernet (POE) capability.
Wireless performance has improved with the deployment of our 5520s, which allows our plant operators to do their jobs more efficiently while on the move.
Having three Cisco 5520 Wireless Controllers provides tertiary redundancy for our wireless networks. The solution is elegantly simple. Preventing downtime is, obviously, a profound part of our supply chain capabilities.
The Cisco 8540 Wireless Controller allows you to reduce your hardware footprint of wireless controllers deployed in your environment. Instead of having a controller per site deployed, you can have a couple of 8540 controllers in your data center that can handle up 6000 Access Points.
Some of the savings on hardware cost is offset by the cost of redundant WAN circuits. The access points will continue to function when connectivity to the Cisco 8540 Wireless Controller is unreachable, but it will not allow any new connections in that wireless environment.
