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]

Could you please share 5-10mins of console output from this AP.

[Saikat Nandy]

Thanks @Kasper Elsborg .. I have gone through the console output.. I can see you have changed hostname and then tried ap-type command followed by archive download command...can you give me plain simple console output of the AP please.. without running any command..I reckon the AP is still in this phase - 

AP Image type : EWC-AP IMAGE
AP Configuration : EWC-AP CAPABLE

If true, just simply connect the console and reload the AP and give me 5-10mins data without running any command. Thanks.

[Kasper Elsborg]

@marce1000 initially i don't know, but if I do a transfere for example the 17.12.x it will stay on the same 17.15 before and after reload

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

could the ap be locked somehow?

[marce1000]

   - @Kasper Elsborg      What is the output of show version on the AP , before the EWC upgrade is attempted ?

 M.

[Kasper Elsborg]

@Saikat Nandy here is the complete output from factory reset to install of ewc

@marce1000 show ver is done before and after. its in the output file

[marce1000]

  - @Kasper Elsborg  - So at the end of 9130ap.txt you have this AP10#  prompt, what commands do you have
                                   available from there if you type for instance ?

  M.

[Kasper Elsborg]

@marce1000 the donwload of image is 17.12.x and the show ver. looks like it switches from primary to backup

before upgrade
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

after upgrade

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 : EWC-AP CAPABLE

[Kasper Elsborg]

@marce1000 

AP10#
Exec mode commands
ap-type Set the access point type
archive Archive commands
capwap CAPWAP exec commands
clear Reset functions
configure Configure parameters
connect Open a terminal connection
copy Copy a file
debug Debugging functions (see also 'undebug')
delete Delete a file
disable Turn off privileged commands
enable Turn on privileged commands
exec-timeout Set the exec-timeout
logging Logging commands
logout Logout out from CLI
more Display a file
no Negate a command or set its defaults
nslookup query internet name server
ping Send echo messages
reload Halt and perform a cold restart
show Show running system information
terminal Terminal parameters
test Test susbystems, memory and interfaces
traceroute Trace route to destination
undebug Disable debugging functions (see also 'debug')
AP10#

[marce1000]

  - @Kasper Elsborg  What happens if you type  ap-type EWC-AP  without any other parameters ?

 M.

[Kasper Elsborg]

@marce1000 

AP10#ap-type
capwap Switch to CAPWAP AP type
ewc-ap Switch to EWC AP type
workgroup-bridge Switch to Workgroup Bridge(WGB) AP type
AP10#ap-type ewc-ap
% Incomplete command.
AP10#ap-type ewc-ap
WORD URL of AP image <tftp|sftp>://<server_ip>/<file_path>
AP10#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
AP10#

AP10#?
Exec mode commands
ap-type Set the access point type
archive Archive commands
capwap CAPWAP exec commands
clear Reset functions
configure Configure parameters
connect Open a terminal connection
copy Copy a file
debug Debugging functions (see also 'undebug')
delete Delete a file
disable Turn off privileged commands
enable Turn on privileged commands
exec-timeout Set the exec-timeout
logging Logging commands
logout Logout out from CLI
more Display a file
no Negate a command or set its defaults
nslookup query internet name server
ping Send echo messages
reload Halt and perform a cold restart
show Show running system information
terminal Terminal parameters
test Test susbystems, memory and interfaces
traceroute Trace route to destination
undebug Disable debugging functions (see also 'debug')
AP10#

[Kasper Elsborg]

@Saikat Nandy just a reboot output 

[Saikat Nandy]

@Kasper Elsborg , so you are getting this logs - 

Sun Aug 11 06:14:29 UTC 2024 Starting Controller...Please wait for a few minutes ....
Sun Aug 11 06:14:29 UTC 2024 Created controller running file: Sun Aug 11 06:14:29 UTC 2024
Sun Aug 11 06:14:30 UTC 2024 IOSd monitor 9107 started
Sun Aug 11 06:14:30 UTC 2024 fromdev_wired0 count = 257
Sun Aug 11 06:14:30 UTC 2024 Deleted controller running file: Sun Aug 11 06:14:29 UTC 2024
Sun Aug 11 06:14:30 UTC 2024 Container is not running.
Sun Aug 11 06:14:30 UTC 2024 Unmount system level file systems
Sun Aug 11 06:14:30 UTC 2024 Clean up, may take a while, please be patient...
Sun Aug 11 06:14:30 UTC 2024 Container cleanup finished

User Access Verification

Username: eeprom_api[5340]: EEPROM initialized by pid 5340
eeprom_api[5340]: FW: SAgE phys_buff=0xA2600000 / 3ffac00
eeprom_api[5340]: FW: SAgE virt_buff=0x7fb8dbd000
eeprom_api[5340]: System page_size=4096, mask=FFFFFFFFFFFFF000
eeprom_api[5340]: Closing dummy socket
eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1
eeprom_api[5340]: read 0 bytes from eeprom: ffffffff 16 28 ffffffff
eeprom_api[5340]: read 0 bytes from eeprom: 38 33 40 2a
eeprom_api[5340]: I_SKU: Hardware ID = C401
eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1
eeprom_api[5340]: I_SKU: Hardware ID = C401
eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1
eeprom_api[5340]: I_SKU: Hardware ID = C401

What happens after this? I am actually interested in that logs...

[Kasper Elsborg]

@Saikat Nandy I know the guide says to be patient, and it will take 15 min the first time to start up, but its still at the same stage, now here 2 hours later. First day I left it over night, and no change

User Access Verification
Username: eeprom_api[5340]: EEPROM initialized by pid 5340
eeprom_api[5340]: FW: SAgE phys_buff=0xA2600000 / 3ffac00

eeprom_api[5340]: FW: SAgE virt_buff=0x7fb8dbd000

eeprom_api[5340]: System page_size=4096, mask=FFFFFFFFFFFFF000

eeprom_api[5340]: Closing dummy socket

eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1

eeprom_api[5340]: read 0 bytes from eeprom: ffffffff 16 28 ffffffff

eeprom_api[5340]: read 0 bytes from eeprom: 38 33 40 2a

eeprom_api[5340]: I_SKU: Hardware ID = C401
eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1

eeprom_api[5340]: I_SKU: Hardware ID = C401
eeprom_api[5340]: read 0 bytes from eeprom: 6 0 f 1

eeprom_api[5340]: I_SKU: Hardware ID = C401

[marce1000]

 - @Kasper Elsborg   - I am a bit worried about those eeprom messages at the end of your output because they could
                                   indicate a hardware problem. Do you have another 9130 AP to try with ?

  M.

[Kasper Elsborg]

I try find another monday, when I get back to the office. 

Thanks for your support