Cisco 9120 AXI - Downgrade from EWC to Lightweight

[PHaug]

Hi, 
One of my customers has 67 Cisco 9120AXI access points at one of their locations, and 32 of them are running running EWC image. 

There is also 19 Cisco 2700I access points on the location, but they are outside the scope of my question. 

All of theese access points are Connected to a central WLC (Cisco 9800 Cloud), serving multiple locations.

Whenever connectivity to the Central WLC is lost we have experienced that one or multiple 9120 access points have started operating as a EWC, and multiple of the other access points have joined this EWC. 

When the Central WLC is brought back up again, many of the access points are still connected to the EWC. We can perform a shutdown / no shutdown on the access point's switch port, but due to administrative distance one of the other 9120 access points will resume the role as EWC, prioritized over the 9800. 

Normally one can convert the EWC to Lightweight CAPWAP mode with the "ap-type capwap" command. 
The access points will still start operating in EWC mode whenever connection to Central WLC is lost, or upon a reboot. 

From what I have seen, one can install software for the 9120 AXI to operate as lightweight access point. 
https://www.cisco.com/c/en/us/support/wireless/catalyst-9120ax-series-access-points/series.html#~tab-downloads

I have seen a lot of guidelines for migrating from CAPWAP to EWC, but none the other way. 
How does one install this software from console access?

Will the Lightweight AP 15.3.3.-JPN1 software remove all of the 9120's EWC functionality, or is there some additional ROM-software which makes the 9120 capable operating as EWC?

[JPavonM]

This command on the AP running as EWC "ap-type capwap" should do the trick.

If it's not, the recovery method would do the trick.

[jagan.chowdam]

Converting EWC Back To Lightweight CAPWAP Mode

Login to the ap shell from the EWC. You should see an ap prompt which is the ap name not the EWC name.

If AP running in EWC mode needs to be converted back to lightweight capwap mode, it can be done via:

AP1#ap-type capwap
AP is the Master AP, system will need a reboot when ap type is changed to CAPWAP
. Do you want to proceed? (y/N) y

Important: This command will perform a complete factory reset of both AP and EWC partition. Make sure to backup existing EWC configuration before conversion.

CJ

/** Please rate all useful responses **/

[Rich R]

I wrote about observing the same behaviour on another thread recently.  As @JPavonM said the AP recovery re-flash method guarantees to remove the EWC capability from the AP completely.

Of course you can also issue the command to join the WLC to all the APs from the EWC AP.

You can also try the option 43 method.  I haven't tested this myself so not sure how effective it will be in the scenario you mention - you might still need to reboot the APs.

https://www.cisco.com/c/en/us/products/collateral/wireless/embedded-wireless-controller-catalyst-access-points/white-paper-c11-743398.html#Conversion

Converting EWCs to CAPWAP using option 43

DHCP option 43 is a vendor-specific option and is used for providing WLC IP addresses to the access point. Using option 43 with a specific subtype option, you can have the EWC convert to CAPWAP and join a WLC appliance or virtual controller. After the AP receives DHCP option 43 and subtype 0xF2 at bootup, the AP type will be converted to CAPWAP, and the AP will follow the regular joining process.

The DHCP configuration on the switch is shown below.

Switch(dhcp-config)#option 43 hex F2056464645801

[rlyle]

this command "ap-type capwap" doesn't work on the AP I'm having this trouble with, It's a 9120AXI-B and running this image file: 

Cisco IOS Software [Bengaluru], C9800-AP Software (C9800-AP-K9_IOSXE-UNIVERSALK9-M), Version 17.6.4, RELEASE SOFTWARE (fc1)

running into this error: WLC345D.A8D3.9A6C#ap-type capwap
^
% Invalid input detected at '^' marker.

[marce1000]

  @rlyle >...running into this error: WLC345D.A8D3.9A6C#ap-type capwap......
                Use the console of the AP and type the command  apciscoshell
                first , then try again , 

 M.

[rlyle]

Thanks Marce1000, I managed to get the AP back into lightweight mode but now running into thsi error:

No valid user found, please configure a valid user from Controller[*08/23/2024 17:08:57.0910] Discovery Response from 10.1.104.32
[*08/23/2024 17:08:57.0910] Discovery Response from 10.1.104.32

I'm trying to get it to connected to a 9800 and ran into these initial errors:

[*08/23/2024 16:59:25.9240] CAPWAP State: Discovery

[*08/23/2024 16:59:25.9270] Discovery Response from 10.1.104.32

[*08/23/2024 16:59:25.9270] Discovery response from MWAR 'DENwlcHA.32' running version 17.3.4.40 is rejected.

[*08/23/2024 16:59:25.9270] Failed to decode discovery response(status = 4).

[*08/23/2024 16:59:25.9270] CAPWAP SM handler: Failed to process message type 2 state 2.

[*08/23/2024 16:59:25.9270] Failed to handle capwap control message from controller - status 4

[*08/23/2024 16:59:25.9270] Failed to process unencrypted capwap packet 0x55793a0000 from 10.1.104.32

[*08/23/2024 16:59:25.9270] Failed to send capwap message 0 to the state machine. Packet already freed.

[*08/23/2024 16:59:25.9270] Discovery Response from 10.1.104.32

[*08/23/2024 16:59:25.9270] Discovery response from MWAR 'DENwlcHA.32' running version 17.3.4.40 is rejected.

[*08/23/2024 16:59:25.9270] Failed to decode discovery response(status = 4).

[*08/23/2024 16:59:25.9270] CAPWAP SM handler: Failed to process message type 2 state 2.

[*08/23/2024 16:59:25.9270] Failed to handle capwap control message from controller - status 4

[*08/23/2024 16:59:25.9270] Failed to process unencrypted capwap packet 0x55793d8000 from 10.1.104.32

[*08/23/2024 16:59:25.9270] Failed to send capwap message 0 to the state machine. Packet already freed.

[*08/23/2024 16:59:27.5310] Start: RPC thread 2592629632 created.

[marce1000]

 - @rlyle >...Discovery response from MWAR 'DENwlcHA.32' running version 17.3.4.40 is rejected.
                   Check if controller and software version are compatible with the AP according to :
                   https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

      +! This field notice could be applicable: https://www.cisco.com/c/en/us/support/docs/field-notices/724/fn72424.html

 M.

[Rich R]

17.3.4 is very old - update to currently supported release as per TAC recommended link below.

Make sure to read the upgrade path which applies in the release notes of the chosen release.  eg:
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-9/release-notes/rn-17-9-9800.html#Cisco_Concept.dita_59a2987f-2633-4630-8c7b-a8e8aecdeaf7
https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-12/release-notes/rn-17-12-9800.html#Cisco_Concept.dita_59a2987f-2633-4630-8c7b-a8e8aecdeaf7

What version of software is currently installed on the AP?