Controllerless Networks

i'm try to upgrade one of iap-205-rw but after reboot iap boot in to old firmware.

sh ver
Aruba Operating System Software.
ArubaOS (MODEL: 205), Version 6.4.2.6-4.1.1.6
Website: http://www.arubanetworks.com
Copyright (c) 2002-2015, Aruba Networks, Inc.
Compiled on 2015-05-12 at 10:27:51 PDT (build 50009) by p4build

sh image
Primary Partition Build Time :2015-05-12 10:27:51 PDT
Primary Partition Build Version :6.4.2.6-4.1.1.6_50009
Backup Partition Build Time :2017-03-2 04:25:52 PST
Backup Partition Build Version :6.5.1.0-4.3.1.2_58595

Try to switch-partition-reboot:
Reboot Time and Cause: AP rebooted Thu May 4 11:06:33 UTC 2017; CLI cmd at uptime 0D 0H 6M 40S: switch-partition-reboot

But iap still load 6.4.2.6. I'm try 6.4.4.8, 6.5.1.0.
Iap allso don't convert into standalone ap.

Did you try any other version of Instant for the upgrade?

We try:

ArubaInstant_Taurus_6.5.1.0-4.3.1.2_58595

6.4.4.8-4.2.4.6_58505 (manual and auto upgrade from web interface)

ArubaInstant_Taurus_6.4.2.6-4.1.3

Are you trying  to upgrade a single IAP in a cluster or is this a single IAP which is not in a cluster?

We have 4 new point.

First ap was upgrade on new firmware and configured, then we add points to cluster. For the first time this AP was added to cluster, but then she down from claster. I think cuz fail firmware upgrade. 

If she boot first, other point's can't join claster.

Then we try to upgrade this ap without cluster. 

AP was cleared to default settings, write erase all and from web interface. 

Ap don't  convert to standalone ap. 

Are all of the IAP's the 205 model? It sounds like the cluster is split between old and new firmware. Do you see anything in the logs when the upgrade fails or when it fails to reboot as a standlone AP?

All ap was same model and firmware. 3 ap work in cluster propertly. 

We don see anything in logs. AP upload firmware successfully go to reboot and boot with old firmware. Now all operation was with single ap.

If you can, could you post the tech-support? (Remove any private info if needed :) )

In attachment.

Attachment(s)

aruba-support.txt   238 KB 1 version

Hi,

Is it possible to take console access to this IAP & run the following command from apboot

apboot> factory_reset

apboot>save

apboot> boot

If possible , put this IAP in a different vlan at time of testing & then try the upgrade process.

We try to find console cable. 

The AP single in broadcast domain for most time that we try to fix it.

With console cable AP say crc error on main partition image. 

Send AP back to reseller.

Reboot Time and Cause: AP rebooted Thu May 4 13:08:25 UTC 2017; Image Upgrade Successful
34:fc:b9:c0:b8:82# sh image

Primary Partition Build Time :2015-05-12 10:27:51 PDT
Primary Partition Build Version :6.4.2.6-4.1.1.6_50009
Backup Partition Build Time :2016-12-7 02:12:08 PST
Backup Partition Build Version :6.4.2.6-4.1.3.4_57646

sh version
Aruba Operating System Software.
ArubaOS (MODEL: 205), Version 6.4.2.6-4.1.1.6
Website: http://www.arubanetworks.com
Copyright (c) 2002-2015, Aruba Networks, Inc.
Compiled on 2015-05-12 at 10:27:51 PDT (build 50009) by p4build

AP uptime is 1 minute 25 seconds
Reboot Time and Cause: AP rebooted Thu May 4 13:11:52 UTC 2017; CLI cmd at uptime 0D 0H 1M 24S: switch-partition-reboot

Same result(