The AP-315 requires ArubaOS 6.5.0.0 as a minimum; so it will not work with a controller on 6.4.
The AP-345 requires ArubaOS & Aruba InstantOS 8.3.0.0; so it will not run on 6.x at all.
If the IAPs would be supported, this is how to convert IAP to a controller AP:
AP303H-1a:68# convert-aos-ap cap ?
<name> controller address
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Feb 20, 2023 11:14 AM
From: ajhancock
Subject: Converting IAPs to CAPs via console cable
Hello there folks.
I am having a few issues getting AP345s and AP315s to upgrade their firmware. We are on code 8.10.0.4 currently. These APs are older, probably 2018 or so. I was told to console into the AP as it boots and then direct it to go to an older controller environment we have that is running 6.4 code. Once it lands there, I can then swing to our 8.10 controller and provision it there.
Is there any documentation out there or a procedure list for consoling into an AP.
Also would like to note that I am getting DHCP and a controller address of 10.100.XX.XX. The AP never gets a 169.XX.XX.XX and stays in IAP mode even with the correct 10.100.XX.XX address.
Thanks in advance.
Aaron H