I am hoping that some one can help me with this issue. I have 3-4 instant AP-105's that I have attempted to convert from VC to campus mode AP (thin). During the process 3 out of 4 AP's have been stuck in this reboot/upgrading loop and seem to have trouble loading the image they got from the controller. The AP's are sitting in my lab setup (thankfully) and are not directly attached to the controller as they are normally connecting over the network (L3) to my controllers in the DC.
After some time I was able to fix 1 AP by directly attaching it to the controller and running 'tftpboot' from the AP console. The problem is that in production I don't have the luxury of having a local controller at every location. So, this will not work for me. Is there a way to recover from this issue if the AP is not local to the Aruba controller?
Here are the troubleshooting steps I used:
1. I have done a purgeenv > saveenv > boot several times and but that did not seems to no avail.
2. I tried to run 'tfptboot' command from the 'apboot>' prompt but it fails:
apboot> tftpboot
eth0 up: 1 Gb/s full duplex
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3
Retry count exceeded
3. Then I directly connected the AP to the test controller (Aruba650) and run 'tftpboot' and that worked fine. The AP was able to boot load the image from the controller and came up after that.
apboot> tftpboot
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 10.2.10.13
DHCP subnet mask: 255.255.255.240
DHCP def gateway: 10.2.10.1
DHCP DNS server: 10.2.10.1
DHCP DNS domain: lab
Controller address: 10.2.10.1
Using eth0 device
TFTP from server 10.2.10.1; our IP address is 10.2.10.13
Filename 'mips32.ari'.
Load address: 0x2000000
Loading: *###########################################################
done
Bytes transferred = 3850268 (3ac01c hex)
Here are the details on 1 of the affected AP's and OS version when the issue was happening:
#show version:
ArubaOS Version 6.1.3.1 (build 32786 / label #32786)
Built by p4build@cartman on 2012-03-12 at 23:43:35 PDT (gcc version 4.3.3)
#show ap database
AP Database
-----------
Name Group AP Type IP Address Status Flags Switch IP
---- ----- ------- ---------- ------ ----- ---------
d8:c7:c8:c4:6a:40 default 105 10.2.10.13 Upgrading I 10.2.10.1
Here's the message from the AP console:
AP rebooted Fri Dec 31 16:01:37 PST 1999; SAPD: Reboot after successful image upgrade
shutting down watchdog process (nanny will restart it)...