Issue flexconnect mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 09:39 AM
There are two modes in Flex-connect deployments and these modes are: connected mode and standalone mode.when APs lose connection to the Controller, the APs will run Standalone mode. However, some AP devices can join the controller, but others cannot. It has switched to EWC mode. Can someone please explain this to me and give me a solution ?
- Labels:
-
Catalyst Wireless Controllers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 09:45 AM
- Make sure that involved APs can do CAPWAP only and or if needed convert them as explained in :
https://www.cisco.com/c/en/us/support/docs/wireless/embedded-wireless-controller-on-catalyst-access-points/215303-embedded-wireless-controller-conversion.html#toc-hId-1622399608
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:20 AM - edited 05-25-2023 10:21 AM
yeah, i tried this way, which is to convert ewc mode to capwap mode. But command ap-type capwap sentence doesn't execute
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:47 AM
>....But command ap-type capwap sentence doesn't execute
You may need to switch to the underlying AP shell first as explained in
https://www.cisco.com/c/en/us/support/docs/wireless/embedded-wireless-controller-on-catalyst-access-points/215303-embedded-wireless-controller-conversion.html#toc-hId--865113225
M.
-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:23 AM
Hi
You are not wrong but this could be like this:
There are 2 types of image the AP can support: Capwap mode or standalone mode (now a days called mobility express /EWC)
In capwap mode, it can be as local mode or flexconnect mode.
In flexconnect mode it can be in connected mode or standalone mode. But this standalone mode can not be confused with the standalone mode x capwap mode.
If your AP is running a EWC, this means you need to convert it to capwap mode first. Then, after that you can join it to the WLC as local mode or flexconnect mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:30 AM
yeah, when ap loses connection to controller and i know that it is running ewc mode. I tried the ap-type capwap command, but it doesn't seem to exist. And
How do we know that the Ap has an ewc image when connecting to the controller?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2023 10:40 AM
Use the command show version
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-26-2023 06:46 AM
As @marce1000 already explained above the command must be executed from the AP CLI not the EWC CLI.
Use "wireless ewc-ap ap shell username <admin>" to access the AP CLI from the EWC CLI.
Note you may have configured a different AP username that is not admin so you will use whatever credentials you configured for the AP. The Cisco default will be admin and Cisco123
You can also disable EWC through option 43: https://www.cisco.com/c/en/us/products/collateral/wireless/embedded-wireless-controller-catalyst-access-points/white-paper-c11-743398.html#Conversion but note https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc75102
And to permanently remove the EWC software so that it cannot ever re-activate you should re-flash the AP using the procedure at https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html
Please click Helpful if this post helped you and Select as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's and TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's, Best Practices for 9800 WLC's and Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
