Wireless Access

Hello Community,

We tested an IAP 535 as the conductor with IAP 635 as a member(we have two 635s). When we tested this it worked and the firmware was 8.9.0.2. Between testing and deploying the IAP 535 was upgraded to ArubaInstant_Draco_8.11.1.1_87111. When the IAP 635 joined on the network, it stated that the AP could not join the cluster because of firmware mismatch.

We attempted to log into the IAP 635 and install ArubaInstant_Norma_8.11.1.1_87111 however, it would not take the update. We set the Conductor to not allow "auto join" for new IAPs. Since our IAP 535 was on Draco we attempted to run the install upgrade-image tftp://<IP>/ArubaInstant_Draco_8.11.1.1_87111. When we did this, it told us that we needed to upgrade from the conductor.

However, the conductor is not seeing the devices. So we cannot update the two 635s from the conductor. My thought at this point is to factory reset the IAP 635s, get them on their own network not seen by the Conductor. Once on that network, upgrade the IAPs and then once they have the same firmware as the conductor allow them to join that network again.

Has anyone ran into this issue and knows of a possible work around or resolution to resolve this issue or resetting the device(s) and starting from scratch the correct path?

Thanks, 

when you have different model APs in an instant cluster and you upgrade the the VC, the VC will then upgrades the rest of the AP's that are the same model as it self.

for the remaining model APs, you need to have them in an isolated VLAN and then upgrade them to the similar firmware version, then reboot them and bring them back to the initial instant cluster and they will join without an issue.

AP-635s require Norma_8.11.1.1_87111 firmware class.

Also note that 8.11.1.2 was recently released.

Hello Community,

We tested an IAP 535 as the conductor with IAP 635 as a member(we have two 635s). When we tested this it worked and the firmware was 8.9.0.2. Between testing and deploying the IAP 535 was upgraded to ArubaInstant_Draco_8.11.1.1_87111. When the IAP 635 joined on the network, it stated that the AP could not join the cluster because of firmware mismatch.

We attempted to log into the IAP 635 and install ArubaInstant_Norma_8.11.1.1_87111 however, it would not take the update. We set the Conductor to not allow "auto join" for new IAPs. Since our IAP 535 was on Draco we attempted to run the install upgrade-image tftp://<IP>/ArubaInstant_Draco_8.11.1.1_87111. When we did this, it told us that we needed to upgrade from the conductor.

However, the conductor is not seeing the devices. So we cannot update the two 635s from the conductor. My thought at this point is to factory reset the IAP 635s, get them on their own network not seen by the Conductor. Once on that network, upgrade the IAPs and then once they have the same firmware as the conductor allow them to join that network again.

Has anyone ran into this issue and knows of a possible work around or resolution to resolve this issue or resetting the device(s) and starting from scratch the correct path?

Thanks, 

Hello Community,

We tested an IAP 535 as the conductor with IAP 635 as a member(we have two 635s). When we tested this it worked and the firmware was 8.9.0.2. Between testing and deploying the IAP 535 was upgraded to ArubaInstant_Draco_8.11.1.1_87111. When the IAP 635 joined on the network, it stated that the AP could not join the cluster because of firmware mismatch.

We attempted to log into the IAP 635 and install ArubaInstant_Norma_8.11.1.1_87111 however, it would not take the update. We set the Conductor to not allow "auto join" for new IAPs. Since our IAP 535 was on Draco we attempted to run the install upgrade-image tftp://<IP>/ArubaInstant_Draco_8.11.1.1_87111. When we did this, it told us that we needed to upgrade from the conductor.

However, the conductor is not seeing the devices. So we cannot update the two 635s from the conductor. My thought at this point is to factory reset the IAP 635s, get them on their own network not seen by the Conductor. Once on that network, upgrade the IAPs and then once they have the same firmware as the conductor allow them to join that network again.

Has anyone ran into this issue and knows of a possible work around or resolution to resolve this issue or resetting the device(s) and starting from scratch the correct path?

Thanks, 

Does the 635 have access to the Internet to pull the firmware?  What method did you initially try when upgrading the cluster?  If you are manually upgrading the conductor then you will have to provide all of the images (Norma and Scipio, Draco is 510/518/570) for a successful multi-model upgrade to complete, this is documented in the CLI bank.

https://www.arubanetworks.com/techdocs/CLI-Bank/Content/instant/upgrade-image.htm

Hello Community,

We tested an IAP 535 as the conductor with IAP 635 as a member(we have two 635s). When we tested this it worked and the firmware was 8.9.0.2. Between testing and deploying the IAP 535 was upgraded to ArubaInstant_Draco_8.11.1.1_87111. When the IAP 635 joined on the network, it stated that the AP could not join the cluster because of firmware mismatch.

We attempted to log into the IAP 635 and install ArubaInstant_Norma_8.11.1.1_87111 however, it would not take the update. We set the Conductor to not allow "auto join" for new IAPs. Since our IAP 535 was on Draco we attempted to run the install upgrade-image tftp://<IP>/ArubaInstant_Draco_8.11.1.1_87111. When we did this, it told us that we needed to upgrade from the conductor.

However, the conductor is not seeing the devices. So we cannot update the two 635s from the conductor. My thought at this point is to factory reset the IAP 635s, get them on their own network not seen by the Conductor. Once on that network, upgrade the IAPs and then once they have the same firmware as the conductor allow them to join that network again.

Has anyone ran into this issue and knows of a possible work around or resolution to resolve this issue or resetting the device(s) and starting from scratch the correct path?

Thanks,