ArubaOS and Controllers

Reply
Occasional Contributor I
Posts: 7
Registered: ‎09-30-2011

AP120s not coming up aftes upgrade 3.4.4.3 -> 6.1.2.3

Hi all,

I have a problem with a controller 3200 and 12 AP 120. I upgraded the controller from version 3.3.1.10 to version 3.4.4.3. After that, the controller is working fine.

Aster that, I upgraded from 3.4.4.3 to 6.1.2.3. As the release notes says, this can be done directly, without any additional hop. I copied it to partition 1 and reloaded the switch. The controller is working and it has updated the config file also, but the 12 AP 120 are not coming up.

When I telnet to the controller, there is this message:

Ancillary files are not present
*****************************************************************
* WARNING: An additional image upgrade is required to complete the *
* installation of the AP and WebUI files. Please upgrade the boot *
* partition again and reload the controller. *
*****************************************************************

After that, I entered using web interface and there was a dialog with the same message. I pushed "Upgrade now" and after a while rebooted the controller, but there was the same message again.

In the AP database, all APs are down, upgrading or rebooting, but none of then comes up. And if I look at the log, I si that Aps are asking for a file that doesn't exist on the controller:

Oct 26 12:26:22 sapd: <311013> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| Image upgrade failed; details follow.
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| FTP Failed: 3. Trying TFTP.
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| FTP Failed: 3. Trying TFTP.
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| Flash Image upgrade failed: 255
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| Flash Image upgrade failed: 255
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| ncftpget mips64.ari: server said: No such file or directory.
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| ncftpget mips64.ari: server said: No such file or directory.
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| transfer timed out
Oct 26 12:26:22 sapd: <311014> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| transfer timed out
Oct 26 12:26:23 nanny: <303086> |AP 00:1a:1e:c0:35:88@10.0.2.244 nanny| Process Manager (nanny) shutting down - AP will reboot!
Oct 26 12:26:23 nanny: <303086> |AP 00:1a:1e:c0:35:88@10.0.2.244 nanny| Process Manager (nanny) shutting down - AP will reboot!
Oct 26 12:26:23 sapd: <311002> |AP 00:1a:1e:c0:35:88@10.0.2.244 sapd| Rebooting: SAPD: Reboot after image upgrade


Any ideas?
Is there any way to put the file mips64.ari into tpm directory, so APs can download it?

Thank you
Guru Elite
Posts: 21,492
Registered: ‎03-29-2007

Re: AP120s not coming up aftes upgrade 3.4.4.3 -> 6.1.2.3

Downgrade to 5.0.4.x, let the APs come up and then try again. You needed to do a double upgrade.


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 7
Registered: ‎09-30-2011

Re: AP120s not coming up aftes upgrade 3.4.4.3 -> 6.1.2.3

Hi,

I did as you said. Upgraded to 5.0.4.1 and all APs upgraded. Then I rebooted to the partition where 6.1.2.3 but same results. I uploaded that version again and rebooted, and it worked.

So I suppose that the upgrade can be done from version 3.4.4.3 to 6.1.2.3, but I should have upgraded 6.1.2.3 files twice. The problem was that the controller was in a remote location, and I had to upgrade using a dsl line.
Guru Elite
Posts: 21,492
Registered: ‎03-29-2007

Re: AP120s not coming up aftes upgrade 3.4.4.3 -> 6.1.2.3


Hi,

I did as you said. Upgraded to 5.0.4.1 and all APs upgraded. Then I rebooted to the partition where 6.1.2.3 but same results. I uploaded that version again and rebooted, and it worked.

So I suppose that the upgrade can be done from version 3.4.4.3 to 6.1.2.3, but I should have upgraded 6.1.2.3 files twice. The problem was that the controller was in a remote location, and I had to upgrade using a dsl line.




I am glad you got it to work. There are two different things that needed to be done:

1- The APs needed to upgrade to 5.0.4.1 before 6.1.2.3 to work properly because the controller to AP behavior has changed in 6.1.2.3.
2- The controller itself needed to upgrade a single partition to 5.0.4.1 and then to 6.1.2.3 to load all the new RF dashboard files. You managed to accomplish this. I'm sorry for all the extra time that was spent.


Colin Joseph
Aruba Customer Engineering

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

Occasional Contributor I
Posts: 7
Registered: ‎09-30-2011

Re: AP120s not coming up aftes upgrade 3.4.4.3 -> 6.1.2.3




Don't worry, I left my pc to do it at night :)

Thanks for the help

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