Is there any way to remotely factory default an access point (in my case an AP225)? Can it be done from the controller? Can it be done from a telnet session?
I have an AP which is not trivial to physically get to that I need to factory default. It's stuck to some AOS8 controller which I no longer want this specific AP on ... and I am unable to make it move ...
Not that I am aware of. So you can not reprovision the AP from the controller and put it in a different AP group with a different system profile to a controller you want to move the AP to?If not then you have to physically console into the device and purge it.
Factory reset a single AP:
From the Master controller CLI in enable mode:
Profesional Services Enablement
Hi Brant,uhm, I have a short question, do you know if the option still works today with ARUBA OS8.x?
The KB of commands still shows the reset-bootinfo command, but so far I'm not able to use the "provision-ap" command in the CLI of the MC.
Does you or anyone other community member have an idea? :)
Thank you very much in advance!
(md7005) #provision-ap reprovision
all Reprovision all APs in provisioning_ap_list
ap-name Reprovision AP with this name
ip-addr Reprovision AP at this IP address
ip6-addr Reprovision AP at this IPv6 address
serial-num Reprovision AP with this serial number
wired-mac Reprovision AP at this MAC address
(md7005) #provision-ap reprovision all
reset-bootinfo Restore factory default boot variables
restore restore file or configuration
Hoping it OK to keep this thread going:We provision APs with whitelist-db. Lately had lots of APs to re-name or re-group (the new group was to move them onto a new cluster via LMS IP). Mostly this went fine using Excel and the following:whitelist-db cpsec modify mac-address <MAC> ap-group <New Group>Followed by:ap-regroup wired-mac <MAC> <New Group>But some APs got 'stuck' in some way and required a furtherreset-bootinfo wired-mac <MAC>My problem is that some further APs refuse to change group or name. The whitelist-db shows the correct info, but the ap-regroup, ap-rename, and reset-bootinfo commands cause the APs to reboot, but they come back up with old details rather than what the whitelist shows.I tried the provision-ap reprovision wired-mac <MAC> commmand but that didn't help either. I think I was flat out of luck at the point reset-bootinfo failed to work. What do I do now?e.g. Trying to rename and regroup cluster02-test / SouthW-Std-InRoom to Test-AP / South-Std (attempted in separate steps for name and group)
(md7005) #provision-ap reprovisionall Reprovision all APs in provisioning_ap_listap-name Reprovision AP with this nameip-addr Reprovision AP at this IP addressip6-addr Reprovision AP at this IPv6 addressserial-num Reprovision AP with this serial numberwired-mac Reprovision AP at this MAC address(md7005) #provision-ap reprovision all(md7005) #resreset-bootinfo Restore factory default boot variablesrestore restore file or configuration
Think I've answered my own question!
I've been picking off APs from Airwave and hadn't realised that all the MAC addresses I worked with previoulsy were lower case, but the most recent ones from AW are upper case. It wasn't until I put these into the previous spreadsheet that I spotted this difference. The commands below work just fine for lower case MACs, but there's no error to tell you that upper case MACs don't work. So it's a bit odd that in some instances Aruba shows lower case MAC, and in others, it shows upper case. PITA when you forget this is significant for commands.
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.