Wireless Access

Reply
Occasional Contributor I

Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

I have a client that is upgrading from 5.0.1.0 to 6.3.1.6.  According to the 6.3.1.6 release notes you need to go to an intermediate version first, as shown here:

 

For ArubaOS 3.x or ArubaOS 5.0.x versions earlier than ArubaOS 5.0.3.1, download the latest version of Aruba OS 5.0.4.x.

 

Instead of going to 5.0.4.x we went to 5.0.3.3 and then to 6.3.1.6.  This appeared to work and our "show image version" shows that 6.3.1.6 is installed:

 

Partition : 0:0 (/dev/hda1)
Software Version : ArubaOS 6.3.1.6 (Digitally Signed - Production Build)
Build number : 43301
Label : 43301
Built on : Fri Apr 18 15:00:26 PDT 2014
----------------------------------
Partition : 0:1 (/dev/hda2) **Default boot**
Software Version : ArubaOS 5.0.1.0 (Digitally Signed - Production Build)
Build number : 24398
Label : 24398
Built on : Sun Jun 13 23:49:08 PDT 2010

 

However, it appears that it didn't really work since APs will not connect when running on 6.3.1.6.  Additionally, when accessing the GUI in 6.3.1.6 we get the following message:

 

Ancillary image stored on flash is not for this release
**************************************************************
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

 

Using the "Upgrade Now" option from this message does not resolve the issue.  Is this a result of going from 5.0.1.0 to 5.0.3.3 instead of 5.0.4.x?  My thought was going to 5.0.3.3 put us above the 5.0.3.1 version mentioned in the Release Notes.

 

 

Any feedback would be greatly appreciated, Thanks!

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Did you upgraded the memory in the 3200 ?

It's required to upgrade to 6.2.x and up
Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor I

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

No, we didn't change any hardware.

 

#show mem


Memory (Kb): total: 761348, used: 274416, free: 486932

 

What I see in the 6.3.1.6 guide says you need to have 40 MB free.

 

#show storage


Filesystem Size Used Available Use% Mounted on
none 300.0M 1.7M 298.3M 1% /tmp
/dev/hda3 392.7M 79.4M 293.1M 21% /flash

 

Do you have specifics for what you are referring to?  We didn't get any errors during the upgrade regarding space/memory.

 

Additionally, I've upgraded other 3200s that had 5.0.3.3 installed and was able to install 6.3.1.6 without issue.  The difference between those and these is that these started on ArubaOS 5.0.1.0.

 

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Victor is correct, but did you reload into 5.0.3 first?  I would have expected to see that version in one of the partitions.

 

The aps themselves also need to be upgraded to the intermediate version before going to 6.3.


If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Occasional Contributor I

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

We only did the upgrades on the Partition that has 6.1.3.6 installed, which is why you don't see the 5.0.3.3 showing up.  To be honest, I'm working with a client and I didn't complete the steps myself - so there could be something I'm missing.  For instance, I do not know if the APs were ever booted to the intermediate version first.

 

Of course, that could explain why the APs won't connect.. but it wouldn't necessarily explain why the controller gets an error message.

 

I did see in the 6.3.1.6 Release Notes there is a Bug ID of 95044 which gives a similar error, but they state it only occurs with 7200 series..

 

95044 Symptom: All access points went down when the controller to which they were connected rebooted and an error was displayed - Ancillary image stored on flash is not for this release. This issue is resolved by writing the boot partition information to the secondary bank of the NVRAM.


Scenario: This issue occurred when the controller rebooted due to a watchdog reset. This issue is observed only in 7200 Series controllers.

 

Could this be related to having 6.1.3.6 on one partition and something as old as 5.0.1.0 on the remaining partition?

Occasional Contributor I

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Since the release notes state if you are upgrading from something older than 5.0.3.1 you need to upgrade to 5.0.4.x first.  Could there be something missing by going to 5.0.3.3 and then to 6.3.1.6?

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Follow this to fix it:

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/Tutorial-How-to-fix-a-corrupt-OS/m-p/150468 

 

Then you need to upgrade your 3200 controller memory , contact your local Aruba team and they should able to assist you with purchasing the memory

Thank you

Victor Fabian
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Occasional Contributor I

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Thanks for the information.

 

Also, I'm confused about the memory. The 6.3.1.6 release notes state the following:

 

Issue the show memory command to confirm that there is at least 40 MB of free memory available for an upgrade using the CLI, or at least 60 MB of free memory available for an upgrade using the WebUI. Do not proceed unless this much free memory is available. To recover memory, reboot the controller. After the controller comes up, upgrade immediately.

 

Issue the show storage command to confirm that there is at least 60 MB of flash available for an upgrade using the CLI, or at least 75 MB of flash available for an upgrade using the WebUI.

 

The show storage command shows:

 

Filesystem Size Used Available Use% Mounted on
none 300.0M 1.7M 298.3M 1% /tmp
/dev/hda3 392.7M 79.4M 293.1M 21% /flash

 

Based on this, we have plenty of space and we already have the 6.3.1.6 version installed, so it doesn't appear to be a memory/space issue. Can you clarify the requirements you are looking at? Additionally, the link you provided states that the 3200 doesn't support 6.4x without a memory upgrade, but I'm not trying to go to 6.4x.

 

 

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

The memory upgrade refers to the RAM. Do a show memory which will show you if you need to purchase. This thread will help you http://community.arubanetworks.com/t5/Controller-Based-WLANs/How-to-Identify-differences-between-3200-and-3200XM-controller/ta-p/180516

If my post is helpful please give kudos, or mark as solved if it answers your post.

ACCP, ACMP, ACMX #294
mclarke@arubanetworks.com
Occasional Contributor I

Re: Upgrading 5.0.1.0 to 6.3.1.6 - 3200 Controller

Thanks, this is helpful.  I did run the "show mem" command earlier in the thread.  Here's the output again:

 

#show mem

Memory (Kb): total: 761348, used: 275120, free: 486228

 

According to the article you posted, the 3200 would have "5" digits for FREE space and the 3200XM would have "6".  We show 6, so this should be good to go.

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