Hi Candace,
This code version 6.4.2.6-4.1.1.11 is compatible with IAP 135's , 205's and many other IAP's.
ArubaInstant_Cassiopeia_6.4.2.6-4.1.1.11_52666 --->Aruba Instant code for IAP-134 and IAP-135
ArubaInstant_Taurus_6.4.2.6-4.1.1.11_52666 --->Aruba Instant code for IAP-204/205
If you already have a cluster of IAP 135's running 4.1.1.11, then while introducing the new 205's to the same cluster, you would have to make sure that the current code and country information on 205's are same as that of the IAP 135's, since both these IAP's run on different platforms.
These new units may come with a different code version. You would have to upgrade these 205's to 4.1.1.11, using this file "ArubaInstant_Taurus_6.4.2.6-4.1.1.11_52666" from the support site.
While you upgrade these new units, make sure you connect it to a different subnet than the existing IAP 135's.
**If connected to the same subnet (as that of 135's) , it will receive the master beacon from an IAP 135 (acting as Master) , but won't get the code . In such situation you would see these 205's stuck in slave state.
So, make sure you connect these devices to a different subnet, mention the correct country information (if its rest of the world ) and upgrade to the same version (4.1.1.11) as running in IAP-135's.
Once 205's are up with the new code version , you can unplug it from that subnet and plug it back to the 135's subnet . IAP-135 (master) should then show all these new IAP's under the AP section.
You won't have to repeat this process for further upgrades, once the 135's and 205's are part of same cluster , you would see a colomn added under Maintenance -> Firmware, that allows to add the files for both the platforms.
Regards,
Anshul Bharthan
