03-12-2023 03:35 AM
Hello,
I have a setup that consists of 4 9105AXI aps and one 9115AXI ap.
I have upgraded all APs to version 17.6.4, and was able to join all 9105 APs to the EWC on the 9115, except for the 9115 itself, that did not show between the APs.
any idea?
Thx
Solved! Go to Solution.
03-12-2023 04:11 PM - edited 03-12-2023 04:14 PM
So there are a few possibilities here. To be sure you need to connect to the AP (on the EWC) and see what it shows in the log:
wireless ewc-ap ap shell username admin
Note the username (admin in example above) will be the one you set for the AP in the initial setup and likewise for the password.
Not sure if "show log" will show you anything useful - might need to do "term mon".
Anyway I'm going to guess as to possible cause: how are your APs getting their IP addresses? Are you using static IPs? If so did you configure an IP on the EWC AP (it needs its own IP separate from the EWC WLC)? This is why the recommended way is to use DHCP. As soon as the AP has an IP address it should join the EWC WLC immediately.
03-12-2023 03:50 AM
>...except for the 9115 itself,
- Check the EWC logs just after boot or capture the boot process , examine it , perhaps you can obtain additional info's,
M.
03-14-2023 04:08 AM
My proble was solved, and after restarting the AP, i cant access the EWC cli, when i connect the console cable to the AP, i cannot reach the Configure Terminal.
I tried to press the mode button for reset, and tried to convert it to capwap then back to EWC with no luck.
Now i need to change the EWC ip address, and i cant reach the CLI of the EWC
any idea
03-12-2023 05:13 AM
i would check the config :
I would also connect the console cable and what is failing.
Some new AP need newer code for the AP to work.
I have upgraded all APs to version 17.6.4 <-- is this broken after upgrade ?
03-12-2023 04:11 PM - edited 03-12-2023 04:14 PM
So there are a few possibilities here. To be sure you need to connect to the AP (on the EWC) and see what it shows in the log:
wireless ewc-ap ap shell username admin
Note the username (admin in example above) will be the one you set for the AP in the initial setup and likewise for the password.
Not sure if "show log" will show you anything useful - might need to do "term mon".
Anyway I'm going to guess as to possible cause: how are your APs getting their IP addresses? Are you using static IPs? If so did you configure an IP on the EWC AP (it needs its own IP separate from the EWC WLC)? This is why the recommended way is to use DHCP. As soon as the AP has an IP address it should join the EWC WLC immediately.
03-14-2023 04:01 AM
My proble was solved, and after restarting the AP, i cant access the EWC cli, when i connect the console cable to the AP, i cannot reach the Configure Terminal.
I tried to press the mode button for reset, and tried to convert it to capwap then back to EWC with no luck.
Now i need to change the EWC ip address, and i cant reach the CLI of the EWC
03-14-2023 04:39 AM
>...when i connect the console cable to the AP, i cannot reach the Configure Terminal.
- Post screenshot as to where you get stuck (or console log)
M.
03-14-2023 04:55 AM
And if all else fails use the recovery process documented here:
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html
to re-flash the AP back to factory CAPWAP default then upgrade and configure as required.
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