Wireless Access

Reply
New Contributor
Posts: 1
Registered: ‎03-11-2014

AP 105 won't connect to controller

I have a setup of four AP 105's.  Three of them work just fine, but the fourth boots with "invalid image format" errors and keeps cycling through reboots.  I have tried many of the suggestions provided by the community to others that have experienced this problem (purgeenv, factory_reset, clear os) with no success.  The last thing I tried (setenv serverip) at least changed the behavior of the boot process in that it appears to at least try to download the OS image from the controller, but the result is the same - endless reboots. Here is the last log from a boot attempt:

 

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: 172.16.100.159
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 172.16.100.1
DHCP DNS server: 172.16.100.24
DHCP DNS domain: building.local
Using eth0 device
TFTP from server 172.16.100.7; our IP address is 172.16.100.159
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: T checksum bad
T T T T T T T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex

ARP Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 172.16.100.159
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 172.16.100.1
DHCP DNS server: 172.16.100.24
DHCP DNS domain: building.local
Using eth0 device
TFTP from server 172.16.100.7; our IP address is 172.16.100.159
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

 


I have noted a difference between the three AP's that work and the one that doesn't.  The three that work begin their boot with:

 

APBoot 1.4.0.3 (build 37726)
Built: 2013-03-21 at 20:13:41

 

while the one that does not work begins:

 

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

 

Could the difference in AP boot version be causing a problem?  Any suggestions for what I might try next?

 

Thanks.

MVP
Posts: 562
Registered: ‎11-28-2011

Re: AP 105 won't connect to controller

I'd log it with Aruba TAC and see if you can get a replacement.

 

This looks bad...

 

"Loading: T checksum bad".

 


Thanks.

 

Kudos appreciated, but I'm not hunting! (ACMX 104)
Regular Contributor II
Posts: 232
Registered: ‎03-14-2012

Re: AP 105 won't connect to controller

I had this issue once. I resolved it be enabling TFTP Service on the AP and then configured the TFTP Server IP Address on the AP as well (which was my Controller). And then also configured the AP with its Master Controller IP Address. To enable TFTP Service, use the below command:

apboot> setenv bootcmd tftpboot
Regular Contributor II
Posts: 232
Registered: ‎03-14-2012

Re: AP 105 won't connect to controller

However, you need to be sure you can reach out to the Controller from your Network.
Guru Elite
Posts: 21,513
Registered: ‎03-29-2007

Re: AP 105 won't connect to controller

"T" means bad transmission.  "#" means good transmission.  Something is wrong with the connectivity between your access point and the controller.



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: