05-01-2025 09:13 AM
I have 18 Cisco 140ac access points in one of my schools. I am having problems with some of the APs unjoining and then rejoining. When this happens, the unjoined AP shows as "Mesh Extender", then that goes away when it rejoins. I don't have Mesh Extenders set for any of the APs. I looked at the logs and found some errors, and found some suggestions on this forum in this post:
https://community.cisco.com/t5/wireless/cbw140ac-un-joins-every-few-minutes/td-p/4664934
Another post suggest checking each AP:
However, when I log in to the Management IP address, there is no "Action" Button where I can edit each AP. Tried Chrome and Edge, same issue, so don't think it is a browser issue.
Note: Originally AP01 was primary AP, I gave it a management address which I use to access the APs. However, AP14 shows as primary in the AP list, but a check on "Primary AP Information" still shows AP01 (all APs are listed as Primary Capable). I am accessing via browser, as I am using VPN to the school network (ciscobusiness.cisco connection won't work from my office). Firmware version 10.6.1.0., there are later versions available.
Would accessing via ciscobusiness.cisco make a difference and show me the Action button? I need to get the edit action working so I can see what is going on. I will be going to the school next week (it is a 1.5 hour trip each way, so I can't just go check it quickly).
Thanks in advance for any ideas or suggestions.
Solved! Go to Solution.
05-08-2025 01:39 PM
UPDATE: I have all APs now running on the latest firmware, 10.10.1.0. This seems to have fixed the unjoining issue I have been having with some of the units. I tried to upgrade from 10.6 directly to 10.10, but it didn't work. The Preferred Primary AP, AP01, was not the Primary, rather another AP, AP14 had that role (all my APs are Primary Capable). I changed the Primary to AP01 (which is also the Master AP), and tried to upgrade to 10.7.1.0. That worked, so I did incremental upgrades from 10.7 to 10.8, then 10.8 to 10.9, then 10.9 to 10.10. All upgrades worked fine, and all of the APs are running without interruption. And I set the Master AP to auto check for upgrades (it wasn't working at 10.6, but that is a known problem). I shouldn't encounter this issue again.
I am going to check my two other schools with these APs and do upgrades as necessary. And I will make note to check these installations from time to time as well.
RIch R, thanks again for your assistance.
05-02-2025 06:30 AM - edited 05-02-2025 08:52 AM
Chrome & Edge are both based on the Chromium browser engine so not much difference so try Firefox including older versions.
Updating to latest available software version is essential to ensure you have the fixes for any known bugs that have been fixed.
Shortcuts like ciscobusiness.cisco will only work locally when you are actually connected to the device because they are designed to intercept the request and redirect it to the device. I wouldn't expect it to make any difference but you won't know until you try.
05-05-2025 06:53 AM
Rich R, thank you for your quick reply. Turns out I was trying to edit in the wrong area of the web gui, the Action button is where it should be (I haven't had to look at these APs for quite a while, and my brain failed me once again). I will upgrade the firmware to see if this helps with an unjoining issue I am having with some of the APs.
Firmware is currently 10.6.1.0, there are 10.7, 10.8, 10.9, 10.10 versions available. Not sure if I can go from 6 to 10 though, would you have any idea if I could? I can do each one separately otherwise.
Again, thanks for your help, it is appreciated.
05-05-2025 02:25 PM
Always best to refer to the release notes which should mention any caveats or warnings:
I don't see any restrictions on upgrading there.
05-06-2025 08:41 AM
Rich R, yes I don't see any notice on the release notes about having to do incremental upgrades. I will back up my configuration and try the 10.10 upgrade when I am at the school tomorrow. Thanks again for the response.
I will post my results here as well for any other users.
05-08-2025 01:39 PM
UPDATE: I have all APs now running on the latest firmware, 10.10.1.0. This seems to have fixed the unjoining issue I have been having with some of the units. I tried to upgrade from 10.6 directly to 10.10, but it didn't work. The Preferred Primary AP, AP01, was not the Primary, rather another AP, AP14 had that role (all my APs are Primary Capable). I changed the Primary to AP01 (which is also the Master AP), and tried to upgrade to 10.7.1.0. That worked, so I did incremental upgrades from 10.7 to 10.8, then 10.8 to 10.9, then 10.9 to 10.10. All upgrades worked fine, and all of the APs are running without interruption. And I set the Master AP to auto check for upgrades (it wasn't working at 10.6, but that is a known problem). I shouldn't encounter this issue again.
I am going to check my two other schools with these APs and do upgrades as necessary. And I will make note to check these installations from time to time as well.
RIch R, thanks again for your assistance.
05-08-2025 02:15 PM
You're welcome - glad to hear it seems to have resolved the issue and fingers crossed .... <smile>
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide