Here are the steps to convert an AP (that is not a UAP) to an IAP.
Also important to note is that the above command has several permutations to allow you to convert a number of ways. You can even build a list of APs to convert ahead of time, making it easier later to come back and kick off the process.
The following are some of the differences in the command structure:
In order to track the status of the conversion process, here are some useful commands:
Another important thing to note is that the AP conversion process will tie the converted AP to whatever region the controller is assigned for regulatory purposes. Just b/c you can convert and AP doesn’t mean that you can use a US controller to create a bunch of rest of world (RW) IAPs.
Hope that this helps you out if you need some extra IAP but only have APs laying around.
I NEVER THOUGHT THAT WOULD BE POSSIBLE,
I was always thinking that this is a hardware matter.
Anyway, this will be a great addition as I have a couple of CAPs at the office and I prefer to convert them IAP, some question here,
- Is it possible to FTP an InstantOS6 and then convert a CAP with,
- once the CAP is converted to IAP, the AP won't revert back if we do reset it from boot prompt ?
Yes, you can ftp a v6 code and have it convert the AP that way per a colleague of mine that did so. It should not revert back on a reset as far as I know.Keep in mind this feature is really only intended for AP 3xx series that were not IAP already.
the note you shared is important "feature is really only intended for AP 3xx series that were not IAP already"
TO understand more, is there a hardware requirement to run InstantOS that 3xx series meet?
I think we can convert a 210 CAP that can connect to a ArubaOS8.6 and then load the InstantOS from there? is that right? or 200 CAP series won't support InstantOS code?
Please note that this command has been designed to convert an AP for test and lab use only. Aruba does not recommend using this command to convert APs for production deployment. A CAP converted to IAP using this command will not be supported by Aruba as such an AP will not be recognized as an IAP by Support. Also, such a converted AP will not be recognized as an IAP by Central and will not be manageable by Aruba Central. AOS 8.6 User Guide is being updated to highlight the above points.
the only thing I can see in AOS8.6 user guide is this note
can you please point me which page number I have to check-in user guide?
After we converted AP to IAP, can we convert it back to AP ( in order to get the normal support & services) ?
This is a one-way command. The APs will be permanently changed to remember the regulatory domain.
We are in the process of making the updated documentation available.
Wanted to know if the new document is available?
Thank you very much for the guide. Today i converted AP-305 to IAP-305 and there is one little thing i want to point out. If you use below version of the command
ap convert active all-aps server tftp <server address A.B.C.D> <code filename>
and leave it like this, any new CAP that you will connect and provision, it will be turned to IAP !. I did this today and waiting for the CAP to come up and it seemed like ages. Then i restarted it and waited again, then it occurred to me that second AP was already converted. Also why i selected all-aps, initially i tried with specific-aps and tftp server which didnt work for some reason. My TFTP was 100% fine and working (because few mintues earlier, i converted my 7010 to 8.6 from 6.5). So i tried changing specific APs to All-aps and didnt change it after converting the first AP. So when i plugged in the second 305 and after provisioning it from controller, it never came back as CAP
have you tried to convert AP-200 serie by chance ?
The AP-200 series cannot run InstantOS beyond version 6.5, so trying to convert them to v8 or higher is not possible.