Aruba Instant & Cloud Wi-Fi

Reply
Contributor I
Posts: 79
Registered: ‎04-09-2014

Can IAP115 and IAP215 be used to form a Virtual Controller?

I have IAPs115 and IAPs 215, checking at firmware in the download site I realized that they have different firmware for each series. So I think that probably they cann't co-reside inside the same Virtual Controller,.... but I want to confirm!

Guru Elite
Posts: 20,578
Registered: ‎03-29-2007

Re: Can IAP115 and IAP215 be used to form a Virtual Controller?

4.1.1.7 should be available for both platforms.  Please let me know if you cannot find that version of code for both.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Guru Elite
Posts: 8,188
Registered: ‎09-08-2010

Re: Can IAP115 and IAP215 be used to form a Virtual Controller?

They can, you just have to manually match the firmware.


Thanks,
Tim

Tim Cappalli | Aruba ClearPass TME
@timcappalli | ACMX #367 / ACCX #480 / ACEAP / CWSP
Contributor I
Posts: 79
Registered: ‎04-09-2014

Re: Can IAP115 and IAP215 be used to form a Virtual Controller?

I can find the firmware for both of them, but I see different files for each, let say:

one file for 114/115 and other for 214/215. So, when I upgrade any APs from the Virtual Controller, I usually do a maintenance task when I upload just 1 file, I don't want the customer to do a different procedure.

Guru Elite
Posts: 20,578
Registered: ‎03-29-2007

Re: Can IAP115 and IAP215 be used to form a Virtual Controller?

The 115 is a different model from the 215 and requires different firmware (Pegasus vs. Centaurus).  If it is a GA release of code, if the VC differs in model from an IAP that is trying to join, it requests the image server for the GA version of code for that new platform.

 

A certificate on IAPs with versions older than 4.1.1.6 expired, so that the image on them need to be manually upgraded to 4.1.1.7 and above.   You could be running into that issue if the code on an AP is older than that it cannot request, check or upgrade to 4.1.1.7 automatically.  You should upgrade all of your platforms manually to 4.1.1.7.  The issue should be fixed to check and automatically upgrade after that.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: