Wireless Access

I have a requirement to place an image on an AP (from factory default) without the AP having access to a controller. I understand that there are files - mips.ari, mips32.ari, mips64.ari. What the usage for these files and will one of them be able to do the job.

Thanks.

Words of warning!

Following this procedure if done incorrectly might brick the AP!!

Do not attempt to upgrade the AP boot code unless told to by TAC - otherwise more than likely you will be phoning to RMA the AP.

Only upgrade the ap 'os' image.

This is for an AP-105 (with 8MB flash) (command syntax differs slightly with newer boot code)

Note: value for bootfile is used as the image name.

APBoot 1.0.9.12 (build 22797)
Built: 2009-11-04 at 15:53:54

Model: AP-10x
CPU:   AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM:  128 MB
POST1: passed
Copy:  done
Flash: 16 MB
PCI:   scanning bus 0 ...
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  168c  0029 00002   01 10000000 00000000 00000000 00000000
       01  00  168c  0029 00002   01 10010000 00000000 00000000 00000000
Net:   eth0
Radio: ar922x#0, ar922x#1

Hit <Enter> to stop autoboot:  0
apboot> printenv
bootdelay=2
baudrate=9600
autoload=n
boardname=Talisker
servername=aruba-master
bootcmd=boot ap
autostart=yes
bootfile=mips32.ari
ethaddr=00:24:6c:c2:eb:e2
stdin=serial
stdout=serial
stderr=serial
ethact=eth0

Environment size: 209/65532 bytes
apboot> setenv serverip 192.168.254.9

apboot> help upgrade
upgrade boot <file>
   - upgrade the APBoot image from <file>
upgrade os <file>
   - upgrade the OS image from <file>

apboot> upgrade os mips32.ari
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 192.168.254.45
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.254.254
DHCP DNS server: 192.168.254.254
DHCP DNS domain:
Controller address: 192.168.254.9
Using eth0 device
TFTP from server 192.168.254.9; our IP address is 192.168.254.45
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: #################################################################
         ######################
done
Bytes transferred = 5659932 (565d1c hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Erasing flash... .......................................................................................done
Erased 87 sectors
Copying to flash...
Writing ......................................................................................done
Verifying flash... 5659932 bytes were the same
Upgrade successful.
apboot>

That's brilliant, Giles, thanks. What are the other two files used for mips and mips64?.

mip64.ari is ap-12x

mips.ari is for ap-6x etc

just use the bootfile specified in the printenv of the AP you are using.

Thanks Giles. I was struggling to convert some IAP105s to AP105s (I only have an Aruba 200 running 5.0.4.11), when I came across this post. Worked a treat.

Hi everyone,

Ap is not reach the controller and it doesn't upgrade the os. I want to upgrade with the tfpt server from my computer, so I need this file which is name is "mips32.ari". Where can I download it?

I'm waiting your help, thank you.

Regards

This is an old thread.

Access points cannot operate without a controller, so obtaining the image and upgrading them manually will not fix anything.  Fix connectivity between the access point and the controller and then everything should work.  What are you using for the access points to discover the controller?

I couldn't explain exactly. We configure the Ap in the office and after we setup it on the location.

Sometimes we can make a mistake. If we don't configure correctly, we should configure remotely ofcourse. and if we have zyxel v2 modem on the location, Ap is cannot upgrade from the controller. So we must take it back

and must configure in the office again.

That's why I'm searching that file. If I have that file in my computer, I can upgrade with tftp server. I don't know it's clearly or not.

Regards.