Reuse evaluation key

Using the trial/eval keys, you can re-use them 3 times for up to 90 days.
After 90 days or before, you will have to backup the config (NOT a flash backup), wr erase all, and then either re-configured (great practice) or paste in the new config.
You cannot use the flash backup as it will restore the old key timers and will show expired upon reboot.
Backup Config Only
In the WebUI
1.Navigate to the Maintenance > File > Copy Files page.
2.Select the source where the file or image exists.
3.Select the destination to where the file or image is to be copied.
4.Click Apply.
In the CLI
copy startup-config flash: <filename>
copy startup-config tftp: <tftphost> <filename>
copy running-config flash: <filename>
copy running-config ftp: <ftphost> <user> <password> <filename> [<remote-dir>]
copy running-config startup-config
copy running-config tftp: <tftphost> <filename>
The default.cfg cannot be overwritten at runtime through tftp/ftp.
Copy the file into the controller under a different name, then set boot boot config-file to that file.
After a reboot, if you would like this to be your default.cfg, set the boot config-file back to default.cfg
then issue a write mem.

Upgrade Firmware

1. Backup config
CLI
#backup flash
GUI
-click Maintenance/File/Backup Flash/Create Backup
-list backup file
#dir
-rw-r–r–    1 root     root          446 Jan 11 06:35 AUDITTRAIL-HISTORY.log
-rw-r–r–    1 root     root          230 Jan 11 06:35 AUDITTRAIL-LOGIN_OUT-HISTORY.log
-rw-r–r–    1 root     root        14136 Jan 11 06:34 default.cfg
-rw-r–r–    1 root     root         7617 Jan 11 06:16 default.cfg.2016-01-11_06-16-50
-rw-r–r–    2 root     root         7698 Jan 11 06:24 default.cfg.2016-01-11_06-24-03
-rw-r–r–    1 root     root        10621 Jan 11 06:34 default.cfg_writemem_2016-01-11_06-34-53
drwxr-xr-x    3 root     root         1024 Jan 11 06:26 fieldCerts
-rw-r–r–    1 root     root        23327 Jan 12 00:29 flashbackup.tar.gz
-rw-r–r–    1 root     root         1324 Nov  8 17:22 lic
-rw-r–r–    2 root     root         7698 Jan 11 06:24 original.cfg
drwx——    2 root     root         1024 Nov  8 10:02 tpm
-copy backup somewhere else
CLI
#copy flash: flashbackup.tar.gz ftp: 10.0.10.102 ftp Password
GUI
Maintenance/File/Backup Flash/Copy Backup
-export license
#license export license
#dir
-rw-r–r–    1 root     root          446 Jan 11 06:35 AUDITTRAIL-HISTORY.log
-rw-r–r–    1 root     root          230 Jan 11 06:35 AUDITTRAIL-LOGIN_OUT-HISTORY.log
-rw-r–r–    1 root     root        14136 Jan 11 06:34 default.cfg
-rw-r–r–    1 root     root         7617 Jan 11 06:16 default.cfg.2016-01-11_06-16-50
-rw-r–r–    2 root     root         7698 Jan 11 06:24 default.cfg.2016-01-11_06-24-03
-rw-r–r–    1 root     root        10621 Jan 11 06:34 default.cfg_writemem_2016-01-11_06-34-53
drwxr-xr-x    3 root     root         1024 Jan 11 06:26 fieldCerts
-rw-r–r–    1 root     root        23327 Jan 12 00:29 flashbackup.tar.gz
-rw-r–r–    1 root     root         1324 Nov  8 17:22 lic
-rw-r–r–    1 root     root         1469 Jan 12 00:48 license
-rw-r–r–    2 root     root         7698 Jan 11 06:24 original.cfg

drwx——    2 root     root         1024 Nov  8 10:02 tpm

2. Download firmware

A. Go the the Aruba support site.
(Login with your partner account)
Read the release notes for upgrade order i.e
Upgrading From an Older version of ArubaOS Before you begin, verify the version of ArubaOS currently running on your controller. If you are running one of the following versions of ArubaOS, you must download and upgrade to an interim version of ArubaOS before upgrading to ArubaOS 6.4.2.4.
For ArubaOS 3.x.versions earlier than ArubaOS 3.4.4.1, download the latest version of ArubaOS 3.4.5.x.
For ArubaOS 3.x or ArubaOS 5.0.x versions earlier than ArubaOS 5.0.3.1, download and install the latest version of ArubaOS 5.0.4.x.
For ArubaOS 6.0.0.0 or 6.0.0.1 versions, download and install the latest version of ArubaOS 6.0.1.x
Go to download software.
B. Choose the relevant ArubaOS that fit your controller model.
C. Read the release notes (upgrade notes)
D. Download the firmware to your pc.
E. Login to the the controller as admin
Go the maintenance

Choose the right method (I prefer ftp)

Use ftp much faster than tftp
3CDaemon (old..but working when needed – found some download links for u)
TFTPd (my favorite *There is also 64bit bersion)

Note: If you are planning to upgrade a 3200 to 6.2 that one requires that you upgrade the memory

3. upgrade non default boot

4. it will automatically reboot and choose partition that we upgrade (partition 1) as default boot

5. because current default boot is partition 1 and we want to upgrade all the latest firmware into partition 1.

We need to boot from partition 0 first then upgrade partition 1

boot from partition 1
You have to reboot the controller and enter in the cpboot mode.
You do it by when you reboot the controller just press mm enter enter until you get this mode…
It will tell press any key to enter in the cpboot but it just like 3 secs… so i just press enter until i get into it
After that
For Partition 0
cpboot> bootf 0
For Partition 1
cpboot> bootf 1
GUI
click Maintenance/Controller/Boot Parameters
6. Once partition 1 upgraded to latest version then we can do the same thing to partition 0

7. I encounter this error “write Device: No such file or directory” when I upgrade from 5.0.4.to 6.4.4.1

SOURCE: https://support.arubanetworks.com/Documentation/tabid/77/DMXModule/512/Command/Core_Download/Method/attachment/Default.aspx?EntryId=13579
Log in to the WebUI from the PC or workstation.
Navigate to the Maintenance > Controller > Image Management page. Select the Upload Local File option, and click the Browse button to navigate to the image file on your PC or workstation.
To see the current boot partition, navigate to the Maintenance > Controller> Boot Parameters page.
Select No for Reboot Controller After Upgrade. Reboot manually after the upgrade.
Click Upgrade. Ignore the following error message when the upgrade is complete: “write Device: No such file or directory”
Navigate to Controller > Boot Parameters. Make sure that the partition you upgraded to is the boot partition.
Navigate to Controller > Reboot Controller. Select Yes next to Save Current Configuration Before Reboot?
When the boot process is complete, log in to the WebUI and navigate to the Monitoring > Controller > Controller Summary page to verify the upgrade, including country code. The Country field displays the country code configured on the controller

3400 Basic Config

L: admin
P:
# clock set 2016 january 10 20 35 00
(config) # ip name-server 10.0.20.2
(config) #clock timezone GMT +7
(config) #ntp server 10.0.20.2
-adding license
CLI
(config) #license add Qk2xOyvN-+35poVEz-5fHDA7fS-UzoWBNB9-ifi5jF0F-eC8
The limit for Access Points has been constrained to the platform limit [256]
#show license
License Table
————-
Key                                               Installed    Expires     Flags  Service Type
—                                               ———    ——-     —–  ————
Qk2xOyvN-+35poVEz-5fHDA7fS-UzoWBNB9-ifi5jF0F-eC8  2016-01-10   2016-02-09         Access Points: 512
                                                  21:12:03[1]  21:12:03
License Entries: 1
Flags: A – auto-generated; E – enabled; R – reboot required to activate
GUI
click Configuration/Network/Controller/License Management/Licenses
copy and paste the license into “Add New License Key”
(config) #interface vlan 1
(config-subif)#ip address 10.0.10.243 255.255.255.0
Switch IP Address is Modified. Switch should be rebooted now
(config-subif)#exit
(config) #ip default-gateway 10.0.10.1
(config) #write memory

Ancillary files are not present

When you login GUI, instantly that message appear

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.                        *
*********************************************************************
Ancillary file(s) or digest file missing.
Ancillary image is missing please upgrade the image again.

SOLUTION:
That is because AirOS version different between partition 0 and partition 1.
When we make it the same, the problem gone