Heterogeneous AP:
a) When using Heterogeneous AP management ‘anyap’ profiles must be used to configure Access Points which are not the same model as the Virtual Controller. These profiles must exist on the Virtual Controller prior to the Virtual Controller adopting and managing other Access Point models. Adoption and management of other Access Point models will succeed without any defined auto provisioning rules if the ‘anyap’ profiles are named “default-”. For example, an AP 8533 Virtual Controller will successfully adopt and manage an AP 7602 Access Point without an AP 7602 auto provisioning rule if the AP 8533 has an ‘anyap’ profile named “default-ap7602”. Otherwise you will need to create suitable auto provisioning rules for the other Access Point models if you choose to use a different naming convention for your ‘anyap’ profiles.
b) When using Heterogeneous AP management be aware that APs operating as Virtual Controllers have much less persistent storage than actual WiNG controllers. Because of this it may not be possible for you to update all APs simultaneously when using multiple AP models. The Virtual Controller may not have enough free persistent storage to hold the firmware update images for multiple AP models. The amount of free persistent storage is unique to every Virtual Controller installation. If your Virtual Controller does not have enough free storage for multiple firmware update files you will need to download a single appropriate firmware update file to the Virtual Controller, update the AP models that correspond to that firmware update file, delete that firmware update file from the Virtual Controller, then repeat the download/update/delete process for the next AP model.
