Network Management

Hi guys,

Recently I upgraded my AirWave to version 8.2.5. I tried to upgrade my cluster of 20 IAPs from 6.5.1.0-4.3.1.3 to 6.5.3.0, but it has failed. It has been upgrading for one hour, but after this hour the status in AirWave Firmware Upgrade Jobs page change from "In Progress" to "Failed", and in the Firmware Server Log the reason is timeout:

Thu Nov 30 08:43:28 2017: Starting a pass for Firmware upgrade job(Thu Nov 30 07:41:43 2017)
Thu Nov 30 08:43:28 2017:     ARUBA01 Firmware upgrade timed out
Thu Nov 30 08:43:28 2017: Job failed, sending email for Firmware upgrade job(Thu Nov 30 07:41:43 2017)

 The cluster has two models of IAPs, but I uploaded in AirWave the two upgrade files before upgrading. Also the IAPs are in managed mode, since Instant GUI Config is enabled.

Why this time out? What is the reason? Please help!

Regards,

Julián

Hi guys,

In System > Event Log I found some logs as "Could not find suitable firmware image:6.5.1.0-4.3.1.3_59179(Ursa) for ArubaInstant". The Ursa upgrade file is for IAP models 304/305 and 365/367. Really I have not two models of IAP as I told in my previous message but three, some IAP-325, one IAP-277 and one IAP-365, but the IAP-365 already has version 6.5.3.0 and was rebooting constantly because it couldn't join to the cluster as the cluster has version 6.5.1.0-4.3.1.3, but I thought IAP-365 could join to the cluster after upgrading to 6.5.3.0, but the upgrade failed.

What could happen? Please help!

Regards,

Julián 

Are you enforcing Instant Firmware Version in that group?

Hi,

Does all three model IAPs are part of cluster? If yes then try load IAP 365 model 6.5.1 code, airwave will push the firmware to the slave IAPs which is newly joining to the cluster, since IAP 365 is not in VCs firmware verson it is failing to join the cluster.

upload the 6.5.1 firmware for model 365 , airwave will automatially push this firmware and device firmware will downgrade and join the cluster, once it become part of cluster try upgrade the code to 6.5.3

Regards,

Pavan

Hi Collin and Pavan,

@Collin,

Enforce Group Firmware Version is set to No, but what is the difference of this setting?

@Pavan,

No, IAP-325 and IAP-277 are part of the cluster, IAP-365 is not. IAP-325 and IAP-277 are running 6.5.1.0-4.3.1.3, and IAP-365 is already running 6.5.3.0, because of this mismatch IAP-365 is not in the cluster and IAP-365 is rebooting all the time. But I want to upgrade the cluster (IAP-325 and IAP-277) to 6.5.3.0 and after that, IAP-365 will join to the cluster.

Many thanks for your help,

Julián

Hi,

If we set group enforcement firmware version to YES, then any device added to this Airwave group will be updated to the version which is set in the group.

since you have set to NO, need to manually update the firmware version, if you are adding any new device to match with exisitng VCs. Since you are adding new IAP with new code its is keep rebooting.

Regards,

Pavan

Hi Pavan,

Then you say if I set Enforce Group Firmware Version to YES, existing cluster (IAP-325 and IAP-277) will upgrade to 6.5.3.0 and after that the IAP-365 will join to the cluster and stop rebooting? Is that the problem?

Regards,

Julián

If you have added IAP 365 to same group and want to upgrade (IAP-325 and IAP-277) to 6.5.3 version then either you upgrade by uploading firmware to firmaware page and set enforce group firmware by selecting 6.5.3 verison from drop down list and click apply (you could schedule downtime)

Regards,

Pavan

Hi Pavan,

Ok, I will do that and let you know. Many thanks!

Regards,

Julián

Hi Pavan,

I have just upgraded the cluster. I have decided to disconnect IAP-365 first (since it was doing problems) and then upgrade (I keep Enforce Group Firmware Version set to No) and the upgrade was successfull. However, after the upgrade I see the following message within the  Group > Instant Config: Error--- Cannot compare policies from different models desired[6.5.1.0-4.3.1] actual[6.5.3.0-6.5.3].

What happens now? How can be solved?

Regards,

Julián

Hi Pavan,

Don't worry, now the error dissapeared and all is good. I guess AirWave only needed time :)

Regards,

Julián