Resetting a Cisco Air Cap 1552E access point to factory defaults!

[Cap-24]

I am trying to reset a Cisco Air Cap 1552 E access point back to it's factory defaults.  I have tried every mode button press and release from what I read online, but nothing is working.  I do not have an option to reset it via a controller.  Can someone suggest what is the right way to do this.  Thanks in advance. 

[coolbreeze]

If it is not in a boot-loop, and you are able to press Return and get a login prompt on the console, and you are able to login to the AP (assuming console cable connection), then try configuring the AP with IP address information, and primary controller information.  The commands you use will differ based on if you are using AirOS vs Catalyst environment.  AirOS would be something like:

AP# capwap ap ip address [ip_address] [netmask]
AP# capwap ap ip default-gateway [gateway_address]
AP# capwap ap primary [controller-hostname] [controller-ip]
AP# show capwap ip config
AP# reload

This thread has good information in general, and commands for the catalyst controller/9800 version / IOS XE AP commands: https://community.cisco.com/t5/wireless/9800-wlc-cli-command-for-ap-primary-controller-assignment/td-p/4308489

If this is a default out of box AP, try the default creds to login - cisco/Cisco, enable, Cisco
If this is not a default out of box AP, then back to figuring out how to factory reset it.
Another option is to maybe try DHCP options (and configure DHCP such as on the local switch if not currently using) to help point it to the controller, if you don't have the ability to login to the AP via console and can't get factory reset figured out.  https://community.cisco.com/t5/wireless-mobility-knowledge-base/configuring-dhcp-option-43-and-option-60/ta-p/3143572
Depending on your environment, checking what the cisco-capwap-controller.[domain.com] resolves to, and set a static DNS entry with pointer to the controller as well - the DHCP options and link above are another approach to addressing the same thing, fyi.

If you have console access to the AP, you can try "capwap ap erase all" on the AP to factory reset the AP from within the CLI without using the mode button.

I still haven't found my notes for factory default issues on these....I wanna say it was unplug the AP power, hold down the mode button, plug in the AP power, keep holding the mode button longer than 20 but not longer than 45 second...or was it longer than 60 seconds?  Or try following the on-screen prompts in the console while holding down the mode button but in my experience is hit or miss with the 1500s series for some reason (hence I usually have my notes).

[Cap-24]

@coolbreeze Thanks for your efforts in trying to assist with this Access point issue.  I can't log into the access point.  We typically would set a static IP, DG, and put in capwap primary controller IP, then plug into same WLC switch subnet and device would join the WLC.  

When it comes to the reset of the AP via the Reset button?  Should I see something in putty that tells me to release the button as it is resetting? It does not seem to be working with any amount of seconds.  Any other ideas?  

[coolbreeze]

hmm, short of maybe setting up DHCP on the switch using DHCP options liked mentioned/linked in the last comment to help it find the WLC and pull an IP address to workaround not being able to set static information on the AP itself (since don't have login access to the AP) and force it to pull new login settings.
I have a spare 1500 series unit I can test tomorrow and report back - it *should* say / usually give prompts in the putty session while you're trying to reset it, but usually it's kind of obvious if it does assuming it's behaving normally.

What's the actual model, and any version ID (can be identified on the product label on the AP with VID 01 or VID 04, for example)?  Do you have others of the same model types deployed in the environment (thinking for comparison sake, I've had issues/differences in 1500s between VID versions, or if you have another unit to test if it does the same behavior trying to reset it)?

Just to be clear, which is your ultimate goal:

1) to get it to join the WLC (to deploy)

2) or to factory reset it (like before equipment disposal)

3) or to factory reset it to help you do your normal process to join it to the WLC (static IP and controller info, etc) to deploy?

[MHM Cisco World]

Move the AP to same subnet of WMI of wlc 9800 and check boot again

Share it here please 

MHM

[MHM Cisco World]

So now it join wlc 

Try reset it from wlc 

Or even why you need reset if it join?

MHM

[coolbreeze]

Sorry that was actually me that marked your post helpful since that was a good suggestion that would work - although it looks like it reported it as an accepted solution which I didn't realize it would do...  Looks like the OP replied to my comment including plugging into the same switch as the WLC is a method they typically use I think, but seem to require setting static IPs on the AP, so I don't think it has joined the WLC, and is possible their previously shared boot logs are from while plugged in on the same switch as the WLC (same subnet is an assumption though)

[MHM Cisco World]

Sorry it me by accident select as solution' but I remove it.

[Cap-24]

@coolbreeze @MHM Cisco World - Thanks for the help on this.  Just to clarify, I cannot log into this AP or connect it to our WLC.  

The goal is to get it connected to our WLC, was assuming the factory reset and setting static IP would help with this process.  I don't have total access to the network or how our other outdoor AP's (same model) where set up orginally.

Model - AIR-CAP1552E-A-K9, VID:V01

[coolbreeze]

got it, thanks for clarifying - I have a spare unit of similar series I can look at tomorrow to check in Putty.  Are you using any power injectors or just PoE?

[Cap-24]

@coolbreeze I am using a PoE Injector to power up the AP. Thanks for your help on this issue.

[Rich R]

> Just to clarify, I cannot ... connect it to our WLC.  

Why not? 
DHCP with option 43 will allow it to discover the WLC.  Remember outdoor APs and any AP in bridge mode needs the ethernet MAC allowed on the controller - did you remember to add it?
config auth-list add mic 00:11:22:33:44:55

[Cap-24]

@Rich R  -  I meant that I have not been able to connect it to our WLC so far, but I am sure it is possible.  We have a switch that connects to our WLC. When I plug my computer into that switchport, I can ping the WLC.  Now plug in PoE from ethernet port of AP, and  I go from the PoE Injector's switch connection into that switchport I was referring to.  Is this right, and should the AP then connect to the WLC.  Not really sure how the DHCP with option 43 is suppose to work if this is the method right now how my AP will connect to WLC. Thanks for your input. 

[coolbreeze]

So the idea of using DHCP and with option 43, is to workaround the fact you cannot log into the AP to set a static IP address for the AP and a primary controller address for the WLC.  This assumes being able to have administrative rights to the relevant switch to create a DHCP scope on the switch, or know where DHCP lives if on a server and working with the correct sysadmins to get a scope for that plus option 43 configured so when you plug in the AP, it will pull an IP address AND also find the WLC in its discovery process.

The laptop plugging into the same switch where the WLC connects and pinging it indicates layer 3 reachability, but not necessarily that you are on the same subnet - putting the AP in the same subnet as the WLC is another workaround method but also assumes that DHCP is enabled so the AP can pull an IP address to communicate with the WLC.  If when you plug in the laptop to that switchport and it pulls a dynamic IP address that is also in the same subnet as the WLC, then that would give you information it is in the same subnet.  For instance, if the WLC is 172.30.1.5 IP address and assuming a /24 or 255.255.255.0 mask, then if the laptop pulls a DHCP address in 172.30.1.x range, then it is in the same subnet, and plugging the AP into that port instead may work.

However if you are using VLANs and different subnets, you'd have to configure a port to be in the same subnet as the WLC, and it still would need to be able to pull an IP address.  Apologies if you know some of this already, I am just covering the bases analyzing the situation not knowing the full details.

If the AP is able to pull an IP address that is in the same range as the WLC when you plug the AP into the switch that also connects to the WLC, it should be able to find it as is.  Otherwise you will need to find a way to configure the switchport to be in the same VLAN or subnet as the WLC, and/or create a DHCP scope with option 43 on the switch or with the server admins if there's a local DHCP server, OR figure out how to wipe the AP (as we are still doing) with the mode button alone to try and do your normal method of consoling onto the AP to set static IPs and controller addresses.

I'll report back on what I find with the 1500 series AP I have here; the prompt listed by @Rich R is what you would see in the putty session and goes back to the holding it down for longer than 20 seconds until it says something else if I recall.

Made a crude diagram of what I think you are saying you are trying/able/usually do with arbitrary IP examples to make sure I'm following correctly:

[Cap-24]

@coolbreeze  - Appreciate your explanation.  I am hoping that we can figure out the reset option.  I would have to ask our network guy if the DHCP option could be used in this situation to get this AP connected to our WLC. Everything in this network seems to be set statically. 

[coolbreeze]

Alright, here we go.  See if this works for you - this was on a test 1562 that's in mesh mode, but works the same and should be the same for 1550s, mesh mode or not, and whether you are using IOS XE/Catalyst or older AirOS version:

1) Disconnect the cable that goes to the switch for ethernet from the PoE injector.
2) Plug AP into the PoE injector "To AP" / PoE port.
3) Press and hold down the mode button - make sure you are actually on it and don't slip off while waiting for boot.
4) Plug the injector into the wall power.
5) Continue pressing until the prompt says you have been holding it for 21 to 30 seconds on the timer/counter.
6) Release the mode button
7) AP will go through full reset and boot
Once it shows it is going through Discovery and channel scanning, you should be able to press Return to get a login prompt
9) Login with username "cisco" and password "Cisco" (capital C)
10) Type "enable" then use password "Cisco" (capital C)
11) You should now have access to configure the AP.

Example Putty Terminal below, comments are preceeded by !!!!!!

!!!!!!!!!!!!!!!!!!!1) DISCONNECT AP/INJECTOR FROM SWITCH. CONNECT AP TO POE INJECTOR ONLY
!!!!!!!!!!2) PRESS AND HOLD MODE BUTTON AND THEN ALSO CONNECT POWER TO WALL ON INJECTOR

!!!!!!!!!!!!!!!!!!!!!THIS IS WHAT IS SEEN IN PUTTY:

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

Wait for the button to be released ....
Button pressed for 24 seconds  (this will count, let go when the number is 21 or above)

Performing full factory reset..

Setting env for full reset..
SF: Detected MX25L3205D with page size 64 KiB, total 4 MiB
Erasing SPI flash....Writing to SPI flash.....done
do_resetb
do_clear fips env

Setting env for configuration reset..
Erasing SPI flash....Writing to SPI flash.....done
do_format_storage
Creating 1 MTD partitions on "nand0":
0x000000200000-0x000010000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
Remove UBI volume storage (id 5)
No size specified -> Using max size (69201920)
Creating dynamic volume storage of size 69201920
reset u-boot
resetting ...

BootROM - 1.78
Booting from SPI flash, Secure mode
BootROM: RSA Public key verification PASSED
BootROM: CSK block signature verification PASSED
BootROM: Boot header signature verification PASSED
BootROM: Box ID verification PASSED
BootROM: JTAG is disabled

General initialization - Version: 1.0.0
Detected Device ID 6920
Master bootloder version 1.4a
High speed PHY - Version: 2.0
BoardId = 0x23board SerDes lanes topology details:
| Lane # | Speed| Type |
------------------------------|
| 1 | 0 | SGMII1 |
| 2 | 5 | PCIe1 |
| 4 | 5 | PCIe2 |
----------

---------------------

!!!!!!!!!!! {full output omitted for brevity} !!!!!!!!!!!!!!!!!!!!

____ _
/ ___|(_) ___ ___ ___
| | | |/ __| / __|/ _ \
| |___ | |\__ \| (__| (_) |
\____||_||___/ \___|\___/
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **

U-Boot 2013.01-ge1c49d93a (Jul 28 2023 - 09:08:14) SDK version: 2015_T2.0p10

!!!!!!!!!!! {full output omitted for brevity} !!!!!!!!!!!!!!!!!!!!

Factory full reset detected...

DATAWIPE : Initating Data wipe
[*01/01/1970 00:00:32.8229] error: open /dev/cookie
[*01/01/1970 00:00:32.8268] cat: can't open '/COOKIE_PID': No such file or directory
DATAWIPE : Securely clearing files
DATAWIPE : Restoring shared boot variables

!!!!!!!!!!! {full output omitted for brevity} !!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!CHANNEL SCANNING AND DICOVERY PROCESS AFTER FACTORY RESET

[*07/04/2019 00:01:28.4389] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:01:28.4462] bftype is 6
[*07/04/2019 00:01:28.5682] DOT11_DRV[1]: Stopped Radio 1
[*07/04/2019 00:01:28.6000] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*07/04/2019 00:01:28.8774] DOT11_DRV[1]: DOT11_DRV[1]: Skipping channel set bypass_channel_set:1 radio_reset:0
[*07/04/2019 00:01:30.2824] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:01:31.4363] DOT11_DRV[1]: Stopped Radio 1
[*07/04/2019 00:01:31.4681] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*07/04/2019 00:01:31.7641] DOT11_DRV[1]: DOT11_DRV[1]: Skipping channel set bypass_channel_set:1 radio_reset:0
[*07/04/2019 00:01:33.2919] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:01:34.4367] DOT11_DRV[1]: Stopped Radio 1
[*07/04/2019 00:01:34.4687] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*07/04/2019 00:01:34.7628] DOT11_DRV[1]: DOT11_DRV[1]: Skipping channel set bypass_channel_set:1 radio_reset:0
[*07/04/2019 00:01:36.1385] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:01:36.1641] DOT11_CFG[1]: poe_power_mode: low_pwr_mode=6, allowed_tx_ant=3, allowed_rx_ant=3
[*07/04/2019 00:01:36.3218] DOT11_DRV[1]: Stopped Radio 1
[*07/04/2019 00:01:36.3533] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*07/04/2019 00:01:36.6493] DOT11_DRV[1]: DOT11_DRV[1]: Skipping channel set bypass_channel_set:1 radio_reset:0
[*07/04/2019 00:01:38.0249] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:01:39.2025] DOT11_DRV[1]: Stopped Radio 1
[*07/04/2019 00:01:39.2342] DOT11_DRV[1]: DOT11_DRV[1]: set_channel Channel set to 36
[*07/04/2019 00:01:39.5126] DOT11_DRV[1]: DOT11_DRV[1]: Skipping channel set bypass_channel_set:1 radio_reset:0
[*07/04/2019 00:01:40.9152] DOT11_DRV[1]: Started Radio 1
[*07/04/2019 00:02:42.8770] CAPWAP State: Init
[*07/04/2019 00:02:42.8784]
[*07/04/2019 00:02:42.8784] PNP is not required,
[*07/04/2019 00:02:42.8784] Starting CAPWAP discovery
[*07/04/2019 00:02:42.8784]
[*07/04/2019 00:02:42.8871]
[*07/04/2019 00:02:42.8872] CAPWAP State: Discovery
[*07/04/2019 00:02:42.8886] Not sending discovery request, AP does not have an IP!!
[*07/04/2019 00:02:42.8970]
[*07/04/2019 00:02:42.8970] CAPWAP State: Discovery
[*07/04/2019 00:02:53.7119] ipv6 gw config loop in discovery timer expiry
[*07/04/2019 00:02:55.7120] ipv6 gw config loop in discovery timer expiry
[*07/04/2019 00:02:57.7122] ipv6 gw config loop in discovery timer expiry
[*07/04/2019 00:02:59.7123] ipv6 gw config loop in discovery timer expiry
[*07/04/2019 00:03:01.7125] ipv6 gw config loop in discovery timer expiry
[*07/04/2019 00:03:03.7135] ipv6 gw config loop in Ac discovery

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  ONCE I SAW IT CHANNEL SCANNING AND TRYING TO DO DISCOVERY, I PRESSED THE RETURN KEY AND IT GAVE ME USERNAME: PROMPT, SO AUTHENTICATED WITH DEFAULT CREDS cisco, Cisco 

Username: cisco
[*07/04/2019 00:03:05.7137] ipv6 gw config loop in Ac discovery

Password:
[*07/04/2019 00:03:07.7138] ipv6 gw config loop in Ac discovery

!!!!!!!!!!!!!!!!THIS THEN GIVES THE AP DEFAULT NAME> PROMPT, TYPE EN AND PASSWORD DEFAULT Cisco 

AP156F.A90D.37DD>en
Password:
[*07/04/2019 00:03:09.7140] ipv6 gw config loop in Ac discovery

AP084F.A90D.37DA#

!!!!!!!!!!!!! AP DEFAULT NAME# now should have configuration access

Updated diagram what to do to achieve that: