We have a 3 AP cluster (virtual controller) running for quite some time but need to add a new additional AP. The IAP-205 is EOL so we have purchased an IAP-305.
IAP-205 running firmware 220.127.116.11
IAP-305 running firmware: 18.104.22.168
What is required to join the IAP-305 to the 205 cluster as it does not appear to autojoin.
Instant VC clusters require thal all the members be on the same firmware version.
You cannot join 8.x with 6.x.
The best solution would be to backup and restore the configuration from the 205 VC to the 305 AP.
Shutdown the 205's and bring up the 305 as a VC.
Thankyou for the reply.
I assume that I wouldn't be able to join the 6.X APs into the new 8.X VC until I updated the firmware on these APs then.
Is it possible that I could backup one of the existing 6.X APs (not the preferred master) and restore this config to the 8.X AP?
As a side issue, the certificate on the VC appears to have expired so I cannot automatically check for new firmware, are you able to point me to any docs on how I can renew this cert.
I don't believe there is any firrmware available to bring a 205 to 8.x
You can backup any member of the VC using the 'Maintenance Backup '
You will need to manually update the 205 from the support portal.
This document should give you a starting point
If I cannot get 8.X firmware for the IAP-205 then is it even possible to run the 305 and 205 in the same cluster?
I have attempted to downgrade firmware on the 305 and also restore a config to it from one of the 205s but it doesn't appear to work. CLI is giving me an error that it is running in a degraded state (assume because it is trying to join existing cluster and isn't able to).
If it's not possible to run the 305 in a cluster with the 205 then how can I put it in standalone mode so I can at least make use of this new AP?
Alll Instant AP's must be on the same firmware to be a member of a VC.
You can convert an AP to 'standalone'
You will have to control it separatly from other AP's.
An AP that tries to join a VC with different firmware will constantly reboot to restart the 'swarm join'...you won't be able to do anything on the CLI.
Thanks. I have lost access to the AP now since trying to downgrade the firmware so will have to try get to it via console. I am able to get to GUI but not back to it via SSH. The default admin credentials (admin/serial number) and (admin/admin) do not work via the GUI but they worked via SSH when I previously had access. This was the case before I lost access via SSH also. Any idea why the creds don't work via GUI?
Not sure, if you solved your issue so far, but just wanted to mention, that you can run the IAP205 and IAP305 in the same cluster. Both IAP's need to run the same version of software and both IAP's support 6.5.4.x.
This is what I ended up doing, all now working. Thanks.
Hi All, is the problem solved?so what is the solution? Because I am facing same situation as IAP 205 won't join IAP 305 cluster or reverse. Please advice.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.