We have a mixed environment iAP-115/iAP-225 environment. I have already gone through the confusion of the -225 rebooting if ethernet 0 and 1 were hooked up, also that the iAP-225 insisted on being the Virtual Controller, and I have also updated Airware to version 8.2.2.1. However, for the purposes of this problem, we have put Airwave in monitor-only mode, and are updating using the VC.
We have ordered and received a number of new iAp-325s that will eventually replace all the existing -115s and -225s. I can't rip them all out and start over; we have to stay "up" throughout the process. These -325s were shipped with firmware version 6.4.4.4-4.2.3.0. I was told by Aruba engineers that the Virtual Controller must be at this code for them to join the cluster. Guess what? This code is not available to me (or anyone else). So I updated the VC code to 6.5.0.0-4.3.0.0_56428, thinking that a higher code might force the iAP-325s to upgrade. Now my Aruba Engineers are telling me not to install the iAP-325s, and that some pretty elaborate measures are needed. (Shut down all iAPs in the cluster, put in one iAP-325 as master, update it, then bring the other older iAPs back online. This might solve one iAP-325, but I have hundreds more). Bear in mind this is a school system, in session daily, and heavily dependent on wireless for our 1 to 1 initiatives. There has got to be a better way. Can someone steer me to that better way?