Wireless Controller & Access Point Firmware Upgrade

Why wireless upgrades need a different validation standard

A wireless upgrade can complete cleanly by every measure the controller reports — all access points joined, all radios up, no alarms — and still be a failure from the users' point of view. Clients that will not associate on one band, roaming that has become sticky, throughput that has dropped on a specific device type, or a captive portal that no longer renders on one mobile OS are all outcomes that a controller dashboard shows as healthy. Wireless validation therefore has to be done from the client side.

The upgrade itself has a dependency other device types do not carry: access points run firmware supplied by the controller, so controller and AP versions move together. That means the compatibility matrix matters — not every AP model is supported on every controller version, and upgrading a controller to a version that has dropped support for an older AP model will strand those APs. Establishing which AP models are in the estate, and confirming every one of them is supported on the target version, is the single most important pre-check in a wireless upgrade.

Access point download and reboot also takes time proportional to the estate. A few hundred APs pulling an image across WAN links to branch sites is a materially different exercise from thirty APs on a campus LAN, and window planning has to reflect that.

Wireless platforms we support

Post-upgrade wireless validation

• AP join state — every access point rejoined and running the expected firmware version, with any that failed to join identified and addressed rather than left as a count discrepancy.
• Client association — real clients tested on each SSID across both bands, including the device types your users actually run rather than a single test laptop.
• Authentication — 802.1X, PSK and captive portal flows verified end to end, including RADIUS reachability and certificate validity.
• Roaming — client roaming between APs tested on the floor, with attention to fast-transition behaviour if it is in use.
• Throughput — sample throughput measured against the pre-change baseline at representative locations.
• RF configuration — channel and power settings intact, since automatic RF management occasionally re-converges differently after a controller version change.

Where a site survey belongs in the picture

If wireless performance complaints predate the upgrade, a firmware upgrade will not resolve them — coverage and capacity problems are design problems, not software problems. ENCSE runs a substantial Ekahau-certified wireless survey practice alongside this lifecycle work, and where an assessment suggests the underlying issue is RF design rather than software currency, we will tell you that rather than sell you an upgrade that cannot fix it.

Frequently asked questions

Will Wi-Fi be down during a controller upgrade?

Yes, for the duration of the controller reboot and the subsequent AP rejoin cycle, unless the controllers are deployed in a redundant pair that supports staged upgrade. Access points typically take several minutes to download firmware, reboot and rejoin, and that window scales with estate size and WAN bandwidth to remote sites. We size the expected outage during planning.

Do all access points need to be upgraded together?

AP firmware is supplied by the controller, so in a controller-based architecture the APs move with it. What can be staged is which sites or controller groups you upgrade in which window. For large estates we normally recommend a phased rollout by site rather than a single estate-wide change.

What if my older APs are not supported on the new controller version?

Then upgrading the controller to that version would strand them, and we would flag this before the work is scheduled rather than after. The options are to select a target version that still supports the installed AP models, or to plan an AP refresh alongside the upgrade. This is exactly the kind of finding the assessment exists to surface early.

Can you validate wireless performance after the upgrade?

Yes. Beyond controller-side checks we test from the client side — association, authentication, roaming and throughput at representative locations. For estates where wireless performance is business-critical, a post-upgrade validation survey using Ekahau tooling can be scoped as part of the engagement.

Do you upgrade cloud-managed wireless?

Cloud-managed platforms handle firmware differently, with the vendor controlling release trains and the customer choosing when to take them within a supported window. We support planning and executing those scheduled upgrades, including compatibility checking and post-change validation, even though the mechanics differ from an on-premises controller.

Related services

• Network Device Firmware Upgrade
• Enterprise Wireless Solution
• Wireless Site Survey
• Network Device Health Check
• Request an Upgrade Assessment