converting C9130AXI into EWC

[Paulyp5]

I am currently trying to convert a C9130AXI  into EWC I have done a factory reset using 30 sec push of factory reset button see below

Wait for the button to be released ....
Button pressed for 36 seconds

Setting env for full reset..
Writing to Nand... done
Auto boot mode, use bootipq directly
APPS power cycled and restart reason is 0x10
Hit ESC key to stop autoboot: 0
Specified BOOT: part1

however I am unable to get the login option for user name and password   It keep getting the discovery mode below 

*02/27/2024 08:04:42.2927] CAPWAP State: Discovery
[*02/27/2024 08:04:42.2979] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

Any help will be appreciated thanks. 

[marce1000]

     >...Hit ESC key to stop autoboot: 0
      - Did you execute the above too ?

 - Despite the CAPWAP discovery message(s) ; what happens if you attach a console and type return ?

 M.

[Paulyp5]

Thanks for the quick reply pressing ESC key it goes into bootloader mode see below 

Button is pressed. Configuration reset activated..
Keep the button pressed for > 20 seconds for full reset

Keep the button pressed for > 30 seconds for full factory reset (clear fips flag)

Wait for the button to be released ....
Button pressed for 34 seconds

Setting env for full reset..
Writing to Nand...
Erasing block 0x768000
Erasing at 0x76f000 -- 100% complete.
done
Auto boot mode, use bootipq directly
APPS power cycled and restart reason is 0x10
Hit ESC key to stop autoboot: 2
(BTLDR) # fbgv
Unknown command 'fbgv' - try 'help'
(BTLDR) # (BTLDR)

Not sure what command to use after that to be able to log in 

[marce1000]

 - Ok , leave the ESC aside (not needed) and start the AP again : does the console react at all if logins are attempted by pressing return (when you see the capwap messages) ?

 M.

[Paulyp5]

nothing seems to happen when pressing the return it seems to just go into a capwap discovery loop see below.

[*02/27/2024 08:41:25.0137] CAPWAP State: Init
[*02/27/2024 08:41:29.1835] Start: RPC thread 2861753232 created.
[*02/27/2024 08:41:29.1835] PNP:Server not reachable, Start CAPWAP Discovery
[*02/27/2024 08:41:29.1841]
[*02/27/2024 08:41:29.1841] CAPWAP State: Discovery
[*02/27/2024 08:41:29.1889] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/27/2024 08:41:29.1893]
[*02/27/2024 08:41:29.1893] CAPWAP State: Discovery
[*02/27/2024 08:41:58.6582]
[*02/27/2024 08:41:58.6582] CAPWAP State: Discovery
[*02/27/2024 08:41:58.6626] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/27/2024 08:42:28.1213]
[*02/27/2024 08:42:28.1213] CAPWAP State: Discovery
[*02/27/2024 08:42:28.1237] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/27/2024 08:42:57.5790]
[*02/27/2024 08:42:57.5790] CAPWAP State: Discovery
[*02/27/2024 08:42:57.5819] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/27/2024 08:43:27.0392]
[*02/27/2024 08:43:27.0392] CAPWAP State: Discovery
[*02/27/2024 08:43:27.0427] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*02/27/2024 08:43:38.5278] Restarted PnP Discovery timer after time sync for 60 seconds
[*02/27/2024 09:36:57.5700] PNP:Server not reachable, Start CAPWAP Discovery
[*02/27/2024 09:36:57.5700]
[*02/27/2024 09:36:57.5700] Going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*02/27/2024 09:36:57.5700]
[*02/27/2024 09:36:57.5701] Restarting CAPWAP State Machine.
[*02/27/2024 09:36:57.5702] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*02/27/2024 09:36:57.5909]
[*02/27/2024 09:36:57.5909] CAPWAP State: DTLS Teardown
[*02/27/2024 09:36:57.7216] upgrade.sh: Script called with args:[ABORT]
[*02/27/2024 09:36:57.7774] do ABORT, part1 is active part
[*02/27/2024 09:36:57.8042] upgrade.sh: Cleanup tmp files ...
[*02/27/2024 09:36:57.8358] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*02/27/2024 09:36:57.8358] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*02/27/2024 09:37:12.4066]
[*02/27/2024 09:37:12.4066] CAPWAP State: Discovery
[*02/27/2024 09:37:12.4134] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[Paulyp5]

nothing seems to happen when I press the return key it just goes into a repeat capwap state discovery.

[marce1000 · Accepted solution]

 - Disconnect the network cable (if connected)  , reboot again ; check if a change in behavior can be observed ; also check correctness of serial operator equipment by using another cisco device and verify if inputting to console is possible , 

 M.

[Rich R · Accepted solution]

It's normal for a lightweight AP to continuously cycle through discovery looking for a WLC - that doesn't stop you from logging in.
Like Marce says more likely a problem with your console cable.  Cisco APs are very fussy about console cables.  Are you sure the cable works properly - have you ever used it with a Cisco AP before (routers, switches etc don't count)?
Generally cables based on genuine FTDI (not counterfeit/fake) chipset work well.  Before buying a cable always check the reviews to make sure it has been tested with Cisco APs.

When you press enter/return that should trigger the AP to provide a login prompt.  Even if the discovery continues just carry on and type your username and password (default Cisco/Cisco)
Then "enable" - password Cisco again.
Then follow instructions: https://www.cisco.com/c/en/us/support/docs/wireless/embedded-wireless-controller-on-catalyst-access-points/215303-embedded-wireless-controller-conversion.html

[Paulyp5]

Thank you all for your help managed to get it going was just getting confused continuously cycle through discovery looking for a WLC.

[Rich R]

You're welcome - glad to hear you got it going.