How do I bring a remote AP up on ArubaOS 6.x code if the default image is 3.3.x?

Aruba Employee

Question:  How do I bring a remote AP up on ArubaOS 6.x code if the default image is 3.3.x?

 

Product and Software:This article applies to all Aruba controllers and ArubaOS 3.x or later.

 

Remote APs, (RAP2, RAP5, RAP5WNs) have three images:

- running image

- flash image

- zero-touch provisioning or backup image

You can see what images a RAP has on it by issuing the "show ap image version ip-addr <ip address of ap>" command on the controller CLI.

--------------------------command output----------------------------

(Aruba) #show ap image version ip-addr 10.69.32.152

AP Image Versions On Controller

-----------------------------------------

5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:40:27 PDT 2010

5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010

Access Points Image Version

------------------------------------

AP Running Image Version String Flash (Production) Image Version String Flash (Provisioning/Backup) Image Version String Matches Num Matches Num Mismatches Bad Checksums Bad Provisioning Checksums Image Load Status

-- ---------------------------- --------------------------------------- ------------------------------------------------ ------- ----------- -------------- ------------- -------------------------- -----------------

10.69.32.152 5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010 5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010 3.3.2.11-rn-3.0.1(p4build@trinidad.arubanetworks.com)#21263 Wed May 6 22:30:18 PDT 2009 Yes 1 0 0 0 Done

--------------------------command output---------------------------

The running image is what the AP is running at the time. The flash image is what is buried in the AP flash that it boots off of. The provisioning image is what you see only during zero-touch provisioning of that AP. The running and flash images are updated when an AP boots to a controller. The provisioning image, however, must be updated manually via the CLI. In this example, the AP has a flash and running image that is on ArubaOS 5.0. But the backup (or zero-touch) image is still on the 3.3.2.11-rn-3.0.1 code. If the user does the reset procedure (also known as the paperclip or paperpin) on this remote AP, only the provisioning options of the RN code are available, not the updated ArubaOS 5.0 code. Missing will be the ability to statically give an AP an IP address, configure PPPoe settings, and configure a broadband wireless modem on startup. To upgrade the provisioning image, this AP must be booted to a controller that has the desired version of the provisioning image (in this case, it does). Then issue the "apflash" command to the backup partition:

-----------------------------command ------------------------------

(Aruba) #apflash ip-addr 10.69.32.152 backup-partition

-----------------------------command------------------------------

To verify that it is upgrading, issue the "show ap image version" command:

--------------------------command output---------------------------

(Aruba) #show ap image version ip-addr 10.69.32.152

AP Image Versions On Controller

-----------------------------------------

5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:40:27 PDT 2010

5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010

Access Points Image Version

------------------------------------

AP Running Image Version String Flash (Production) Image Version String Flash (Provisioning/Backup) Image Version String Matches Num Matches Num Mismatches Bad Checksums Bad Provisioning Checksums Image Load Status

-- ---------------------------- --------------------------------------- ------------------------------------------------ ------- ----------- -------------- ------------- -------------------------- -----------------

10.69.32.152 5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010 5.0.0.0(p4build@cartman)#23711 Mon Mar 22 12:33:07 PDT 2010 3.3.2.11-rn-3.0.1(p4build@trinidad.arubanetworks.com)#21263 Wed May 6 22:30:18 PDT 2009 Yes 1 0 0 0 In Progress (44 secs)

--------------------------command output---------------------------

When you are upgrading the backup partition, the AP can still accept clients as usual. When the process is complete, however, the AP reboots. If you reset the remote AP using a paperclip, you see the new ArubaOS 5.0 features.

If you have 3.x code on the RAP, you cannot bring that RAP up on the controller that is running 6.x code and you will see these error messages:

---------------------------command output---------------------------

Aug 11 09:36:16 <authmgr 124062> <ERRS> |authmgr| No server group for MAC=00:21:6a:8a:e9:4c IP=0.0.0.0 in authentication profile default, method=MAC AAA profile=YCOE_Admin_Test-aaa_prof found.

Aug 11 09:36:16 <authmgr 132030> <ERRS> |authmgr| Dropping EAPOL packet sent by Station 00:21:6a:8a:e9:4c 00:24:6c:5c:82:d1

Aug 11 09:36:31 <sapd 311013> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| Image upgrade failed; details follow.

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| ERROR: File size exceeded 5242880 bytes

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| Local write failed: Success.

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| ncftpget mips64.ari: no space.

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| FTP Failed: 3. Trying TFTP.

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| ERROR: File size exceeded 5242880 bytes

Aug 11 09:36:31 <sapd 311014> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 sapd| Flash Image upgrade failed: 255

Aug 11 09:36:32 <nanny 303086> <ERRS> |AP 00:0b:86:67:2f:21@10.10.10.254 nanny| Process Manager (nanny) shutting down - AP will reboot!

---------------------------command output---------------------------

Note: AP has tried upgrading the code with tftp: and ftp: both and then it rebooted.

 

Upgrade the RAP backup image to ArubaOS 5.0.2.0 code. After that, RAPs can communicate to any 6.x codes. Aruba has started shipping new RAPs with the 5.x code. However if you have the old manufactured RAP, upgrade the code to ArubaOS 5.0.2.0 and then to 6.x.

Version history
Revision #:
1 of 1
Last update:
‎07-04-2014 11:49 PM
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: