Bonjour Colin,
Sorry for the delay, stuff got in the way !
I adapted your solution a little and it worked like a charm.
- The M3s were on 6.3.1.8, I upgraded the 7220s to that version.
- On the licensing site, I migrated all the licences (minus the minimum to cover the AP-65 and AP-70) to the 7220s with license pooling. Did a license export to save those for later.
- On the M3s, created an "AP-65" AP profile and migrated all the -65 and -70 to that profile.
- I created an "aruba-65" DNS entry pointing to the M3s.
- I modified the "aruba-master" DNS entry to point to the 7220s,
- I provisionned the AP-65s and -70s with the "AP-65" profile, changing the Host-controller name to "aruba-65" as you suggested.
- On the M3s, I did a "flash backup", downloaded it to my laptop, un-gzip-tared it and modified the "default.cfg", changing the controller name and IP addresses (the M3s and 7220s share the same vlans).
- I then re-tared-zipped the folder and uploaded it to the master 7220. After a "flash restore" and "license import", the controller booted fine.
- I did the same procedure for the slave M3 to the slave 7220.
- With everything up, and all the controllers having the same AP profiles, I used a maintenance window to reboot the non -65 and -70 APs which happily attached to the 7220s.
- After testing that everything was working like it should, I upgraded the 7220s the 6.4.1.0 (another maintenance window) and we started provisionning/installing our brand new AP-205s (boy, do they run hot).
- A little housekeeping later (removing the superfluous APs from the respective controller generations, modifications to Airwave...), everything is up and users are happy!
Thank you very much for your guidance.
#AP205#7220