04-26-2023 05:02 AM
I'm looking to add another 9120 to connect to my my 9120 running EWC. It seemed to join the EWC and it shows up as an online AP, but it shows as standby, like it's another standby EWC. It also looks as if it has both the AP and the EWC image.
I was looking through the documentation and it is not very clear on this. How do I configure this AP as a client to join the EWC I already have running? Does it need a firmware reload with just the AP firmware?
Thanks.
Solved! Go to Solution.
04-27-2023 07:30 AM
I think this FAQ will help you grasp the EWC concept better than just looking for guides.
04-28-2023 09:28 AM
So let me add my own summary:
EWC enabled APs will run EWC by default and elect primary and standby WLC automatically.
Non WLC APs are CAPWAP only.
You can "convert" EWC AP to CAPWAP only but me and others have found this to be a little unreliable. If the AP can't find WLC it re-activates the WLC and sometimes it seems to do it at random. If you want to ensure an AP cannot ever become an EWC WLC then you have to remove the WLC software and the only reliable way I've found to do that is follow the re-flashing process in
https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html
That resets it back to 8.10.130.0 CAPWAP image and you can then install the later CAPWAP image of your choice.
04-26-2023 05:21 AM
Hello,
Check this:
Step 1 |
Choose Wireless Settings > Access Points. The Access Points Administration window is displayed. You can only administer those APs that are associated to the controller. |
Step 2 |
Click the Edit icon adjacent to the AP you want to manage. |
Step 3 |
Under the General tab, you can edit the following AP parameters:
|
04-26-2023 06:51 AM
Hi Flavio,
On the 91xx access points, it's EWC, not Mobility Express. I don't have those options.
04-26-2023 07:29 AM
Ah sorry, didn't realized that. This is more like 9800.
You should be able to Configuration> Wireless> Access Point and change the AP role under "AP mode".
04-26-2023 05:33 AM
M.
04-26-2023 06:59 AM
marce1000,
I understand that, but for EWC, are client APs CAPWAP or do they require the AP EWC image, but without the AP controller image? Cisco documentation is not very clear on this.
Thanks.
04-26-2023 07:22 AM
- Just try the command mentioned in my previous link , you may need this first :
EWC#wireless ewc-ap ap shell username admin (change credential accordingly)
M.
04-26-2023 07:28 AM
Since it's associated with the primary EWC, the console does not allow commands. I get the following if I try to enter a command:
Standby console disabled
So it looks like anything I do must be done through the primary controller.
Thanks.
04-26-2023 07:43 AM
- Use this procedure to enable standby console from primary : (from config mode)
redundancy
mode sso
main-cpu
standby console enable
M.
04-26-2023 08:22 AM
Thanks for that.
What part of that guide and what command were you referring to?
04-26-2023 08:49 AM
- The needed commands are shown in my previous post , comes fro, searching in Cisco documentation ,
M;
04-26-2023 09:51 AM
No, they are only for converting from CAPWAP to EWC and back. I'm already on EWC with this access point, but it looks like another controller/AP instead of a EWC client AP. I need to know how to convert it to an EWC client AP.
Another issue is that I cannot get into config mode due to the "Standby console disabled" message.
Thanks.
04-27-2023 04:12 AM
So I think I have a better understanding of how this works. The ap1g7 image is a CAPWAP image that the EWC firmware comes with. For EWC, you install both the ap1g7 image and C9800 controller image and it becomes an an EWC access point with both a controller and usable AP resource.
When you set up the EWC and have it running, another EWC AP can join and its AP resource will be used. In the EWC configuration page, you can convert it to CAPWAP, and instead of having the C9800 image, it uses just the ap1g7 image and only an AP resource is available.
You can have multiple EWCs set up for redundancy, which explains why another EWC AP can join the running EWC and use it's AP resource.
So currently, since I don't want redundant EWCs, I set it to to use CAPWAP, and it seems to be working ok. For configuration, the extra AP running CAPWAP, joined to the EWC, has not accepted any clients (LED is still green) yet because it is physically close to the EWC AP. Once I relocate it farther away, I should have clients joining it?
Do I have this right? Does anyone else use EWC on this forum?
Thanks.
04-27-2023 04:31 AM
And to answer the original question, the EWC client is simply a CAPWAP AP or an EWC/AP using only the AP resource.
Again, do I have this right?
04-27-2023 04:33 AM
- Client AP = capwap only ,
M.
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