AP 9130 AXI-e in EWC

[Kasper Elsborg]

Hi I have an ap 9130 I want to run an wlc in EWC mode. I followed this guide 

However when I cmd ap-type ewc-ap tftp://192.168.0.82/ap1g6a tftp://192.168.0.82/C9800-AP-iosxe-wlc.bin 

Image upgrade not needed, changing AP Type to EWC-AP

a show version 

AP Running Image : 17.15.0.83
Primary Boot Image : 17.15.0.83
Backup Boot Image : 17.15.1.6
Primary Boot Image Hash: 9bfadbd55fb8aadfe02a49e1c0dc4472ee411883a33545f4c5b0ac3
404829db112b0e80a93f0c594bc44cf8920c7a8b3be2a26c4ae9d0a0d022258ad44195a21
Backup Boot Image Hash: 9850b7ecf3943d0aaa313fbed521acb67631cbb0304dfede3230e95
4c871a7d23e85d349f130331c518ab13bd19db0f82ef77bfc4b17a8a2ef8689a800fb78f0
AP Image type : EWC-AP IMAGE
AP Configuration : EWC-AP CAPABLE

However I cannot enter a conf t. it looks like the ewc is not starting up.

I've tried 

archive download-sw /rel capwap tftp://192.168.0.82/ap1g6a

archive download-sw ewc-ap tftp://192.168.0.82/C9800-AP-iosxe-wlc.bin

to triger an download and its transfering.

last output of reload are.

[*07/13/2024 04:02:24.3486] chatter: tohost_virtual :: ToHost: device 'virtual' went down
Sat Jul 13 04:02:25 UTC 2024 Starting Controller...Please wait for a few minutes ....
Sat Jul 13 04:02:25 UTC 2024 Created controller running file: Sat Jul 13 04:02:25 UTC 2024
Sat Jul 13 04:02:25 UTC 2024 IOSd monitor 9110 started
Sat Jul 13 04:02:25 UTC 2024 fromdev_wired0 count = 247
Sat Jul 13 04:02:25 UTC 2024 Deleted controller running file: Sat Jul 13 04:02:25 UTC 2024
Sat Jul 13 04:02:25 UTC 2024 Container is not running.
Sat Jul 13 04:02:25 UTC 2024 Unmount system level file systems
Sat Jul 13 04:02:25 UTC 2024 Clean up, may take a while, please be patient...
Sat Jul 13 04:02:25 UTC 2024 Container cleanup finished

Any Ideas?

[Saikat Nandy]

This looks quite odd to me. Would you mind to move the AP back to CAPWAP first and then try 17.12.5 EWC image once.

[Kasper Elsborg]

@Saikat Nandy I still dont have a conf t cmd

ap-type capwap

!reload!
!
!
!

ap-type capwap

!reload!
!
!
!

[*08/11/2024 23:00:43.5782] CAPWAP State: Discovery
[*08/11/2024 23:00:43.6164] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

AP10#c[*08/11/2024 23:00:54.5772] ipv6 gw config loop in discovery timer expiry
onf t
^
% Invalid input detected at '^' marker.
AP10#
AP10#[*08/11/2024 23:00:56.5774] ipv6 gw config loop in discovery timer expiry

AP10#
AP10#[*08/11/2024 23:00:58.5776] ipv6 gw config loop in discovery timer expiry
conf t
^
% Invalid input detected at '^' marker.
[*08/11/2024 23:01:00.5779] ipv6 gw config loop in discovery timer expiry
AP10#[*08/11/2024 23:01:02.5781] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:01:04.5788] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:06.5790] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:08.5792] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:10.5794] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:12.5796] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:13.5890]
[*08/11/2024 23:01:13.5890] CAPWAP State: Discovery
[*08/11/2024 23:01:13.6300] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*08/11/2024 23:01:24.5921] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:01:26.5923] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:01:28.5926] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:01:30.5928] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:01:32.5930] ipv6 gw config loop in discovery timer expiry

AP10#
AP10#
AP10#sho[*08/11/2024 23:01:40.1505] PNP:Server not reachable, Start CAPWAP Discovery
[*08/11/2024 23:01:40.1505]
[*08/11/2024 23:01:40.1505] Going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*08/11/2024 23:01:40.1505]
[*08/11/2024 23:01:40.1507] Restarting CAPWAP State Machine.
[*08/11/2024 23:01:40.1509] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.1509]
[*08/11/2024 23:01:40.1509] OOBImageDnld: capwap OOBImageDownloadTimer failed to stop
[*08/11/2024 23:01:40.1509] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.1509]
[*08/11/2024 23:01:40.1509] OOBImageDnld: capwap wtpStopOOBImageDownloadProgressTimer failed to stop
[*08/11/2024 23:01:40.1969] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.1969]
[*08/11/2024 23:01:40.1969] OOBImageDnld: capwap OOBImageDownloadTimer failed to stop
[*08/11/2024 23:01:40.1969] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.1969]
[*08/11/2024 23:01:40.1969] OOBImageDnld: capwap wtpStopOOBImageDownloadProgressTimer failed to stop
[*08/11/2024 23:01:40.2392]
[*08/11/2024 23:01:40.2392] CAPWAP StateŸ"Q1MTeardown
[*08/11/2024 23:01:40.3233] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.3233]
[*08/11/2024 23:01:40.3233] OOBImageDnld: capwap OOBImageDownloadTimer failed to stop
[*08/11/2024 23:01:40.3233] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:40.3233]
[*08/11/2024 23:01:40.3233] OOBImageDnld: capwap wtpStopOOBImageDownloadProgressTimer failed to stop
[*08/11/2024 23:01:40.4651] status 'upgrade.sh: Script called with args:[CANCEL]'
[*08/11/2024 23:01:40.5128] do CANCEL, part1 is active part
[*08/11/2024 23:01:40.5584] status 'upgrade.sh: Cleanup tmp files ...'
v[*08/11/2024 23:01:40.5995] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*08/11/2024 23:01:40.6001] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*08/11/2024 23:01:40.6001] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
er[*08/11/2024 23:01:45.2227] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:45.2227]
[*08/11/2024 23:01:45.2227] OOBImageDnld: capwap OOBImageDownloadTimer failed to stop
[*08/11/2024 23:01:45.2227] Failed to stop timer, NULL timer handle
[*08/11/2024 23:01:45.2227]
[*08/11/2024 23:01:45.2228] OOBImageDnld: capwap wtpStopOOBImageDownloadProgressTimer failed to stop
[*08/11/2024 23:01:45.2477] dtls_queue_first: Nothing to extract!
[*08/11/2024 23:01:45.2477]
[*08/11/2024 23:01:46.2482] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:48.2484] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:50.2486] ipv6 gw config loop in Ac discovery

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to
restrictions as set forth in subparagraph (c) of the Commercial
Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

cisco C9130AXI-E ARMv8 Processor rev 4 (v8l) with 1819300/1119768K bytes of memo
ry.
Processor board ID xxx
AP Running Image : 17.15.1.6
Primary Boot Image : 17.15.1.6
Backup Boot Image : 17.15.0.83
Primary Boot Image Hash: 9850b7ecf3943d0aaa313fbed521acb67631cbb0304dfede3230e95
4c871a7d23e85d349f130331c518ab13bd19db0f82ef77bfc4b17a8a2ef8689a800fb78f0
Backup Boot Image Hash: 9bfadbd55fb8aadfe02a49e1c0dc4472ee411883a33545f4c5b0ac3
404829db112b0e80a93f0c594bc44cf8920c7a8b3be2a26c4ae9d0a0d022258ad44195a21
AP Image type : EWC-AP IMAGE
AP Configuration : NOT ME OR EWC-AP CAPABLE
1 Multigigabit Ethernet interfaces
2 802.11 Radios
1 Bluetooth Low Energy Radio (2652R1)
Radio FW version : QC_IMAGE_VERSION_STRING=WLAN.HK.2.9.r5-00063-QCAHKSWPL_SILICO
NZ-1
NSS FW version : NSS.FW.12.2-149-HK.E_custC

Base ethernet MAC Address : 0C:75:BD:B2:14:28
Part Number : 32-40127-01
PCA Assembly Number : 000-00000-00
PCA Revision Number : A0
PCB Serial Number : xxxx
Top Assembly Part Number : 800-105663-01
Top Assembly Serial Number : xxx
Top Revision Number : A0
Product/Model Number : C9130AXI-E
Cloud ID : Q2ZZ-6VNT-6BNX

AP10#[*08/11/2024 23:01:54.2490] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:01:55.2585]
[*08/11/2024 23:01:55.2585] CAPWAP State: Discovery
[*08/11/2024 23:01:55.3021] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*08/11/2024 23:02:06.2060] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:02:08.2062] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:02:10.2065] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:02:12.2067] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:02:14.2069] ipv6 gw config loop in discovery timer expiry
[*08/11/2024 23:02:16.2076] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:02:18.2078] ipv6 gw config loop in Ac discovery
[*08/11/2024 23:02:20.2080] ipv6 gw config loop in Ac discovery
AP10#conf t
^
% Invalid input detected at '^' marker.

[Saikat Nandy]

Since you have done 'ap-type capwap', it has changed to capwap mode - 

AP Image type : EWC-AP IMAGE
AP Configuration : NOT ME OR EWC-AP CAPABLE

In capwap mode you won't be able to go to config t.

[Rich R]

Wow - long discussion!  But @Saikat Nandy has already suggested part of what I would suggest.  ME and EWC can both be tricky and troublesome like this so I always recommend going back to CAPWAP mode then converting.

While the AP is in CAPWAP mode install a different version CAPWAP image - eg 17.12.1 
https://software.cisco.com/download/home/286323627/type/286288051/release/15.3.3-JPQ using regular archive command
Then upgrade it to another different version eg 17.12.5 
https://software.cisco.com/download/home/286323627/type/286288051/release/15.3.3-JPQ4 the same way - at which point you have a regular CAPWAP image in both boot partitions.
Then try to convert to your target EWC image eg https://software.cisco.com/download/home/286323627/type/286323077/release/17.15.3 using the ap-type command.
If you still get the error swap to the other partition and try again.

If that still doesn't work then the radical option (which has always worked for me when stuck like this) is to completely re-write the AP flash (which removes all traces of EWC from 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
Take note of https://community.cisco.com/t5/wireless/cisco-c9130axi-e-how-to-recover/m-p/5285043/highlight/true#M282746 - the guide document still hasn't been corrected!
That restores the AP to 8.10.130.0 CAPWAP image so from that point you need multiple upgrades (using only CAPWAP images) to get back up to 17.15 EWC
8.10.130.0 -> 8.10.196.0 [15.3(3)JK11] -> 17.9.7 [15.3(3)JPN6] -> convert to 17.15.3 EWC
If you don't go through the steps you end up with incorrect partition sizes which cause problems with installing software.

* see Impossible to delete the eWC controller image from AP once installed

[marce1000 · Accepted solution]

 - @Rich R   - All of that walk through the dark forests being well explained and the fact that the EWC solutions are being phased out I repeat my plea for @Kasper Elsborg  to switchover to the 9800-CL platform for instance ,

 M.

[Kasper Elsborg]

@Rich R thanks so much for the detailed walkthrough.

But  @marce1000 is right, no need to pursue this issue any longer.

But you know how it is, it nerdy to pursue an error and not giving up. It gives an edge and insight. This ap was just for lab purposes, so no wireless was hurt in the operation

However I also wanted to try and run a mini pc with vmware, for the solo purpose of an wlc, and at the same time keep the cost low. I have ordered a GMKtec mini pc for the purpose.

Thanks guys 

[marce1000]

  @Kasper Elsborg   - Ref : https://www.cisco.com/c/en/us/products/collateral/wireless/catalyst-9800-series-wireless-controllers/nb-06-cat9800-ser-wirel-faq-ctp-en.html

                                  If you talk about a mini PC then take care of :
    >...

Q. Which hypervisor tools and functionality are supported for a private cloud?

A.  The Cisco Catalyst 9800-CL Wireless Controller for Cloud runs Cisco IOS XE Software and can be deployed as a VM inside the customer’s data center on hypervisors such as VMware ESXi, open-source KVM, Microsoft Hyper-V, and as Cisco NFVIS on the Cisco ENCS.

                For instance the 9800-CL is not supported on VMware workstation,

 M.

[Rich R]

You're welcome <smile>

[Kasper Elsborg]

@marce1000 as esxi 8.0 now has a free tier again, and the GMKtec has a Intel Ethernet Controller I226-V that supports esxi, this is the great choice