Controller Based WLANs

What does this error message mean: "Filename: Mips32.ari TFTP Error: ‘File not found’ in AP-105"?

Question: What does this error message mean: "Filename: Mips32.ari TFTP Error: ‘File not found’ in AP-105"?

 

Product and Software: This article applies to AP-105.

The root cause of this error is that the AP cannot perform a code upgrade.

 

Scenario 1

Check the ArubaOS code.

The minimum requirement to bring up an AP-105 is ArubaOS 3.3.3+ or ArubaOS 3.4.1+.

If the controller is running pre 3.3.3 code, upgrade the code to fix the issue.

 

Scenario 2

If the AP is not connected to the controller directly, bring up the AP in the controller and then connect it to the desired location. This process loads mips32.ari to the AP so that the AP can upgrade the code.

 

Scenario 3

The AP has no power adapter and you want to use the PoE feature. A few controller series like the 200 and 3000 Series do not support PoE. In this case, the AP cannot be terminated physically in the controller. Instead, connect the AP to the PoE switch, which is connected to the controller. Then assign a static IP configuration for the AP using the following commands:

apboot> setenv ipaddr <ip address>

apboot> setenv netmask <netmask>

apboot> setenv gatewayip <ip address of the gateway>

apboot> setenv master <ip address of the master>

apboot> setenv serverip <ip address of the TFTP server>

apboot> setenv bootcmd tftp

apboot> save

apboot> boot

Locally configure the TFTP server for the AP and load the mips32.ari file from the controller with the help of the TFTP application.

Version History
Revision #:
1 of 1
Last update:
‎07-03-2014 02:59 PM
 
Labels (2)
Contributors
Comments
yohanssc

I want to download this file Mips32.ari for AP-105 device. Please give me this file download link.

 

APBoot 1.2.4.4 (build 26618)
Built: 2011-01-07 at 13:42:04

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
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 192.168.x.xx
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.x.xx
DHCP DNS server: 192.168.x.xx
DHCP DNS domain: xx
ADP multicast 1
ADP broadcast 1
ADP multicast 2
checksum bad
ADP broadcast 2
checksum bad
ADP multicast 3
checksum bad
checksum bad
checksum bad

Retry count exceeded
DNS request 1 for aruba-master to 192.168.x.xx
checksum bad
checksum bad
checksum bad
T Using eth0 device
TFTP from server 192.168.x.xx; our IP address is 192.168.x.xx
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: checksum bad
T T checksum bad
T checksum bad
checksum bad
checksum bad
T checksum bad
checksum bad
T T checksum bad
T checksum bad
checksum bad
T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad

ARP Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex

checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad

 

 

ThanKs :)

 

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.